Privacy
Your trip stays on your phone.
- Sent to On Report’s server:
- what you share with family (encrypted on your phone first)
- what the codes you correct mean
- a count of crew per airline (never who)
- the flights you look up or ask about in Loads
- only if on: name, seat and flights (Crew on this flight)
- only if on: push token, coming flights (Inbound at the gate)
- The Privacy page lists everything else, and when.
- Never sent: your limits, block, credit, pay and sick time.
- No ads. No account needed. You can turn each one off.
On this phone
Your flights, notes, and settings are saved in this app’s storage on this phone. Limits, block, credit, pay, and sick time never leave it.
On iPhone and iPad, iCloud sync (on unless you turn it off in Settings) keeps what you type the same on your own iPhone and iPad: van times, hotels you type and the ones it remembers for you (with their phone numbers), hotel notes, your Only me things to do (layover tips), notes, codes you taught, your usual commute flights and home airports, your name, seat, airline, home and base, and your clock, base-time and weather display choices. It goes through your own iCloud, under your Apple ID, and never to On Report’s server. Your schedule, limits, block, credit, pay and sick time are not part of it.
FLICA files from Downloads, on iPhone and iPad: if you choose your Downloads folder (Settings › Calendar › Read FLICA files from Downloads), On Report looks in that folder only after you tap a FLICA month, and opens only the FLICA files (.vcs or .ics) downloaded since, at most three; if more than one came, it asks which one to read. It reads it on this phone, keeps no copy, changes nothing in the folder, and never sends it. Which folder you chose stays on this phone; Stop forgets it.
On Report’s Safari extension, on iPhone and iPad, if you turn it on in Safari: it works only on your airline’s FLICA site. For 10 minutes after you open a month, on any page of that site except the sign-in page, it may show Continue to that month; only your tap opens that month’s page. On the month’s page it only shows a note to tap Send, then Download, and a Sign in to FLICA button that opens your airline’s FLICA sign-in page when you tap it. It doesn’t submit, click or request anything, and it reads only the page’s address, not the page or anything you type. You sign in to FLICA yourself; the extension never sees your username or password. Safari saves the file you download, and On Report reads it on this phone. The extension itself sends nothing to On Report’s server or anyone else. On Report isn’t affiliated with or endorsed by CAE or FLICA.
At American, the same Safari extension also works on cci.aa.com, American’s CCI, and only on its calendar page. For 10 minutes after you tap Open in On Report, it shows a box there with a button for that month. Only when you tap it, it presses CCI’s month arrows until that month shows, then ⋯, Export and Save as file, and nothing else. To find those buttons it looks only at the buttons’ names and the month’s name on the page; it doesn’t read your schedule or anything you type, and it never shows on a sign-in page. You sign in to CCI yourself; the extension never sees your username or password. Safari shows the file, you share it to On Report, and On Report reads it on this phone. The extension sends nothing to On Report’s server or anyone else. On Report isn’t affiliated with or endorsed by American Airlines.
In the iPhone and Android apps, if you allow it, On Report reads your phone calendar on the phone. It keeps events that look like flights, your crew app’s reserve, day and training codes, vacation days, and sick days, and drops anything that looks like pay or leave. Sick days show only on this phone. Your calendar itself isn’t uploaded; flight details from it go to On Report’s server only for the features this page lists, when you turn them on.
It reads 32 days back to 62 days ahead. It never changes or deletes your own events.
Add my trips to a calendar, if you turn it on in Settings › Calendar: On Report adds an event for each flight on your trips (the flight, its scheduled times and its departure airport) to a calendar you pick, or to one it creates named On Report. When a trip changes, it updates or removes only the events it added. It never changes your other events, and it doesn’t read its own events back as your schedule. It writes nothing until you turn this on and pick a calendar. If you already allowed calendar access, your phone may not ask again. On Report sends none of this to its server. If that calendar syncs or is shared, for example with iCloud, Google or a work account, those events go there like any other event. On iPhone and iPad, the On Report calendar is made in your synced calendar account (usually iCloud) when you have one. Turning this off leaves the events already added.
If you allow location, the apps check where the phone is when you open Loads, only to start the search from your home airport to your base when you’re near home, and from base to home anywhere else. The location is compared with the airports on the phone and is never kept or sent.
If you’ve already allowed location, the app also checks roughly where the phone is to ask about a commute flight you may have missed. This happens only while the app is open, from 15 minutes after the flight’s departure until its arrival. The location is compared with the departure airport in the app’s own list and is never stored or sent. On Report never asks for location for this.
Codes you correct are saved on this phone. While Share what my codes mean is on (it is on until you turn it off in Settings › My schedule), the phone sends On Report’s server your airline, whether you are a pilot or FA, the code, and what you chose it means (like RVA = Reserve), with a scrambled (hashed) copy of this phone’s device key. It never sends the label you typed, your calendar or its name, or any date or time. Other crew at your airline see only how many phones agreed, never who. Turn it off, or tap Delete my sharing, and this phone’s answers are deleted from the server; an answer no phone has sent again in a year is deleted on its own. They can also go inside a sample you send yourself: in Settings › My airline’s schedule didn’t read, Include the codes I’ve taught (airline, pilot or FA) is off unless you check it, and the sample shows them (like Codes taught: VS = Vacation; RVA = Reserve) before you send it.
A schedule sample (Settings › My airline’s schedule didn’t read › Make a sample) is made on the phone and sent only by you, from the share sheet, to support@onreport.app. It keeps only events that name an airport, and blanks emails, phone numbers, crew names and employee numbers before you see it. You see all of it, blanks included, and can delete anything else before sending.
The next-flight card is on unless you turn off Next flight on the lock screen in Settings. It shows your next flight’s number, airports, times, report time, hotel van time if you set one, trip, and countdown on the lock screen, where anyone holding the phone can read it without unlocking it. The phone makes the card itself; to do it, it sends nothing about your trip anywhere unless you turn on Live gate and delay (below). The home-screen widget shows your next report or out time and trip day the same way. Reminders (before report, hotel van, short call, LATT) are notifications the phone makes itself; the van reminder names the hotel, and a notification can show on the lock screen unless your phone hides previews.
The app lock covers On Report’s own screens. It does not hide the lock-screen card, the widget, or the app’s thumbnail in recents on Android 12 and earlier, and it does not encrypt what the app stores on the phone; your phone’s passcode encryption does that. Turn the card and the widget off in Settings if you want the lock to cover everything.
Until you read your calendar or import a file, the trip on screen is an example. It is not a live schedule and it is not connected to any airline system.
Family sharing
Family sharing starts only when you send someone an invite. From then on, the phone sends On Report’s server the flight number, city pair, and times (departure and arrival) of your flights from two days ago on (or every flight in a file you import), and each night’s hotel name and phone number if you turn that on. It also sends each reserve day as on call or off, a training day as just training, and a vacation day as just vacation: never its code, sessions or times, and never a sick day. It updates itself when your trip changes; you don’t share each trip. Your phone encrypts all of this before it leaves, so On Report’s server can’t read the flights, dates, hotels or other trip details in it. It can see the name you gave each invite, which family login opened it, when your phone last updated it, and roughly how big it is. The server keeps the name you gave the invite (as readable text; it isn’t inside the encrypted trip), a random key that identifies this phone without an account, and your recovery code only as a scrambled (hashed) value, never the code itself. The code is shown to you once and is not kept on the phone. On iPhone and iPad, the phone keeps that key in its Keychain on this device only. It does not go to iCloud Keychain, and it does not move to a new iPhone or iPad. On Android it stays on the phone. Enter your recovery code in Settings › Family to keep sharing. The key is not otherwise backed up or recoverable. The keys that read your shared trip stay on this phone. So you can restore sharing on a new phone, On Report’s server keeps a locked copy of them that only your recovery code can open; the server never gets the code and can’t open that copy. Delete my sharing deletes it. On iPhone and iPad, Settings › Also keep family invite keys in iCloud Keychain is off unless you turn it on. On, a copy of the invite keys, the invite links, and the recovery private key goes to your iCloud Keychain, which Apple end-to-end encrypts. Turn it off and that copy is removed. This is separate from Sync with my iPhone and iPad. For each call to the server, it keeps a scrambled copy of the caller’s address for up to a day, so it can slow down anyone who calls too often. It does not keep the address itself. On Report’s server runs on Vercel, and its database is kept by Supabase.
A code that isn’t confirmed is shown to family as Nothing shared for this day.
A family member opens the invite’s link on their own phone (a page that can open the On Report app on iPhone, iPad or Android, then they tap Continue), and that signs them in on that phone with no email or password. The link carries the key to read your trip; that part of the link never reaches On Report’s server. A key works on one device only. To follow you on another device, they need a new invite from you. The server keeps a random id for that login and a session that lasts a year from the last time they look. In On Report, the phone keeps that session in the Keychain (iPhone and iPad) or encrypted with a key in the Android Keystore (Android), and nothing else of theirs. If they add an email so they can sign in on another device, the server keeps that email and a scrambled copy of their password; a login made with an email also keeps the name typed with it. The invite works once and expires after 7 days. Revoking them deletes their link and their encrypted copy of your trip from On Report’s server, and your phone stops sharing with them, so they get nothing new from you. Others you invited aren’t affected, and inviting the same person again makes a new key. Anything already shown or saved on their phone, including a copy the app already opened, stays on their phone. Their login and its sessions are deleted too, unless another crew member has also invited that phone. When you revoke the last person, the encrypted shared trip is deleted too. If your phone hasn’t updated it in 14 days, it is deleted.
Copies already on a family phone stay there. Backups may keep old copies, from before encryption, for up to 7 days under our current plan.
You can delete it yourself in the app. Delete my sharing, in Settings › Family, deletes everything the server keeps for this phone: your invite links, the family logins only you invited, the encrypted shared trip, your name on Crew on this flight and the reports you sent, your Loads requests, the numbers you gave other crews and your Loads credits, the scrambled recovery code, the airline codes you shared and what they mean, your line in the crew count (airline and seat), and which purchase this phone uses for Pro, and when it ends. The trip on your phone stays. Copies already on a family member’s phone stay there. Backups of On Report’s server may keep older copies, from before family sharing was encrypted, for up to 7 days under our current plan. Delete my login, on the family page or in On Report, deletes a family member’s own login, with its password and their links to you.
Can’t open the app any more? Email support@onreport.app with the name on your invite, or the family login’s email, and we delete the sharing or the login for you.
Crew on this flight
Crew on this flight is off unless you turn it on. It sends your name, your seat, and the flight number, date, and city pair of your flights, so other On Report users on those flights can see you. Any On Report user who lists one of those flights sees who has turned this on for it; a phone can list up to 20 flights a day, from yesterday to two days ahead. A deadhead on the flight is included and labeled. Turn it off and your name comes off every flight at once. The flight numbers are kept one more day, so no phone can look up more flights than one person flies, then deleted. It is not the airline’s crew list. Crew on this flight is not end-to-end encrypted: other On Report users have to see it, so On Report’s server can read it too. Crew on this flight stays off for an airline that uses FLICA until a later update.
A name with profanity or a slur is not listed. Each name has Report and Hide this person. Report sends the server the flight, the name you see, and a scrambled code made from this phone’s device key, never your name. A name reported by 3 phones is hidden from everyone until On Report has looked at it. A report is deleted after 90 days; if On Report hides the name for good, its flight and name are kept without the code. Hide this person is kept on this phone only.
Pro purchases
The Pro purchase check is separate: when Pro is on sale, the phone asks the App Store or Google Play whether this phone’s account has Pro, and when it does and this phone has a device key, it sends the store’s receipt with that key to On Report’s server.
If you subscribe to Pro, the App Store or Google Play takes the payment. The phone asks the store whether you have Pro. When you have Pro and this phone has a device key, the phone also sends the store’s receipt with that key to On Report’s server, which checks it and keeps which purchase it was and when it ends, so the server can tell a subscriber from a free phone. It never sees your payment details or your Apple or Google account. On iPhone and iPad that receipt is the store’s signed purchase, and On Report’s server checks the signature itself and does not send it on to Apple. On Android that receipt is the Play purchase token, and the server checks the token with Google. The website does not ask the store, and while Pro is not on sale the phone sends no receipt.
Links to other sites
While the app is open, your phone also checks on its own in the hour and a half before each of your departures: it asks nasstatus.faa.gov (the FAA) for airport delay programs, aviationweather.gov (NOAA) for the weather and forecast at your airports, and fly.faa.gov (the FAA) for your next flight’s EDCT. It asks the same when you tap Check now under Airports or FAA EDCT on a leg. These automatic checks run only while the app is open, never in the background. Weather requests carry an airport code and your IP address, and the FAA delay request only your IP address (your phone picks your airports out of the FAA’s whole list); an EDCT request carries that flight’s callsign (airline code and flight number) and its departure and arrival airports. Nothing else about your trip is sent, and each request goes from your phone to that site directly, not through On Report’s server. Weather and FAA delay answers are kept on your phone for 10 minutes.
While On Report is open, your phone reads the FAA’s airport status (nasstatus.faa.gov) at most every 5 minutes, and again when you come back to the app. A ground stop at an airport in your next 48 hours, or at 5 or more of the FAA’s Core 30 airports, shows a banner on Today. Tapping it opens Airports. The reason and the expected end come from that same feed when the FAA includes them. FAA Command Center advisories opens fly.faa.gov. Nothing beyond that FAA request is sent to On Report’s server. With Inbound at the gate on, you may get a push when an FAA ground stop starts or ends at either airport of a registered flight. It uses the flights Inbound at the gate already has. Nothing else is sent.
Links open public pages the same way, from your phone: the FAA (nasstatus.faa.gov and fly.faa.gov), NOAA (aviationweather.gov), the National Weather Service (forecast.weather.gov and radar.weather.gov), FlightAware (flightaware.com), status.onreport.app (System status, opened only when you tap it), and maps. When you tap Map, Directions or Food nearby under tonight’s hotel, your phone sends the hotel name and city to Apple Maps or Google Maps. A hotel you type for a layover city is remembered on this phone (up to three per city) and offered the next time you lay over there. Removing it from the layover where you last typed it forgets it, and deleting the app removes this phone’s copy. It goes to family only when Show each night’s hotel and its phone is on, inside the encrypted copy, and to your own iCloud when iCloud sync is on (it’s on unless you turn it off), stored by Apple under your Apple ID. On Report’s server can’t read it.
Things to do, on iPhone and iPad: when you search Apple Maps for a place, your phone sends the words you type to Apple only when you tap Search. A night with a hotel also sends that hotel’s name and the city, and the places offered are around the hotel. A night with no hotel sends the city name, and the places are around that city’s downtown. The hotel or the downtown is found from the airport in this app’s own list. The places themselves are not searched around the airport, and the search never uses your location. If you pick a place, the tip keeps only Apple’s ID for it, and its name is looked up again from Apple when the tip is shown. On Android, a Google Maps link you paste stays on the phone and opens only when you tap it.
If you agree to share Things to do tips, each new tip’s city, place name, address, category, note and, on iPhone, Apple Place ID go to On Report’s server with a scrambled ID for this phone, unless you keep that tip private. The version of the tips terms you accepted is sent the same way. Each tip is checked before other users see it, and an automated service may help check it. Other users see the tip, never your name, your airline or who wrote it. A tip waiting to be checked is deleted after 14 days. A declined tip and its reason are deleted after 30 days. When you delete a shared tip, or use Delete my sharing, it is deleted from the server. Delete my sharing also deletes the reports and blocks you made. A tip you report is hidden from you, and the report is kept 90 days. A tip reported by 3 phones is hidden from everyone until it is checked again. Opening a city’s shared tips sends that city’s code to On Report’s server with the same scrambled ID.
Nothing else goes to other servers, on the web or in the iPhone and Android apps, beyond what this page lists.
Live gate and delay
The app also asks On Report’s server whether Live gate and delay, Inbound at the gate and Loads are switched on there, at most once each time the app opens and each time you open the Loads tab, and once Loads is on, which airlines have answered a request it still keeps; those checks carry nothing but your IP address. Live gate and delay, which asks FlightAware about a flight through On Report’s server, stays off until Settings shows it and you turn it on. Then, from 3 hours before a flight’s scheduled departure until 12 hours after, the flight you open, or your next flight on Today and the lock-screen card, is looked up. For each one, the phone sends the flight number, date, departure and arrival airports, and scheduled departure time with this phone’s device key, without end-to-end encryption. The server keeps that record, linked to this phone, until a day after the scheduled departure; Delete my sharing deletes it sooner. Your name, hotel, and the rest of your trip are not sent. While it is off, no flight is looked up. FlightAware’s answer about a flight is shared by everyone who looks that flight up, holds nothing about who asked, and is deleted two days after it was fetched. To keep the daily limit, the server also counts the flights this phone adds, for a day.
Separately, when a flight is looked up, the server keeps that flight’s scheduled and actual departure and arrival times (its flight number, city pair and date) for 90 days, to work out On Report’s own on-time figures. That record holds nothing about who asked, so it isn’t linked to you and isn’t part of the flights deleted a day after the flight.
Inbound at the gate
Inbound at the gate, on iPhone and iPad, stays off until Settings › Notifications shows it and you turn it on. Then your phone asks Apple for its push token and sends that token with the device key to On Report’s server. Each time the app reads your calendar, it also sends your flights in the next day and a half: each one’s flight number, date, city pair and scheduled departure time. Your name, hotel, and the rest of your trip are not sent. Deadheads are not sent. Inbound watches only the flights your phone sends this way, up to 16 new ones a day; it never uses your family sharing or Crew on this flight. Each one is kept, linked to this phone, until a day after its scheduled departure, until it leaves your calendar or you tap Not on this flight, or until you turn Inbound at the gate off. To keep the daily limit, the server also counts the flights this phone adds, for a day.
About 2 hours before one of those flights, the server asks FlightAware which airplane is coming in for it (its flight and tail number). It asks again about 45 minutes before only if the day looks irregular, and about 40 minutes before that airplane lands to check its times (and near its gate time if its position can’t be followed or doesn’t show it at the gate). That answer is shared by everyone on the flight and holds nothing about you. The server then follows that airplane by its transponder code on adsb.lol, a public network of ADS-B receivers (positions under the Open Database License), checks the FAA’s public delay programs and, during one at the airplane’s origin, the FAA’s EDCT page for its flight, and sends your push through Apple, which receives the push token and the push’s words. adsb.lol’s positions are used live and not kept: only the airplane’s latest position, and when it was seen taking off, landing and at the gate, are held with that flight’s tracking, and they are deleted with it a day after the flight, so never more than about 26 hours.
The server keeps the push token until you turn Inbound at the gate off; your phone sends it again each time the app opens while it’s on, and one not sent for 90 days is deleted. Your flights, and what it worked out about each inbound airplane, are deleted a day after the flight. While Inbound at the gate is running, to learn each airport’s taxi time, the server keeps the minutes from touchdown to the gate, from FlightAware’s times only, with only the airport and the time, never a flight, an airplane or anything about you, for 120 days. It counts your flights for 30 days to keep the monthly limit. Turn it off, or tap Delete my sharing, and the token and your flights are deleted.
Loads and Search flights
Loads, in the Loads tab, sends nothing until you first open that tab. From then on, while the tab is open and each time you open the app or come back to it, your phone asks On Report’s server for open requests about the airline chosen in Settings, sending that airline and the device key if this phone has one (a phone with none sends a random value made for that app session and never saved; the server keeps nothing for a read). While the tab is open it also asks for answers to your own requests, sending only the device key once this phone has one; on iPhone and Android it asks that too each time you open the app or come back to it, and every 5 minutes while the app is open. When you ask about one flight, your phone sends that flight number, date, and city pair with its device key to On Report’s server. When you leave the flight blank, it sends the airline you choose, the date, and the city pair with its device key, and crews answer each flight they see: the flight number and the same answers, up to 8. Search flights sends only a date and two airports with the device key; On Report’s server asks FlightAware for that day’s published schedule and keeps the list until two days after that day, shared by everyone who searches that route and day. With 1 stop, your phone also sends the airline set in Settings, so connections go through that airline’s hubs on the way; with none set, an airline with no hub list (such as Southwest, or a regional that flies for several airlines), or no hub on the way, it uses the three hubs with the least detour. The same is asked for the legs to and from those hubs. With Pro, for each listed nonstop leaving within 3 hours the app sends that flight number, the date and the two airports with the device key, and the server asks FlightAware whether it is on time, delayed or canceled; the answer is shared like the list. You can paste up to 6 flights in one ask; each is its own request. On Report users at that airline can see a request and type open-seat and standby numbers and whether the cockpit jumpseat is open or taken, which come back to you. When you answer, only those numbers, that jumpseat answer, the flight number on a route, and the request’s id are sent, with the device key. The “Checked at” time is the time the answer was stored, shown on the departure airport’s clock; it is not a separate send. Thanks closes your request so it leaves Help a commuter and sends only that request’s id with the device key; the person who answered last is credited once. Ask for an update sends only that request’s id with the device key, and the server keeps the time you asked. The request goes back to Help a commuter for everyone at that airline, including crew who already answered. The server keeps the request, the numbers, and a credit count, never a name, and deletes a request two days after its flight; Delete removes yours sooner. If you turn on the switch under Commute, the phone sends the same request on its own for the commute flights it knows, to work before a trip and home as it ends. The example trip shows a sample request and answer on this phone and never sends it. Nothing is scraped from any airline system.
Late flight home (Settings › Commute) stays off until you turn it on. Then, once after a trip’s last flight is in at an airport that isn’t one of your home airports, and when you tap Check again, the app makes that same search from that airport to each home airport without opening the Loads tab, and for at most 4 listed flights that should already have left it sends the flight number, the date and the two airports with the device key; the server asks FlightAware whether each has left and when it is now due out, and the answer is shared like the list. Nothing about it is kept linked to this phone beyond the counts below; the result stays on this phone.
Crew count
So On Report knows how many crew use it at each airline, the iPhone and Android apps send, once a day, the airline and pilot or flight attendant chosen in Settings, with a scrambled form of the device key. The server keeps one row per phone: that airline, that seat, the day it last checked in, and, if you answered Today’s “Does your trip look right?”, Looks right or Something’s off. Never a name, a trip, a calendar or a place, and the row can’t be matched to family sharing. Turn off Count me in my airline’s crew numbers in Settings › My schedule, or Delete my sharing, and the row is deleted. Family mode never sends it.
Limits and counts
On Report’s server counts the lookups and searches made with each device key, per day and per 30 days, to enforce limits, and keeps those counts only for that window, up to a day and up to 30 days, after which the next lookup or search starts the count again.
The Limits page is a 14 CFR 117 worksheet for the trip on screen (yours, or the example). It is computed on the phone and nothing is sent. It is not a company release and it is not legal advice.
On Report is published by Off Duty Studios, LLC, a New Mexico limited liability company. It is not affiliated with any airline. There is no advertising and no analytics beyond the crew count above.
Updated November 15, 2026.