Guideline 4.4.1 - Design: Keyboard Extension Requiring Full Access Without Justification

Apple is rejecting your custom keyboard extension because it requests Full Access (the 'Allow Full Access' toggle in Settings) without providing adequate justification for why it needs network connectivity. Full Access gives a keyboard extension the ability to transmit everything the user types to your servers — Apple understandably scrutinizes this carefully. When a keyboard requests Full Access, it gains access to the network, the shared container with the host app, and the ability to send keystroke data externally. Apple requires that you (1) clearly explain to users what data you collect and why, (2) have a visible privacy policy, and (3) actually need Full Access for a core feature — not just analytics or crash reporting. Legitimate reasons for Full Access include: cloud-based predictions or autocorrect (the keyboard needs to query your server), GIF/sticker search (needs network to fetch media), or cloud sync of learned words across devices. Illegitimate reasons: basic analytics, ad serving, or features that work fine without network access. The fastest compliant path is to either remove the Full Access requirement (if your keyboard can function without it) or provide clear in-app disclosure explaining exactly what data is transmitted, why it's necessary, and how it's protected.