Privacy Policy

• When you request access:your first name, last name, email address, and whatever you write in the “reason for access” box. That reason text is kept as you wrote it, so please don't put anything sensitive in it.
• Your password: stored only as a salted, deliberately slow one-way scramble (scrypt). The password itself is never written down, never logged, and cannot be read back — not even by the owner.
• What you build: your trips and their names, your travel preferences and weightings, the results Astra calculated for you, and any destinations you save or add to a comparison.

• Account activity: when your account was created, verified, approved, and activated; when you last signed in; and how many times you've signed in.
• Administrative history: approvals, denials and suspensions are written to a permanent, tamper-resistant log. That log is deliberately never deleted.
• Your sign-in session: one cookie, described below.
• Abuse-prevention records:to stop password guessing and signup spam, the sign-in, access-request, password-reset and account-activation pages record where each attempt came from, along with the type of request and a timestamp. Rather than your IP address itself, we store a scrambled one-way version of it, which is enough to tell one visitor’s attempts apart from another’s and nothing more. These records exist only for rate limiting and are not used to track you.

Everywhere else in the product, rate limits are counted against your account, and your email address is likewise fingerprinted rather than stored in those records.

ASTRA sets exactly one cookie, astra_session. It holds a random string and nothing else — no name, no email, no account details. It lets the site recognise you as signed in, expires after seven days, and cannot be read by JavaScript in your browser.

There are no advertising cookies, no tracking pixels, no analytics cookies, and no session recording or replay. That is why the site has no cookie banner: the one cookie it sets is strictly necessary for signing in.

ASTRA runs on a handful of outside services. Each one is used for a single job, and each gets only what that job needs.

• Neon — the database, hosted in Amazon's US East (Northern Virginia) region. Everything described above is stored here.
• Vercel — hosting. Serves the site and handles the network traffic between your browser and the app.
• Resend — sends the site's emails (verify your address, approval, activation, password reset). Receives your email address and the message itself.
• Duffel — the travel data provider used for flight and hotel prices. It receives only the search: airport codes, travel dates, the number of travelers and rooms, cabin class, and the destination's coordinates. It does not receive your name, your email address, or your ASTRA account identifier, and no booking or passenger details are ever sent.
• Sentry — error and performance monitoring, so problems can be found and fixed. Reports are filtered before they leave the site: your email address, username, IP address, session cookie and authorisation headers are removed, as are the location headers the hosting provider adds. Your opaque account identifier is attached so an error can be traced to a specific session, and ordinary technical details — browser type, the page you came from, and your language setting — may be included.
• Inngest — runs trip builds in the background. Receives only internal record identifiers, not personal details.
• An exchange-rate service and an uptime monitor — receive currency codes and a health check respectively. Neither receives anything about you.

Your information is not sold, rented, or handed to anyone else. Nobody buys advertising here, because there is no advertising.

• Payment card or bank details — ASTRA takes no payments and has no way to.
• Your phone number, postal address, or date of birth.
• Passport, visa, or any government identification.
• Your location, beyond the airports and destinations you type in yourself.
• Anything for marketing, profiling, or resale.

Your account and your trips are kept for as long as ASTRA exists, unless you ask for them to be removed. Expired sign-in sessions, one-time email links and abuse-prevention records are cleared out by routine housekeeping; that housekeeping runs opportunistically rather than on a fixed schedule, so a record may sit for a few days before it is removed. The administrative log of approvals and suspensions is kept permanently.

You can delete saved destinations and clear or change comparisons yourself, at any time, and those deletions are permanent. If you cancel a trip build before it finishes, its results are discarded rather than kept.

There is currently no self-service way to delete your account. If you want your account and your remaining trip data removed, email trevor.elrod@astratraveler.com and it will be done by hand. The same address works for asking what is held about you, or for getting something corrected.

Traffic is encrypted in transit. Passwords are stored using a slow, salted one-way function. Sessions are checked against the database on every request and can be revoked. Changing your password signs out every other session. Access to every page and every trip is checked against your own account.

That said, this is a personal project maintained by one person, not a company with a security team. It has not been independently audited. Please don't store anything here you would be seriously upset to lose or to have exposed.

ASTRA is not intended for children under 13, and accounts are only created for people who have been invited directly.

This policy carries a version number, shown below. If it changes materially, the version changes with it and you may be asked to accept the new version. The version you agreed to was recorded when you requested access. See also the Terms of Service.