Which keyboard apps are open-source and avoid sending typing telemetry?

1. Open-source keyboard projects that state “no telemetry”

AnySoftKeyboard is a long-running open-source keyboard that advertises privacy-conscious defaults and, according to coverage, “doesn’t need network permission to work,” a practical indicator that it won’t send telemetry by design ^{[1] [9]}. OpenBoard—an AOSP-based fork—markets itself as privacy-friendly and free of tracking or telemetry and is recommended repeatedly in open-source app roundups ^{[2] [10] [7]}. FlorisBoard presents itself on GitHub as an open-source keyboard that “respects your privacy,” publishing code and signature hashes for users to verify APKs ^[3]. Simple Keyboard is described in reviews and project pages as minimalist, lightweight and privacy-focused, explicitly noting the ability to type “without any tracking” ^{[4] [10]}. Alternatives and smaller projects such as FUTO/Tiny and HeliBoard (a fork of OpenBoard) are listed among open-source Gboard alternatives that claim to avoid background data collection ^{[5] [11]}. Newer community-funded projects like Urik likewise advertise “no telemetry” and full transparency of source code ^[6].

2. How these projects substantiate privacy claims

Most projects rely on three public signals to substantiate privacy: open-source repositories where code can be audited (GitHub pages for FlorisBoard and HeliBoard, project sites for AnySoftKeyboard/OpenBoard) ^{[3] [11] [1]}, distribution on privacy‑focused stores like F-Droid or SourceForge listings rather than ad-dependent channels ^{[7] [8]}, and explicit documentation about permissions and telemetry (some projects publish APK signature hashes or note the lack of network permissions) ^{[3] [9]}. Journalistic and how‑to coverage repeatedly highlights that these keyboards “stay offline” and “avoid telemetry,” signaling community vetting beyond mere marketing ^{[10] [9]}.

3. Important caveats and where reporting stops

Public claims and open code are strong indicators but not absolute proof that no telemetry ever occurs: audits require following build reproducibility, checking release binaries, and confirming that forks or repackaged APKs haven’t added network code—issues documented in community discussions about forks and distribution channels ^{[11] [7]}. Sources reviewed here note that some apps must be sideloaded or installed via F‑Droid, which shifts trust to the distributor and the user’s verification steps ^{[2] [7]}. Reporting reviewed does not include independent third‑party network telemetry audits for every project, so definitive technical confirmation beyond project claims is not available in the supplied material ^{[2] [6]}.

4. Practical steps to choose and verify a no‑telemetry keyboard

Prefer projects with public GitHub repositories and explicit statements about network permissions (AnySoftKeyboard, FlorisBoard, OpenBoard), install from F‑Droid or the project’s signed APK to avoid repackaged builds, inspect app permission lists for network or internet access before enabling as the system keyboard, and consult project release signatures or hashes where provided ^{[1] [3] [7]}. For higher assurance, community audits or building from source are available options for these open projects ^{[3] [7]}.

5. Final trade-offs: privacy versus features

Choosing an open-source, no‑telemetry keyboard reliably reduces the risk of remote logging of keystrokes, but users should accept trade-offs: some feature gaps (fewercloud-based predictions, fewer language packs or AI assistants) and occasionally more manual setup than mainstream keyboards, a reality highlighted across reviews and roundups ^{[10] [12] [4]}. The projects cited provide transparent code and explicit privacy claims; technical certainty about telemetry absence requires verification steps beyond the claims in the reporting reviewed ^{[1] [6]}.