We built Airport.blog to answer one question quickly and then get out of your way. That principle shapes what we collect: the minimum needed to show the right airport and keep the feeds honest.
What we collect
Search terms you type, the airport pages you open, your coarse region derived from IP, and standard request data such as browser and referring page.
If you send us a correction or a press request, we keep your name, email and message so we can reply and audit the fix.
What we never collect
No account is required to use any part of this site, so we hold no passwords, no travel documents and no payment details. Bookings happen entirely on the partner’s own site.
We do not buy third-party profiles, and we do not sell or rent anything we collect.
Cookies and measurement
One first-party cookie remembers your last airport and unit preferences. Aggregate analytics are collected without cross-site identifiers and are retained for 14 months.
You can clear both at any time from your browser without losing access to anything.
Partner and affiliate links
Parking, hotel and transfer cards marked “Partner” pass an anonymous click identifier so the partner can attribute a booking. The identifier contains no personal data.
Once you land on a partner site, their privacy policy governs what happens next.
Your choices
You can ask for a copy of anything tied to your email address, or ask us to delete it, by writing to [email protected]. We answer within 30 days.
Where local law gives you a right to object to analytics, honouring a Global Privacy Control signal is enough — no form required.
Retention and changes
Correspondence is kept for two years; raw request logs for 30 days; aggregate counts indefinitely.
Material changes are announced on this page with a new date at the top, and we keep prior versions available on request.