Version 1.4 · Effective 19 September 2026
This app records audio. If anyone else is in the aircraft or on the intercom, they are being recorded too. Recording laws differ by country and by US state, and several require the consent of everyone recorded. Telling the people on board is your responsibility, not ours.
MyFlightHelper transcribes cockpit and radio audio, shows nearby airports, weather and charts, keeps a Hobbs and tach log from photographs of your meters, and holds checklists you build. Some of those features are paid for, which means there is an account with a balance behind them. This policy explains exactly what the app collects, what the server keeps, where it goes, and what you can delete.
Most of it. The app is built to work with no connection, which means most data never leaves the device:
Deleting a flight in the app deletes its transcript and its audio from the device. Deleting a meter log deletes its photographs with it, and deleting an attachment deletes the file. Uninstalling the app removes all of it.
If you use cloud backup, it is written to your own Google Drive or OneDrive and nowhere else. It carries your flights, transcripts, meter figures, checklists, notes, pinned airports, your meter photographs and your attached documents — enough that signing in on a new device gives you the app you had, not an inventory of what you used to have. The documents go up as separate files alongside the backup, each named by a hash of its own contents. The first backup sends every document you hold and takes correspondingly longer; after that only documents you have added since are sent, because the app remembers what it has already put there.
Recorded audio is the one thing a backup never carries. A three-hour flight is over 100 MB, which would be hours of upload and would fill your drive. The transcript of what was said comes back; the recording of it does not. A single file larger than 5 MB is also left behind, and the app tells you when that happens rather than quietly skipping it.
It passes through our server on the way, and you should know that rather than assume otherwise. The access token needed to write to your drive is held on the server and never given to the device, so the upload is made by the server on your behalf: your backup — including your transcripts — is readable by our server for the moment it takes to forward it. It is not written to disk there and no copy is kept, but "we cannot read it" would be untrue and this policy is not going to say it. If that is not acceptable, do not use cloud backup; everything else in the app works without it.
| What | Goes to | Why |
|---|---|---|
| Cockpit and radio audio | Deepgram (United States) | Speech-to-text. Sent as it is captured, or in one batch after a period offline. |
| Your callsign and nearby station names | Deepgram | Sent with the audio so the transcriber recognises them. This is why accuracy improves when your callsign is set. |
| Airport identifiers near you | NOAA Aviation Weather Center | To fetch weather. Identifiers only — never your coordinates. |
| Chart requests | FAA (aeronav.faa.gov) | To download terminal procedure charts. |
| Your network address | ipapi.co | Only when GPS is unavailable and the app falls back to an approximate location. The app shows a prominent warning whenever this is in use. |
| Photographs of your Hobbs and tach meters | OpenAI, via our server | Only when you ask for a photograph to be read. The image is sent, the number comes back, and our server keeps neither. |
| What you type when asking for a checklist draft | OpenAI, via our server | Only when you use drafting. Your description and the aircraft you name are sent, together with the titles of sections you already have so the draft extends rather than repeats them. The items inside your existing checklists are never sent. |
| Your name, email and payment details | Paddle, if you subscribe | Paddle is the merchant of record: they take the payment and handle the tax. We never see or store card details. What comes back to us is a customer and subscription id, what was paid, and when the period ends. |
| Sign-in token, then your email and name | Our server | An account is required to use the app at all. It is what lets the paid-per-request features be metered, and what lets a backup be written to your own drive. |
| Your backup, if you turn cloud backup on | Your own Google Drive or OneDrive, via our server | The server holds the token that can write to your drive, so it makes the upload for you. It forwards the file and keeps no copy. See above for what a backup does and does not contain. |
Audio is sent to Deepgram, Inc. so it can be transcribed; there is no on-device speech recognition in this version. Deepgram processes it in the United States. We do not keep a copy on our servers — the audio passes through to Deepgram and the resulting text comes back to your phone.
Deepgram's handling of that audio is governed by their own terms and by the account we hold with them; their retention and model-training practices are theirs to state, not ours, and we will not characterise them here beyond pointing you at the source. Their privacy policy is at deepgram.com/privacy.
Two features send data to OpenAI, and both only when you ask for them: reading a number off a photograph of a meter, and drafting checklist sections from a description you write. Neither happens on its own, and the app works without either — meter figures can be typed and checklists written by hand.
Both go through our server, which holds the API key so it never reaches your device. The server passes the request on, returns the answer, and stores neither the photograph nor the text. Point your camera at a meter rather than at anything else you would not want processed in the United States: whatever is in the frame is what gets sent.
OpenAI's handling is governed by their own terms. Their privacy policy is at openai.com/policies/privacy-policy.
An account is required to use the app at all, free or paid. Signing in with Google or Microsoft tells us three things: a stable identifier for you at that provider, your email address, and your display name if the provider supplies one. We never receive your password, and we do not request access to your mail, contacts, calendar, or any file in your drive other than the single backup this app creates. (Sign in with Apple is described in the app for a future iOS build and is not currently offered on any platform.)
We store the identifier so that the paid-per-request features — transcription, gauge reading and checklist drafting — can be metered and rate limited per account. Your session is a signed token held on your device; it expires after fourteen days, which is why the app keeps working offline for that long and then asks you to sign in again.
An account record is created the first time you use the app while signed in. It holds:
Separately from the account record, the server holds the access and refresh tokens that let it write to your drive on your behalf. They are kept out of the web root, they are never sent to your device, and they grant access only to files this app created — not to the rest of your drive. Signing out discards the session; revoking the app's access in your Google or Microsoft account settings ends it from your side at any time.
The ledger records that a request happened and what it cost. It does not hold what was in it: not the audio, not the transcript, not the photograph, not the text you typed, and not the checklist that came back.
It is append-only, which is deliberate and worth knowing: entries are never edited or deleted, and a correction is written as a further entry. That makes the history of an account something you can check, and it means a line about your usage stays there while the account does.
A small number of people operate this service and can open an administration page showing account records — the list above, and no more. They can change roles and balances, and every such change is recorded with who made it. They cannot see your transcripts, recordings, photographs, checklists, flights or position, because none of that is on the server at all.
Signing in with Apple and choosing Hide My Email gives us only a relay address. That works fine — we do not need your real one.
You can delete any flight and all of its audio, any meter log and its photographs, and any checklist and its history, from within the app at any time. To delete your account and everything we hold about it, email privacy@logoslegacy.com from the address you signed in with; we will action it within 30 days. That removes your account record, your roles and your usage history, subject only to the financial records named under Retention above.
You can also ask for a copy of your account record and its ledger at the same address.
If you are in the UK, EEA or Switzerland you have rights of access, rectification, erasure, restriction, portability and objection under the GDPR. If you are a California resident you have equivalent rights under the CCPA and CPRA. The same address handles both.
Our lawful basis for processing is performance of a contract — you asked the app to transcribe your flight, or to read a photograph, and an account and its ledger are what let us provide and meter that — together with legitimate interest in operating the service and preventing abuse of features that cost money, and legal obligation for anything we must keep for accounting.
MyFlightHelper is not directed at children under 16 and we do not knowingly collect their data.
Our servers and Deepgram's are in the United States. If you use the app from outside the US, your audio is transferred there for processing.
The version and date at the top of this page always identify what is current, and they are the only way to tell whether anything has changed — the app does not display this policy or announce a change to it. If a change materially affects what leaves your device or who receives it, we will put a note on the home page as well.
Logos Legacy Venture LLC, Missouri, United States — privacy@logoslegacy.com