Last updated: 2026-11-01
This document explains what data the app collects, why, and what I do (and don't do) with it. FlyFun Weather is a personal project — I'm a single developer, not a company. The entire codebase is open source so you can audit exactly what happens with your data.
When you sign in with Google, the server receives your email address and display name during sign-in. These are stored to identify your account.
When you sign in with Apple, Apple's Private Relay system is used. The server receives a private relay email address — I never see your real email unless you choose to share it. Your display name may also be provided depending on your Apple ID settings.
You can also sign in with just your email address: the app emails you a one-time sign-in link and code. To deliver and secure it, the server briefly stores your email address and the IP address of the request. These records are deleted automatically after 24 hours.
Like any web server, requests are logged with the requesting IP address, for security and troubleshooting.
If you submit feedback on a briefing, the comment and associated flight reference are stored.
If you donate, payment is handled entirely by Stripe — card details go straight to Stripe and never reach this server. The app records the donation (amount, currency, whether it is recurring, and Stripe's payment reference) linked to your account if you were signed in. Your account email is pre-filled on the Stripe checkout page unless you choose not to.
Briefings are shareable by direct link to any authenticated user of the app. If you share a briefing URL with another pilot, they can view it. This is intentional — the app is designed for a small trusted community of pilots. If you don't want a briefing to be viewable by others, you can mark flights as private.
Viewers see your display name (never your email). Your aircraft tail number, debriefs and trip notes are never shown to other users.
If you enable auto-refresh on a flight, the app will:
Your email is used solely for delivering these briefing notifications and account-related messages (welcome email, etc.).
I will never use your email for marketing, newsletters, promotions, or share it with any third party.
If you allow notifications in the iOS app, briefing updates are delivered through the Apple Push Notification service. The notification content — the route (e.g. “EGTF → LFAT”), the trip name for trip updates, and the new assessment — passes through Apple to reach your device. You can turn notifications off in the app or in iOS Settings.
If you allow notifications in the Android app, briefing updates are delivered through Google’s Firebase Cloud Messaging. The notification content — the route, the trip name for trip updates, and the new assessment — passes through Google to reach your device. You can turn notifications off in Android Settings or in your settings on the website.
You can choose to connect your FlyFun Weather account to an AI assistant such as ChatGPT or Claude. When you do, that assistant can read your flights and briefings and create or refresh flights on your behalf, using access you authorized. What the assistant then does with that data is governed by its provider's own privacy terms (OpenAI or Anthropic), under your account with them — not by this app. You can see and revoke connected assistants and API tokens from Settings.
If you use the Autorouter integration (for GRAMET cross-section data), the app uses a secure authorization process to connect to your Autorouter account. You are redirected to autorouter.aero to authorize access — your Autorouter password is never shared with or stored by this app.
After authorization, an access token (valid for approximately one year) is stored encrypted on the server. This token allows the app to fetch GRAMET data on your behalf. No username or password is stored.
You can disconnect your Autorouter account at any time from your settings, which removes the stored token.
Every briefing refresh logs:
This usage data serves two purposes:
There are no third-party analytics, no tracking pixels, no cookies beyond the authentication session cookie. I don't use Google Analytics or any similar service.
The app tracks the real cost of each briefing (AI usage, infrastructure share, storage) and makes this available publicly, so anyone can see what the app costs to run. You can also see your own usage and cost breakdown in the app.
The app interacts with these external services during normal operation:
| Service | Data Sent | Purpose |
|---|---|---|
| Open-Meteo | Coordinates, altitudes | Weather forecast data |
| Autorouter | Access token + route | GRAMET cross-section images |
| OpenAI / Anthropic | Weather + route context (airports, dates, positions); no account identifiers | AI-generated briefing summary |
| SMTP / Resend | Your email + briefing summary | Email delivery |
| Google / Apple | Sign-in tokens | Authentication (sign-in) |
| Stripe (only if you donate) | Your account email (unless you opt out), account id, amount; card details entered directly with Stripe | Payment processing |
| Apple Push Notification service (iOS, if enabled) | Device push token + notification text (route, trip name, assessment) | Briefing notifications |
| Google Firebase Cloud Messaging (Android, if enabled) | Device push token + notification text (route, trip name, assessment) | Briefing notifications |
| OpenStreetMap / Stadia Maps (map tiles) | Your browser loads map images directly from them, so they see your IP address and the map area displayed | Background map |
No account identifiers (your name or email) are sent to AI providers. The context that is sent describes the weather along your route — airports, dates and approximate positions.
You can download a complete, machine-readable (JSON) copy of the personal data held about your account — account details, preferences, flights, briefings, trips, followed flights, debriefs, aircraft, feedback, usage history, devices, API tokens and connected apps, and donations — at any time:
Encrypted credentials (e.g. your Autorouter token), token values and server-internal values are intentionally excluded for security.
You can delete your account and all associated data (flights, briefings, preferences, credentials) at any time:
This will permanently remove everything linked to your account and cannot be undone.
The complete source code is open source, so you can verify every claim on this page by reading the code yourself — or ask your favorite AI coding agent to review it for you. A more detailed technical breakdown of exactly where each of these practices lives in the code is in the project's PRIVACY.md. If you spot any issue, please raise a GitHub issue and I will address it.
If you have questions about your data or want to report a concern, reach out via the GitHub issue tracker.
If you believe your data may have been exposed, please report it privately using the “Report a vulnerability” button on the project's GitHub Security page (see SECURITY.md). If a breach affects your personal data and is likely to put you at high risk, you will be notified, and the relevant data-protection authority — in the UK, the ICO — will be informed as required by law.