Skip to content

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

2.2 Data collected automatically

3. Purposes of processing

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

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):

ProviderPurposeLocation / 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:

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:

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.