FlightPeek

Last updated: 24 October 2026

Privacy policy

What FlightPeek stores, why, for how long — and what we deliberately do not collect.

Controller

KCraft Studio LTDNeofytou Nikolaidi & Theod. KolokotroniONISIFOROU CENTER (2nd floor)Agios Theodoros, 8011 PaphosCypruscontact@kcraft.io

What we do not collect

The app requests no location access, no contacts and no microphone. The camera opens only at your request to scan a boarding pass — the barcode is read on the device; no image is stored or transmitted. The app contains no third-party advertising or tracking components, and we do not sell data. We openly describe one exception below: we report subscription purchases to Meta. The optional calendar import reads your events exclusively on the device: a flight number is detected locally — only that number is sent to our server, never the event content. The same applies to text shared via the share sheet and to screenshots you pick for import: the text is recognised on the device, the image never leaves it.

What data we process

Account
Email address, an optional display name, and your password as a bcrypt hash — it is never stored in clear text. An anonymous account without an email address is possible. Legal basis: performance of a contract, Art. 6(1)(b) GDPR.
Tracked flights
Flight number and date of the flights you add, along with the status data retrieved for them. This reveals when and where you travel, so we treat it like account data and do not pass it on. Legal basis: performance of a contract.
Boarding passes
Scanned or imported boarding passes (name, flight number, seat, booking reference) stay exclusively on your device. Only the flight number and date are sent to our server — the same information as a manual search.
Sign-in with Google or Apple
If you sign in with Google or Apple, we receive a signed token containing your email address and, where provided, your name. The provider learns that you sign in to FlightPeek — not which flights you track. With Apple you can hide your email address. Legal basis: performance of a contract, Art. 6(1)(b) GDPR. Both are optional; an email account or anonymous use work just as well.
Sign-in by code
In the dashboard for businesses you sign in with a code we send to your email address. The code is valid for 15 minutes. Legal basis: performance of a contract, Art. 6(1)(b) GDPR.
Compensation claim
If you submit a compensation claim in the app, it goes, after your express confirmation, to one of our partners, which assesses and pursues the claim under its own responsibility; its privacy policy applies. The form shows you which partner is responsible. To Compensair Ltd, London, we transmit the travellers' names, your email address, the booking reference and the flight details. To Flightright GmbH, Berlin, we transmit the flight number, flight date, number of travellers, your language and a case identifier; you give Flightright your name and email address yourself when you complete the claim on their site. We do not store names or the booking reference. We store the email address, the number of travellers, the case identifier and the processing status to show you the status in the app. Legal basis: performance of a contract at your request, Art. 6(1)(b) GDPR. If a flight you track arrives at least three hours late or is cancelled, FlightPeek asks Flightright in advance whether a claim exists. Only the flight number, flight date and a case identifier go to Flightright, no information about you. If Flightright confirms a claim, we notify you by push; whether you file it is up to you. Legal basis: our legitimate interest in pointing you to a possible claim, Art. 6(1)(f) GDPR.
Push token
A device identifier issued by the operating system, used to deliver notifications, plus the platform (Android or iOS). Without it we cannot send anything. If the service reports a token as invalid, we delete it. We only send notices about offers and the end of your subscription if you have switched them on in the app under Account → Alerts; for this we store the time of your consent. You can switch them off there at any time. Legal basis: consent, Art. 6(1)(a) GDPR.
Subscription
Whether your subscription is active and until when. Payment itself is handled by Apple and Google — we see no card details and no billing address. For FlightPeek Business, see the section below.
Purchase reports to Meta
When you subscribe, start a trial or your subscription renews, we report this to Meta to measure whether our advertising works: the type of event, amount, currency and product, plus your email address, account identifier and country — these three only as an irreversible hash (SHA-256). The app itself contains no Meta component for this; the report is sent from our server. Legal basis: legitimate interest in measuring the success of our advertising, Art. 6(1)(f) GDPR. You can object at any time by email; we record the objection on your account and stop reporting your purchases.
Server logs
Accessing our API produces technical logs (timestamp, requested path, error states). Legal basis: legitimate interest in secure operation, Art. 6(1)(f) GDPR.
Error diagnostics
If an error occurs in the backend or the app crashes, a technical report (error message, code location, timestamp, app version and device type) is sent to our own GlitchTip installation. Request contents, passwords and screenshots are expressly excluded; we remove user identifiers before sending. Legal basis: legitimate interest in reliable operation, Art. 6(1)(f) GDPR.
Usage statistics in the app
The app reports which screens are used and which steps are taken, along with language, device type and app version, directly to our own Matomo installation. The app stores nothing on your device for this and sends no identifier. Matomo tells visits apart using a checksum of IP address and device details that cannot be reversed; Matomo stores the IP address itself only in shortened form. Older app versions still kept a random identifier on the device; the update deletes it. Legal basis: legitimate interest in comprehensible usage statistics, Art. 6(1)(f) GDPR.

What is not recorded: which flight you track, your booking reference, your name or your email address. The statistics count steps — "paywall opened", "flight added" — not destinations.

FlightPeek Business for businesses

Businesses such as transfer companies use FlightPeek Business to plan airport pickups. Two roles need to be distinguished.

Data of the business and its members
We are the controller for the business as our contracting party (name, owner, billing and contact details) and for members' own accounts (email address, name, sign-in). Legal basis: performance of a contract, Art. 6(1)(b) GDPR. What the business sets within its access about its members — role, invitations, assigned pickups, drive times, notification settings — we process on its behalf, as well as the meeting point, webhook address and API keys (only as a hash).
Pickups and passengers
What a business enters for a pickup — flight number, date, a note such as the passenger's name, a booking reference, the handover time — we process on behalf of the business under Art. 28 GDPR. The business is the controller; passengers should address questions and requests to it. The terms are set out in our data processing agreement.
Visibility within the business
Dispatch sees the flights assigned to the business, not a driver's private flights. Drivers can mark individual flights as private in the app. If the business removes a member, the member keeps their account and own flights; the business's notes and details are removed.
Pickup page for passengers
If the business shares a pickup link, anyone with the link sees the flight status, estimated handover time, the business's name and meeting point and the driver's first name — not the passenger's name. The link is valid until 24 hours after landing.
Calendar, webhook, API, email import
The business sets up these features itself. The data then goes to the destinations it chooses — its calendar, its webhook address, its own system. Where we offer email import and the business uses it, we only analyse forwarded booking confirmations to detect flight numbers and dates; we do not store the email itself.
Payment with Stripe
The business pays for the subscription via Stripe. Stripe collects name, email address, billing address, VAT ID where applicable and payment details; we never see card details. We store the customer and subscription identifiers at Stripe, the subscription status, the period and the number of billed members. Legal basis: performance of a contract, Art. 6(1)(b) GDPR, and statutory retention obligations, Art. 6(1)(c) GDPR.

Recipients and third parties

To track your flight we send the flight number and date to a flight data provider. Your email address or account identifier is not transmitted — the provider does not learn who is flying, only which flight is queried.

FlightAware AeroAPI / AeroDataBox
Flight data. Flight number and date are transmitted.
Google Firebase Cloud Messaging / Apple Push Notification service
Delivery of push notifications and lock-screen Live Activities. Push token and message content (flight number, status, times, and for alerts to a business's dispatch also the pickup note) are transmitted. Google LLC and Apple Inc. are certified under the EU-US Data Privacy Framework.
adsb.lol
Live aircraft position from an open community network (ODbL licence). Only the aircraft identifier is queried — no personal data.
Flightradar24
Second source for the live position when the open network does not receive an aircraft. Only the flight number is transmitted — no personal data.
AirLabs
Supplementary airport data such as gate and baggage belt. Flight number and airport code are transmitted.
Open-Meteo
Weather at the arrival airport. The airport's coordinates are queried — not yours.
Mapbox
Map rendering in the app. Loading map tiles transmits your IP address to Mapbox, Inc. (USA); Mapbox is certified under the EU-US Data Privacy Framework.
Stripe Payments Europe, Ltd., Dublin
Payment processing, invoices and customer portal for FlightPeek Business. Stripe processes the data partly on our behalf and partly under its own responsibility, for example for fraud prevention and statutory obligations for payment services. Transfers to Stripe, LLC in the USA rely on the EU-US Data Privacy Framework.
Compensair Ltd, London / Flightright GmbH, Berlin
Assessment and enforcement of compensation claims if you submit a claim in the app; with Flightright also the advance check of delayed flights without information about you (see above). The United Kingdom is covered by an adequacy decision of the European Commission.
Meta Platforms Ireland Ltd., Dublin
Measuring advertising success using hashed purchase reports (see above). Meta Platforms, Inc. in the USA is certified under the EU-US Data Privacy Framework.
RevenueCat
RevenueCat, Inc., USA: subscription management. Your account identifier, purchase data from the store, language, an app device identifier and, if available, email address and display name are transmitted. Transfer to the USA based on the EU Standard Contractual Clauses.
Email delivery service
Resend (Plus Five Five, Inc., USA): sending password reset and sign-in codes, invitations to a business, and alerts and the evening summary to dispatch. Transfer to the USA based on the EU Standard Contractual Clauses and the EU-US Data Privacy Framework.

Server location

Our servers are operated by Hetzner Online GmbH in Germany. The database, statistics (Matomo) and error reports (GlitchTip) are kept there — within the EU. The recipients listed above only receive what is described for each of them.

How long we store data

Account data
Until the account is deleted.
Raw responses from flight data providers
90 days, then deleted automatically.
Refresh tokens
7 days without use, 180 days for accounts without an email address; each use extends the period.
Password reset and sign-in codes
15 minutes.
Server logs
30 days.
Error reports
90 days.
Statistics
Individual visits for 180 days, then only aggregated figures without reference to any visit.
Data of a business
Until the end of the business contract, then at most 30 days. Billing records are kept for as long as tax and commercial law requires.
Compensation claim details
For as long as your account exists.

Providing an email address is voluntary; the app can still be used without one, just without an account across devices. For FlightPeek Business it is required to sign in. There is no automated decision-making within the meaning of Art. 22 GDPR.

Your rights

You have the right to access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and objection (Art. 21 GDPR). You can delete your account directly in the app, which also removes tracked flights, push tokens, compensation claim details and memberships in businesses. If you own a business with an active subscription, cancel it first; we delete the business's data 30 days after the contract ends. For anything else, an email to contact@kcraft.io is enough.

You also have the right to lodge a complaint with a supervisory authority. Ours is the Commissioner for Personal Data Protection of the Republic of Cyprus; you may also contact the authority in your country of residence.

This website

The public pages set no cookies and load no external fonts. Only when you sign in to the dashboard for businesses do we set two cookies that keep you signed in (at most 7 days) and cannot be read by scripts. Whether you want to see the site light or dark and which alerts you have already seen in the dashboard are remembered locally by your browser; this information never leaves your device. Both are strictly necessary for the function you requested, which is why there is no consent banner.

We count page views ourselves. No third-party service is involved, and the data does not leave our servers. We store: the page you opened, the language, the referring website (its name only, not your search query), the source and name of an advertising campaign if the link carries them, the country and whether you are on a phone, tablet or computer. We do not count pickup pages or the dashboard for businesses.

We do not store your IP address. We derive the country from it and then discard it. To tell visitors apart from page views we build a checksum from IP address, browser identifier and a secret value. It includes the current date, cannot be reversed and is different the next day. Anyone returning tomorrow counts as a new visitor.