Privacy Policy
FlightScore — iOS, Apple Watch, Android, and Web
Version 2026.10.1 · Effective date: October 1, 2026 · Last updated: October 1, 2026
This Privacy Policy explains how Monsoro, LLC, a South Carolina limited liability company ("Monsoro," "we," "us," or "our"), collects, uses, and shares information when you use FlightScore, our flight-planning and preflight risk-briefing app and website (the "Service"). FlightScore is a product brand of Monsoro, LLC. The paid tier is called FlightScore Pro.
1. Information we collect
The table lists categories the Service actually handles. "Source" is who provides it or which device permission starts it.
| Data | Purpose | Source |
|---|---|---|
| Email address, password (handled by our authentication provider; we do not see it in plain text), optional display name, and a user ID | Create and protect your account, sync your data, and send service email | You. If you use Sign in with Apple or Google, those providers share an identifier and the name or email they are configured to send. |
| Trips (airports, route, time, flight rules, alternates, persons on board, fuel and NavLog fields, remarks), aircraft (model, registration, performance, weight and balance, maintenance dates), pilot profile and logbook (certificates, ratings, endorsements, times, landings, approaches, instructor sign-offs, personal minimums), notes, scratch pad and ink, checklists, and documents you upload | Plan flights, briefings, logbook, and sync across devices | You |
| Precise location, including while a cockpit or FlightScore Live session you started is running in the background | Nearby airports, local weather, your position, and a recorded track | Your device, after you allow location |
| FlightScore Live: pilot name, flight legs, score, and position track (latitude, longitude, altitude, speed, heading, and status text) while the session is active | Show the live link you created to whoever has it | You, when you start a Live session |
| Shared briefing content | Show a briefing link until it expires or you revoke it | You, when you create a share link |
| Microphone and on-device speech (airport codes, checklist voice, and, on iOS, ATC transcription). Optional readback clips are a rolling buffer of about 12 seconds kept on the device. | Voice input and optional local readback export | Your device, after you allow the microphone. We do not upload raw audio unless you choose to export or share a clip. |
| Apple Watch blood-oxygen (SpO2), only if you turn that Watch feature on | Show a reading on your Watch for awareness. It is not used in the risk score and it is not medical advice. | Apple Health on the Watch. The reading stays on the device. We do not send it to our servers. |
| Subscription status, product, store, renewal and expiration dates, and whether signup access is active. Not your full payment card number. | Turn FlightScore Pro on or off and restore purchases | Apple App Store, Google Play, RevenueCat, and Stripe (web checkout). The card number stays with the store or Stripe. |
| Crash reports, error logs, masked session-replay snapshots, and your user ID (not your email) on web | Find and fix crashes | The app, via Sentry. Replays mask text and block media. They are captured on web errors and on a sample of web sessions. |
| Web performance traces (timing, page metrics, device and browser data) and your user ID when you are signed in | Measure web performance | The website, via Honeycomb / OpenTelemetry. This is web-only. |
| Pages viewed on the website, IP address, and user agent | Host the site and measure aggregate page views | Your browser, via Vercel (hosting, CDN, and Vercel Web Analytics) |
| Push notification token and notification preferences | Deliver notifications you enable | Your device, via Apple Push Notification service, Firebase Cloud Messaging, or the browser's web push service |
| Settings, recent routes, and cached weather or offline packs stored on the device | Remember preferences and work offline | Your device |
Some features run on the device only (on-device speech and models, the optional audio clip, and Watch SpO2). Those inputs are not sent to us unless a feature you choose explicitly uploads or shares a file.
2. How we use information
- Provide the Service: plan trips, compute risk scores and briefings, sync your data, and keep your logbook.
- Generate AI-assisted briefings and answers (Section 3).
- Authenticate you and protect accounts.
- Manage FlightScore Pro and free-tier limits.
- Send service emails (sign-up confirmation, password reset, account deletion, and subscription notices) and push notifications you enable.
- Diagnose crashes, fix bugs, and measure performance.
- Comply with law and enforce our Terms.
We do not sell your personal information. We do not share it for cross-context behavioral advertising. The Service does not include an advertising SDK. Vercel Web Analytics counts pages on our own site. It is not used to advertise to you on other sites.
3. Service providers
We share information with providers that help us run the Service, under their own terms. Airport and route queries below do not include your name or email.
| Provider | Purpose | Data involved |
|---|---|---|
| Supabase | Database, authentication, file storage, server functions | Account data and the content you save |
| Apple (Sign in with Apple, App Store, Apple Push Notification service) | Sign-in, purchases, and push on Apple devices | Sign-in identifier, purchase records, push token |
| Google (Sign-In, Google Play, Firebase Cloud Messaging) | Sign-in, purchases, and push on Android | Sign-in identifier, purchase records, push token |
| Browser web push | Web notifications you enable | Push subscription endpoint |
| RevenueCat | Subscription status and the FlightScore Pro entitlement | App user ID, purchase receipts or transactions, subscription status |
| Stripe (via RevenueCat Web Billing) | Web subscription payments, if you subscribe on the web | Payment details (handled by Stripe, not stored by us) and email |
| Google Gemini API | AI briefing text, summaries, and Ask features, called from our server | Route, airport, and weather text, your personal minimums and aircraft details, and the questions or document excerpts you submit. We do not add your account name or email to those prompts. A file sent for extraction is labeled with the file's name. |
| Sentry | Crash and error reporting | Stack traces, device and OS data, masked replays, user ID |
| Honeycomb | Web performance tracing | Request timing, page metrics, device and browser data, user ID when signed in |
| Vercel | Website hosting, CDN, and Web Analytics | IP address, user agent, pages viewed |
| Resend | Transactional email | Email address and the content of that email |
| Aviation Weather Center, National Weather Service (api.weather.gov), FAA NOTAM, TFR, NAS Status, procedure-chart, and CIFP services, CheckWX, NOAA Storm Prediction Center, Iowa Environmental Mesonet | Weather, NOTAM, TFR, airport status, charts, and model guidance | Airport or station identifiers, route coordinates, or a public product download. These calls do not include your name or email. |
| Leidos (1800wxbrief) | Optional official preflight briefing, when you request one | Departure, destination, route, the optional ICAO flight plan, and the optional 1800wxbrief username you enter |
| AirNav | Fuel prices at an airport | Airport identifier only |
| OpenAIP | Optional airport enrichment if you save an OpenAIP key on the device | Airport identifier and the key you stored locally |
| Open-Meteo | Winds and model data along a route | Coordinates |
| OpenSky Network | Nearby aircraft traffic on the map | A bounding box around the map position |
| Esri / ArcGIS Online | Street basemap and VFR/IFR chart tiles | Tile requests (IP address and user agent) |
| Windy.com | Embedded wind map | Map center coordinates |
| OurAirports | Public airport reference data | The download request itself (IP address) |
We may also disclose information if required by law, to protect rights and safety, or as part of a merger, acquisition, or sale of assets. This policy still describes that information.
4. Retention
We keep account, trip, aircraft, logbook, document, checklist, and settings records while your account is active. When you delete your account, that deletion request removes those records from our database and then deletes the login. Shared briefing rows are tied to the account and are removed with it. They also expire on their own: a new link lasts 14 days unless you revoke it sooner, and a scheduled job deletes an expired link the day after it expires, or seven days after you revoke it.
A new FlightScore Live link expires 24 hours after you create it. Renewing it starts another 24 hours. Anyone with the link can view the session, including position, until that expiry. After it expires, the link can still show that it has expired, and the position is not included. There is no public listing of other pilots' sessions. Live position rows and the session row stay with your account until you delete the account. The database includes a daily job that deletes position rows for sessions whose link expired more than 30 days earlier. That job is created only when the database scheduler is available, and it does not delete the session row. Push-notification watch rows, which store a push token for a trip, are deleted about two hours after the planned departure and also when you delete the account.
First-party product telemetry is deleted on a schedule. Sampled client HTTP and performance events (client_telemetry_events) are deleted after 30 days. Trip score-change history (trip_score_events) is deleted after 90 days. Those daily jobs are created only when the database scheduler is available. Deleting the account also removes trip score-change rows, because they are tied to the account.
Information that stays only on your device (caches, the optional audio clip, and Watch SpO2) remains until you clear it, turn the feature off, or remove the app. Crash logs, store purchase records, and email-delivery logs are kept by those providers under their own schedules. Our product code does not set a day count for database backups or for those providers.
5. Your choices and rights
In the app. You can access and correct the flights, aircraft, and logbook entries you saved, and export trips, logbook, and aircraft data in the formats the app offers (including JSON, CSV, and GPX where that export exists). You can turn off location, microphone, Health, and notifications in the device settings.
Delete your account.
- Web, and Android (the site or the Android shell, which uses the same Settings screen): Settings → Account → Delete Account & All Data → Yes, Delete.
- iPhone and iPad: Settings → Delete Account → Confirm delete account.
If the session token is more than five minutes old, the deletion request asks you to sign in again and retry. That check is in the deletion service. You can also email support@monsoro.co and ask us to delete the account. Deleting the app does not delete the account. Deleting the account does not cancel an App Store or Google Play subscription.
US state privacy laws. Depending on where you live, including California (CPRA), Virginia, Colorado, Connecticut, Utah, and other states with a consumer privacy law, you may have the right to know, access, correct, and delete personal information, and to appeal a denial. We do not sell personal information and we do not share it for cross-context behavioral advertising. Email support@monsoro.co. We will respond within 45 days, unless the law gives us a permitted extension, in which case we will tell you.
GDPR and UK GDPR. If those laws apply, you may have the right to access, correct, delete, and port your personal information, to object to or restrict certain processing, to withdraw consent where we rely on consent, and to lodge a complaint with a supervisory authority. Email support@monsoro.co. We will respond within one month, unless the law allows more time, in which case we will tell you.
We will not discriminate against you for exercising these rights. We may need to verify that the request comes from you.
6. Children's privacy
FlightScore is a general-audience app, not a social app, and is not directed to children under 13. We do not knowingly collect personal information from children under 13. If a parent or guardian believes a child under 13 has provided us personal information, they can email support@monsoro.co and we will delete it.
7. Security
Data is sent over HTTPS/TLS. Our database uses row-level security so each account can access only its own records. No system is perfectly secure, and we cannot guarantee absolute security.
8. International users
We are based in the United States. Our providers may process data in the United States and other countries. Those countries may have different data-protection laws than yours.
9. Changes
We may update this policy. We will change the version and the effective date at the top. For a material change, we will also give notice in the app or by email. The date on this page is the date that version took effect.
10. AI assistant connectors
If you connect an assistant such as Grok, ChatGPT, Claude, or Cursor, FlightScore can send that assistant the flights, times, and aircraft you ask about, basic aircraft details from your hangar, your personal minimums, and the weather, risk band, and reasons for that request. We do not send your email, phone number, logbook, documents, payment details, location history, or certificates through the connector.
The purpose is to answer the question you asked in that assistant. The assistant's provider handles what it receives under its own terms. FlightScore does not sell this information and does not use it to train a model. You can disconnect an assistant in Settings. Disconnecting stops new access right away. We keep daily usage counts and an activity log of creates, changes, and deletes for 400 days. Deleting your account deletes those rows.
The connector is a FlightScore Pro feature. It is decision support only. It is not an official briefing, and it cannot file a flight plan.
11. Contact
Monsoro, LLC (South Carolina) — FlightScore
Monsoro, LLC, 1726 Gold Hill Rd Unit #564, Fort Mill, SC 29708
Email: support@monsoro.co
See also: Terms of Service · End User License Agreement · Aviation Disclaimer