Privacy Policy

Effective date: October 11, 2026

61Insights ("we", "us", or "our") operates the 61Insights flight training platform available at app.61insights.com. This policy explains what data we collect, how we use it, and your rights regarding that data.

1. Information We Collect

We collect information necessary to provide the service:

• Account information — your name and email address, provided through our identity provider (Auth0) when you sign up or sign in.
• Flight and training records — flight logs, approach analysis results, task grades, and notes that you or your instructor enter into the platform.
• Uploaded files — KML track files you upload for approach analysis. These are processed server-side and stored associated with your account.
• Flight track location — when you start recording a flight in the 61Insights mobile app, we collect precise GPS location for the duration of that flight. Recording begins only when you tap “Engine start” and ends when you tap “Shutdown”, and a notification is shown on your device for as long as it is running. The track is stored with the flight record it belongs to and is used to draw your flight path and to score maneuvers and instrument approaches against ACS standards. We do not track your location at any other time, and the app does not request background location access.
• Engine instrument photos — if you photograph the Hobbs or tach gauge to record engine times, that photo is stored with the flight record. Photos are re-encoded on your device before they are uploaded, which removes embedded metadata including any location tag the camera recorded.
• Flight review date — if you choose to enter it, the date of your last flight review (14 CFR 61.56), which you type yourself on your Profile page. We use it only to show when your next one is due and to remind you in the app (and, if you allow them, by push notification) before it is due and the day after it. Only you can see it: it is never shown to your instructor, your school or anyone else, and it is deleted when your account is deleted, at the end of the 30-day window. Clearing it stops the reminders.
• Notifications — the in-app notifications we record for you, whether you have opened them, and your notification preferences. See section 2.
• Nudge history — if you or your school turn on encouragement to keep training, a record of each note we send you (which kind, and when), whether you opened it, whether it was also sent as a push, which school it came from, whether you muted that kind afterwards, and whether you trained again in the 14 days after (for a reminder, booking a lesson counts too). We use it to measure whether these notes actually help, and to send at most one a week. At a school, your instructors, flight operations and administrators see your most recent note and whether you came back, along with when it was sent and whether you opened it, in the At-risk view of their Roster Progress; for a self-serve pilot, nobody else sees it. See section 2.
• Device token — if you allow notifications in the 61Insights Android app, a push token for each phone you use it on (at most five). It identifies the phone to Google Firebase Cloud Messaging so we can deliver push notifications to it. We store the token, the platform (Android), the app version, and when it was registered and last used. See section 2.
• School billing (school administrators) — if your school subscribes to 61Insights, the school's name and the billing contact email address it gives us, the state of its subscription (for example active, payment failed, or on the Flight School of One plan), the number of members holding the instructor role each month and the number of administrators beyond the first 10 (the figures the school's bill is calculated from), and its invoices. Card and bank details are entered on Stripe's own pages and held by Stripe: we never see or store them. We show the card brand and last four digits on the school's Billing page, read from Stripe when the page is opened; we do not store them. Students' and instructors' training records are never sent to Stripe. See section 2.
• Training gaps and completion estimates — your instructor or school administrator (or you, if you train on your own) may record a break in your training with its dates, a category (weather, illness or maintenance) and an optional short note. We use these, with your flight records and engine times, to estimate how many more flights and hours you are likely to need before you are ready for your practical test. The category “illness” records only that training paused; please do not put medical details in the note. See section 5.
• Google Drive (self-serve pilots, optional) — if you train on your own, you may choose to keep your flight tracks in your own Google Drive. See section 4.
• Beta AI assistant connector (optional) — if you connect an AI assistant such as Claude or ChatGPT to your 61Insights account, the sign-in and connection records that let it act as you, and the lesson-plan previews it prepares. See section 6.
• Usage data — standard server logs including IP addresses, browser type, and pages visited, used for security and debugging.

We do not collect or store payment card or bank details: when a school pays by card, Stripe collects and holds them. Outside of a flight you are actively recording, and of track files you choose to upload, we do not collect location data.

2. How We Use Your Information

• To operate and deliver the 61Insights service — storing and displaying your flight records, computing approach scores, and tracking progress against your syllabus.
• To share your training records with instructors and flight school administrators at the school (tenant) you are enrolled in, consistent with the purpose of the platform.
• To send email. Invitations to join a school, and the daily digest (on by default; turn it off on your Profile page) of what needs you, are sent by 61Insights through Amazon SES (part of Amazon Web Services). Sign-in, email verification and password emails come from Auth0. You can also turn the digest off with the unsubscribe link in every digest.
• To show you in-app notifications about your training, or your students' training — a lesson plan to review, a flight ready for your self-assessment, a reply on a lesson plan — and, once you have entered your flight review date, a reminder in the app before it is due and the day after. Notifications and digests to instructors and school staff about their students include the student's name. These are not marketing. You can mute any kind of notification, turn the daily digest off, or clear your flight review date on your Profile page.
• To send encouragement to keep training — a note in the app when your training stalls (no lesson in a while, or nothing booked after your last one) or when you reach a milestone (a syllabus stage, a task flown to standard for the first time, being ready for your practical test, a lesson count). Only when you turn it on, or your school turns it on for its students (you can still turn it off). At most one a week (a further milestone reached in the same week is still shown in the app, but is never sent as a push). These are not marketing. You can turn encouragement off, or mute any kind of it, in Notification preferences on your Profile page.
• To send push notifications to your phone, once you have allowed them in the Android app: the same encouragement and your flight review reminders, held until 8:00 your time if they would arrive between 21:00 and 8:00. A push may name your school (if you are a school student), a syllabus stage or task, a lesson count or a due date. It never includes a numeric grade or score, a comment, or other people's names; a milestone may say that you flew a named task to standard, finished a stage, or are ready for your practical test. A milestone may show on your lock screen; a reminder's text is hidden on the lock screen. You can turn push off with the Push notifications (all your phones) switch in Notification preferences, which turns push off on every phone you use, or for the 61Insights app in your phone's Android settings.
• To bill schools that subscribe. We send Stripe the school's name, its billing contact email, an internal school identifier and, each month, the highest number of members who held the instructor role and of administrators beyond the first 10 (the school is billed per instructor and per administrator beyond the first 10, on those monthly peaks). We use the school's billing status to decide which features the school has; see the School Subscription and Software License Agreement. Invoices, receipts and payment emails come from Stripe to the billing contact. We never use billing information for advertising.
• To diagnose bugs and improve reliability using server logs and error reports.

We do not sell your personal data. We do not use your data for advertising.

3. Data Sharing

Your training data is visible to:

• You
• Instructors assigned to you at your flight school
• Flight operations administrators and tenant administrators at your flight school

We use the following third-party services to operate the platform:

• Auth0 — authentication and identity management
• MongoDB Atlas — primary database hosting
• Amazon Web Services — cloud infrastructure, and email delivery (Amazon SES) for invitations and the daily digest
• Sentry — error and crash reporting. Reports identify you only by an internal account identifier; we do not send your name or email address to Sentry.
• Stripe — payment processing and invoicing for schools that subscribe. It receives the school's name, its billing contact email, an internal school identifier, the monthly counts of members holding the instructor role and of administrators beyond the first 10, and the school's payment method, which Stripe holds and we never see. Stripe keeps its own records as its privacy policy describes.
• LaunchDarkly — feature flag delivery, keyed on the same internal identifier.
• Google Firebase Cloud Messaging — delivers push notifications, which may include a short description of a training reminder or milestone. It receives your phone's push token; the notification's words (its title and body, which may end with your school's name); its type (for example, flight review due or overdue); its in-app link; the delivery channel and lock-screen setting; a one-way hash used to avoid duplicate notifications; and internal identifiers (a notification id and a school id). Google also sees the phone's connection to its messaging service, as the Firebase software in the app does. It never receives your email address or a numeric grade or score.
• Google — only if you choose to connect Google Drive, as described in section 4.
• Amazon Bedrock (part of Amazon Web Services) — runs an AI model (Anthropic's Claude) inside our own AWS account to draft lesson plans and to write the short insight that compares a student's self-assessments with the instructor's grades. For a lesson-plan draft it receives the student's name, course and syllabus position, the candidate lessons and tasks, the task grades of recent flights, the student's stated objective and the lesson plan's discussion. For the insight it receives only the dates, confidence, task names, answers and S/U grades of the student's last few self-assessed flights, with no name.

Each of these processors is bound by data processing agreements consistent with applicable privacy law. We do not share your data with any other third parties except as required by law, or at your direction: if you connect an AI assistant of your own, it receives what it asks for on your behalf, as described in section 6. That provider is a third party you choose, not a processor we engage.

4. Google Drive and Google User Data

This section applies only to self-serve pilots who choose to connect Google Drive. School students' tracks are stored by 61Insights as described elsewhere in this policy.

• What we ask for. We request a single Google permission, drive.file. It lets 61Insights create files in your Drive and open only the files 61Insights created. It does not let us see, read or change any other file in your Drive.
• What we do with it. We use this access only to save your flight track files to your Drive and to read them back so the app can show you your flights. We do not use it for anything else.
• Where your Google access lives. You grant access in your browser, and the access token stays on your device. Our servers never receive or store a Google access token or refresh token.
• Temporary copy while a track is transferred. Our server prepares each track file and keeps it in encrypted storage for up to 7 days so your browser can transfer it to your Drive. That temporary copy is deleted as soon as the transfer is confirmed, or after 7 days, whichever comes first. We keep a summary of each flight (the maneuvers and their results, not the track) as part of your training record.
• Your files are yours. Files in your Drive belong to you. Deleting or disconnecting your 61Insights account does not delete them. You can disconnect Google Drive at any time in the app, or revoke access from your Google Account permissions page.
• Optional shared copy, off by default. Separately, you may choose to share a copy of each new track for 30 days to help us improve the flight analyzer. The copy does not contain your name, email address, device name or tail number. It does contain positions and times, and a track usually starts and ends at your home airport, so it is not fully anonymous. It is stored encrypted and deleted after 30 days. Turning this option off deletes every copy we still hold. Deleting your account deletes them too.

61Insights' use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not sell data obtained through Google APIs. We do not use it for advertising. We do not use it to develop, improve or train generalized artificial intelligence or machine learning models. No person at 61Insights reads it unless you ask us to, it is needed for security or to comply with the law, or it has been aggregated and made anonymous.

5. Training Gaps and Completion Estimates

Completion estimates are shown to instructors and school administrators, and to self-serve pilots for their own training. A school student does not see an estimate or any recorded training gaps. An estimate is a projection from your recorded training, not an assessment of you, and it is never shared outside your school (for a self-serve pilot, with anyone else). Recorded training gaps, and the snapshots we keep to check how accurate our estimates are, are deleted automatically 12 months after your last training activity, or 12 months after you are judged ready for your practical test, whichever comes first.

Instructors, flight operations and administrators also see an At-risk view in Roster Progress: the days since each student's last lesson and, for a student on a recorded break, only that it is a break, its category and its end date, never the note. A school student does not see this view of their own record.

6. AI Assistants (Beta Connector and Plugin)

61Insights offers a beta connector that lets you use an AI assistant of your own choosing, such as Claude (made by Anthropic) or ChatGPT (made by OpenAI), with your 61Insights account. It uses the Model Context Protocol (MCP) at mcp.61insights.com. Using it is optional: nothing reaches an AI assistant unless you connect one yourself, and during the beta access is turned on per account.

• Signing in and permissions. You connect from your assistant and sign in to 61Insights in your browser with your usual login (OAuth). A consent screen lists what the assistant is asking for: reading training records, reading your school's operational or people analytics (useful only if your role already shows them), and, where lesson planning has been turned on for your account, creating, editing and approving lesson plans. Each session lasts at most 5 minutes. We issue no long-lived or refresh credentials, so your assistant has to sign you in again after that.
• The same permissions as the web app. The assistant acts as you. Every request goes through the same checks as the web app: your current school memberships, your role and your assigned students. It can see only what you can already see in 61Insights, and removing you from a school takes effect on the next request. So an instructor or administrator who connects an assistant can make the records of the students they can see available to it: names, courses, progress, grades, flights, analyzer results, lesson plans and their messages, and each student's email address as the web roster already shows it to them. Schools and instructors decide whether to use an AI assistant with student records, choose one they are comfortable with, and are responsible for telling their students.
• Your AI provider receives what the assistant asks for. The answers 61Insights gives your assistant are sent to the AI provider you chose. From then on they are handled under your agreement with that provider and its privacy policy, for example Anthropic's privacy policy or OpenAI's privacy policy. That provider is a third party you (or your school) choose, not a processor we engage: we do not control what it keeps, for how long, or whether it uses conversations to improve its models. Its settings and terms differ between personal plans and business or enterprise plans, so check the plan you or your school use.
• Changes only after your yes. The only changes an assistant can make are to lesson plans, and only where lesson planning has been turned on for your account. Each change is first shown to you as a preview. It is saved only after you explicitly confirm that preview; if you say no, it is discarded. A saved change becomes part of the training record like any other lesson plan.
• Temporary previews. A preview is stored encrypted while it waits for your answer and expires after 15 minutes. Once you confirm a change, an encrypted record of it is kept for 24 hours, so that a repeated confirmation is not saved twice, and is then deleted automatically.
• Connection records, logs and limits. Sign-in and connection records for the connector are stored encrypted, apart from training records, and expire within minutes of the session ending; an assistant's registration with the connector expires after 7 days. To protect the service we count requests per account and per network address in short time windows (for example, up to 120 assistant requests a minute per account, and 30 previews and 10 saved changes per 10 minutes). These counters store a keyed one-way hash rather than your address or account, and expire within two hours. The connector's logs and metrics record which tool ran and its outcome, not the content of the answer; the requests it makes to 61Insights are logged and error-reported like those of the web app (see Usage data and Sentry above).
• Disconnecting. You can disconnect the connector in your assistant's settings at any time, or simply stop using it. Because a session lasts at most 5 minutes and is not renewed on its own, the assistant's access ends within 5 minutes of your last sign-in. You or your school administrator can also ask us at privacy@61insights.com to turn access off for your account; it stops on the next request.
• The 61Insights plugin. We also publish a plugin for Claude, and a package for ChatGPT, with ready-made workflows for the assistant. It contains only written instructions for the assistant and the connector's address. It runs no code of its own and collects, stores and sends nothing itself: everything it does goes through the connector described in this section.
• No sale, no training. We do not sell data that passes through the connector, use it for advertising, or use it to train AI models.

7. Data Retention

Your flight records and training data are retained for as long as your account is active and your enrollment at a tenant school is in good standing. If your account is deactivated, your historical data is preserved for record-keeping purposes and remains accessible to school administrators. Your flight review date is deleted as soon as you clear it, and when your account is deleted. A notification is deleted 30 days after it has been dealt with, and in any case 180 days after it was last updated. Your nudge history is kept for 12 months and deleted with your account. A phone's push token is deleted when you turn the push switch off (this deletes the tokens of all your phones), when Google tells us it is no longer valid, when you have more than five phones (the least recently used phone is dropped), when another account signs in on that phone (the token moves to that account), after 270 days without use, and with your account. When you sign out on a phone, the app asks us to delete its token and switches notifications off on that phone. This is best effort: if the phone is offline, neither step is retried, and the token is then deleted when Google reports it invalid or after 270 days without use. Each queued push is checked again when it is about to be sent, against your push switch and mutes (and, for encouragement, your own choice, your school's switch-off and your school membership), and is dropped if it no longer applies. Clearing your flight review date also deletes its queued reminders immediately. A push notification we queue is deleted 14 days after it was queued, whether or not it was sent, and with your account.

If you use the beta AI assistant connector, a lesson-plan preview expires after 15 minutes and a confirmed change's temporary record after 24 hours, and sign-in and connection records expire within minutes of the session ending. What your AI provider keeps is governed by its own policy (see section 6).

A school's billing records — its subscription status, its monthly instructor and administrator counts, and a log of any billing change our staff make with the reason for it — are kept for seven years after the billing period they describe, for tax and accounting, and then deleted. Records of Stripe's notifications to us are deleted after 30 days. When a school closes its account, we end its subscription that day and Stripe issues a final invoice for the period up to the closing date; once that invoice is settled, we ask Stripe to delete the customer record. Stripe keeps what the law requires of it, such as invoices already issued. If a school stops paying and moves to the Flight School of One plan, nobody's records are deleted: members who are made inactive can still sign in and view their own records.

You may delete your account from the Profile page in the app, or request deletion by contacting us at the address below. See Delete Your Account for exactly what is removed, what your flight school keeps, and the 30-day window in which a deletion can still be undone. Note that flight records may be retained by your flight school under their own obligations.

8. Security

All data is transmitted over TLS. Access to your training data is enforced by role-based access controls — only authenticated users with an appropriate role at your school can view your records. We do not store passwords (authentication is delegated to Auth0).

9. Children's Privacy

61Insights is intended for use by student pilots and flight training professionals. We do not knowingly collect personal information from anyone under 13. If you believe a minor has provided us personal data, please contact us so we can delete it.

10. Your Rights

Depending on your jurisdiction, you may have the right to access, correct, or delete your personal data. To exercise these rights, contact us at privacy@61insights.com. We will respond within 30 days.

11. Changes to This Policy

We may update this policy as the service evolves. We will update the effective date at the top of this page. Material changes that affect how your data is used will be communicated via the platform's announcement system.

12. Contact

Questions about this policy? Email us at privacy@61insights.com.