91 Dispatcher — Privacy Policy

Effective date: March 18, 2026

Last updated: March 18, 2026

1. Introduction

91 Dispatcher ("we," "us," "our") provides a preflight decision-support tool for general aviation pilots ("the Service"). This Privacy Policy describes how we collect, use, store, and protect your personal information when you use the Service.

By creating an account, you consent to the data practices described in this policy.

2. Information We Collect

2.1 Account Information

Email address (used for authentication and communication)
Name (displayed on briefs and your profile)
Password (stored as a salted hash by AWS Cognito — we never see or store your plaintext password)

2.2 Pilot Profile Data

Certificate type (Student, PPL, CPL, ATP)
Ratings (Instrument, Multi-Engine, CFI, CFII)
Home airport
Total flight hours and IFR hours
Personal minimums (ceiling, visibility, crosswind limits, custom rules)

2.3 Aircraft Records

Tail numbers and aircraft type
Avionics configuration, equipment, and performance data
Maintenance notes and squawks
Ownership type

2.4 Flight Records

Flight dates, departure and destination airports, routes
Flight times (total, PIC, SIC, instrument, cross-country, night)
Approach counts and types
Landing counts (day and night)
GPS track data (KML files uploaded by you)

2.5 Dispatch Briefs

Route and departure time inputs
Weather data retrieved at brief time (METARs, TAFs, SIGMETs, PIREPs)
Risk assessment results and verdicts
Brief acknowledgment timestamps

2.6 Usage Analytics

Pages visited, features used, session duration
Device type and browser (no IP address stored)
Collected via PostHog (see Section 5)

2.7 Information We Do NOT Collect

Payment information (handled entirely by Stripe — see Section 5)
Government-issued identification
Social Security numbers
Precise real-time location (GPS tracks are uploaded by you after flights, not tracked live)

3. How We Use Your Information

We use your data to:

| Purpose | Data used |

|---|---|

| Generate dispatch briefs | Pilot profile, aircraft data, flight history, personal minimums |

| Compute currency and proficiency | Flight records (approaches, landings, hours) |

| Provide risk assessments | All pilot, aircraft, and flight data combined with weather |

| Display your logbook and statistics | Flight records |

| Render flight replays | KML GPS tracks |

| Send operational notifications | Email address (brief confirmations, stale brief warnings) |

| Improve the product | Anonymized usage analytics, aggregated brief quality metrics |

We do not use your data to:

Target advertising (we have no ads)
Build marketing profiles
Share with insurance companies, the FAA, or any regulatory body
Sell to third parties

4. Data Storage and Security

4.1 Infrastructure

All data is stored in Amazon Web Services (AWS) in the US East (N. Virginia) region:

Authentication: AWS Cognito (encrypted at rest, SOC 2 compliant)
Database: Amazon DynamoDB (encrypted at rest with AWS-managed keys)
File storage: Amazon S3 (encrypted at rest, private by default)

4.2 Access Controls

Your pilot profile, flight records, and aircraft data are owner-scoped — only you can read or modify them via the API
Shared reference data (airports, approach procedures, waypoints) is read-only for all authenticated users
Administrative access is limited to the development team and requires multi-factor authentication

4.3 Data in Transit

All data transmitted between your browser and our servers is encrypted via TLS 1.2+. API calls to third-party weather services are made server-side (never from your browser).

5. Third-Party Services

We use the following third-party services. Each processes limited data as described:

|---|---|---|---|

| Anthropic (Claude API) | AI-powered brief narratives and risk summaries | Brief context (weather, pilot profile, route — no raw flight tracks or PII beyond name) | Not retained by Anthropic per their API data usage policy |

| Aviation Weather Center (aviationweather.gov) | Weather data — METARs, TAFs, SIGMETs, PIREPs, winds aloft | Airport ICAO codes and route corridors (no PII) | Not applicable (public government API) |

We do not sell, rent, or trade your personal information to any third party.

6. Data Retention

| Data type | Retention period |

|---|---|

| Account and profile | Until you delete your account |

| Flight records | Until you delete individual records or your account |

| KML GPS tracks | Until you delete individual tracks or your account |

| Dispatch briefs | Until you delete individual briefs or your account |

| Usage analytics | 12 months from collection |

6.1 Account Deletion

You can delete your account from inside the app — **Pilot → Profile → Danger

Zone → Delete account** — or by contacting us at privacy@91dispatcher.ai.

Deletion is irreversible and there is no recovery window.

Destroyed permanently:

Your Cognito login
Your pilot profile and public profile
Your notification contacts, and the delivery logs naming them
Your tracked flights, including recorded positions
Your in-app notifications
Your SMS and WhatsApp messages with us
Every S3 object you own: GPS tracks, video, and cockpit audio

Kept, with your identity removed: your flights, aircraft, dispatch briefs,

trips, drill history, feedback and subscription record are reassigned to an

anonymous identifier that is not linked to you and cannot be reversed to reach

you. We keep these to understand how the product is used in aggregate. On the

way through we also remove the details that would make them identifiable

anyway — specifically the narrative text of your briefs, which contains your

name.

We do not remove aircraft tail numbers from this retained data. Tail

numbers are broadcast publicly over ADS-B and listed in the public FAA

registry, so removing ours would not conceal anything, and keeping them lets us

report on the aircraft types pilots actually fly. If your aircraft is enrolled

in the FAA's Limiting Aircraft Data Displayed (LADD) programme and you would

like its tail number removed as well, tell us at privacy@91dispatcher.ai.

If you would prefer this data destroyed rather than anonymised, say so at

privacy@91dispatcher.ai and we will remove it.

One limitation, stated plainly: if you have an active paid subscription,

the app will refuse to delete your account and ask you to cancel your

subscription first. This is deliberate — deleting the account while billing

continued would leave you with nothing to cancel it with.

7. Your Rights

You have the right to:

Access your data — all your data is visible in the app (profile, logbook, briefs)
Export your data — flight records can be exported; brief JSON is available via the API
Correct your data — edit your profile, aircraft, and flight records at any time
Delete your data — delete individual records in the app, or request full account deletion
Withdraw consent — stop using the Service at any time; request account deletion

If you are a resident of the European Economic Area (EEA), you may also have rights under GDPR including the right to data portability and the right to lodge a complaint with a supervisory authority.

If you are a California resident, you have rights under the CCPA including the right to know what personal information is collected and the right to opt out of the sale of personal information. We do not sell personal information.

8. Cookies and Tracking

The Service uses:

Authentication cookies — session tokens set by AWS Cognito to maintain your login state (strictly necessary, no consent required)
PostHog analytics — first-party JavaScript tracking for product usage analytics (no advertising cookies)

We do not use third-party advertising cookies or tracking pixels.

9. Children's Privacy

The Service is not intended for use by anyone under 16 years of age. We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, contact us at privacy@91dispatcher.ai and we will delete it.

10. Beta Program

During the beta period:

The Service is provided as-is with no uptime or data durability guarantees
Data loss may occur due to infrastructure changes, schema migrations, or bugs
We will make reasonable efforts to preserve your data but cannot guarantee it
This Privacy Policy may be updated more frequently during beta as features change

11. Changes to This Policy

We may update this Privacy Policy as the Service evolves. Material changes will be communicated via email or in-app notification at least 14 days before taking effect. Continued use of the Service after changes constitutes acceptance.

The "Last updated" date at the top of this document indicates the most recent revision.

12. Contact

For questions, data requests, or concerns about this Privacy Policy:

Email: privacy@91dispatcher.ai

*By creating an account, you acknowledge that you have read and understood this Privacy Policy.*