Privacy Policy

Last updated 25 July 2026

Who we are

FlightDeck and FlightDeck Remote are developed and operated by DotTech Holding B.V., a company registered in the Netherlands. For anything in this policy — including requests about your personal data — contact us at privacy@flightdeckai.app.

For the purposes of the EU General Data Protection Regulation (GDPR), DotTech Holding B.V. is the data controller for the limited personal data described below.

What this policy covers

This policy covers three things:

• FlightDeck — the desktop application that runs coding agents on your own computer.
• FlightDeck Remote — the companion iOS app that pairs with your computer.
• The FlightDeck relay — the service we operate that forwards encrypted messages between the two.

FlightDeck (desktop)

The desktop application collects nothing and sends us nothing. It has no analytics, no crash reporting, no update pings, and no accounts. Your code, your repositories, and your agent conversations stay on your machine.

Two kinds of network traffic do leave your computer, and neither goes to us. First, the coding agent you choose to run (for example Claude Code) talks directly to its own provider, under that provider's terms and privacy policy — FlightDeck does not intermediate, inspect, or copy that traffic. Second, if you choose to enable FlightDeck Remote, your computer connects to our relay as described below. Remote is entirely opt-in; if you never pair a phone, your computer never contacts us.

FlightDeck Remote (iOS)

There are no accounts and no sign-up. You pair the app to your own computer instead.

Stored on your device

• Cryptographic keys — your device identity keypair and key-agreement keys, held in the iOS Keychain. They never leave your device.
• Pairing records — which computers you are paired with, their names, and when pairing happened.
• A relay access credential, if your relay requires one, held in the Keychain.
• Your preferences — app-lock setting, dictation language, notification choices.
• A local cacheof the most recent session state and transcripts, so the app can show you something before it reconnects. This lives in the app's own sandboxed storage and is removed when you delete the app.

Camera

The camera is used for one purpose: scanning the pairing QR code shown on your computer. Frames are processed on your device to read the code. No image is stored, and none is transmitted anywhere.

Microphone and voice dictation

If you hold the microphone button to dictate a reply, the app records audio and passes it to Apple's speech recognition framework to turn it into text. This transcription is not guaranteed to happen on your device — Apple may send the audio to its servers to process it, which is governed by Apple's privacy policy. The audio is not sent to us and we do not store it. The resulting text stays in the compose box for you to review, and is only sent to your computer — end-to-end encrypted — when you choose to send it.

The relay: what it can and cannot see

Your phone and your computer establish a shared secret directly with each other and encrypt every message with it (X25519 key agreement, HKDF-SHA256 key derivation, and ChaCha20-Poly1305 authenticated encryption, all via Apple's CryptoKit and its Rust counterpart). The relay only ever holds the resulting ciphertext.

The relay cannot read:your messages, your agents' output, your prompts, your code, your file paths, your terminal contents, or your repository names.

The relay does see and store:

• Device identifiers and public keys for your phone and computer, so it can route and authenticate messages.
• Pairing identifiers, and the name of your computer— which is usually a device name you chose and may contain your own name (for example “Ruud's MacBook Pro”). This is stored unencrypted so the app can show you which machine is which.
• Short-lived, single-use pairing tokens (they expire about two minutes after being issued).
• Your Apple push notification token, if you enable notifications, so it can wake the app.
• Encrypted message envelopes awaiting delivery, plus their timing, ordering, and size. Even though the contents are unreadable, this metadata reveals when you were active and roughly how much traffic there was.

The relay's operational logs record connection, device and pairing identifiers and pairing tokens — never message contents. The relay runs on Microsoft Azure, whose platform logging records network-level connection metadata including IP addresses. Azure acts as our data processor.

Push notifications

When an agent needs you and your phone is not connected, the relay asks Apple to wake the app. That push carries no content whatsoever— it is an empty “wake up” signal. The app wakes, reconnects, decrypts the messages waiting for it, and writes the notification you actually see on your own device. The notification text is therefore composed locally and never passes through Apple or through us.

Apple sees your push token and the fact that a push was sent, as described in Apple's privacy policy. You can revoke this at any time in iOS notification settings, or by turning notifications off for a machine in the app.

What we do not do

• No analytics or usage tracking, of any kind, in either app.
• No advertising, and no advertising identifiers. The app does not track you across apps or websites.
• No third-party analytics, attribution, or crash-reporting SDKs.
• No selling or sharing of personal data. There is nothing to sell.
• No profiling and no automated decision-making.

How long we keep things

• Encrypted messages awaiting delivery are deleted as soon as the recipient confirms receipt. Undelivered messages are capped per pairing (1,000 by default) and the oldest are dropped past that limit.
• Pairing tokens expire roughly two minutes after being issued and can only be used once.
• Pairings, device keys and push tokens are kept while the pairing exists. Unpair in the app — or delete the app — and they are removed from the relay.
• Operational logs are retained for a limited period for reliability and abuse prevention, then deleted.

Legal basis

Where GDPR applies, we process the limited data above to perform the service you asked for — connecting your phone to your computer (Article 6(1)(b), performance of a contract) — and to keep that service secure and reliable (Article 6(1)(f), legitimate interests). Camera, microphone, speech recognition and notification access are each requested through iOS permission prompts and are entirely optional; the app works without them.

Your rights

You have the right to access, correct, delete, restrict, and object to the processing of your personal data, and to data portability. Because we hold so little, the most effective control is in your hands directly: unpairing a machine, or deleting the app, removes your device keys, pairing and push token from the relay. For anything else, write to privacy@flightdeckai.app and we will respond within one month.

If you are in the EU or EEA and you believe we have handled your data improperly, you can lodge a complaint with your local supervisory authority. In the Netherlands that is the Autoriteit Persoonsgegevens.

International transfers

The relay is hosted on Microsoft Azure. Push notifications are delivered by Apple, and speech recognition may be processed by Apple, both of which may involve processing outside the EEA under their own safeguards and standard contractual clauses.

Children

FlightDeck is a developer tool and is not directed at children. We do not knowingly collect personal data from anyone under 16.

Changes to this policy

If we change this policy we will update the date at the top of this page. Material changes to how the relay handles your data will also be noted in the FlightDeck release notes.

Contact

DotTech Holding B.V., the Netherlands — privacy@flightdeckai.app