Data Processing Addendum
Effective December 1, 2026.
The short version. When people use your app and send a report through Flight Data, you decide what is collected and why, and we store and deliver it for you. Data protection law calls you the controller and us the processor, and asks for a written agreement between us. This is it. We handle the personal data in your users' reports only to run Flight Data for you, we keep it secure, we tell you if something goes wrong, we use only the helpers listed here, and we delete it when you say so or when you leave. Reports are stored in the United States, so the European Commission's standard contract terms for sending data abroad are part of this too. The rest of this document says the same things precisely.
This Addendum is part of the Flight Data Terms of Service (https://flightdata.dev/terms, the "Terms") between you and Diradical LLC ("we," "us," "our"). It applies whenever data protection law applies to personal data in the reports your apps send. You accept it when you accept the Terms; nobody has to sign it. If your organization needs a signed copy, write to us and we'll send one.
Words the Terms define mean the same here. "Controller," "processor," "personal data," "processing," "data subject" and "personal data breach" mean what they mean in the GDPR.
1. What this covers
The personal data in your users' reports, while we hold it for you. Not your own account, and not what is on your Mac.
"Data protection law" means the EU General Data Protection Regulation (Regulation (EU) 2016/679, the "GDPR"), the UK GDPR and the UK Data Protection Act 2018, and the Swiss Federal Act on Data Protection, each as it applies to you.
"Report data" means the personal data in the reports your apps send to Flight Data with FlightDataKit, and in what you file them under, for as long as our service holds it. It has two parts, described in Annex 1: the sealed contents, which we can't read, and the readable details our service needs to route, count and limit reports.
This Addendum doesn't cover:
- your account, your organizations and your subscription. For those we are a controller in our own right, and our Privacy Policy (https://flightdata.dev/privacy) applies;
- reports once Flight Data Recorder has downloaded and opened them on your Mac, or anything you or an agent you allow does with them there. That processing is yours.
2. Who is who
You are the controller. We are your processor.
For report data, you decide what your apps collect and why, so you are the controller, and we process it on your behalf as your processor. If you are yourself a processor for someone else (for example, you build an app for a client), we are your sub-processor, and you confirm that the controller has agreed to that.
You remain responsible for what the Terms give you in section 6: telling your users what your app sends, having a legal basis for it, and answering them. Because the contents of a report are sealed, we can't check what your apps collect. Don't use Flight Data to collect special categories of personal data (such as health data) or data about children unless the law allows you to and you have taken the steps it requires.
3. What we do with report data, and only on your instructions
We receive, store, count, deliver and delete it. Nothing else.
We process report data only on your documented instructions. Your instructions are the Terms, this Addendum, how you set up your apps and your account (which app sends what, to which key, and each app's settings), and what you and your organization's members do in Flight Data Recorder, such as deleting a report. Your instructions include storing report data in the United States, as section 11 describes. If you need something else done with report data, write to us; we'll do it if it is lawful and the service can do it.
The processing is: receiving reports from the devices that send them; storing them; checking and counting them against your plan and against the limits that protect the service from abuse; delivering them to the Macs your organization's members have signed in on; and deleting them. Annex 1 has the details.
We don't open report contents, and can't. We don't sell report data, share it for advertising, combine it with data from other customers to learn about people, or use it to train AI.
If the law of the United States, the EU or one of its member states, or the UK requires us to process report data in some other way, we'll tell you before we do, unless that law forbids us to tell you. If we think one of your instructions breaks data protection law, we'll tell you.
4. Who has access
Only the people at Diradical who run the service, under a duty of confidentiality.
We let only the people who need it to run and support Flight Data reach the systems that hold report data, and each of them is bound to keep it confidential. That duty continues after they stop working with us.
5. Security
The measures in Annex 2. We may improve them, and won't weaken them.
We keep the technical and organizational measures in Annex 2, which take into account what the data is, how it is processed and what could go wrong. We may change them as the service changes, but not in a way that lowers the overall protection of report data.
Some of the protection is in your hands. The private keys that open your reports are made and kept on your Macs, and we never have them: keep them safe and backed up. You decide what your apps collect, who is a member of your organization, and what you allow agents to read.
6. Other companies that help us (sub-processors)
You agree to the ones in Annex 3. We'll tell you before adding one, and you can object.
You give us general authorization to use sub-processors for report data. Annex 3 lists the ones we use today.
Before we add or replace a sub-processor, we'll tell the owners of your organization by email at least 30 days ahead, and update the list. If you have a reasonable objection on data protection grounds, tell us within that time. We'll try to resolve it. If we can't, you may stop using Flight Data and delete your organization before the change takes effect, and Apple's rules on refunds apply to any subscription.
We hold each sub-processor, by contract, to data protection duties that match the ones in this Addendum, and we remain responsible to you for what they do with report data.
7. When one of your users asks about their data
We send them to you, and help you answer.
We can't tell whose report is whose: the contents are sealed, and the readable details don't name anyone. If someone writes to us about a report they sent through your app, we won't answer the request ourselves. We'll tell them to contact the developer of the app, as the Privacy Policy says, and if they tell us which app it was, we'll let you know.
Flight Data Recorder gives you what you need to answer most requests yourself: you can open a report, save its files, and delete it or only its attachments. Where you need our help to respond to a request under data protection law, ask, and we'll give the help that is reasonable given what we are able to see.
8. If something goes wrong, and other help
We'll tell you about a breach without undue delay, and help with the assessments the law asks of you.
If we become aware of a personal data breach affecting report data we hold for you, we'll tell the owners of your organization by email without undue delay, and within 48 hours where we can. We'll say what happened, what data and roughly how many reports are affected, what we have done about it, and what we suggest you do, and we'll add to that as we learn more. Telling you is not an admission that we are at fault.
On request, we'll give you the information we have that you reasonably need to carry out a data protection impact assessment or to consult a supervisory authority about your use of Flight Data.
9. Keeping, returning and deleting report data
You can take a copy and delete at any time. When you leave, we delete what we hold.
While you use Flight Data, Flight Data Recorder downloads your reports to your Macs, which is how report data is returned to you, and you can delete reports, their attachments, an app or your organization at any time. How long reports are otherwise kept is in section 10 of the Privacy Policy.
When your organization is deleted, or the Terms end, we delete the report data we hold for it, and it ages out of our backups within the periods the Privacy Policy states, unless a law we are subject to requires us to keep it, in which case we'll keep it sealed and do nothing else with it.
10. Showing that we comply
We'll answer reasonable questions, and you may audit us where the law gives you that right.
We'll make available the information you reasonably need to show that we keep to this Addendum: this document and its annexes, the Privacy Policy, the published list of what our service can and can't read, and written answers to reasonable questions, up to once a year.
If that isn't enough to meet your obligations under data protection law, you, or an independent auditor you appoint who is bound to confidentiality, may audit how we process your report data. Give us at least 30 days' notice; keep to once a year, unless a supervisory authority requires more or there has been a breach; do it in working hours and at your own cost; and agree the scope with us first, so that no other customer's data is exposed and the service's security isn't weakened. For the parts of the service our hosting provider runs, its published certifications and audit reports take the place of an inspection of its premises.
11. Sending data outside Europe
Report data is stored in the United States. The European Commission's Standard Contractual Clauses apply, with the UK and Swiss additions.
We store and process report data in the United States. Where data protection law applies to you and restricts sending personal data to a country that doesn't have an adequacy decision, you and we agree to the following, which are part of this Addendum:
- The EU Standard Contractual Clauses approved by Commission Implementing Decision (EU) 2021/914: Module Two (controller to processor) where you are a controller, and Module Three (processor to processor) where you are a processor. You are the data exporter and we are the data importer. Annex 4 has the choices the Clauses leave open, and Annexes 1 to 3 are their annexes.
- For the UK, the Clauses as amended by the UK Information Commissioner's International Data Transfer Addendum to the EU Commission Standard Contractual Clauses, version B1.0, completed as Annex 4 says.
- For Switzerland, the Clauses as adapted in Annex 4.
If a court or authority decides that one of these can no longer be relied on, we'll work with you to put another lawful mechanism in place.
One protection doesn't depend on any contract: report contents are sealed on the sender's device to a key only you hold. We can't hand over what we can't read. If an authority asks us for report data, we'll follow the Clauses: tell you unless we are forbidden to, challenge a request we have reasonable grounds to think unlawful, and give no more than the request requires.
12. Liability
The limits in the Terms apply, except where the law or the Clauses don't allow a limit.
Each of us is liable under this Addendum subject to the limits in section 17 of the Terms. Nothing in this Addendum or the Terms limits either party's liability to a data subject under the Standard Contractual Clauses or under data protection law, or any liability the law doesn't allow to be limited.
13. How this fits with the Terms
For report data, the Clauses come first, then this Addendum, then the Terms.
If this Addendum and the Terms disagree about report data, this Addendum governs. If the Standard Contractual Clauses apply and disagree with either, the Clauses govern.
This Addendum lasts for as long as we hold report data for you. We may change it as section 18 of the Terms describes, and we won't change it in a way that takes it below what data protection law requires of a processor.
Section 19 of the Terms (governing law and disputes) applies to this Addendum, except that the Standard Contractual Clauses are governed as Annex 4 says.
14. Contact
Questions about this Addendum, and anything it says to send us, go to the address in section 21 of the Terms:
support@diradical.com
Annex 1. Details of the processing
This is also Annex I of the Standard Contractual Clauses.
A. The parties
| Data exporter | Data importer | |
|---|---|---|
| Who | You: the organization that agreed to the Terms | Diradical LLC, a Pennsylvania limited liability company |
| Contact | The owners of your organization in Flight Data, at the email addresses of their accounts | The address in section 21 of the Terms; support@diradical.com |
| Role | Controller, or processor for another controller | Processor, or sub-processor |
| What the transfer is for | Using Flight Data to receive reports from your apps | Providing Flight Data |
Each party is taken to have signed the Clauses on the date you accepted the Terms.
B. The processing
| Subject matter | Storing and delivering the reports your apps send |
| Nature | Receiving, storing, counting and limiting, delivering to your organization's Macs, and deleting |
| Purpose | Providing Flight Data to you under the Terms |
| How often | Continuously, whenever one of your apps sends a report |
| How long | Until you delete a report, an app or your organization, or the Terms end, and then for the periods in section 10 of the Privacy Policy |
| Whose data | The people who use your apps and send reports, and anyone they mention or picture in what they send |
| Sub-processors | Annex 3: hosting, for as long as we hold the data |
Report data we can't read (sealed on the sending device): the title and description of a report; contact details the person gave; your app's own questions and their answers; labels; every attached file, such as screenshots, documents and logs; crash logs and periodic reports; and the text of the work items you file reports under.
Report data our service can read:
- which app and report type a report is for, and whether it is feedback, a crash or a periodic report;
- the app's version and build, the platform, the operating-system version, the device model and the language setting;
- an identifier of the app's executable, and whether the app was a test build;
- a keyed hash of a random identifier FlightDataKit makes for each installation, with a short random handle and when it was first and last seen;
- where the app and device support Apple's App Attest: the public half of the key the copy enrolled, what Apple's attestation states about the copy, and a counter;
- the ID of the key a report is sealed to, the sizes and fingerprints of its sealed parts, and when it arrived and changed;
- whether it is held over a plan's limit, and how you have sorted it.
Special categories of data: none that we ask for or know of. Whether a report contains any depends on your app and on what your users write and attach, and the contents are sealed.
C. The supervisory authority
The authority that Clause 13 of the Standard Contractual Clauses points to: the one in the EU member state where you are established; if you aren't established in the EU, the one where your representative under Article 27 of the GDPR is; and if you need no representative, the one in a member state where the people whose data is transferred are. For the UK it is the Information Commissioner, and for Switzerland the Federal Data Protection and Information Commissioner.
Annex 2. Security measures
This is also Annex II of the Standard Contractual Clauses.
- Sealing. Report contents are encrypted on the sending device, before upload, with HPKE (RFC 9180: X25519, HKDF-SHA256 and ChaCha20-Poly1305), to a public key that ships in your app. The matching private key is made on your Mac and kept in its keychain. Our service holds no key that opens a report, so the contents stay encrypted in our storage and in our backups.
- In transit. Every connection to our service uses HTTPS.
- At rest. Our database is encrypted at rest and accepts only encrypted connections. Sealed files are stored as they arrived, encrypted.
- Sign-in. Developers sign in with Sign in with Apple; we hold no passwords for them. Sign-in tokens are stored only as hashes. An app token is not a secret and can only send reports.
- Separation. Each organization's reports are kept apart by organization and app, and a request is answered only for a member of that organization, according to their role.
- Genuine senders and limits. Where the app and device support Apple's App Attest, the service can check that a report comes from a genuine copy of your app, and you can choose to accept only those. Reports are rate-limited by installation and by app, and an installation that sends abuse can be blocked.
- Access by us. Only the people who run Flight Data can reach its systems, through an operators' console with its own sign-in. Security-relevant actions are recorded, and those records are kept at least 90 days.
- Logs. Our server's logs record the kind of request, its result, timing and size, and for signed-in requests the internal IDs of the user and session. They don't record internet addresses, tokens or report contents.
- Deleting. You can delete a report, its attachments, an app or your organization yourself, at any time.
- Backups. Our database is backed up automatically, and those backups are kept 7 days.
- Hosting. The servers, the database and the storage run in Amazon Web Services data centers, under AWS's own physical and environmental security.
- Changes and review. Changes to the service are tested before they are deployed. The source of FlightDataKit, where the sealing happens, is available to you to read. No outside party has audited the service or the kit yet.
Annex 3. Sub-processors
This is also Annex III of the Standard Contractual Clauses.
| Company | What it does with report data | Where |
|---|---|---|
| Amazon Web Services, Inc. | Hosts Flight Data on Amazon Lightsail: the servers, the database, the storage that holds sealed reports, and the database's backups | United States (US East, Ohio) |
Apple is not a sub-processor for report data. Checking an App Attest proof and a Sign in with Apple token happens on our own server with Apple's published keys, and we send Apple nothing about your users' reports. Amazon also sends our email, which goes only to developers about their accounts and carries no report contents.
Annex 4. The Standard Contractual Clauses: what we choose
Where section 11 applies, the Clauses are completed like this.
| Clause | Choice |
|---|---|
| Clause 7, joining later | Not used |
| Clause 9(a), sub-processors | Option 2, general written authorization, with the notice period in section 6 |
| Clause 11(a), an independent body for complaints | The optional wording is not used |
| Clause 13, supervision | As in Annex 1, part C |
| Clause 17, governing law | Option 1: the law of Ireland |
| Clause 18(b), courts | The courts of Ireland |
| Annexes I, II and III | Annexes 1, 2 and 3 of this Addendum |
For the UK. The International Data Transfer Addendum is completed with: in Table 1, the parties and contacts of Annex 1; in Table 2, the Clauses as completed above; in Table 3, Annexes 1 to 3; and in Table 4, either party may end the Addendum as its section 19 allows.
For Switzerland. References to the GDPR include the Swiss Federal Act on Data Protection; the supervisory authority is the Federal Data Protection and Information Commissioner, alongside any EU authority; "member state" isn't read to stop people in Switzerland from claiming their rights where they live; and the Clauses also protect the data of legal entities for as long as Swiss law does.