Keyboard Cache Prevention

Overview

Keyboard Cache Prevention reduces the chance that sensitive text entered into iOS fields is learned by the system keyboard, autocorrect, spell checking, or predictive suggestions. It is intended for passwords, OTPs, account identifiers, payment details, recovery answers, and other data that should not appear later as keyboard suggestions.

When enabled, AppTego hardens fields that your app marks as sensitive and fields that iOS already treats as sensitive.

When To Use It

Use this control for:

• Login, signup, MFA, password reset, and account recovery forms.
• Payment, card, wallet, bank account, and transfer fields.
• Healthcare, identity, government, enterprise, or regulated data entry.
• Any field where learned suggestions could leak private information in another app or later session.

How It Works

The protected app applies standard iOS text-input hardening to sensitive fields so keyboard learning and related typing assistance are reduced where privacy matters. Public documentation does not describe internal method interception or lifecycle details.

Mark fields as sensitive through the AppTego SDK when they are not already recognized by iOS as sensitive.

How to Enable the Control

Navigate to Preventative Controls from the AppTego portal, and expand the Data Sharing Protection section. Under this section you will find the Keyboard Cache Prevention control. Click Enable to enable it for the next build or for it to be applied with a live push (if enabled).

API Configuration Example

{
  "KeyboardCachePrevention": {
    "protection": true
  }
}

Implementation Guidance

Use the AppTego SDK to mark custom sensitive fields, such as account numbers, recovery answers, or proprietary identifiers. Password, new-password, one-time-code, and payment fields should also use the appropriate native iOS field types so the operating system treats them as sensitive.

Compatibility Notes

• This control does not disable third-party keyboards. Use Third-Party Keyboard Detection when third-party keyboard risk matters.
• This control does not prevent clipboard exposure. Use Clipboard Protection for copy/cut leakage risk.
• It prevents future learning on protected fields; it does not delete data the keyboard may have learned before the control was enabled.
• Some users rely on typing assistance for accessibility. Apply the control to fields that are genuinely sensitive.

Related Controls

• Third-Party Keyboard Detection
• Clipboard Protection
• Storage Encryption