Conaer Aviation
Privacy policy
Last updated 2026-07-31
We wrote this so you can actually read it. It says what we collect, why we collect it, who else sees it, and how to get it back or get it deleted.
We run no analytics. No Google Analytics, no advertising pixel, no session recorder, no product analytics tool, no tracking cookie. We do not sell your personal information and we do not share it for advertising. We never have.
Who we are
Conaer LLC runs the Conaer Aviation products at app.conaeraviation.com. That is the Alternate Engine for Part 121 dispatchers, Conaer Ground School, Dispatch Prep, the trainer at /fly and the safety management trainer at /sms.
For anything about your personal information, write to privacy@conaeraviation.com. A real person reads it.
What we collect and why
Your account
- Email address. It is how you sign in and how we reach you about the account. We need it to give you an account at all.
- Password. Stored only as a PBKDF2-HMAC-SHA256 hash with 200,000 rounds and a random salt that belongs to your account alone. We cannot read your password and neither can anyone who steals the database file.
- Account settings. A display label, your role, your daily usage limits, and whether the account is bound to a particular operator. The operator binding is set by an administrator and it is what stops one carrier account seeing another carrier configuration.
- Google sign in, if you choose it. We ask Google for your email address and basic profile, and we keep the email address and whether Google says it is verified. We do not receive your Google password.
Your planning defaults
If you set them: a home base airport identifier and how far ahead of departure to prefill the estimated time of arrival. That is it. We keep them so the console does not ask you the same two questions every shift.
How much you use it
A count per account per day of how many requests you made, and how many of those were the expensive kind. We use it to apply fair use limits and to keep a leaked account from running up a bill. It is a number, not a history of what you looked at.
Your study progress
If you are signed in, Ground School and Dispatch Prep progress, and the trainer logbook, rank and per-question right and wrong counts, are saved against your account so they follow you to another device. If you are not signed in, that progress stays in your browser and never reaches us.
Problem reports
When you flag a question or a piece of content as wrong, we store what you wrote, which screen and question it was on, the page address, your account identifier and your browser user agent string. We need the technical details to reproduce the problem. This is the only place we store a user agent string.
Planning records
Every run of the Alternate Engine is written to an audit log with the time, the destination, the estimated time of arrival that was used, the operator identifier and the full result. This is the record of what the tool said and when it said it, and a tool that has to hold up as if it were legally binding needs one.
Worth knowing: that log does not carry your account identifier. It records that a verdict was issued for a destination at a time under an operator ruleset. It does not record which person asked.
Files you upload
- Operations specifications and chart supplement PDFs are stored on our server so the engine can use the rules in them. They stay until the operator record is deleted.
- A knowledge test report you upload to the exam decoder is read in memory to pull out the codes and is not saved to disk. The image does go to our language model provider when the report is a photo or a scan, because that is how the codes get read. See the sharing section below.
Location, only if you turn it on
The console has a location toggle and it is off until you switch it on. If you switch it on, your browser sends one set of coordinates so we can find the nearest airport and show you its weather. We do not store the coordinates and we do not track you.
Technical and security data
- Our host keeps ordinary web server request logs, the same as any web service.
- When a sign in attempt fails we hold the network address and the submitted username in memory for about a minute so that repeated guessing gets throttled. Neither is written to our database.
Cookies
Three, all of them ours, all of them necessary to sign you in and keep you signed in safely. No advertising cookies and no analytics cookies, because there is no advertising and no analytics.
Your signed in session. HttpOnly, Secure, SameSite=Lax, path /, expires after 30 days. Deleted when you sign out.
An older access token cookie that we still accept for API clients. HttpOnly, Secure, SameSite=Lax, path /. Cleared when you sign out.
A one time random value that protects Google sign in from being forged. HttpOnly, Secure, SameSite=Lax, scoped to /auth, expires after 10 minutes, and deleted the moment sign in completes.
What we store in your browser
Some things live in your own browser storage and never leave it unless you are signed in and the app syncs your study progress. Clearing your browser storage clears all of it. None of these hold a password, a session token or an email address.
Light or dark, so the app opens the way you left it.
The same choice for the trainer at /fly.
Up to five airports you recently searched, with the identifier and the city, so they are one tap away next time.
Whether you turned the location toggle on or off.
A timestamp, so a one time animation does not replay on every visit.
The last route pack you loaded, kept so the console still works when you lose signal.
Which product you opened last, so the home page can offer it first.
Ground School progress, your answers and your review queue.
Dispatch Prep progress, and the revision marker used to merge it with the copy on your account without losing answers.
State for the dispatch trainer.
State for the safety management trainer at /sms.
The console also keeps route packs in IndexedDB under a store called packs, and the app registers a service worker that caches pages and images so it opens offline. Both are caches of the app itself, not records about you.
Who we share it with
We do not sell your personal information and we do not share it for advertising. These are the companies that handle data on our behalf or that your browser contacts when you use the site.
Our hosting provider. The application and the database run there, so Render holds everything described on this page.
Our language model provider. We send it raw NOTAM text to turn into plain English, approach chart PDFs to extract minimums from, and a knowledge test report image when you upload a photo or a scan to the exam decoder. We do not send it your email address, your password or your account record.
An alternative provider for the same routing step. It is not enabled in our production configuration today. If we ever switch to it we will say so here before we do.
Only if you choose Continue with Google. Google tells us your email address and whether it is verified. Google Fonts also serves the typeface on every page, which means your browser sends Google your network address and browser details when a page loads.
Password reset messages are sent through an outbound mail service, which necessarily handles your email address. We will name it here once it is fixed for launch.
We fetch charts, airport data, NOTAMs, weather and forecasts from FAA and NOAA services, including the Aviation Weather Center. Those requests carry an airport identifier, a route or a time. They do not carry anything about you.
The console map loads tiles from ArcGIS, from OpenStreetMap through CARTO, and radar from Iowa State University. Loading a map tile tells that provider your network address and roughly which area you are looking at. The Leaflet mapping library is loaded from unpkg.com.
We will also hand over information if the law requires it, for example a valid subpoena or court order, and we will tell you when we are allowed to. If the business is ever sold or merged, account data would transfer with it, and this policy would follow it until we told you otherwise.
How long we keep it
- Your account for as long as you have one, and then until you ask us to delete it.
- Sign in sessions for 30 days, then they expire and get swept from the database automatically.
- Password reset links for 30 minutes, single use, then deleted.
- Study progress and usage counters for as long as the account exists.
- Uploaded operations specifications until the operator record is deleted.
- The alternates audit log indefinitely. After 90 days the bulky result is moved to a compressed archive with a checksum so it can be proved unaltered, and the row keeps the time, destination, estimated time of arrival, operator and a summary. We keep this on purpose. It is the record of what a dispatch planning tool told a dispatcher, and it carries no account identifier.
How we protect it
- Everything runs over HTTPS, and we send a strict transport security header so your browser refuses to fall back to plain HTTP.
- Passwords are salted and hashed with 200,000 rounds of PBKDF2-HMAC-SHA256 and compared in constant time.
- Session cookies are HttpOnly and Secure, so page scripts cannot read them, and SameSite=Lax, so another site cannot ride them.
- Sign in attempts are throttled by network address and by username, so guessing a password at scale does not work.
- Changing your password kills every existing session on the account before it issues the new one.
- We send a content security policy, a no-sniff header and a referrer policy that keeps the airports and routes in a page address from leaking to other sites.
- Accounts can be bound to one operator, and a bound account is refused outright if it asks for another operator ruleset.
No system is perfectly secure and we will not pretend otherwise. If you find a hole, please write to us before you write about it anywhere else.
Your rights
Wherever you live, you can ask us to:
- tell you what personal information we hold about you and give you a copy
- correct anything that is wrong
- delete your account and the personal information attached to it
- stop processing it, or object to processing that rests on our legitimate interests
Write to privacy@conaeraviation.com. We will answer within 45 days, and we will tell you if we need longer. We may have to check that the request really comes from you, usually by asking you to send it from the address on the account. We will not charge you and we will not treat you worse for asking.
One limit, stated plainly. Deleting your account does not remove rows from the alternates audit log, because that log carries no account identifier and exists as a record of what the tool computed. We keep it as a business record.
California residents
If you live in California, the California Consumer Privacy Act as amended by the California Privacy Rights Act gives you specific rights. Here is the disclosure it asks for.
Categories of personal information we have collected in the last 12 months: identifiers (your email address, an account identifier, a network address held briefly for sign in throttling); internet or network activity (your browser user agent string, only when you file a problem report, plus your usage counts); geolocation data (only if you switch the location toggle on, and we do not store it); and commercial information only if we ever charge you, which we do not today.
Where it comes from: directly from you, from Google if you use Google sign in, and from your browser when you use the site.
Why we collect it: to run your account, to save your settings and study progress, to apply fair use limits, to keep the service secure, to fix defects you report, and to keep the planning audit record.
Who we disclose it to for a business purpose: the service providers named in the sharing section above.
Sale and sharing: we do not sell personal information and we do not share it for cross-context behavioral advertising, and we have not done either in the last 12 months. We do not sell or share the personal information of anyone under 16. Because we do not sell or share, there is nothing to opt out of, so you will not find a Do Not Sell Or Share My Personal Information link on this site.
Sensitive personal information: we do not collect it and we do not use it to infer anything about you, so there is nothing to limit. Your password is stored only as a hash we cannot reverse.
Your rights: to know what we collect and to get a copy, to delete, to correct, to opt out of sale or sharing, to limit the use of sensitive personal information, and not to be discriminated against for exercising any of them.
How to exercise them: email privacy@conaeraviation.com. An authorized agent may act for you if they show us written permission signed by you. We will verify the request before we act on it.
Retention: the periods are in the section above.
If you are in the EU or the UK
We are a small United States business and our servers are in the United States, so using Conaer from Europe means your information is processed in the United States. If we take on European customers at any scale we will put the standard contractual clauses in place with our providers and say so here.
Conaer LLC is the data controller. The legal bases we rely on are:
- Performance of a contract. Running the account you asked us for. That covers your email address, your password hash, your settings and your study progress.
- Legitimate interests. Keeping the service secure and free of abuse, fixing the defects you report, and keeping the planning audit record so the tool can show what it said and when.
- Consent. Sharing your location, which is off until you turn it on and which you can turn off at any time.
- Legal obligation. Where a law requires us to keep or produce something.
You have the rights the GDPR gives you: access, rectification, erasure, restriction, portability, objection, and withdrawal of consent at any time without affecting what we did before you withdrew it. Email privacy@conaeraviation.com. You can also complain to your national data protection authority, or to the Information Commissioner Office in the United Kingdom, and we would rather you came to us first so we can fix it.
We do not make decisions about you by automated processing that produce legal or similarly significant effects.
Children
Conaer is built for pilots, student pilots and aircraft dispatchers. It is not directed to children under 13 and we do not knowingly collect personal information from a child under 13. If you believe a child under 13 has given us personal information, email privacy@conaeraviation.com and we will delete the account and the information.
Student pilots can be young, so to be clear: nothing here is aimed at children, and we ask for no more than an email address to open an account.
How to contact us
Email privacy@conaeraviation.com for anything on this page, including a request to see, correct or delete your information. Tell us what you want and which email address the account uses, and we will take it from there.
Changes to this policy
When we change something that matters, we update the date at the top of this page and, for a change that affects how we handle your information, we email account holders before it takes effect. We review this page at least once a year. If we ever add analytics, a tracker or advertising, this page will say so on the day it happens, and it will not say it quietly.