Privacy Policy
Last updated: October 14, 2026
1. Data controller
Francesco Antonio Sessa
C. de Fray Ceferino González 9, 28005 Madrid, Spain
Tax ID (NIF): ESZ4443995D
Email: privacy@flightguard.app
2. Data collected
2.1 Data provided by the user
- Email address — collected only if the user activates an alert. Used exclusively to send notifications relating to the selected flight.
- Flight number and date — used to calculate the risk score. They are not personal data in themselves, but if linked to an email they form part of your alert subscription.
2.2 Data collected automatically
- IP address — used exclusively for rate limiting (max 5 requests/hour). It is not stored permanently: the counter expires after 1 hour.
- Navigation data — collected in anonymous, aggregated form via Umami Analytics (see Cookie Policy). Umami does not use cookies and does not track the user across sessions.
- Usage statistics (PostHog): pages viewed and actions on the site, in the app and in the dashboard for teams (for example starting a flight check or a free trial), with browser and device type and the country derived from the IP. The IP address is anonymized and not stored. Until you accept cookies, PostHog stores nothing on your device and your visits are not linked together; if you accept, a random identifier stored in a cookie links your visits (see the Cookie Policy). In the mobile app the identifier stays in memory only and resets at every launch.
- Session recording: only if you accept cookies, and only on the FlightGuard for teams page and in the dashboard for teams, PostHog records how the page is used (movements, clicks, scrolling) to find where the interface is unclear. Form fields are always masked, and in the dashboard all text is masked too, so travelers' data is not recorded.
- Ad measurement (Google Ads): only if you accept cookies, and only on the FlightGuard for teams page and in the dashboard for teams, the Google Ads tag records whether you came from one of our ads (click identifier, page, browser, IP address) and whether you then started a free trial or a subscription (with the plan value). We do not send Google your name, email or any traveler data.
- Interactions with alert emails — see section 7.
- Expo Push Token — if you use the mobile app (iOS/Android) and enable push notifications from the settings, we generate an anonymous device identifier via Expo (ExpoPushToken[...]). The token does not contain personal or contact data: it only serves to deliver push notifications to your specific device. It is associated with the alert email, the platform (iOS/Android) and the IANA timezone (e.g.
Europe/Rome) in order to respect quiet hours. Revocable at any time from the "Push notifications" toggle in the app settings.
3. Purposes of processing
- Calculation of the risk score for the requested flight
- Sending of email alerts (only if requested by the user)
- Rate limiting and security of the service
- Monitoring the status of the flights subject to alerts (delays/cancellations), also after the flight date, to improve the accuracy of the model
- Aggregated and anonymous analytics to improve the service
- Usage statistics and session recording (PostHog) to measure what works on the site, in the app and in the dashboard for teams
- Measuring the results of Google Ads campaigns for FlightGuard for teams (which ads lead to trials and subscriptions)
4. Legal basis
Processing is based on the user's consent (art. 6.1.a GDPR) for the alert subscription and the sending of emails, and on legitimate interest (art. 6.1.f GDPR) for rate limiting, security of the service and aggregated analytics, including PostHog statistics without cookies. PostHog statistics cookies (which link visits together) are based on your consent, which you can withdraw at any time from "Manage cookies". Google Ads measurement is also based on your consent (art. 6.1.a GDPR) and is withdrawn the same way.
5. Data retention
- Alert subscription (email + flight number + date) — retained as long as the alert is active and, in any case, no longer than 90 days after the flight date (to measure the flight outcome). It is deleted at any time at the user's request (see section 8).
- Operational record of the alert — retained in our key-value store for a maximum of 30 days from creation, with automatic expiry.
- Tracking of clicks on links in emails — linked to the alert ID, retained until the alert is deleted.
- Expo Push Token — retained as long as the device is active. It is immediately marked as revoked if: (a) the user disables notifications from the app; (b) the operating system reports the token as no longer valid (app uninstall, permission revocation); (c) the user requests it via email. Tokens revoked more than 30 days ago are deleted.
- Rate limiting — IP counter retained for 1 hour.
- PostHog usage statistics: events retained for 1 year, session recordings retained for 30 days. You can ask for their deletion at privacy@flightguard.app.
- Flight outcome (delay/cancellation) — objective data linked to the flight number and date, do not contain email or other personal identifiers; retained indefinitely for statistical analysis.
6. Sharing with third parties
Data is not sold and we do not share your email address or other contact data with third parties for direct marketing purposes. To provide the service we use the following data processors (art. 28 GDPR):
| Provider | Purpose | Location / Transfer |
|---|---|---|
| Cloudflare, Inc. | Hosting, CDN, database (D1), key-value store (KV) | EU (WEUR region) |
| Resend (Resend Technologies, Inc.) | Sending of alert emails (receives your email address and the content of the email) | United States — transfer covered by EU Standard Contractual Clauses |
| Anthropic PBC | Generation of the natural-language explanation of the risk score (receives flight number, date, score and aggregated data on the risk signals — not the email address) | United States — transfer covered by EU Standard Contractual Clauses |
| Umami Analytics (self-hosted) | Anonymous traffic analysis, without cookies or persistent user identifiers | EU (servers managed directly by the controller) |
| PostHog Inc. | Usage statistics for the site, the app and the dashboard for teams; session recording only on the pages for teams (receives navigation events, device type and the IP, which is anonymized; for business customers the user ID and company ID, not name or email) | EU (Frankfurt, Germany) |
| Expo (650 Industries, Inc.) | Push notification service (receives your device token, the iOS/Android platform, and the text of the notification — not the email address). The token is an anonymous device identifier. | United States — transfer covered by EU Standard Contractual Clauses |
| Apple Inc. (APNs) and Google LLC (FCM) | Native OS channels for delivering push notifications: Expo forwards the already-prepared content to the respective system channel. They do not introduce new processors beyond those already covered by the use of iOS/Android. | United States — covered by the iOS/Android terms |
FlightAware is used as a public source of flight information (flight number, schedules, status): it receives no personal data of the user.
With your consent to marketing cookies, the affiliate partner Travelpayouts (independent data controller) may collect data via third-party cookies for affiliate conversion attribution and remarketing. This processing takes place only with prior consent and is governed by the Travelpayouts privacy policy; see also the Cookie Policy.
With your consent to cookies, on the business pages Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland) receives the Google Ads measurement data described in section 2 and processes it to measure conversions under the Google Ads Controller-Controller Data Protection Terms. The data may be transferred to Google LLC in the United States, a transfer covered by the EU-U.S. Data Privacy Framework and the Standard Contractual Clauses. The tag does not use the data for personalized ads (ad_personalization off). Google's notice: Google, privacy and ads.
7. Tracking of alert emails
The alert emails sent by FlightGuard contain:
- Open-tracking pixel — an invisible image served from our domain (
/pixel) that tells us when the email is opened. The event is recorded in aggregated, anonymous form via Umami, without permanently storing the IP address. - Tracked redirect links (
/r/<slug>) — the links in the emails go through an endpoint that records the click, linking it to your alert ID, in order to measure which content is useful. The click log is deleted together with the alert. - UTM parameters — the links to the site contain parameters
utm_source=flightguard&utm_medium=emailto identify the traffic channel in aggregated analytics.
To disable tracking you can delete the alert (see section 8): the deletion also removes all the associated click history.
8. User rights
Pursuant to articles 15-22 of the GDPR you have the right to:
- Access your data
- Request its rectification or deletion
- Restrict or object to the processing
- Request portability
- Withdraw consent at any time
- Lodge a complaint with a supervisory authority: the Spanish Data Protection Agency (AEPD), competent for the controller, or the authority of the EU country where you live
Deletion via the "cancel alert" link present in every email, or via the DELETE /api/alerts/:id endpoint, immediately removes the email, the alert record and the associated click history from all our archives (KV and D1). For any other request, write to privacy@flightguard.app: we respond within 30 days.
9. Cookies
See our Cookie Policy for information on the cookies used.
Business customers (FlightGuard for teams)
When a company uses FlightGuard for teams, the company is the controller of its travelers' data (name, work email, flights) and FlightGuard processes it on the company's behalf as processor. This data is stored separately from the consumer service, is used only to monitor the trips and send the alerts the company configured, and is not used for marketing or affiliate offers. Payments are handled by Stripe, which receives the billing details of the company.
To improve the dashboard, FlightGuard records with PostHog how the company's users use it (for example sign-in, travelers added, alerts sent), linking events to the user ID and the company ID, without name or email. Session recording in the dashboard, active only with cookie consent, masks all text and form fields. Technical events sent by our server (for example an alert being sent) do not use cookies.
10. Changes
We publish changes to this policy on this page by updating the date at the top. For substantial changes, we will inform subscribed users by email.