AirportDate

Privacy Policy

Last updated: 12 June 2026

AirportDate (operated by AI Lora, “we”) helps people meet at airports. That only works if you trust us with your data, so this policy says plainly what we collect, why, and what control you have. Questions or requests: privacy@airportdate.com.

The short version

  • Your location is always approximate — the airport, terminal and zone you choose at check-in. We never collect or share exact GPS.
  • We ask for each permission separately, at the moment it unlocks a feature — never as a bundle. You can review and withdraw them anytime in Settings → Consents.
  • Your phone number is never shown to other users.
  • Deleting your account is a hard delete, not a deactivation in disguise.

What we collect

  • Account data— email address, date of birth and phone number. Needed to run your account, verify you're a real person and enforce our 18+ rule.
  • Profile data— display name, photos, bio, gender, who you're interested in, home city and travel intents. Shown to other users; you choose what to add.
  • Sexual orientation (optional) — only if you add it for dating, with your explicit consent. Deletable anytime.
  • Verification data — a live selfie compared against your profile photos, which also estimates your age (biometric data, processed only with your explicit consent). Optionally a passport or driving licence if you join groups that require ID verification.
  • Airport check-ins — the airport, terminal and zone you choose, your trip mode and optionally your destination or flight number. Approximate by design; never GPS coordinates.
  • Messages and activity — your chats, likes, matches, blocks and reports, so the product works and so we can act on abuse.
  • Payment data — handled by Stripe. We never see or store your card number.
  • Analytics — anonymous usage events, only if you allow analytics in the cookie banner or Settings.

Boarding passes

If you scan a boarding pass, we extract the flight details and then delete the image. We keep the extracted text (flight number, times, terminal), not the picture.

Why we process it (lawful bases)

Running your account, check-ins and matching is necessary to provide the service you signed up for (contract). Biometric selfie verification and the orientation field are special category data and are processed only with your explicit consent. Optional features — push notifications, marketing-style email, analytics, AI processing of your profile, live trip sharing — each have their own consent, asked when you first use the feature. Fraud prevention, abuse moderation and legal compliance (including UK Online Safety Act duties) rest on legitimate interests and legal obligation.

Who processes data for us

We use a small set of processors to run AirportDate: Supabase (database, authentication, storage), Vercel (hosting), Resend (transactional email), Stripe (payments), Twilio via Supabase (SMS verification codes), OpenAI (boarding pass text extraction and content moderation fallback), ElevenLabs (optional voice features), Aviationstack (live flight data), Google Places (airport points of interest), Sentry (error monitoring, personal data scrubbed) and PostHog (analytics, only with your consent, no personal data). Each receives only what its job requires.

How long we keep it

While your account is active. Boarding pass images are deleted immediately after extraction. Expired check-ins stop being visible automatically. If you delete your account, your data is hard-deleted — we keep only what the law requires us to keep (for example payment records).

Your rights

Under UK GDPR you can access, correct, export, restrict, object to and delete your data. Export and deletion are built into Settings — you don't need to email anyone, but you can: privacy@airportdate.com. You can also complain to the Information Commissioner's Office (ICO) at ico.org.uk.

Age

AirportDate is for adults only. We check your date of birth at signup and use age estimation during selfie verification, as required by the UK Online Safety Act. Under-18 accounts are removed.

Changes

If this policy changes in a way that matters, we'll tell you in the app before it takes effect, and the cookie banner will re-ask for choices it covers.