Does a third-party keyboard work in Safari Private Browsing on iPhone?
Private Browsing changes what Safari remembers, not which keyboard iOS shows you. A custom keyboard works exactly the same in a private tab as in a normal one — with the same one exception that already applies everywhere else.
Open a Private Browsing tab and the whole point is that Safari is about to behave differently: no history kept, no autofill offered, tabs that lock behind Face ID if you leave the app. It is reasonable to wonder whether the keyboard is part of that shift too — whether Private Browsing quietly swaps in Apple’s own keyboard the way a password field does, on the theory that a private tab deserves the same caution. It does not. Type into a private tab and you get exactly the keyboard you would have gotten in a normal one: your themes, your key sounds, your lighting, all of it.
What Private Browsing actually turns off
Private Browsing is a setting inside Safari, and everything it changes lives inside Safari: new tabs stop being added to your browsing history, Safari stops offering to save new passwords or autofill entries from that session, cookies and site data get discarded once the tab closes rather than lingering, and — since recent iOS versions — the whole set of private tabs can be locked behind Face ID or your passcode if you switch away from Safari. Every one of those is Safari deciding what it will remember about itself. None of them is a decision about which keyboard extension gets to draw on screen, because that decision was never Safari’s to make in the first place.
Why the keyboard has no idea a tab is private
A keyboard extension is handed a text field and reports back keystrokes; it is not handed a flag saying “this is a private tab” or “this is a normal one”, because iOS never tracks or exposes that distinction to a keyboard at all. The same is true of which website you are on, which tab you have open, or how many other tabs are sitting behind it — a keyboard extension only knows about the field it is currently attached to, and Private Browsing is not a property of that field. So there is nothing for a keyboard to react to even if it wanted to, and no setting anywhere that makes a keyboard behave one way in a private tab and another way in a normal one.
This is the same structural point that explains why no third-party keyboard can tell which app it is running inside, just applied one level down: it cannot tell which Safari mode it is running inside either, for the same reason.
The one exception, and it is not about Private Browsing
A private tab can still fall back to Apple’s own keyboard for exactly one reason, and it is the same reason it would happen in a normal tab: a secure text field. A password box, a card number field, a passcode prompt — any field a website or Safari itself marks as secure — always shows Apple’s keyboard, whether Private Browsing is on or off. That override belongs to the field, not to the browsing mode, so a login form behaves identically in a private tab and a regular one, and an ordinary search bar or comment box stays on your usual keyboard in both.
Where the actual privacy question lives
If the underlying worry is “can my keyboard app see more of what I type in a private tab”, the honest answer is that a keyboard extension has the same access to a text field either way — it sees the characters you type into that field, same as any keyboard on any platform, and Private Browsing does not add or remove anything from that. The privacy question that actually matters is a much older one: does this keyboard send what it sees anywhere. That comes down to Full Access and the keyboard’s own network behaviour, not to whichever mode Safari happens to be in.
Where Kibo fits
Kibo’s themes, all 17 key sounds and its backlight effects show up in a private Safari tab exactly as they do everywhere else, because nothing about Kibo changes based on Safari’s mode — it cannot even detect it. Full Access stays off by default and Kibo works completely without it; turning it on unlocks only the Copy word, Copy line and Paste buttons on the keyboard toolbar, which read the system clipboard. Kibo has no account, no analytics and no server, so what gets typed into a private tab is exactly as untouched by the keyboard as what gets typed anywhere else on the phone.
Frequently asked questions
Does Safari switch to Apple’s keyboard automatically in Private Browsing?
No. Private Browsing only changes what Safari remembers — history, autofill, cookies — and has no effect on which keyboard appears. A custom keyboard shows up in a private tab exactly as it does in a normal one.
Can a keyboard app tell it is being used in a private tab?
No. A keyboard extension only ever sees the text field it is currently attached to, and iOS does not expose Safari’s browsing mode to it. There is no signal for a keyboard to detect, whether or not it wanted to.
Does a password field in a private tab still use Apple’s keyboard?
Yes, for the same reason it would in a normal tab: any field marked as secure always falls back to Apple’s own keyboard, regardless of Private Browsing. That override is attached to the field, not to the browsing mode.
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.