Terms of service

These terms are the contract between you and Flight API for use of flight-api.dev and the historical flight status API (the “service”).

Creating an account, minting a key, or running a lookup accepts them. If you use the service for an organisation, you warrant you can bind it. The Privacy policy describes the personal data side; it is part of this contract.

Effective 28 August 2026. English is the governing language.

One authenticated GET takes a flight number and a UTC date and returns a settled record — or selected: null if nothing disrupted. Coverage, freeze rules and what is never stored are on the coverage page. The live contract of the API is the reference.

The record is the product. How we produce it stays ours. You do not get a feed, a dump, or a licence to the internals.

Access is Google or a magic link to the inbox. There is no password. The dashboard stays closed until the address is proven — Google’s verified email, or the click on the link. Links expire in 15 minutes and are single-use.

You are responsible for the inbox, the Google account, and every key issued under you. Tell us if either is compromised. We may refuse an address, a domain, or a jurisdiction we cannot serve.

Keys are hashed with SHA-256 and compared in constant time. The plaintext is shown once, at creation. We cannot retrieve it later. Treat it as a secret: server-side only, never in a public repo or a browser bundle.

A request without a valid key is refused. Revoking a key is immediate. You may mint more than one; abuse of a single key is abuse of the account.

You may query the API for your own products and internal tools, including commercial ones, within the plan you pay for.

• Do not share keys, resell raw responses as a competing API, or wrap us as the public face of another status product without a written deal.
• Do not scrape the site to bypass metering, hammer endpoints, or probe for sources.
• Do not attempt to identify passengers from a record. The payload is operational, not a passenger list.
• Do not use the service for anything unlawful where you operate.
• Do not overload, reverse-engineer, or interfere with the resolve path.

We may rate-limit, suspend a key, or close the account if this section is broken.

Published plans, allowances and overage rates live on Pricing. A credit window is 30 days whether you pay monthly or yearly. One authorised request consumes one credit before the resolve runs. The remaining balance is returned on the response.

An account with no active subscription may run a short evaluation — 25 lookups — and is then refused with 402 until a plan is paid. Evaluation is not a commercial licence.

Stripe handles cards. Fees are in USD as shown at checkout. Taxes may be added where Stripe is required to collect them. Yearly is prepaid; we do not prorate a downgrade mid-cycle. Overage, where the plan allows it, is billed at the published per-request rate. Enterprise is a separate written order.

Chargebacks without talking to us first are grounds to suspend keys while it is investigated. Unused credits expire at the end of the window. They are not refundable and do not roll.

Records are our best settled view of a historical disruption. Aviation data is messy. A re-resolve can update a row. We publish no SLA number; the response already carries the measured wall clock.

Do not treat a record as a legal finding, a passenger-rights decision, or a substitute for the airline’s own data. If you build a claims or compensation product on top, the legal conclusions are yours.

We own the service, the site, the mark, and the method of producing a record. A paid plan grants a worldwide, non-exclusive, non-transferable licence to use the JSON you receive in your products for the term of the subscription. Evaluation lookups are for evaluation only.

You own your company profile, your keys’ names, and the software you write against the API. Feedback you send us can be used without restriction.

Keys, usage, billing state and unpublished product detail are confidential. Frozen flight records returned to you are licensed data, not a public dump — do not republish the entire archive. This survives termination for three years.

We aim to keep the endpoint up. Maintenance, upstream outages and force majeure happen. Published plans include no uptime credit. Enterprise may negotiate one in writing. We may change, throttle or withdraw features with notice on the docs or by mail, except where we must act immediately against abuse.

The service is provided as-is. We disclaim implied warranties of merchantability, fitness and non-infringement to the fullest extent the applicable law allows.

We are not liable for lost profits, lost data, business interruption, or indirect, incidental or consequential loss, even if advised. Our aggregate liability under this contract is capped at the fees you paid us for the service in the 12 months before the claim. Nothing excludes liability for death, personal injury, fraud, or anything else that cannot be limited under the applicable law.

You will indemnify us against claims, damages and reasonable legal costs arising from your use of the API, your product’s conclusions, your combination of a record with passenger data, or your breach of these terms.

You may stop using the service and delete the account from the dashboard, or by mailing support@flight-api.dev. We may suspend or close an account for non-payment, abuse, legal risk, or prolonged inactivity on an unpaid evaluation.

On close, keys die. Licensed use of already-received JSON for your existing product may continue; you may not keep calling the API. Sections on IP, confidentiality, liability, indemnity and law survive.

We may update these terms. The new version is posted here with a new effective date. Material changes get an email to the account. Continued lookups after the date accept the new terms. If you do not agree, stop and delete the account before that date.

This contract is governed by the laws of the operator’s place of establishment, without regard to conflict-of-law rules. Exclusive jurisdiction: the competent courts of the operator’s place of establishment, except we may still seek injunctive relief where your keys or our IP are at risk.

If a clause fails, the rest stands. Failure to enforce a right once is not a waiver. These terms are the entire agreement for the service.

Flight API
support@flight-api.dev