Privacy

What we know about you.

Nothing. Last updated 21 September 2026.

LocalTC is a hobby project, not a company. It has no servers, no accounts and no analytics. The long version is below, split into the two things that could plausibly touch your data: this website, and the program you install.

The short version. This website stores nothing on your device and collects nothing about you. The software processes your voice entirely on your own computer and sends it nowhere. Neither one has any way to identify you, so there is no profile to see, export or delete.

1. This website

The site is a handful of static files. There are no cookies, no local or session storage, no analytics, no tag manager, no advertising, no tracking pixels and no embedded third-party content. The two fonts are served from this site rather than from a font CDN, specifically so that loading the page does not tell anyone else that you did.

There is no form, no sign-up, no newsletter and no comment box anywhere on it, so there is nothing for you to submit and nothing for us to store.

Hosting

The site is hosted on GitHub Pages. To serve a page to you, GitHub necessarily handles technical data such as your IP address, the browser you use and the time of the request, and may retain it to keep the service running and to prevent abuse. That processing is GitHub's, under the GitHub Privacy Statement. GitHub Pages gives the owner of a site no access to those logs and no visitor statistics, so we never see any of it.

Links that leave

Links to GitHub, Buy Me a Coffee and other sites are ordinary links: nothing is loaded from those services until you click. Once you do, you are on their site under their policies. If you choose to donate, Buy Me a Coffee handles the entire transaction — your payment details never pass through this site and are never seen by the author, who sees only what Buy Me a Coffee shows a creator: a name or handle, an amount and any message you write.

2. The software

LocalTC runs on your computer and is built to keep working with the network cable pulled out.

Your voice is captured by push-to-talk and transcribed on your own CPU or GPU. It is never uploaded, and there is nowhere for it to be uploaded to.
The language model runs locally through Ollama, on 127.0.0.1 — your own machine talking to itself.
Recordings, logs and settings are written to your own disk, under %LOCALAPPDATA%\LocalTC and the project's recordings folder. They are yours: nothing reads them but you, and deleting them is deleting them.
There is no telemetry, no crash reporting, no usage counting, no update check and no licence check.

The connections it does make

These are the only times LocalTC reaches the network, and each one is something you asked for:

Setup. Downloading the speech model, the ATC voice and the language model from the services that publish them. After that, flights work offline.
SimBrief import, if you use it. The username or Pilot ID you type is sent from your machine to SimBrief to fetch your own flight plan, and their privacy policy covers what they do with it. Type a plan in by hand and this never happens.

Sending a bug report

Developer mode records your flight, including the audio of everything you said, and Export session packs that into a zip in your Downloads folder. Nothing is sent anywhere by the program. If you decide to attach that zip to a bug report, you are choosing to share your voice recordings, your settings and your flight plan — it is worth opening it first to see what is in it. Anything you post in a public issue is public, and held by GitHub.

3. Your rights

Privacy law gives you the right to see, correct, export and erase the personal data an organisation holds about you. We hold none, so there is nothing to act on — which is the point. If you have written to us on GitHub, that correspondence sits in GitHub's systems and their privacy statement governs it.

4. Children

This site is not directed at children and knowingly collects nothing from anyone, of any age.

5. Changes, and how to check

If this policy changes, the date at the top changes with it. Every edit is in the public commit history of the repository, so you can read exactly what changed and when.

You do not have to take any of this on faith. Open your browser's developer tools on this page: the network tab shows only files from this domain, and the storage tab is empty.

6. Contact

Questions about any of this belong in the project's issue tracker, where the answer helps the next person too.