What data can an iPhone keyboard actually see?
A keyboard extension can read the field it is attached to, and almost nothing else. Here is exactly where the boundary sits, and why being able to observe text is a different question from being able to send it anywhere.
A keyboard extension can read the text field it is attached to — a sentence that is entirely true, and that describes far less access than most people picture when they read it.
What the extension is actually handed
When you tap a text field, iOS does not give the keyboard the app around it. It gives the keyboard a narrow interface onto that one field — usually called a text document proxy — carrying the characters immediately before the insertion point, the characters immediately after it, whatever is currently selected, and a small set of attributes describing the field itself.
Those attributes are the part nobody thinks about, and they are what makes a keyboard feel appropriate rather than generic:
- the keyboard type the field asked for — email, URL, number pad, phone — which is why the layout changes when you tap into a different box;
- the autocapitalisation and autocorrection behaviour the field requested;
- the label the return key should carry: Go, Search, Send, Done;
- whether the field is currently empty, and whether the app prefers a light or dark appearance.
What a keyboard does with that is the ordinary business of typing: capitalising after a full stop, offering a completion, deciding whether a sentence needs a space before the next word. The text it receives is the context around the cursor rather than the whole document, and a host app may supply less than the keyboard asks for — long documents in particular often hand over only a window of nearby text.
It is also per-field and per-session. Move the cursor to a different box and the keyboard is talking to a different proxy with no memory of the previous one.
What it cannot see
The list of things outside the boundary is considerably longer than the list inside it, and it is enforced by the system rather than by a keyboard’s good manners.
- Anything in another app. The extension exists only while it is on screen in the app you are typing in, and it has no view onto that app beyond the focused field — not the messages above your draft, not the page behind it, not the screen.
- Secure text fields. Password boxes, payment sheets and similar fields mark themselves as secure, and iOS swaps to Apple’s own keyboard for as long as one holds the cursor. Third-party code is never in the room for that text.
- The clipboard. The system pasteboard is out of reach for an extension in its default sandbox, which is why a keyboard’s own Paste button is the one feature that stops working without Full Access.
- The network. By default there is no route off the device at all — no requests, no sockets, nowhere to send anything to.
- The usual private stores. Contacts, photos, location, calendar and health each require their own permission, and a keyboard extension is not holding any of them.
- Anything typed on a different keyboard. Switch with the globe key and the previous extension is not watching from the background; it is not running.
Observing and transmitting are two different questions
Nearly all of the anxiety about keyboards collapses into that distinction. Reading the field you are typing in is inherent to being a keyboard — Apple’s own keyboard reads the same text, for the same reasons, in order to autocorrect and predict. The question that actually carries risk is whether the text can leave the phone, and that is governed by a separate switch.
With Full Access off, the extension has no network access, so there is no destination. Turning Full Access on lifts that sandbox as a single switch rather than a menu of individual permissions, which is why iOS words the confirmation so severely: it can tell you the capability now exists, but it cannot tell you whether a particular keyboard uses it.
That leaves two practical tests rather than a leap of faith:
- Does the keyboard type normally with Full Access off? Typing needs no permission whatsoever, so a keyboard that refuses to work until you grant it is asking for something typing does not require.
- If it does ask, is the stated reason specific? “Required for full functionality” explains nothing. “Required for the paste button” names a mechanism you can verify by turning the switch off and watching only that button stop working.
A keyboard sits closer to your text than almost anything else on the phone, and sees less of the phone than a browser tab does. The reading is the job; what is worth checking is whether the sandbox around it has been opened.
Where Kibo fits
Kibo runs with Full Access off by default, and everything works in that state: typing, themes, key sounds, backlight effects, the emoji and kaomoji panels, the fancy text styles and its typing languages. The permission is read in exactly one place in the whole app — the Copy word, Copy line and Paste buttons on the keyboard toolbar, which are the only code in Kibo that touches the system clipboard. With the switch off those three show a short message instead of acting, and nothing else is affected.
There is also no destination. Kibo has no account, no ads, no analytics and no server, and makes no network requests, so what it reads from the field in front of it has nowhere to go.
Frequently asked questions
Can a third-party keyboard see what I type in other apps?
No. The extension is only loaded while it is on screen in the app you are typing in, and it is given a connection to that one focused text field. It has no view onto other apps, and it is not running at all between typing sessions.
Can a keyboard read my passwords?
Not from a secure field. Password boxes and payment sheets mark themselves secure and iOS forces its own keyboard onto them, regardless of which keyboards are installed or what permissions they hold.
If a keyboard can read the field, why does Full Access matter?
Because reading and sending are separate. Without Full Access the extension has no network access, so there is no way for anything it reads to leave the phone. Full Access lifts that sandbox, which is what the warning is about.
Can a keyboard see my clipboard?
Not in its default sandbox. The system pasteboard is blocked for keyboard extensions until Full Access is granted, which is why a keyboard’s own Paste button is usually the only feature that stops working with the switch off.
Try it on your own keyboard
Kibo is a free custom keyboard for iPhone with real mechanical key sounds, a wardrobe of themes and RGB backlight effects. No account, no ads, and it works with Full Access left off.