last updated 2026-09-21 · aerology.ai and app.aerology.ai
As of the date above there is no account here, we do not ask who you are, and the only thing you tell us is which flights you are asking about. What follows is what actually happens to that — read off the code and the infrastructure on that date, not off a template.
A forecast needs the flights in your trip, and — only if you move it — the minimum connection time you want us to assume. That is the entire input. Nothing else about you is collected or required.
Today there is no account, no password and no sign-up. No form on either site asks
for your name or your email address. The one address on the landing page is an
ordinary mailto: link: if you write to us, we have your mail, the
same as any other correspondence.
When the app answers a forecast, it writes one line to its own log:
That line carries no name, no account, no cookie value and nothing derived from your IP address. The fingerprint is a property of the itinerary, not of you: two strangers looking up the same trip produce the same one.
Those lines are copied into a data warehouse we own, where each day's rows are deleted 365 days after they arrive. We keep them to answer two questions: how much the service is being used, and whether anyone moves the connection minimum.
The app writes a few other kinds of line to the same log, and they are copied to the warehouse too: for the results page's history chart, the same fingerprint and leg count as a forecast; when you look up flights, the two airports you asked about; when it loads the national figures on the front page, whether it could read them and how old they were; and when it turns away a request that did not come from one of its own pages, which address was asked for and which request headers were missing or pointed elsewhere. None of them carries a name, an account, a cookie value or anything derived from your IP address.
Two things that are true and easy to leave out. When a flight cannot be resolved at all, the app logs that flight's reference so we can report it upstream. And Google Cloud keeps its own web-server log for the app, the way any web server does: your IP address, your browser's user-agent string, and the URL you asked for — which, for a forecast, contains the flight references. We do not copy that log into the warehouse; it stays in Google Cloud Logging, where this project's default bucket keeps 30 days. We count loads of the app's two pages from that log where it stays, by page, and the count keeps nothing about any request.
This landing site is static hosting and sends us no request logs at all — we have
no per-visit record of it. The exception is /llms.txt, a
machine-readable descriptor for automated clients, which is served by a small
service of ours and is logged like the app.
The app sets no cookies of its own, and it keeps nothing about you in your browser — no cookie, no local storage. Neither does this site.
aerology.ai as a whole is not cookie-free, though, and we would
rather say so than write a sentence we would have to defend. Two other hosts under
the domain set cookies on .aerology.ai itself, which means your
browser sends them to every subdomain, this one and the app included:
logbook.aerology.ai, our newsletter, is hosted by Substack and sets
_gcl_au — a Google Ads cookie, about 90 days. Substack controls the
tags on that page; we do not.
at-booking.aerology.ai, a page left over from the site that
preceded this one, carries a Google Analytics tag and sets its cookies. It is on
the list to retire.
Nothing we run reads either of them.
While the app is still in preview it sits behind a Google sign-in gate (Identity-Aware Proxy). That gate is Google's mechanism rather than part of the app, and it comes off when the beta opens.
storage.googleapis.com.
The forecasts themselves are ours. They are computed by our own model service, in our own Google Cloud projects, from the flights you gave us. Your trip is not sent to a third party to be answered.
Three things on this page describe the beta as it stands rather than what comes next:
If any of this changes, this page changes first, and the date at the top says when.
Write to privacy@aerology.ai. If anything on this page turns out not to match what the software does, that is a bug — tell us, and we will fix the page or the code, whichever is at fault.