Privacy Policy

Effective Dec 1, 2026.

The short version. Flight Data collects feedback and crash reports from developers' apps and delivers them to the developer's Mac. Reports are encrypted on the device that sends them, to a key only the developer holds, so our server stores them sealed and we can't read them. For developers who use Flight Data, we keep what it takes to run an account: your name and email address from Sign in with Apple, your organizations and apps, and your subscription status from Apple. For the people who use a developer's app, we store their reports on the developer's behalf, and the developer is the one to ask about them. We don't sell data, show ads, track anyone, or train AI on anything.

This policy covers Flight Data: the service at flightdata.dev, the Flight Data Recorder app for Mac, and FlightDataKit, the code developers add to their apps to send reports. Flight Data is made by Diradical LLC, a Pennsylvania limited liability company ("we," "us," "our").

It speaks to two kinds of people:

1. Reports are sealed

A report's contents are encrypted on the device before it leaves, and opened only on the developer's Mac. We can't read them.

When someone sends a report from an app that uses FlightDataKit, the app encrypts it on their device to the developer's public key before uploading it. The private key that opens it stays with the developer, in the keychain of their Mac. Our server stores the sealed report and never has a key to open it. Flight Data Recorder opens reports on the developer's Mac as it syncs them.

Sealed, so neither we nor our hosting company can read it: the title and description, the contact details the person gave, the app's own questions and answers, labels, every attached file (screenshots, documents, logs) and crash logs. The same goes for the text of the work items a developer files reports under.

Readable by our server, because it needs them to route, count and limit reports:

2. If you're a developer: your account

You sign in with Apple. We keep what's needed to run your account and your organizations.

You sign in to Flight Data Recorder with Sign in with Apple; there are no passwords. Apple gives us an identifier for your Apple Account, your name, and an email address. If you choose Hide My Email, the address is a private relay address that Apple forwards to you, and we never see your real one.

We keep:

We don't hold your encryption keys. The server stores only the short ID of the key each report is sealed to.

We use this to provide the service: to sign you in, sync reports to your Macs, enforce your plan's limits, prevent abuse, and answer you when you contact us. The people who run Flight Data for us (currently only us at Diradical) can see account information and report metadata in our operator console, never report contents.

3. If you use a developer's app

The developer decides what their app asks for and sends. We store your report on their behalf, sealed, and the developer is the one to ask about it.

An app that uses FlightDataKit sends a report only when you submit one, or, if the developer has set it up, as a periodic report of usage totals the app recorded. What a report contains is up to the developer and to you: typically what you write, an email address if you give one, and any screenshot or file you leave attached. The developer's app and its privacy policy should tell you what it sends.

For these reports, we act on the developer's behalf: we store and deliver them as the developer's service provider (in EU terms, a processor), and the developer decides what is collected and what happens to it (the controller). We can't read your report, so we can't search it for your name or email address. To see, correct or delete a report you sent, ask the developer of the app; they can open it and delete it. If you write to us instead, we'll tell you which developer to contact and help them as we can.

Beyond the sealed contents, a report carries the readable details listed in section 1, and:

A report that can't be sent right away waits, sealed, on your device, and FlightDataKit tries again later. One still unsent after 30 days is deleted without being sent.

4. Payments

Apple handles payment. We receive the signed subscription records Apple issues, not your card or Apple Account details.

Paid plans are App Store subscriptions bought in Flight Data Recorder. Apple processes the payment under Apple's privacy policy, and we never see payment details. When you subscribe for an organization, the app gives our server the signed transaction Apple issued, and Apple's server notifications keep it current. From these we keep the transaction's ID, the product, whether it is a real or test (Sandbox) purchase, when it expires or was refunded, and which organization it pays for. We keep these records even after an account or organization is deleted, as the record of what Apple was paid for. Apple also gives us aggregate sales reports.

5. The Flight Data Recorder app

Your keys and your opened reports stay on your Mac. The app talks only to our service and to Apple, and agents get nothing unless you allow them.

What it keeps on your Mac. Your private keys are kept in your Mac's keychain; if you use iCloud Keychain, Apple syncs them to your other devices, end-to-end encrypted. If you lose every copy of a key, nobody, including us, can open the reports sealed to it. The app keeps its own local store: the reports it has opened, with their attachments, your work items, and your apps' settings, in its own storage on your Mac. It also reads Xcode archives from a folder you choose, to find symbols for crash reports, and keeps what it finds there on your Mac.

What it sends. The app talks to our service at flightdata.dev and to Apple, nothing else. It sends what Sign in with Apple gives it and your Mac's name when you sign in (section 2), and then syncs: it downloads your organizations' sealed reports, and uploads your changes, sealing any text you write (a work item, an edit to a report) on your Mac first, so it reaches us sealed like a report. When you subscribe, it passes Apple's signed transaction to our server (section 4). It sends feedback or a crash report about itself only when you submit one (section 6). It contains no analytics or advertising software.

Agents. Flight Data Recorder has no AI model of its own and sends no report to one. Coding agents such as Claude Code or Codex can connect only if you allow them in Settings ▸ Intelligence, which is off by default, and each agent asks your permission the first time. An agent you approve can read opened reports, including what your users wrote and sent, and do what Settings ▸ Intelligence ▸ Permissions allows; it is never given a key or your sign-in. What it reads, it sends to the company that provides its model, under that company's terms and privacy policy.

6. Feedback about Flight Data Recorder, and contacting us

If you send us feedback or a crash report, or email us, we keep what you sent so we can reply and fix what you reported.

Flight Data Recorder uses Flight Data itself. Help ▸ Provide Feedback sends a report only when you click Submit Report: what you type, the choices you make, an email address if you enter one, any file you add, and the readable details in section 1. If the app quits unexpectedly, it keeps a crash log on your Mac (recorded with KSCrash, open-source crash-recording software) and asks the next time you open it; Submit Report sends it, Don't Send deletes it. Either way, the report is sealed on your Mac to our key, and we read it on our own Mac.

Separately, if you've turned on Apple's option to share app analytics with developers, Apple may send us crash logs and aggregated usage statistics, with information that identifies you removed. Flight Data Recorder contains no analytics or third-party tracking software.

If you email us, we'll have your address and whatever you include. We use it to answer you and to fix problems, and we keep correspondence as long as it's useful for support. You can ask us to delete it at any time.

7. Emails we send

We email you only about your account, your organizations and the service itself: security notices, changes to your account or membership, notices about your organization's plan, and important changes to the service, its Terms or this policy. We don't send marketing email. Automated email comes from noreply@flightdata.dev. If you write to us, we reply from support@diradical.com or from a specific person's address of someone at our LLC. If you signed in with Hide My Email, our email reaches you through Apple's relay. We don't email the people who use your apps unless they write to us first.

8. Logs, abuse protection and our websites

Our server's logs don't record IP addresses or report contents, and are kept for a few days. Our websites don't track you.

Our server writes one log line per request: the kind of request, its result, how long it took, its size and, for signed-in requests, the internal IDs of the user and session. It doesn't log IP addresses, tokens or report contents. Our hosting provider keeps these logs for about three days.

To limit abuse, the server counts requests per installation, per app and per internet address. Those counters name only keyed hashes, never a raw address, and are deleted after about two days. Records of ended sign-in sessions are deleted 30 days after they end. Records of security-relevant actions are kept at least 90 days.

The load balancer in front of our servers gives us only totals, such as request and error counts. It doesn't give us a log of requests, so we have no record of IP addresses from it. Our provider may keep its own standard operational records, under its own privacy notice.

Our websites don't use cookies, analytics or ads. The only cookie on flightdata.dev is the sign-in cookie of the console our own operators use. diradical.com is a static website; like most websites, the company that hosts it may keep standard server logs (such as IP address, browser type and pages requested) for security and operations, under its own privacy policy.

9. Who handles data for us

Two companies: Amazon Web Services runs our servers and sends our email; Apple handles sign-in, payments and app verification.

We don't share personal data with anyone else, except where the law requires it. If we're required to hand over data, sealed reports stay sealed: we have no key to open them.

Flight Data is run from the United States, and the data is stored there.

10. How long we keep it, and deleting it

You can delete reports, apps and your account at any time. Some copies take longer to go and here are the details.

What you can do today:

Deleting can't be undone.

Reports are kept for 30 days on Free and 90 days on Indie, counted from when they arrive, and on Studio for as long as the subscription lasts. When a subscription ends, we keep the organization's reports for up to 30 more days; after that, Free's 30 days apply and older reports are deleted. Copies already on your Mac stay there.

Reports held over a plan's limit are deleted 7 days after they arrive, unless the plan is upgraded first.

What you delete goes to Recently Deleted in Flight Data Recorder for 30 days, where you can restore it. After that it's deleted for good, files included, and can't be brought back.

Backups keep deleted data until they age out: 7 days for our database's automatic backups, and up to 6 months for our weekly encrypted backups.

Your account is kept for as long as you use Flight Data.

11. What we don't do

No selling, no ads, no tracking, no training on reports.

We don't sell, rent or trade personal information. We don't show ads, and we don't track anyone across apps or websites. We don't use reports, or anything in them, to train any AI or machine-learning model; we can't read them.

12. Security

Reports are sealed end to end; everything else is protected in transit and at rest.

Report contents are encrypted on the sending device with HPKE, a standard public-key scheme, and stay encrypted on our servers and in our backups. Every connection to our server uses HTTPS. Our database is encrypted at rest and accepts only encrypted connections. Sign-in tokens are stored only as hashes. (An app token isn't a secret: it ships inside the app and can only send reports.) No system is perfectly secure; if we learn of a breach that affects you, we'll tell you as the law requires.

13. Children

Flight Data is a tool for developers, not for children.

Flight Data isn't directed at children, and developers' accounts aren't for children. A developer whose own app is used by children is responsible for what that app collects and sends (see our Terms of Service).

14. Your rights

Depending on where you live, you can ask to see, correct, export or delete your data. Ask us, or for a report you sent, ask the developer.

Depending on where you live (for example, the EU, the UK or California), you may have rights to access, correct, delete or export personal data about you, and to object to how it's used. You can delete your account yourself (section 10). For anything else, email us and we'll answer within the time the law allows.

For readers in the EU and UK: for developers' accounts, we are the controller; our legal bases are the contract with you (to provide the service) and our legitimate interests (to keep it secure and prevent abuse). For reports sent through a developer's app, the developer is the controller and we are their processor, so send requests about them to the developer. You can complain to your local data protection authority. Your data is handled in the United States.

15. Changes to this policy

We'll post updates here with the date, and tell you in the app if a change matters.

If Flight Data starts handling data differently, we'll update this policy first, change the effective date at the top, and tell developers in the app or by email before a significant change takes effect. The current version is always at https://flightdata.dev/privacy.

16. Contact

Diradical LLC 502 W 7th St Ste 100 Erie, Erie County, PA 16502 support@diradical.com https://diradical.com/flightdatarecorder/