Trust & privacy
Last updated: 19 October 2026
This is the plain-language version of Flockdeck's privacy story: what's collected, what isn't, and how that compares to what else is on the market. The privacy policy has the exhaustive, legal version; this page is the short one, for skimming or for linking to.
Nothing to opt out of
Privacy in Flockdeck is structural. There is no "privacy mode" to turn on, because there is nothing to turn off:
- No accounts, no analytics, no telemetry and no crash reporting in the desktop app, on the free tier or any other.
- Spend and usage estimates are worked out on your own machine, from what your agents report about their own usage, and go no further than your own paired devices, and only if you turn on Flockdeck Remote.
- The relay never sees your API keys, unless you type one in yourself through Flockdeck Remote, and never sees the local token the app uses on your own machine.
- Push notifications are end-to-end encrypted. Your desktop encrypts each one with the receiving device's own keys before it leaves your computer; neither the relay nor its push service can read it.
- This website sets no cookies, runs no analytics and loads nothing from anyone else.
- One optional feature sends content to a third party, TypeSafe AI, and
only if you turn it on: status detection sends the last lines of a quiet
pane's terminal output. It is off by default, needs a TypeSafe API key
you supply yourself (in Settings, or as
TYPESAFE_API_KEY), and is described in full in the privacy policy. Everything above holds while it is off. - Downloads keep short-lived access logs. The app, the installer scripts, the update check and the optional lens helper app are served from dl.flockdeck.ai, which keeps standard access logs (IP address, path, time, response code and user agent) for 30 days, stored privately and used only for security, abuse and fixing problems: not for analytics, marketing or profiling, and not shared except as the law requires. The desktop app itself still collects nothing, and none of your code or terminal content is part of a download. lens, which reads your agent session transcripts on your own computer, is fetched only if you choose to install it. See the privacy policy for the logs and the lens download for what it may contact.
- Nobody's data is sold, and nothing is used to train a model, anyone else's or Flockdeck's own, and there is no model here to train.
None of that is a paid feature. It's what the free tier does, because it's what the app does.
Where that differs from what's on the market
As of April 2026, GitHub changed Copilot's policy: Free, Pro and Pro+ plans now train on your prompts and code by default (opt-out, not opt-in). Only Business and Enterprise plans are exempt automatically. Several other coding assistants offer a "zero data retention" mode you can turn on, sometimes only on a paid or team plan.
The Flockdeck app itself collects nothing to begin with, on the free tier as on any other, so there is no default to opt out of. That isn't a promise about a future release; it's what the app already does, and the desktop app's source is available, so you can read it and check.
What is, and isn't, end-to-end encrypted, said plainly
Your terminal input and output through Flockdeck Remote are end-to-end encrypted, once the device and the desktop have each registered a key. Your terminal output and what you type are then encrypted with keys the relay hands out but never holds, so the relay carries them to your other devices without being able to read them, even on a relay you run yourself. Until both have registered, they are protected by TLS only.
The rest still isn't: what each pane's agent has spent, its usage limits, which model routing chose for it, the conversation view of a pane, what you search in it and photos you attach reach the relay decrypted, over TLS, so it can route them. It doesn't record, store or log any of it.
This defeats an honestly-run relay. Against one that's been actively compromised and tampered with to swap the keys it hands out at pairing, that alone isn't enough. A swap like that needs an out-of-band check, and Flockdeck Remote has one: the device and the desktop can each show a code for the other (Verify, under Devices on the phone and in the desktop's Flockdeck Remote settings), and comparing them by eye is what catches a relay that has swapped keys. If your organisation's rules don't allow a third party in that position at all, Flockdeck Enterprise, coming soon, will let you run the relay on your own infrastructure: see Enterprise.
The billing service
Flockdeck Remote through the shared relay is a subscription after a 30-day free trial, sold through Paddle (see the FAQ). The relay learns only an account's plan and the date it's paid until, through the billing service's own connection to it, never an email address, a name or a country. That data stays in the billing service alone, kept only as long as UK tax law requires sale records to be kept, then deleted.
Read more
- Privacy policy: what's kept, why, for how long, and your rights over it.
- Terms of service
- Licences: every third-party component, with its licence in full.
- The desktop app's source is available for noncommercial use under the PolyForm Noncommercial licence: github.com/Flockdeck/flockdeck.
Questions, or a security report: privacy@flockdeck.ai.