Privacy

Last updated: 4 September 2026

We build communication tools for people who cannot easily use an ordinary touchscreen. Those tools handle some of the most personal data there is: what you say, and a video feed of your face. This page explains exactly what happens to it.

The short version: we don't collect anything. We have no servers that receive your data, no accounts, no analytics, and no advertising.

What we do not do

We do not collect, transmit, sell, rent or share any personal information. Specifically:

  • We have no user accounts and never ask you to register.
  • We include no analytics, telemetry, crash-reporting or advertising software. Where a third-party library tried to add network access, we removed it — see below.
  • We operate no servers that receive data from the apps.
  • We do not know who you are, how often you use the apps, or what you typed.

HeadBoard — the camera

HeadBoard uses your device's front-facing camera to follow the movement of your head.

  • Camera frames are analysed on your device, in memory, using Google's MediaPipe face-landmark models bundled inside the app. Each frame becomes a set of numeric landmark positions and is then discarded.
  • No image or video is ever saved. The app contains no code that writes camera frames to storage.
  • Nothing is transmitted. HeadBoard holds no internet permission at all, so it is not technically capable of sending data off your device.
  • The face-landmark models perform no facial recognition or identification, and store no representation that could be used to identify you.

HeadBoard needs Android's Accessibility Service permission in order to move the cursor and tap on your behalf. Android warns that an accessibility service can observe what you do on screen; that capability is exactly what lets HeadBoard control the device for you, and it is used for nothing else.

HeadBoard writes diagnostic logs and usage statistics into its own private storage area on your device, where no other app can read them. They are never uploaded. Clearing the app's data or uninstalling it removes them.

Why HeadBoard has no internet permission

Google's MediaPipe library, which HeadBoard uses for face-landmark detection, bundles a Google component capable of reporting usage statistics. That component would have added internet permissions to the app.

We do not want them, so we strip them from the build. Face landmarking runs entirely offline from models bundled in the app, and the result is that HeadBoard ships with no network permission whatsoever. You can verify this yourself: check the app's permissions on your device, or read the manifest in our public repository.

JustType — what you type

  • JustType has no camera and no microphone permission.
  • What you type is never transmitted. JustType learns which words you use so it can offer them sooner. That is stored in a database on your device and never leaves it.
  • If JustType crashes, it writes a diagnostic report to a file in its own private storage. It is never uploaded. You may choose to send it to us when reporting a problem — that is always your action, never automatic.
  • Backups you create are written to a location you choose, and are yours to manage.

When you enable any keyboard on Android, the system warns that it “may be able to collect all the text you type.” Android shows this for every keyboard, because a keyboard could do that. JustType does not — and because the source code is public, anyone can check.

The one thing that uses the network

JustType can download optional language packs — additional languages such as Spanish or Vietnamese. If you choose to install one, the app downloads it from our public releases page on GitHub.

That is an ordinary web request, which means GitHub receives your device's IP address and the standard information any web server sees. It does not identify you to us, and we receive nothing. If you never add another language, JustType makes no network requests at all.

This is the only connection any of our apps makes.

OpenBoard — the companion keyboard

OpenBoard is the conventional keyboard HeadBoard can drive for swipe-typing. Like the others, it has no internet permission and cannot transmit anything.

It does read and write Android's built-in personal dictionary — the system-wide list of words you have taught your device. That dictionary belongs to Android and is shared with other keyboards you use; it stays on your device.

Children

Our software is used by people of all ages, including children with disabilities. Because we collect no data whatsoever, we hold no information about children — or about anyone.

Word suggestions and adult language

JustType suggests words from a built-in dictionary. That dictionary is built from everyday written and spoken English, which includes coarse language. A communication tool that cannot say a rude word is not a complete communication tool — adults using AAC have the same right to swear as anyone else — so the words are there, and a setting controls how many of them are offered.

In Language Options → Excluded Words:

  • Offensive Wordsthe default. Common swearing and crude terms are not suggested.
  • Potentially Offensive Words — the strictest option. Also hides milder anatomical and sexual vocabulary.
  • None — every word in the dictionary is suggested, including all of the above.

If you are setting up a device for a child, please check this setting. The default is the middle option, not the strictest one. At the default, ordinary swearing is not suggested, but a number of anatomical and sexual terms still are. Choosing Potentially Offensive Words hides those as well.

Two things are true at every setting, including None:

  • Racial, ethnic, religious and anti-LGBTQ slurs are never suggested. They are not in the dictionary at all — no setting reveals them.
  • No setting stops anyone typing anything. These options change which words JustType offers, never what a person is permitted to write. Restricting what a disabled person can say is not something we will build.

Anyone can also add words to their own vocabulary, whatever the setting.

Third-party components

The apps include open-source components from Google (MediaPipe), the Android Open Source Project and others, listed in each repository's NOTICE file. We add no analytics or advertising software of our own, and none of our code contacts a network service.

Where a bundled library has tried to add capabilities we did not want, we have removed them: HeadBoard strips the internet permissions that Google's MediaPipe library would otherwise have contributed, so the app cannot reach the network at all.

Your rights

Because we hold no personal data, there is nothing for us to disclose, correct or delete. Everything the apps create stays on your device, and is removed when you uninstall them or clear their data.

You don't have to take our word for it

The complete source code for all three apps is public and can be inspected by anyone:

Changes to this policy

If this policy changes, we will update it here and change the date above. If a future version ever collected data, we would say so plainly and ask you first.

Contact

Questions about privacy: hello@continuouspath.org

Security vulnerabilities: security@continuouspath.org