Simple Keyboard
Get it on F-Droid . For people who like it minimalistic. No emojis, gifs, spell checker or swipe typing.
Private alternatives to Gboard, Microsoft SwiftKey, Samsung Keyboard, vetted against our public criteria.
Grouped by threat level
Get it on F-Droid . For people who like it minimalistic. No emojis, gifs, spell checker or swipe typing.
On-device voice typing for Android. Speech recognition runs locally, with no network access.
Get it on F-Droid . Supports lots of languages via external packages.
Get it on F-Droid . Supports 23 languages and 54 layouts.
No matches for those filters.
Your keyboard touches every word you type, including your passwords and private messages, down to whatever you search for. The default keyboard on most phones streams pieces of that back to its maker, sold to you as personalization and cloud sync. The keyboards here do the same job entirely on the device, with no network access at all, so the one app that sees everything has nowhere to send it. They are the open-source replacements for Gboard and SwiftKey, along with the stock keyboard your phone shipped with.
A cloud keyboard uploads what you type and the words it learns, sometimes reaching the clipboard too, all framed as prediction and sync. The catch is that no browser setting or app permission closes that hole, because the keyboard is its own app with its own connection, sitting at the input layer beneath everything else. Turning off “personalization” in its settings adjusts what the keyboard does with the data, not whether it collects and sends it in the first place, and you are taking that on faith. The only reliable fix is replacing the keyboard with one that has no network permission to begin with, which is what FlorisBoard and the other picks here are built around.
We hold every keyboard to our public listing criteria, and for this category the bar is unusually simple to state and hard to fake. We favour keyboards that request no network permission at all, because a keyboard that cannot reach the internet cannot leak your typing, period. We pair that with open source, so the no-network claim can be verified in the code rather than trusted, and we check that prediction happens on the device with no analytics buried inside. We only list a keyboard we would type our own passwords into, and we treat any unexplained network access as disqualifying.
The single strongest signal is no network permission at all, because it makes phoning home impossible rather than merely promised. Build on that with open source, so the claim is checkable in code, and on-device prediction, so your dictionary improves without cloud learning and without analytics quietly bundled in. Then weigh the practical side, because a keyboard you fight is one you abandon within a week: the layouts and languages you actually use, plus gesture typing if you rely on it and a feel that does not slow you down. Privacy you cannot live with is privacy you will uninstall, so the right keyboard is both silent and comfortable.
Install one from a trusted source, then open your phone’s system settings to enable it and set it as the default input method. Grant it the input role and nothing else; if it never asks for network access, there is nothing to deny. Type with it for a few days while its on-device dictionary learns your style, which catches up quickly. Then disable or remove the old keyboard so nothing silently falls back to it. From that point on, your typing stays on the device. A private keyboard pairs naturally with a de-Googled mobile OS, since both close leaks that no single app permission can reach on its own.