Privacy
This site sets no cookie at all. It runs no analytics and never will: no counter, no reader account, no form that asks who you are. That is a decision the publisher has taken, not a gap waiting to be filled. What is left is what every web server sees: the request itself, written to the host’s log. Below: what that log holds, who keeps it, what the calculator and the search box send with your typing, and what happens when you follow a link to a claim service.
#What does this site collect about you?
0 analytics scripts run on this site, and 0 reader accounts exist on it, by decision rather than by delay. Nothing you read here is recorded against you by the publisher. The only trace of your visit is the request log kept by the company that serves the page.
There is no file on you here. Nothing about a reader is stored, nothing is joined to anything else, and no third party is asked for data about you. Measuring readers was not postponed; it was decided against, so there is no product to name later and no counter waiting to be switched on.
There is no sign-up. No newsletter, no comment box and no advertising network appears on any page, and every reader gets the same page, built from this site’s own content store and sent as written.
Measured on 22 September 2026, responses from the live site returned no Set-Cookie header at all, and the markup loads nothing from another company. Every response also carries a Content-Security-Policy header that lets a page fetch scripts, styles, fonts, images and data from this site’s own origin only, so your browser would refuse an outside tracker even if one were added by mistake. The webfont is served from this site’s own path, and every outside host named in the pages — legislation.gov.uk, ico.org.uk, cloudflare.com and the regulators the pages cite — is a link that fetches nothing until you click it.
One login does exist, at the publishing back end. It belongs to the people who write and check the pages, and reading the site never creates an account for you.
That absence is why this notice stays short. A site that recorded reading habits would need paragraphs about profiles, retention and consent, and this one has none of those to describe.
Run curl -I against any page here if you would rather read the headers than take this section on trust.
#Which cookies does the site set?
0 cookies are set by this site. Responses measured on 22 September 2026 from an article page, the compensation calculator and the partner redirect carried no Set-Cookie header, and no script on any page writes one. The site has a single light colour scheme, so there is no preference to remember either.
There is no consent banner here, because there is nothing to consent to. A banner exists to ask before a site stores or reads something on your device, and this one does neither: no identifier, no counter and no record of which page you read is kept in your browser by these pages.
No page embeds a video player, a map, a share button or a comment widget either. Those are the usual routes by which another company’s cookie lands on a page that set none itself, and the security header described above would block them.
One boundary sits outside this site. A link to a claim service leads to companies that set their own cookies once you arrive, under their own policies; the last section of this page names that link and what travels with it.
Open the storage panel in your browser’s developer tools on any page here: the cookie list for this site stays empty.
#What happens to what you type into the calculator or the search box?
2 places on this site take typing, and both send it to the server inside the page address. The compensation calculator is a plain GET form worked out on the server, exactly like the search box, so what you enter shows in the URL and lands in the host’s request log. Neither asks for your name.
The calculator’s fields describe the flight, not the person: the airports or countries, the distance, the airline, what went wrong and by how long, the date, the number of passengers and the country where you would claim. None of them identifies you, and the answer depends on nothing else. Choosing an airport loads a list, /data/airports.json, from this site’s own address; no outside service is asked.
A result page with a query string carries a noindex instruction, so a search engine that meets a link to your result leaves it out of its index. The claim letter the calculator fills in keeps your name, your address and your booking reference as bracketed blanks. You complete them in your own copy, after it has left this site, and nothing you entered is stored here.
The search page works the same way. Your query travels as ?q= inside the request, reaches the host and sits in its log like any other URL. Nothing here stores it or matches it to anything.
Keep names and booking references out of both boxes; the airline, the route or the rule is all either one needs.
#Who else handles your request, and for how long?
1 company stands between you and these pages: Cloudflare, which serves every request and stores the content in its D1 database. Like any host, it logs what arrives — the IP address the request came from, the URL asked for and the browser’s user-agent string.
That log is Cloudflare’s, and the publisher neither reads it nor keeps a copy. It still holds data about you: the UK GDPR counts someone identifiable through an online identifier as a data subject, and an IP address is such an identifier, which is why this page names the log instead of telling you that nothing about your visit exists anywhere. A search you run and the flight details you give the calculator land in it too, because both pages are built on the server and what you type rides in the URL.
UK GDPR counts someone identifiable through an online identifier as a data subject, and an IP address is such an identifier, which is why this page names the log instead of telling you that nothing about your visit exists anywhere. A search you run and the flight details you give the calculator land in it too, because both pages are built on the server and what you type rides in the URL.Cloudflare’s privacy policy, at section 11, ties retention to the purpose of collection and to its legal obligations, and publishes no fixed period for this kind of log. This page names no number either. The period is Cloudflare’s to set, and its policy is where to read the current position.
In that policy Cloudflare describes itself as a processor of what it calls Customer Logs, and as a controller of the personal information it collects in its own right. Its UK entity is Cloudflare, Ltd., County Hall/The Riverside Building, Belvedere Road, London SE1 7PB, and its data protection officer is reachable at dpo@cloudflare.com.
One more thing travels with every response. Cloudflare’s edge adds NEL and Report-To headers, which ask your browser to report failed requests to a.nel.cloudflare.com; the reported fraction of successful requests is 0.0, so a page that loads normally is never reported. Those headers come from the host, not from this site’s code.
Source: Cloudflare Privacy Policy, s.11 Data Retention and s.19 Contact Information — cloudflare.com; UK GDPR art. 4(1) — legislation.gov.uk; response headers measured on this site, checked 2026-09-22.
Read Cloudflare’s own policy before you assume a retention period: this site can neither shorten nor extend it.
#What rights do you have over data about you?
8 individual rights sit in the Information Commissioner’s Office guide to the UK GDPR: to be informed, of access, to rectification, to erasure, to restrict processing, to data portability, to object, and rights about automated decision-making. They bind whoever holds data about you.
The publisher keeps no record of your visit, so there is usually nothing here to copy, correct or erase. What can exist is an e-mail you sent to hello@airtravelrights.com or corrections@airtravelrights.com and the reply to it, kept only as long as it takes to close that exchange. Send a request about it to hello@airtravelrights.com.
That mailbox reaches the people who write and check these pages, publishing as Air Travel Rights. There is no company behind it, no office and no named staff, which is what about and contact already tell you. Ask for a copy of an exchange, a correction to it or its deletion, and say which address you wrote from. The UK GDPR and the Data Protection Act 2018 are the framework this page is written against, because most readers are in Great Britain.
No statutory deadline is quoted here, because the ICO page did not render the figure when this was checked. The aim published at contact is a reply within five working days, and an aim is not a deadline.
The ICO takes complaints directly and free of charge if you are in the UK and think an organisation has mishandled data about you. For the request log described above, that organisation is Cloudflare rather than this site.
Name the page and the date when you write about an e-mail exchange; there is no account here to look you up by.
#What happens when you follow a link to a claim service?
More than 70 pages carry a link to AirHelp, a third-party claim service. The link is labelled “(third-party claim service)”, always sits after the free do-it-yourself route, and is tagged rel="nofollow sponsored". The amounts and routes on every page come from the cited act, whichever route you take, so the link adds an option rather than a figure.
AirHelp, a third-party claim service. The link is labelled “(third-party claim service)”, always sits after the free do-it-yourself route, and is tagged The link points at /partner/airhelp on this site, which forwards you to AirHelp through the Travelpayouts network. The forwarding address carries a code, a sub-ID, naming the page that sent you, and that page is the only thing it records. It carries nothing about you: no identifier, no list of the pages you read, nothing you typed.
Once you arrive, AirHelp and Travelpayouts set their own cookies under their own privacy policies, and those policies, not this one, govern what happens next. What you read here before the click is not passed on. This site’s Referrer-Policy header tells your browser to hand another site only this site’s address, not the full URL you were on, so a calculator query never travels with the click.
On the development host the forwarding currently goes to airhelp.com without the code; on the live domain it carries it. The live domain also drops the development host’s X-Robots-Tag: noindex header, which keeps staging out of search results. Analytics is not a pending change. This site is published without measurement and stays that way.
Take the free route named first on each page if you would rather no third party learns of your visit; it needs no link at all.
This page describes how this site handles data; it is not legal advice about your own data-protection rights. For a specific case, contact the ICO or a qualified adviser.
#Sources
- Cloudflare Privacy Policy (data retention, controller and processor roles, UK entity and DPO contact) - cloudflare.com, checked 2026-09-20.
- ICO, A guide to individual rights under the UK GDPR - ico.org.uk, checked 2026-09-20.
- ICO, Make a complaint - ico.org.uk, checked 2026-09-20.
- UK GDPR, Regulation (EU) 2016/679 as it forms part of UK domestic law, art. 4(1): a person identifiable through an online identifier is a data subject - legislation.gov.uk, checked 2026-09-21.
- Data Protection Act 2018 - legislation.gov.uk, checked 2026-09-20.
- Response headers, page markup and redirect behaviour measured on the site itself (no
Set-Cookieon an article, the calculator or/partner/airhelp;Content-Security-Policylimited to the site’s own origin;Referrer-Policy: strict-origin-when-cross-origin; a GET calculator form whose result page carriesnoindex; the webfont served from/_astro/fonts/;NELandReport-Toadded by the host; the partner path answering with a 302) — this site, checked 2026-09-22.
EU) 2016/679 as it forms part of