Third-party keyboard apps have specific rules: they must not transmit keystroke data off-device without clear disclosure and consent, need to support the standard "Next Keyboard" switching, and must work without requiring full network access unless a feature genuinely needs it.
Commonly triggered by requesting "Full Access" for the keyboard without clearly explaining why, or by analytics code that logs typed content more broadly than disclosed.
"Your custom keyboard extension requests Full Access without adequately disclosing what user data is collected and why, per guideline 4.4.1."
Guideline 4.4.1 sets rules for third-party keyboards. They must not send keystrokes off the device without clear disclosure and consent, they must support the standard way of switching to the next keyboard and they should work without network access unless a feature really needs it. Keyboards see everything a person types, which is why the privacy expectations are strict.
A keyboard can capture passwords, messages and personal details, so users must be able to trust it completely. Apple's rules therefore limit what keyboards can collect and make users aware when more access is requested. Requiring the standard switching control also protects usability, so that a keyboard cannot trap a user. The guideline treats this extension as one of the most sensitive on the platform.
It lets the keyboard use the network and share data with its container app, which raises privacy considerations.
Only within the disclosed and limited conditions the guideline sets.
Custom keyboards generally do not operate in secure text fields.
Platform rules change often. This page is a plain-language explanation written by AppReviewFix, not official guidance. Check the current App Store Review Guidelines for the exact wording.