Best Android Keyboard for Privacy: Gboard vs HeliBoard

Gboard types beautifully and quietly sits inside Google's ecosystem. HeliBoard holds no internet permission at all, which means it physically cannot send a keystroke anywhere, but you give up swipe typing, voice input, and Google's forgiving autocorrect to get there. The real question is not which keyboard is better, it is whether the privacy you gain is a benefit you will actually feel or a small window you close while the front door stays open. That answer depends almost entirely on whether you are on a stock phone or a de-Googled one. Below is the version with the setup traps most write-ups skip.

Gboard is Google's own keyboard: closed-source, distributed through the Play Store, and pre-installed on Pixels and most non-Samsung phones. It is free of charge but it is a Google-ecosystem product, not open software. Its behavior on the network is governed by settings and policy, not by anything you can inspect or independently audit.

HeliBoard is the opposite in almost every structural way. It is genuinely open source under GPL-3.0, a maintained fork of OpenBoard, which itself descends from the AOSP LatinIME keyboard. The point worth understanding is that HeliBoard requests no internet permission whatsoever, so Android itself blocks any network transmission. That is a stronger claim than a privacy policy: it is not a promise to avoid sending your typing anywhere, it is an operating-system-enforced inability to. That is why it ships as GrapheneOS's default keyboard, and why it is the coherent choice for anyone who has already removed Google from their phone. One practical note: it is not on the Play Store. You install it from F-Droid, the IzzyOnDroid repository, or a GitHub APK.

Gboard's genuine strength is that it forgives sloppy typing. Glide typing lets you drag a thumb across the keys and land the right word most of the time, and its autocorrect quietly fixes fat-fingered mistakes and learns your habits. It also bundles the ecosystem glue you may lean on without noticing: inline Google Translate, GIF and sticker search, Emoji Kitchen, and a fast emoji search field. If you swipe, dictate, mix languages mid-sentence, or reach for a sticker mid-chat, that is the polish you would miss. On recent flagship hardware Google has also added on-device AI writing tools powered by Gemini Nano (proofread, rephrase, tone) plus a Gemini-assisted voice input mode that Google says does not store your audio or text. The writing tools are hardware-gated to phones with a capable chip, so most mid-range devices never get them.

HeliBoard feels lighter and snappier, with a tiny install size and no account, no ads, and no ecosystem glue. Its compensating strength is control: true Material You dynamic color, custom themes, adjustable height, a toggleable number row, split and one-handed layouts, clipboard history, and a persistent incognito mode that disables learning. What you feel most in ordinary tapping is that its autocorrect is more literal and conservative. It does not do strong whole-sentence context correction, so you catch more of your own typos and add names to its dictionary yourself over time. It is not broken, it is tuned differently, and it starts weak until you seed it.

The biggest one: HeliBoard has no swipe typing out of the box. There is no open-source gesture library good enough to match Gboard, so to enable glide typing you sideload a proprietary, Google-authored binary extracted from a GApps package. There is real irony in installing a Google blob to fix the flagship feature of a Google-free keyboard, and it is a genuine trap in practice. It must be the exact version the app names, it should live in internal storage, and Samsung devices have extra known issues. Even once it loads, most people find swipe good but a notch below Gboard's uncanny accuracy.

Autocorrect has a hidden requirement too: dictionaries are not bundled. You download a dictionary file per language from HeliBoard's repository, and until you do, autocorrect and multilingual typing simply do not work. Voice typing is not built in either. HeliBoard hands dictation off to a separate app, and by default that route can reintroduce Google's cloud, so a truly offline setup means pairing it with an offline engine such as FUTO Voice Input or Sayboard. Add that your Gboard personal dictionary and learned words do not transfer, so autocorrect feels rough for the first week, plus occasional bugs like a missing toolbar or the mic tap closing the keyboard, and no cross-device sync, and you have a keyboard that rewards tinkerers and frustrates people who just want it to work. There is no Japanese or Chinese support either, which is a hard stop for CJK typists.

Two distribution details matter before you commit. If you sideload the raw GitHub APK, you get no update notifications, so you can silently run stale, unpatched builds unless you install through F-Droid or IzzyOnDroid and turn on auto-update. And because F-Droid and GitHub sign their builds with different keys, switching install source later forces an uninstall and reinstall that wipes your settings and learned data. Pick your source deliberately the first time.

It is easy to oversell this, so let me be precise. Gboard is not a keylogger sending every keystroke to Google. Documented behavior is telemetry and metadata, things like which app you are typing in, timing, and language, tied to your device identity and opt-out by default. Google describes prediction training as happening largely on-device through federated learning that returns model updates rather than your raw text. The defensible complaint is that Gboard has network access and cannot be independently audited, not that a specific password left your phone. And much of that telemetry can be blunted without switching at all: turning off Share usage statistics stops the automatic reporting, which removes most of the privacy gap for a lot of people.

HeliBoard's advantage is that it sidesteps the entire trust question. You do not have to believe anyone, because the app holds no network permission, so there is nothing to audit and nothing to leak. That is qualitatively different from a trusted-but-networked keyboard. The catch is scope: on a stock phone with Google Play Services already running, your keyboard is not your dominant leak, so HeliBoard closes a small window while the front door stays wide open. It removes the keyboard as a data vector; it does not de-Google your phone.

One fact predicts the right answer better than any feature list: are you on a de-Googled phone or a stock one? If you run GrapheneOS, LineageOS without Google apps, or /e/OS, then keeping Gboard reintroduces the exact dependency you wiped the OS to escape, and HeliBoard is the obvious, coherent choice. The same goes for privacy-maximalist threat models and F-Droid purists who value verifiable openness and are happy to absorb rough edges. For a fuller map of the field, see our best Android keyboards guide.

Stay on Gboard (with usage stats off) if you swipe-type and will not sideload a Google binary, if you dictate constantly, if you mix languages mid-sentence, or if you simply want it to work with zero setup. And if you want off Gboard for privacy but HeliBoard sounds too raw, there is a middle path worth trying first: FUTO Keyboard is offline and source-available with swipe and offline voice built in and no blob-sideloading dance, at the cost of strict OSI license purity. We compare the two directly in HeliBoard vs FUTO Keyboard. Whatever you lean toward, the safest move is to install the new keyboard alongside Gboard, leave Gboard installed, switch the active keyboard, and live on it for one real week. Android swaps keyboards in a single tap, so you learn whether the suggestions and swipe setup suit your typing with a zero-risk fallback the whole time.