Primary sources · 4
- [1] GDPR Article 12 — Transparent information, communication and modalities — Sets the obligation to respond to data-subject requests without undue delay and in any event within one month · EUR-Lex, Regulation (EU) 2016/679 · Entered into force 25 May 2018 https://eur-lex.europa.eu/eli/reg/2016/679/oj
- [2] ICO — Right of access — UK Information Commissioner's Office guidance on SAR response timeframes · Information Commissioner's Office · Current https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/individual-rights/right-of-access/
- [3] California Consumer Privacy Act §1798.130 — CCPA verifiable consumer request response window (45 days, extendable to 90) · California Office of the Attorney General · Effective 1 January 2020; amended by CPRA 2023 https://oag.ca.gov/privacy/ccpa
- [4] OpenFlights data attribution requirements — Open Database License (ODbL) 1.0 — derivative works must attribute the source · openflights.org/data.php · ODbL v1.0 published 19 June 2009 https://opendatacommons.org/licenses/odbl/1-0/
Email is the only channel — there is no phone number, no public chat, and no social DM queue. One inbox receives data-correction reports, partnership inquiries, GDPR / CCPA requests, methodology questions, and feature suggestions, and one editorial voice answers them.
What to contact us about
The inbox handles five categories: data corrections (an airport name, IATA code, coordinate, or route is wrong), bug reports (the calculator returns an unexpected result), methodology questions (how a number was computed), partnership inquiries (embedding the calculator, bulk data, attribution), and statutory data-subject requests under GDPR, CCPA, or similar regulations. Everything in those categories gets a reply.
| Category | Response | Typical reply window |
|---|---|---|
| Data correction (airport, code, coordinate) | Yes — investigated against upstream sources | 48–72 hours |
| Bug report (calculator, UI, schema) | Yes — triaged by severity | 48–72 hours |
| Methodology question | Yes — answered or pointed to /methodology subpage | 48–72 hours |
| Partnership / embedding / bulk data | Yes — substantive replies welcome | 1 week typical |
| GDPR / CCPA data-subject request | Yes — within statutory deadlines | GDPR 1 month / CCPA 45 days |
| General travel advice | No — point to a travel agent or airline | Brief reply only |
| Specific flight booking question | No — point to the airline or aggregator | Brief reply only |
| Press / publicity outreach | Yes — but no commission, no paid placements | 1 week typical |
Bug reports and data corrections
A useful bug report includes four things — the URL you were on, the browser and device, the input you used, and the expected vs. actual output. A useful data correction includes three things — the IATA code (or country slug) of the entity, the claimed correct value, and a primary-source citation so we can validate without re-investigating from scratch.
- 1Reproduce the issue once
Open the exact URL where the problem appears. Note the browser version and device type. Take a screenshot if the visual layout is part of the bug.
- 2Describe the gap
Write what you expected to see and what you actually saw. For data bugs include the airport IATA codes and the metric (distance, time, CO₂, bearing) that looks wrong.
- 3Cite a primary source
Data corrections should reference an authoritative source — an IATA or ICAO publication, an airline schedule page, or an official aviation-authority document. We can't accept “heard from a pilot” corrections.
- 4Send to info@airmilescalc.com
One email per issue. We reply within 48–72 hours for routine reports; data corrections that require upstream OpenFlights changes can take longer because we have to file with that project too.
Data-subject requests under GDPR, CCPA, and similar
If you are exercising statutory rights under GDPR Articles 15–22, the California Consumer Privacy Act, Brazil's LGPD, the UK Data Protection Act 2018, or any equivalent regulation, write to the same email with “Data subject request” in the subject line. We respond within the statutory deadline for your jurisdiction.
| Regulation | Deadline | Extendable to |
|---|---|---|
| GDPR / UK GDPR (Art. 12) | 1 month | 3 months for complex requests |
| CCPA / CPRA (§1798.130) | 45 days | 90 days with notice |
| LGPD (Art. 19) | 15 days | No standard extension |
| PIPEDA (Principle 9) | 30 days | 30 additional days with notice |
| PIPA / Korea (Art. 35) | 10 days | 10 additional days |
Partnerships, embedding, and bulk data
The calculator is free to link to from any website without permission. Embedding the live UI on a third-party site, white-labeling the distance/CO₂ API, or accessing bulk data exports needs a conversation — we can usually accommodate but require attribution under the OpenFlights ODbL terms that bind the underlying data.