Privacy Policy

Last updated: October 27, 2026

1. Introduction & Scope

SkyReady Aviator (“SkyReady,” “we,” “us,” or “our”) is a mobile application and website that helps pilots keep a digital logbook, track currency and proficiency, plan and record flights, assess flight readiness, and get answers from an AI flight assistant (“Copilot”). This Privacy Policy explains what information the SkyReady Aviator app, the skyready.app website and its free flight tools, and the supporting cloud services (together, the “Services”) collect, how we use and share it, how long we keep it, and the choices and rights you have.

The Services are operated by SkyReady Inc., a corporation incorporated in Delaware, United States.

Who this policy is for. The Services are intended for users located in the United States. We do not target or market the Services to residents of the European Union, the United Kingdom, or other regions, and this policy is written to reflect U.S. privacy law. If you are located outside the United States, please do not use the Services.

This policy applies to the SkyReady Aviator mobile app on iOS and Android, the skyready.app website (including the free flight tools, the airport pages, the weather map, and the signed in account, operator, and support areas), and the cloud services that support all of them. The app and the website share one account and one set of cloud services, so information you enter in either is the same information described below. It does not apply to third party services we integrate with (for example, the app store you downloaded the app from, or your payment provider), which have their own privacy policies.

Using the website without an account. Most of the website (the free tools, the airport pages, and the weather map) works with no account at all. Where those pages let you save a setting, it is stored in your browser only and is never sent to us or linked to any account (see Section 5).

By creating an account or using the Services, you agree to the practices described in this policy.

2. Information We Collect

We collect what we need to operate the Services. Most of your flight data is created on your device first and is synced to our cloud to back it up and make it available on your other devices and on the website (see Section 5). The categories below describe what we collect.

Account & Identity

When you create an account we collect your email address, a password (stored only in hashed form by our authentication provider, AWS Cognito; we never see your password), and your name. Sign in is by email and password; we do not offer sign in with Apple or Google. You can also add a passkey to sign in with your device’s fingerprint, face, or PIN: our authentication provider stores the passkey’s public key and the name of the service that holds it (for example, iCloud Keychain), and your fingerprint, face, and PIN never leave your device. We email you whenever a passkey is added to or removed from your account. If you turn on multi factor authentication (an authenticator app), we store your MFA configuration. We assign you an internal account identifier that is used throughout the Services. To alert you when your account is used on a new device, we keep a scrambled (hashed) fingerprint of each browser or app that signed in, for up to 180 days. A sign up that is never confirmed by email is deleted after 7 days.

Location Data (precise GPS)

SkyReady uses your device’s precise location in these ways.

On the map, while the app is open. The map uses your position to show where you are, center the map on you, run the moving map and in flight alerts, and show weather and airports near you. For this use, your position is used on your device and is not sent to us.
During a flight you start. When you start a flight in the app (the Fly button), the moving map and in flight alerts keep using your position while the app is in the background or the screen is off, until you end the flight. Starting a flight also records its GPS track, whether or not you record cockpit audio.
The GPS track of a flight. The track holds your position, GPS altitude, ground speed and direction of travel, the accuracy of each fix, and the time of each point, and it keeps recording while the app is in the background or the screen is off, until you end the flight or stop the recording. If your device has a barometer, the track also carries pressure altitude, and it carries a measure of acceleration (g load) that helps detect landings. When the flight or recording ends, a reduced copy of the track (up to 2,000 points) is synced to your account and stored on our servers, linked to you, so you can replay the flight in the app or on the website and so the flight can be debriefed (Section 4b). The full resolution track stays on your device. The track always comes from your device’s own GPS, even when an ADS-B receiver is connected.
Your present position as a route point. If you change your route in flight (direct to, divert, or resume) or type your present position into a route, the app saves that exact position as a point in the flight’s route, and the route syncs to your account with the flight.

Location is accessed in the background only during a flight you started or a recording you started, and it stops when you end it. The app never asks for “always” location access. A recorded track is kept until you delete that recording or delete your account (Section 8).

Feedback from the map. When you choose to send feedback from the map, the report includes where the map was centered, rounded to about 1 km (which may be near you if the map is following your position). It is left out while a flight is being recorded or you are moving, and the form shows it before you send.
Map and weather requests. To draw the map, your device requests weather, chart and airport data for the area on screen from our servers. If our own copy of the FAA charts is not available, chart images are loaded instead from the FAA’s chart service, which is hosted by Esri. These requests carry the map area and your IP address. They do not carry your position as such, but the area on screen is near you whenever the map is following your position.
Point lookups on the map. When you press and hold a point on the map, the app sends that point (rounded to about 1 km) and your current altitude to our weather service to fetch the winds there. Route wind requests send the points of your route, rounded the same way.

You control location through your device’s location permission, which you can grant or deny at any time. If you deny it, the rest of the app works; the map will not show your position and you cannot record a GPS track.

Microphone & Cockpit Audio (Flight Recorder)

If you use the Flight Recorder, the app records cockpit audio from your device’s microphone or a connected audio cable or headset, together with your GPS track. Recording happens only when you start it, and it can continue in the background until you stop it. Before you start, the app can show a live input level so you can check your audio connection; nothing is saved from that check. Recorded audio is stored on your device. It is uploaded to us only when you request a debrief for that recording. Section 4b explains what happens then, who processes the audio, and how long each part is kept.

Recordings can include the voices of other people, such as your instructor, passengers, and air traffic control. Before recording audio on a flight with others aboard, the app asks you to confirm that you told them and they agreed. It stores your answer with the recording, together with the names and roles you entered for the people aboard (for example your instructor or a passenger), and this record syncs to your account. You are responsible for getting consent where the law requires it (see our Terms of Service).

Copilot voice input is different: when you speak a question to Copilot, your speech is turned into text on your device using your phone’s built in speech recognition, and the audio is not uploaded. Only the resulting text is sent, as a Copilot question (Section 4).

Camera, Photos & Logbook Scan Images

The app uses the camera for one thing: to scan pages of a paper logbook, using your device’s built in document scanner. It does not scan QR codes and does not take photos for any other purpose. You can also pick logbook page photos from your photo library. On the app or the website you can instead upload a PDF of your logbook. If you use logbook scanning, we collect the photos or PDF of your logbook pages you submit and the flight entries extracted from them. How these images are processed, who can see them, and how long they are kept is described in Section 4a.

Separately, you can choose a file to attach to a support request (an image or a video), an aircraft document for Copilot (Section 4), or a logbook export file to import. These go through your device’s file picker, which gives the app only the file you pick. A logbook export file you import is read on your device; the file itself is not uploaded, and the entries it creates become part of your logbook.

Pilot Credentials & FAA Verification

To tailor currency and eligibility calculations to you, we collect details about your airman credentials: your certificate type and ratings, certificate number, and (if you are a flight instructor) your instructor certificate type, number, and expiration, along with a flag indicating instructor status, an invite code used to link you with students, and, if you save one, an image of your instructor signature. To help confirm these details, we match the name, certificate level, and medical or certificate dates you provide against our copy of the public FAA Airmen Releasable Database, and we store the resulting verification status and, for instructors, the instructor certificates found there.

Medical & Health Information

Because medical currency is central to flight eligibility, we collect your medical certificate class and dates. When you verify your certificate against FAA public records, the result can also show the medical and BasicMed dates on file with the FAA. We do not collect your date of birth. We treat this information as sensitive and use it only to calculate your medical currency and eligibility.

Flight Logbook, Flights & Aircraft Data

The core of the app. We store the logbook entries you create, including flight dates, aircraft tail number and route, flight time categories (for example total, PIC, SIC, dual, night, cross country, instrument), takeoffs and landings, Hobbs, tach and block times, approaches and holds, your remarks and notes, instruction details, and any signatures and endorsements captured on an entry. Entries and endorsements can include details of other people, such as the name and certificate number of the instructor who signed, or of a student. Some endorsements hold what the regulation requires the instructor to record; for example, a TSA citizenship endorsement records the type of identity document shown and its number. We also store the flights you plan (route, aircraft, times, notes), the aircraft you fly (make and model, class and category, equipment, performance data), your checklists, and an optional prior hours baseline so totals carry over from a previous logbook.

Flight Recordings, Transcripts & Debriefs

For each flight you record we store, synced to your account: the recording’s details (times, aircraft, route, your consent answer and the names and roles of the people aboard, and the result of the audio check), the markers you or the app place during the flight, the GPS track described above, and, if you requested a debrief, the transcript of the audio and the debrief generated from it. Audio itself is not synced between your devices. See Section 4b.

Training Relationships (Instructor and Student)

If you use SkyReady’s instructor and student features, we store the links between instructors and students, signature and endorsement requests, any supporting documents attached to an endorsement request, and limited profile details each party agrees to share (such as name and certificate type). For dual instruction flights and endorsements, an instructor may keep their own copy of the training record (see Section 8).

Flight Readiness Data

To support pre flight readiness checks, we store your personal minimums profiles, your planned flights and their route airports, the readiness assessments generated for them, and periodic proficiency snapshots computed from your logbook.

AI Copilot Conversations, Memory & Uploaded Documents

When you use Copilot, we store your conversations and messages so you can return to them. Copilot also keeps a memory of lasting facts you tell it about yourself (Section 4). If you add an aircraft document (such as a Pilot Operating Handbook), the app keeps that document and its extracted text on your device so Copilot can reference it; only short excerpts are sent with your questions.

Preferences & Settings

We store your app preferences, for example units, theme, default airport, map settings, notification and email settings, alert thresholds, saved airports, and the choices you make about the AI features (Section 4). So that we can email you reminders before a currency, medical, flight review, or endorsement expires, the app also syncs a summary of your currency dates; you can turn these emails off.

Device, Technical & Analytics Data

To keep the Services reliable and understand how they are used, we and our analytics and diagnostics providers collect technical data such as app version, operating system, device type, an identifier our analytics provider creates for the installation, crash reports, and usage events (for example, which screens are viewed and which features are used). In the app, analytics events are linked to your internal account identifier when you are signed in; we do not send your name or email address to our analytics provider from the app. The app also records taps: the internal name of the control you tapped and where on the screen, not the text shown. For some lists that internal name includes an airport identifier, an aircraft tail number, or a record’s internal ID. A few events carry short details such as an aircraft make and model, the name of a connected ADS-B receiver, or the text of an error message. You can turn usage analytics off with the Share usage analytics switch (Section 9).

On the website this also includes standard web telemetry: browser type and version, screen size, referring page, the address of each page you view, clicks on page elements (which can include the text of the element you clicked), and basic page performance measurements. We do not attach your account to website analytics. The page address is sent as it is, so on the charts page it includes the map area in view, and when you open a confirm or unsubscribe link from one of our emails it includes the email address in that link.

Session replay. In both the app and the website, our analytics provider (PostHog) may record session replays: a reconstruction of the screens you saw and the taps, clicks, and scrolling you did, so we can see where the Services are confusing or broken. Replays are configured to mask text, including what you type and the text shown on screen, and images, before anything leaves your device or browser. In the app, replay runs for a sample of sessions (about one in ten).

Crash reports. Our crash reporting provider (Sentry) receives crash and error reports from the app. A report names your account only by a one way hash of your internal account identifier, never the identifier itself, your name, or your email address. The same account always gives the same hash, which lets us see how many people a problem affects. Sentry keeps crash reports for up to 90 days and then deletes them. Sentry also receives performance timings for a sample of sessions. Before a report leaves your device, the app removes the fields that hold personal content (such as names, email addresses, messages, logbook and note text, and coordinates) and drops the query part of web addresses. The text of an error message and the path of a request, which can contain something like an airport identifier, are sent as they are. Reports never include screenshots or screen recordings.

Cookies & Browser Storage

The website uses cookies and similar browser storage (localStorage and sessionStorage). We use them for these things:

Keeping you signed in. Your sign in session is stored in your browser so you do not have to sign in again on every page.
Remembering your settings and your own data. Your preferences (such as units and light or dark theme) and, when you are signed in, a copy of the account data a page needs to show your own numbers immediately. Section 5 describes exactly what this includes and when it is deleted.
Analytics. Our analytics provider stores a cookie and a browser storage entry to recognize a returning browser so that repeat visits are not counted as new people. When your browser sends Global Privacy Control, or when you have turned usage analytics off, the website does not load our analytics provider at all, so none of this is stored and nothing is recorded (Section 9).

Separately, the pages with a public form (sign up, the waitlist and beta signup, pilot reports, roadmap votes, feedback) load Cloudflare Turnstile, a bot check, which may store a token in your browser for a short time while it runs. Because the waitlist form appears on most public pages, most public pages load it. It is used only to tell a person from a script.

Some pages show a video. Only a preview image is loaded (from YouTube’s image server) until you press play; pressing play loads the player from YouTube’s privacy enhanced address (youtube-nocookie.com), which then sees your IP address.

We do not use advertising cookies, and we do not allow third parties to track you across other websites. You can clear or block cookies and storage in your browser settings, but signing in and saving preferences will stop working if you do.

Waitlist & Email Signups

If you join the waitlist or a beta signup on the website, we collect your email address, when you signed up and confirmed, and, if you fill in the beta questionnaire, your answers to it. We email you only after you confirm the address through the link we send. A signup you never confirm is deleted 30 days after you sign up. A confirmed signup is kept until you unsubscribe, which deletes it.

Support Communications

If you contact support or submit feedback, we collect the message you send and any attachments (an image or a video) you choose to include on a support request, so we can help you. A support ticket also holds your email address. Feedback sent from the app or the website also carries a short technical context so we can reproduce the problem: the app version and build, your device model and operating system, screen size, language and time zone, the screen you were on and the last few screens and actions you used (their names only), your network type, your plan, when the app last synced, the identifiers our analytics provider uses for your session, and, on the map, where the map was centered, rounded to about 1 km. If you use Report this answer on a Copilot reply and leave its switch on, the question and the answer are sent to us with the report. The form shows this under “What we send with this” before you send. It never includes your logbook entries, audio, transcripts, or your exact position. When you report a problem from certain app screens, you can choose to include one screenshot of that screen; the switch is off by default. It is offered only on screens that show no personal records, such as airports, charts, regulations, and some settings pages, and never on your logbook, flights, endorsements, Copilot, or account screens. Before the screenshot leaves your device, names, tail numbers, certificate numbers, and notes are blacked out. It is stored with the report as an attachment, and like other attachments it is deleted after 30 days and is erased if you delete your account (Section 8). If you email us directly, your email is stored in our email system (Section 7).

Subscription & Payment Data

SkyReady offers paid subscriptions and credit packs. Purchases are processed by the app stores and our subscription provider, RevenueCat: we never receive or store your payment card details. RevenueCat knows you only by your internal account identifier; the app does not give it your name or email address. We do receive and store your subscription status and entitlements (for example, whether you have an active subscription or trial), your credit balance, and related purchase events, linked to your account.

On Your Device Only

Some features use information that stays on your device and is never sent to us:

ADS-B receivers and your local network. If you connect an ADS-B receiver (such as a Stratux or Stratus), the app listens for it on your local network and announces itself to the receiver there. The traffic, weather, position, and attitude data it receives is used on your device to draw the map and give alerts, and is not uploaded. Our analytics receive only that a receiver was connected, its product name, and counts.
Barometer and motion sensors. These are read on your device whenever the map is showing your position. They leave your device only as the pressure altitude and acceleration values in a recorded track, and as the altitude sent with a point lookup on the map (see Location Data).
Calendar. When you choose Add to calendar for a flight, the app opens your device’s calendar editor with that one event. On older versions of iOS the system asks you to allow calendar access first. We never read your calendar or upload anything from it.
Copilot voice. Speech recognition for Copilot runs on your device (see above).
Aircraft documents and imported files. A handbook you add for Copilot and a logbook file you import are read on your device (see above).
Bluetooth headsets. A Bluetooth headset can be the recorder’s audio input. The app uses it through your device’s audio system and does not scan for Bluetooth devices.
Notifications. Reminders and alerts are scheduled on your device. We do not collect a push notification token.

What We Do NOT Collect or Do

We do not sell your personal information, and we do not share it for cross context behavioral advertising.
We do not run third party advertising or ad tracking SDKs in the app.
We do not access your location in the background except during a flight you started, and we do not collect your position except in the ways listed under Location Data: a recorded track, a present position you save as a route point, a point lookup on the map, and the rounded map center in feedback.
We do not use your data, including Copilot conversations, cockpit audio, transcripts, and logbook scans, to train AI models (see Sections 4, 4a and 4b).

3. How We Use Your Information

We use the information described above to:

Provide and operate the Services: maintain your logbook, flights, aircraft, recordings, and preferences; calculate currency, proficiency, and eligibility; generate flight readiness assessments and flight debriefs; and power the Copilot assistant and logbook scanning.
Create and secure your account: authenticate you, enable multi factor authentication, and protect against fraud, abuse, and unauthorized access.
Sync and back up your data across your devices and the website (see Section 5).
Verify pilot credentials by matching the details you provide against the public FAA Airmen Releasable Database.
Enable instructor and student features: link instructors and students, route signature and endorsement requests, and share the limited profile details each party agrees to share.
Process your purchases: confirm your subscriptions, trials, and credit purchases through the app stores and our subscription provider.
Communicate with you about the Services (transactional messages): for example, email confirmations, password resets, data export links, account deletion confirmations, instructor invitations, security notices such as a new device sign in, and responses to your support requests. You cannot opt out of these because they are necessary to operate your account.
Send reminders and updates you can turn off: emails before a currency, medical, flight review, or solo endorsement expires, updates on feedback you sent, and logbook scan results. Each kind can be turned off in your email settings or with the unsubscribe link in the email.
Send marketing communications: product news and tips are sent to account holders only if you turn them on, and to waitlist addresses only after you confirm. You can opt out at any time using the unsubscribe link in those emails or by contacting us; opting out does not affect transactional messages. See Section 9. Our emails do not contain open tracking pixels or click tracking links; we see only whether a message was delivered, bounced, or marked as spam.
Create aggregated and de identified data: we may aggregate or de identify information so it no longer identifies you and use it to understand usage, improve the Services, and for general analytics. We will maintain de identified data in de identified form and will not attempt to re identify it except as permitted by law.
Provide customer support and respond to your feedback.
Maintain, improve, and debug the Services using analytics, session replay, and crash diagnostic data (see Sections 2 and 7), and measure and improve the accuracy of logbook scanning using reviewer corrections (Section 4a).
Comply with the law and protect rights and safety: to meet legal obligations, enforce our terms, and protect our users, the public, and our Services.

We do not use your information for purposes that are incompatible with those listed here without telling you first.

4. AI Features (Copilot)

Copilot is an optional, subscription gated AI assistant that answers aviation and pilot readiness questions. Here is how it handles your data.

We ask first. The first time you use Copilot, logbook scanning, or a flight debrief, the app shows what will be sent and to whom, and asks you to agree. You can withdraw your agreement for each feature in the app under Settings, then Privacy & Security; the app then stops sending data for that feature until you agree again. Withdrawing does not delete what is already stored; use the deletion choices in Section 9 for that.

What is sent when you ask a question. Your app sends your question, up to the last 8 messages of that conversation, and, only if you added one, short excerpts from an aircraft document (such as a Pilot Operating Handbook) that best match your question. Once a document is added, excerpts go with each question. To answer, Copilot can then look up information from your account on our servers, such as:

your pilot profile (home airport, certificates and ratings, certificate numbers, aircraft, medical class and dates, instructor status, endorsements, and preferences);
your logbook entries, including remarks and notes and the instructor or student details recorded on an entry, and your computed currency, eligibility, and personal minimums;
your planned flights and their notes; and
public weather, NOTAM, and airport information for the airports in your question.

Copilot does not receive your location.

Who processes it. Copilot runs on Amazon Bedrock AgentCore in our AWS environment and uses Anthropic’s Claude models for three jobs: answering, giving a new conversation its title, and extracting facts for Copilot memory. Answers and titles come from Anthropic’s Claude API. When the Claude API is unavailable, Amazon Bedrock runs the same models from our AWS environment instead. Either may process your request outside the United States. Facts for Copilot memory are extracted on Amazon Bedrock in the United States.

Copilot memory. Copilot remembers lasting facts and preferences you tell it about yourself, such as the aircraft you fly, your home airport, your certificates, ratings and medical, your personal minimums, and the units you prefer, so you do not have to repeat them. To do this, the memory service keeps the text of your recent Copilot conversations, both your messages and Copilot’s answers, for 90 days, and an AI model extracts lasting facts from them. The facts it extracts are linked to your account and are kept until you delete your account. Copilot is instructed not to remember one time requests. You can see the remembered facts in your data export (Section 9). There is no screen to edit or remove a single fact today. If you withdraw your agreement to Copilot (Section 9), Copilot memory is cleared: the remembered facts and the conversation text the memory service holds are deleted. Your list of conversations stays until you delete it.

Logs. For reliability and abuse prevention, Copilot’s service logs record requests and responses, which can include excerpts of the account information listed above. The Copilot logs we configure are deleted after one month. Timing traces of Copilot requests are also sent to the AWS tracing service.

No training, limited provider retention. Your Copilot data is used to answer you and to run and protect Copilot. It is not used to train AI models. Anthropic deletes the requests it receives within 30 days, unless a request is flagged for violating its usage policies, in which case it may keep it longer to investigate. Amazon Bedrock does not retain your data after processing. We do not sell or share Copilot content for advertising.

Where your conversations live. Your Copilot conversations are stored in your account and synced to your devices so you can return to them. They are kept until you delete them or delete your account (Sections 8 and 9). Deleting a conversation removes its messages from your account and your devices. Its title is removed from our servers 30 days later, and deleting a conversation does not clear what Copilot memory already holds from it. Aircraft documents you add are kept on your device.

Usage records. We keep a record of the AI usage each request consumed (amounts and cost, never the text), for billing and to enforce allowances. Each record expires after 90 days. A monthly total of your usage is kept until you delete your account. When you delete your account, records that have not yet expired are kept without your identity until they do.

A note on accuracy. Copilot is an aid, not an authoritative source. It can make mistakes, and it does not replace official FAA materials, current weather briefings, approved aircraft documentation, or your own judgment and responsibilities as pilot in command. See our Terms of Service.

4a. Logbook Scanning (AI Extraction & Human Review)

Logbook scanning lets you photograph pages of a paper logbook, or upload a PDF of one, and have the flight entries extracted for you. Because this feature involves images of your records and, in one mode, people looking at them, here is exactly how it works.

AI extraction. The photos or PDF you submit are stored in our AWS environment. A PDF is split into page images on our servers, and a Claude model looks at each PDF page to find which way it is turned and where one logbook page ends and the next begins. The page images are then read by Anthropic’s Claude models through Anthropic’s Claude API, or through Amazon Bedrock in our AWS environment when the Claude API is unavailable. Either may process them outside the United States. Your images and extracted data are not used to train AI models. Anthropic deletes them within 30 days, unless a request is flagged for violating its usage policies; Amazon Bedrock does not retain them after processing.

Human review (optional). If you choose the human review option, a reviewer working for SkyReady views your logbook page images and the extracted entries to verify and correct them, and may flag pages that need a clearer photo. Reviewers are SkyReady staff or contractors to whom we have granted review access. They access your images only through our review console, which shows them your page images, the extracted flight data, and an internal account identifier, and not your name or email address (though your pages themselves may show your name, certificate number, or signatures). Reviewers are bound by confidentiality obligations.

You stay in control of the result. Extracted entries are always presented to you for review in the app or on the website first. Nothing is added to your logbook until you accept it.

Retention. Scan images, and any PDF you upload with the page images made from it, are kept for up to 90 days and then deleted automatically. The entries extracted from a scan are kept on our servers until you delete the scan or your account; the scan’s status record expires about 30 days after the last activity on it. Deleting a scan removes its images, its PDF, and its extracted entries right away. When a reviewer verifies a scan, we keep the corrections the reviewer made and a record of the entries released to you, linked to your account, so we can check reviewer work, handle any quality concern you raise, and measure and improve scan accuracy. These are kept until you delete your account, even if you delete the scan. Deleting your account removes all of the above. The reviewers’ own work log (which scan was reviewed, when, and by whom) is kept after that; it holds your internal account identifier and no images or entries.

4b. Flight Recorder (Cockpit Audio, Transcripts & Debriefs)

The Flight Recorder records cockpit audio and your GPS track during a flight you choose to record, and can turn them into a transcript and a debrief.

On your device. Audio is stored on your device. For each recording you choose how long the app keeps its audio on your device (7, 30, or 90 days, or until you delete it; 30 days unless you change it). After that period the app deletes the audio the next time it is opened, and keeps the track, markers, transcript, and debrief. You can delete a recording at any time; this removes its track, markers, transcript, and debrief from your devices and our servers, and audio uploaded for a debrief is deleted on its 7 day schedule (below). Delete debrief on a recording removes its transcript, debrief, and uploaded audio right away. The steps are on our delete account page.

When you request a debrief. Only when you ask for a debrief does the app upload the audio you selected (in whole five minute segments, so a little audio either side of your selection can be included), along with flight context: the tail number and aircraft type, airport and air traffic facility names along your route, your markers, the roles of the people aboard (not their names), a note if you wrote one, and events the app detected on your device, such as engine start and landings. Then:

The audio is stored in our AWS environment, encrypted, and deleted automatically after 7 days, along with the working files made from it.
Deepgram, our speech recognition provider, transcribes it. Deepgram receives the audio and a short list of terms to listen for (your tail number, aircraft type, and route airports). We send each request with Deepgram’s option that opts the audio out of use to improve Deepgram’s models.
Anthropic’s Claude models read the transcript, your GPS track, and the flight context, and produce a debrief, through Anthropic’s Claude API, or through Amazon Bedrock in our AWS environment when the Claude API is unavailable. Either may process it outside the United States.
The transcript and debrief are delivered to your app and synced to your account, where they are kept until you delete the recording or your account.

Your audio, transcripts, and debriefs are not used to train AI models. Deepgram and Amazon Bedrock do not retain them after processing. Anthropic deletes what it receives within 30 days, unless a request is flagged for violating its usage policies.

Other people’s voices. A recording can capture other people. You are responsible for telling them and getting their consent where the law requires it. An instructor or passenger may decline to be recorded.

5. How Your Data Is Stored & Synced

SkyReady is built offline first. Your logbook and most of your data are created and stored on your device first, so the app works without a connection. When you are signed in and online, your data is synced to your SkyReady account in the cloud so it is backed up and available on your other devices and on the website.

Where it is stored. Our cloud services run on Amazon Web Services (AWS) in the United States, and our databases and file storage are located there. The providers in Section 7 process the data described for each of them on their own systems.
On device data (app). Data on your device (including your local logbook database, cached content, recording audio, and the full resolution GPS tracks) stays under your control; removing the app from your device removes the local copy, though synced data remains in your account until deleted (see Section 8).
In browser data (website). When you sign in on skyready.app, your browser keeps a copy of the account data the page you are on needs, so it can show your own numbers immediately instead of reloading them on every page. This includes your profile details, personal minimums, aircraft, home base and saved airports, and a copy of your logbook and your recorded flights. It stays on your computer and is not shared with anyone.
- Signing out deletes it, on every path that ends a session, including a password change and account deletion. Clearing your browser’s site data removes it too. A few display settings (such as theme, logbook column choices, and chart settings) stay after you sign out.
- This copy stays in the browser until you sign out, including after you close the tab. The copy of your account and logbook is not kept longer than 24 hours: once it is older than that, it is deleted the next time you open your account in that browser, and fresh data is loaded. On a public or shared computer (common at flight schools and FBOs) always sign out when you finish.
- If you are not signed in, what is stored is what you type into the free tools (for example the minimums and aircraft you set on an airport page), your display settings, and small markers such as a roadmap vote or a waitlist signup. None of it is linked to an account, and it stays until you clear your browser.
Encryption. Your data is encrypted in transit (TLS/HTTPS) between your devices and our services, and at rest in our cloud storage.
What is synced from your location. The recorded GPS tracks and any present position you saved as a route point, as described in Section 2. Your live position on the map is not synced.

We do not sell your personal information, and we do not share it for cross context behavioral advertising. We share information only in the limited circumstances below.

Service providers. We share information with vendors who process it on our behalf to run the Services, for example cloud hosting, AI processing, speech recognition, authentication, subscription management, analytics, crash diagnostics, and email. They may use the information only to provide services to us. See Section 7 for the list.
Reviewers. If you choose human review for a logbook scan, a reviewer working for SkyReady sees your page images and extracted entries (Section 4a).
Instructors and students you connect with. If you use the instructor and student features, we share the relevant information with the people you choose to connect with, for example a student’s flight entry or endorsement request submitted to their instructor for signature, and the limited profile details each party agrees to share. You control these connections.
For legal reasons and safety. We may disclose information if required by law, regulation, legal process, or governmental request, or where we believe disclosure is reasonably necessary to enforce our terms, prevent fraud or abuse, or protect the rights, property, or safety of our users, the public, or SkyReady. This includes reporting apparent child sexual abuse material to the National Center for Missing and Exploited Children as the law requires.
Business transfers. If SkyReady is involved in a merger, acquisition, financing, or sale of assets, your information may be transferred as part of that transaction. We will notify you of any such change and any choices you may have.
With your consent. We may share information for other purposes with your direction or consent.

We may also share aggregated or de identified data that does not identify you.

7. Third Party Services

We rely on the following third parties to provide the Services. Each receives only the data needed for its function.

Provider	Role	Information involved
Amazon Web Services (AWS)	Cloud infrastructure: hosting, database, authentication (Cognito), storage, transactional email (SES), and request filtering	All account and synced app data, including recorded tracks, transcripts, and debriefs; uploaded audio, scan images and logbook PDFs; account emails
Anthropic (Claude API)	AI processing for Copilot answers and titles, logbook scan extraction, and flight debriefs	Your Copilot questions and the account information described in Section 4; logbook page images, including those made from an uploaded PDF (Section 4a); transcripts, GPS tracks, and flight context for debriefs (Section 4b). Not used to train models; deleted within 30 days unless flagged for misuse; may be processed outside the United States
Amazon Bedrock and Bedrock AgentCore (AWS), using Anthropic’s Claude models	Running Copilot, Copilot memory, and the same AI processing as Anthropic’s Claude API when that is unavailable	The same information as the row above when it stands in for it, and remembered facts. Not used to train models; not retained by the model provider
Deepgram	Speech recognition for Flight Recorder debriefs	Cockpit audio you upload for a debrief, and terms to listen for: your tail number, aircraft type, and route airports (Section 4b). Opted out of model improvement
RevenueCat	Subscription, trial, and credit purchase management	Your internal account identifier, subscription status, entitlements, purchase events, and app and device details. No payment card details
Apple App Store / Google Play	App distribution and payment processing	Your purchase transactions (handled under their own policies)
PostHog	Product analytics and session replay (app and website)	Usage events and taps, masked session replays, an installation identifier, and, in the app, your internal account identifier; on the website, page addresses, clicks, and an analytics cookie (Section 2)
Sentry	Crash, error, and performance diagnostics (app)	Filtered crash and error reports and performance timings tied to a one way hash of your internal account identifier, kept up to 90 days. No screenshots or screen recordings
Cloudflare (Turnstile)	Bot check on sign up and on the website’s public forms	Your IP address and browser signals, sent to Cloudflare by pages that carry one of those forms. No account data
Esri (ArcGIS Online)	Hosts the FAA’s chart image service, used on the website’s charts and as a fallback in the app	Your IP address and the chart area requested. No account data
YouTube (Google)	Videos on some website pages	Your IP address when a preview image loads and when you press play. No account data
Google Workspace	Our own email inboxes (for example support@ and privacy@)	Emails you send us at those addresses and our replies

These providers act as our service providers or processors and are contractually limited to using your information to provide services to us. Their own handling of data is governed by their respective privacy policies.

We also retrieve public aviation data (such as weather from aviationweather.gov and the National Weather Service, and FAA aeronautical, aircraft, and airman records) to power features. We do not send your personal information to these sources. Links in the app and on the website that open another site (for example a flight service briefing site or an FAA page) open in your browser and are governed by that site’s policy.

8. Data Retention

We keep your personal information for as long as your account is active and as needed to provide the Services. When you delete your account, or when information is no longer needed, we delete or de identify it, subject to the following:

Account deletion and the recovery window. Deleting your account is final from your side: the account is disabled right away, and signing in again does not cancel the request. Your data is permanently erased about 30 days later. During those 30 days the deletion can be cancelled only by emailing support@skyready.app from the address on your account. After the 30 days your account cannot be recovered. Deleting your account does not cancel an App Store or Google Play subscription; cancel it in the store. Step by step instructions are at skyready.app/delete-account.
What deletion erases. Your profile and sign in; logbook entries, flights, aircraft, checklists, and endorsements; recorded flights with their tracks, transcripts, and debriefs, and any uploaded audio; logbook scans with their images, reviewer corrections, and release records; Copilot conversations and Copilot memory; saved airports and alerts; support tickets, feedback, and their attachments; data exports; your credit balance; your customer record at RevenueCat; and the app analytics events and app session replays at PostHog that are linked to your account, along with PostHog’s record of you.
Backups. Our databases keep encrypted point in time backups for 35 days, and encrypted daily and monthly backups, with a copy in a second AWS region in the United States, for up to 90 days. After permanent deletion your data can remain in those backups until it ages out: backup copies are deleted within 90 days after permanent deletion.
What is kept after deletion. A record that your account was deleted (your email address, your internal account identifier, the dates, and counts of what was removed) is kept for one year from your request so we can show that we honored it. AI usage records are kept without your identity until they expire (Section 4), and the scan reviewers’ work log is kept (Section 4a). Roadmap votes are kept without your identity. We may also keep information where we must, to comply with law, resolve disputes, or enforce our agreements.
What account deletion does not reach. Website analytics and website session replays, which are never linked to your account, are kept for the period PostHog is set to. Crash reports at Sentry carry only a hashed form of your internal account identifier, not your name or email, and are deleted within 90 days of being sent. Entries already written to our service logs stay until those logs expire (see below). A waitlist signup is separate from your account: a confirmed one stays until you unsubscribe, and an unconfirmed one is deleted 30 days after you sign up. If you claimed or manage an airport or business listing on the website, that listing and claim are kept. Email privacy@skyready.app to ask about any of these.
Instructor training records. When an instructor provides dual instruction or signs an endorsement, the instructor keeps their own copy of that training record. Because flight instructors are required by regulation to keep instruction and endorsement records (FAR 61.189), an instructor’s copy may be retained even if the student later deletes their account.
Items that expire on their own.
- Data export files: 7 days.
- Attachments on support tickets and feedback: 30 days.
- Supporting documents attached to an endorsement request: kept with the endorsement until you delete your account.
- Emails you send to our ticket reply address: the raw message, 30 days (the text is added to your ticket).
- Uploaded flight recorder audio: 7 days (Section 4b).
- Logbook scan images and uploaded logbook PDFs: up to 90 days (Section 4a).
- Copilot conversation text held by the memory service: 90 days, or sooner if you withdraw your agreement to Copilot (Section 4).
- Crash reports at Sentry: up to 90 days (Section 2).
- Copilot request and response logs: one month (Section 4).
- AI usage records: 90 days (Section 4).
- Feedback sent without an account: 12 months.
- Waitlist and beta signups never confirmed by email: 30 days.
- Sign ups never confirmed by email: 7 days. Device fingerprints for new device alerts: up to 180 days.
Kept until you delete them or your account. Recorded tracks, transcripts and debriefs (until you delete the recording); the entries extracted from a scan (until you delete the scan); and Copilot conversation messages (until you delete the conversation).
Kept until you delete your account. Support tickets, feedback you sent while signed in, Copilot conversation titles, remembered facts (unless you withdraw your agreement to Copilot first), and scan corrections and release records.
Service logs. Our other service logs are used only for security, reliability, and debugging. They record your internal account identifier and details of requests, and a few record an email address (for example when you contact support or request deletion) or the name and dates you submit for FAA verification. Some of these logs are set to expire after one month; many have no set expiry today.
Network logs. Web server and firewall logs record IP addresses and the addresses requested. Where we keep them, they are deleted after two weeks to one month.
Test builds. Beta builds installed outside the app stores use our test environment, where the request log also records the content of requests and is deleted after one month.
De identified and aggregated data may be retained indefinitely.
Copies in your browser. The website’s local copy of your data is not subject to the 30 day window above. It is deleted the moment you sign out, and immediately when you ask us to delete your account (see Section 5).

You can request a copy of your data or deletion at any time (see Section 9).

9. Your Rights & Choices

You have choices about your information, and we honor the privacy rights described below for all U.S. users.

Access, export, correction, and deletion

Export / access. You can request a copy of your data from within the app (Settings, then Privacy & Security, then Export My Data) or on the website at Account → Security. We email you a link to download it. The copy includes your profile, logbook, flights, endorsements, recordings’ transcripts and debriefs, Copilot usage and remembered facts, support tickets, feedback, and scan review records; it does not include scan images, audio, or attachments. You can also export your logbook at any time, at no charge.
Correction. You can edit most of your information directly in the app or on the website, or ask us to correct it.
Deletion. You can delete your account (and the data associated with it) from within the app, from Account → Security on the website, or, if you cannot sign in, by emailing support@skyready.app from the address on your account (see skyready.app/delete-account), subject to the retention described in Section 8. Either way, the copy held in the browser you are using is deleted straight away. You can also delete individual recordings, scans, and Copilot conversations in the app (Section 4 explains what deleting a conversation removes).
AI features. You can withdraw your agreement to Copilot, logbook scanning, or flight debriefs at any time in the app under Settings, then Privacy & Security (Section 4). Withdrawing your agreement to Copilot also clears Copilot memory.

Usage analytics

In the app. Turn off Share usage analytics in Settings, then Privacy & Security. Usage events and session replays stop on that device at once. The choice is saved to your account, so it also applies on every other device you sign into and on the website once you sign in there. Crash reports are separate and are not affected.
On the website. If your browser sends Global Privacy Control, the website does not load our analytics provider, so no usage events or session replays are recorded from that browser. The website also follows the switch above when you are signed in, and keeps following it in that browser after you sign out.

Device permissions

You can turn location, microphone, camera, photos, calendar, and local network access on or off at any time in your device settings. The features that need them stop working; the rest of the app keeps working.

Communications choices

Email. You can turn each kind of optional email (reminders, feedback updates, scan results, product news) on or off in your email settings, or unsubscribe using the link in the email. This does not stop transactional account emails.
Notifications. You can turn notifications on or off in your device settings and in the app’s settings.

How to exercise your rights

You can use the tools above, or contact us at privacy@skyready.app. We may need to verify your identity before acting on a request, and you may use an authorized agent to submit a request on your behalf. We will respond within the time required by law (generally 45 days, extendable where permitted). We will not discriminate against you for exercising your privacy rights.

We do not sell your personal information and we do not share it for cross context behavioral advertising, so there is nothing to opt out of in that respect. For the same reason, an opt out preference signal such as the Global Privacy Control (GPC) has no sale or sharing to switch off. Our website still honors GPC by turning off its analytics in that browser before anything is recorded (see Usage analytics above).

Sensitive personal information

Some information we handle is considered “sensitive personal information” under California and other state laws: your account log in credentials, health and medical information (medical certificate details), precise geolocation (the GPS tracks of your flights and any present position you save as a route point), government identifiers where an endorsement records one (Section 2), and the contents of communications captured in cockpit audio you upload for a debrief. We use sensitive personal information only for purposes permitted by law: to provide and secure the Services and to perform the features you ask for. We do not use or disclose it to infer characteristics about you, so the right to limit the use of sensitive personal information does not apply; nonetheless, you may contact us with any questions.

California “Shine the Light”

California residents may request information about disclosures of personal information to third parties for those parties’ direct marketing purposes. We do not share personal information with third parties for their own direct marketing, so there is nothing to disclose.

Categories of personal information (CCPA notice)

In the past 12 months we have collected the following categories of personal information. We do not sell or “share” any of these categories. Retention for each is described in Section 8.

CCPA category	Examples we collect	Sources	Business purpose	Disclosed to
Identifiers	Name, email, account ID, installation ID, IP address, pilot and instructor certificate numbers, an identity document number where an endorsement records one	You; your device; your instructor	Create and operate the account; security; training records	Service providers; instructors or students you connect with
Customer records	Name, contact details	You	Account, support, communications	Service providers
Commercial information	Subscription status, trials, credit balance, purchase records	You; RevenueCat; app stores	Process and manage purchases	Service providers
Internet or network activity	App usage events, session replays (masked), crash and diagnostic data, website visits	Your device or browser	Improve, secure, and debug the Services	Analytics and diagnostics providers
Geolocation (sensitive)	GPS tracks of your flights (position, altitude, speed); a present position saved as a route point; a point you look up on the map; map center rounded to about 1 km in feedback	Your device	Flight replay, debriefs, route planning, support	Service providers
Audio, electronic, and visual	Cockpit audio uploaded for a debrief, transcripts, logbook scan images and PDFs, support attachments, entry and instructor signatures	You; your device	Debriefs, scan extraction and review, logbook records, support	Service providers; scan reviewers working for us
Professional information	Pilot and instructor certificates, ratings, verification status, logbook and training records	You; public FAA databases	Currency, eligibility, and instructor features	Service providers; instructors or students you connect with
Health information (sensitive)	Medical certificate class and dates, BasicMed dates from FAA records	You; public FAA databases	Medical currency and eligibility calculations	Service providers
Account credentials (sensitive)	Password (hashed), passkey public keys, MFA settings	You	Authentication and security	Service providers
Inferences	Currency, proficiency, and readiness calculations; facts Copilot remembers about you	Derived from your data and conversations	Provide the core features	Service providers

10. Data Security

We use technical and organizational measures designed to protect your information, including encryption in transit and at rest, hashed passwords, optional multi factor authentication, alerts when your account is signed in on a new device, and access controls that limit who can access data.

If there is a breach. If we learn of a security breach that affects your personal information, we will investigate, take steps to contain it, and notify you and the appropriate authorities as applicable law requires, without unreasonable delay. We will tell you what happened, what information was involved, and what you can do.

No method of transmission or storage is completely secure, so we cannot guarantee absolute security. Please help protect your account by using a strong, unique password and keeping it confidential.

11. Children’s Privacy

You must be at least 13 years old to use the Services, and they are not directed to children under 13. We do not knowingly collect personal information from children under 13. We do not collect your age or date of birth. If we learn that a user is under 13, we will delete the account and its information. If you believe a child under 13 has provided us personal information, please contact us at privacy@skyready.app and we will delete it.

If you are 13 to 17, a parent or guardian must agree to our Terms of Service and approve any purchase.

12. Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will revise the “Last Updated” date above and, for material changes, provide a more prominent notice (such as an in app or email notice) as required by law. Your continued use of the Services after an update means you accept the revised policy.

13. Contact Us

If you have questions about this Privacy Policy or your information, contact us at:

SkyReady Inc. Email: privacy@skyready.app