Constellations is a travel-planning app run from constellations.li, on the web and as a phone app. This policy describes what information we collect, why we collect it, and what choices you have. It covers the website and the phone app alike; they share one account.
Constellations is operated by Nicholas Steenson, an individual based in New Zealand, under the name NocturnalNick. "We" in this policy means that operator.
Constellations is for people aged 16 and over. We don't knowingly collect information from anyone younger; if you believe someone under 16 has an account, tell us at the address under Contact and we will delete it.
Last updated: 20 November 2026.
Key points
The short version, for everyday reading. The sections below are the full policy and take precedence if anything seems to differ.
- Your trips are private by default. Other people only see what you share with them.
- The app reads your phone's or computer's own location only when you tap something that needs it (setting your location, sharing a journey's progress, working out a pickup), and only while the app or site is open. It never reads location in the background.
- We don't sell your data, run ads, or use analytics or tracking cookies. There's no cookie banner because there's nothing to consent to.
- Forwarded booking emails are read to extract the booking, then the message content is deleted on a 90-day cycle at most. Confirmations our built-in rules don't recognise are read by an AI service (Anthropic) for the same purpose, along with any PDF attached to them. Connie, the assistant, also runs on Anthropic's AI models: what you write to her, and the trip details she looks up to answer, are sent to Anthropic to produce her reply. A second AI service (TypeSafe) reads those emails first, to judge whether each one is a booking at all, and reads messages sent to Connie to decide which AI model answers them. It can also check the results afterwards: whether every booking in an email was found, and, once a conversation with Connie goes quiet, how well she handled it. It also sorts what you send through Help & feedback, for us. When you add an event by hand, it reads the event's name (and venue, if you've picked one) to suggest what kind of event it is.
- Nothing of yours goes to either AI service (Anthropic or TypeSafe) until you allow it. New accounts are asked, on Home or in Connie, the first time; accounts that existed before this choice was added start with it allowed, as the app worked until then. Turn it off at any time under Settings → Connie. While it's off, Connie doesn't answer, your Help & feedback messages and event names aren't sorted by AI, and a forwarded or uploaded booking our built-in rules don't recognise isn't read: you're told how to allow it (by email at most once a day for forwarded ones), and when you allow it, the most recent of those (up to 20, from the last 30 days) are read then.
- A short list of service providers is involved in running the app (email delivery, flight data, weather, drive times, AI, error reports, push notifications, hosting). Each receives only what its job requires, and each is named below.
- You can export your data or delete your account at any time, from the Profile page. Deleting is confirmed through a link we email you, and is permanent once you confirm. A few things other people rely on are kept or handed to them; see Deleting your account.
Information we collect
- Account info: email, display name, a password hash, and a profile picture if you add one. If you sign in with Google, Microsoft or Apple, we also store the identifier that provider gives us for you, so future sign-ins link to the same account. We also keep the sign-in tokens that provider issues for that sign-in. We use them only to show you which address is connected; we don't use them to read anything else from your Google, Microsoft or Apple account.
- Trip data you create: flights, accommodations, transit, activities, events, documents, checklists, to-dos, expenses, attachment links, and notes you add. This includes details of other people that you enter: the names printed on a booking, and the email address of someone you invite or send a postcard to.
- Location from your travel: the arrival points of travel you add. Your "effective location" shown to others is derived from these and from a location you set (next), under the visibility rules described in Sharing trips.
- Location from your device. The app reads where your phone or
computer is only in the three cases below. Each starts with a tap
from you, your phone or browser asks your permission first, and
the position is read only while the app or site is open on screen.
Location is never read in the background, and the phone apps
don't ask for background location access.
- Setting your location. Update on your profile reads where your device is, once, and stores that point. You see the exact point. Other people see only the nearest town, or an area about 40 km across where no town is near. It stays until you update it again. To remove it, choose Remove on the location card of your profile; you're then placed only by the trips you share, like someone who never set one.
- Sharing a journey's progress. On a train, bus, ferry or drive you're travelling on, you can share your progress live or send a single update. Before a flight, train, bus or ferry you can also say you're on your way to the airport or station. This uses your device's precise (GPS) location. While you're sharing live, a new position is sent at most every two minutes, or after you've moved about 150 metres. We keep only the latest position for that leg, not a trail of where you've been. The people who can see that leg see how far along you are and when you're expected to arrive; they aren't shown the position itself. For a drive or bus leg, and on the way to the start of a leg, the position is also sent to our routing provider (TomTom) to work out the remaining drive time, no more than once every 15 minutes. To stop, tap Stop on the leg, which deletes the position, or turn off location permission for Constellations in your phone or browser settings. Sharing ends by itself when you arrive, and otherwise about three hours after the planned arrival. The stored position is deleted when you arrive or tap Stop; if neither happens we delete it within a day of sharing ending.
- Working out a pickup. When you arrange to meet someone and choose to start from where you are, your device's location is read once, sent to TomTom to work out the drive, and kept with the pickup. The coordinates are deleted once your time-to-leave reminder has been sent.
- Travel profile: all of it is optional. It's there so the details are at hand when you need them while travelling, and so we can remind you before a passport, visa, insurance policy or other document you've added expires (60, 30 and 7 days ahead). If you fill it in, it holds the name on your passport, passport number, country and expiry date, Known Traveller and redress numbers, loyalty programme numbers, seat and meal preferences, the countries you've listed as needing no visa or roaming plan, and scans of your passport. Only you can see these (and the operator, in the limited case described under Sharing & sub-processors). The name on your passport is also used to recognise you on bookings that you or people in your constellations forward. Your passport number, passport name, Known Traveller and redress numbers and passport scans are never given to Connie or to an app you connect. These details are stored in our database with the rest of your account and are not separately encrypted there; the scans are files, protected as described under Security.
- Comments and reactions you post on trips, bookings and constellations, seen by the people who can see that trip, booking or constellation.
- Postcards: the photos and caption, who you sent it to (another member, or an email address you type in), and the link that opens it. Anyone holding a postcard's link can open it, and sees your first name, the photos and the caption.
- Conversations with Connie: what you write to her, her replies, the changes she proposes, and the names of files you attach. The text is cleared 60 days after each message, or within a day if you use Clear history.
- Help & feedback: the message you send, a screenshot (one you attach, or one of the screen you were on), and the screen, app version, browser, screen size, language and time zone it was sent from. A report of a comment, postcard, person or reply from Connie is kept the same way, with the text that was reported. Each is deleted on the same cadence as audit logs (see Retention).
- Expenses: amounts, currencies, who paid, how each is split, settlements, and receipt images or files you attach, seen by the people on that trip.
- Payment method metadata: if you use the wallet, we store the label, kind, and optional last four digits you enter for each method. We never collect or store full card numbers, expiry dates, or security codes, and we process no payments.
- Two-factor authentication material: if you enable 2FA, the TOTP shared secret and your backup codes, both encrypted at rest.
- Passkeys: if you add one, its public key, a name, and the identifier of the kind of authenticator it lives in (so the list can say "iCloud Keychain"). The private key never leaves your device.
- Sign-in history: each sign-in's device type (such as "Chrome on macOS") and city, kept with the audit records, so a sign-in from somewhere new can be pointed out to you.
- Company sign-in: if your Work account connects its own sign-in, the provider's address and app settings, with the client secret encrypted at rest.
- Signed-in devices: for each device signed in to your account, its network (IP) address and browser, kept with that device's sign-in.
- Calendar feeds: if you create a calendar link, the secret address that lets a calendar app read your trips. Anyone holding the address can read the feed, and you can revoke it under Settings → Calendar.
- Your own AI key: if you add one, the key, encrypted at rest.
- Push subscriptions: the per-device delivery endpoints your browser issues when you enable push, so signals can reach that device. In the phone apps it is the device token the phone's notification service issues instead (Google's on Android, Apple's on iPhone and iPad). Revocable per device from Settings.
- Forwarded booking emails: when you forward a confirmation to your inbound address, we read the message and persist the extracted booking details along with the text-only source we used to validate the read. The rendered HTML body is not retained. Attachments from recognised bookings (e.g. the ticket PDF) are saved to the matching trip item in your chosen storage backend, where you can view and delete them like any other attachment; attachments from emails we couldn't recognise are kept on your own documents shelf — visible to you and counted against your storage quota — so recognition can be retried or you can file the document yourself, and are deleted on the audit-log cadence if left unfiled. Both the extracted details and the text source are deleted on the same cadence as audit logs (see Retention below).
- Connected services: if you connect Google Drive, we store an encrypted access + refresh token so we can read files you explicitly pick.
- Work account data: if you attribute trips or expenses to a Work account, those records (including receipts, categories, and tax amounts) become visible to that account's admins as described in How Work accounts work.
- Operational logs: request IPs and audit entries for sign-in, password resets, and admin actions. Retained for a maximum of 90 days. Your network (IP) address is also used, briefly, to limit how fast requests can be made.
How we use it
- Render your trips, signals, expenses, and constellation members.
- Send transactional email (verification, password reset, signal delivery) and push notifications you've opted into.
- Keep flight statuses, weather, and jet-lag plans current for your trips.
- Detect and prevent abuse (rate limiting, audit trail).
We do not use your data for advertising, and we do not train AI models on your content.
Google user data
When you connect Google Drive, Constellations requests the
drive.file scope. This scope only grants access to files that you
explicitly pick through the Google Picker; we cannot list, search,
or read your other Drive content. We use the tokens solely to
display links and metadata for files attached to your trips. Tokens
are encrypted at rest with AES-256-GCM and are only decrypted
in-memory at request time.
You can revoke our access at any time from Google Account → Third-party access or by disconnecting under Settings → Storage in the app.
Sharing & sub-processors
We don't sell your data, and we don't share it with anyone except where it's necessary to provide or secure the service. Today that means:
- Resend sends our email and receives forwarded booking emails on our behalf. It handles the address and content of each email we send: sign-in and security emails, signals, a postcard sent to an email address, and the copy of a Help & feedback message that is emailed to us.
- Anthropic and TypeSafe receive nothing of yours unless you have allowed AI (see Key points); you can turn that off under Settings → Connie.
- Anthropic provides the AI models behind two things. The first is the AI fallback we use to extract bookings from confirmations our built-in rules don't recognise, whether forwarded or uploaded. For that it receives the sender, subject, date and content of the email, the text read from its attachments, and attached PDF documents as files, for extraction only. The second is Connie: her replies are generated by Anthropic's models, which receive what you write to her, the earlier messages in the conversation, and the details from your account she looks up to answer (your trips and bookings, for example). If you've added your own AI key, the same things are sent to Anthropic under your account instead of ours.
- TypeSafe sorts things before Anthropic's AI reads them. For a forwarded email our built-in rules don't recognise, it judges whether it's a booking, what kind (and which kind of document), whether it's new or changes or cancels something, and how involved it is; an email it's sure isn't a booking isn't read any further, and what it judged is passed to Anthropic's AI with the email. For a message to Connie, it judges how much work answering takes and whether you're asking her to add or change something, which decides the AI model that replies. Afterwards it may check the result: whether the bookings found in an email match what the email says (an email whose result it rates poorly is read once more by Anthropic's AI), and, once a conversation with Connie has been quiet for five minutes, how well she handled it (whether she got something wrong, said she couldn't find something she could, or asked questions she didn't need to); that last check is only recorded, to improve Connie. For a message sent through Help & feedback, it sorts it for us (what it is, how urgent, how much work, which part of the app); you aren't shown how it was sorted. It receives the sender, subject and text of those emails and the booking details found in them (which can include details read from an attached file, but never the file itself, or anything you upload), the text of each message to Connie with her replies, the name and venue of an event you add by hand, and the text of a Help & feedback message with the screen it was sent from (never its screenshot), for those judgments only. Nothing goes to TypeSafe while your own AI key is the one paying, except a Help & feedback message, which is sent to us and sorted on our account.
- AviationStack / AeroDataBox are the flight data providers used to keep flight times and statuses up to date. They receive flight identifiers (airline, number, date), never personal details.
- Open-Meteo provides the weather forecasts shown on trips. It receives place coordinates and dates, never account data.
- TomTom works out drive times and finds places you search for. It receives the two ends of a drive, which can be your device's position when you share a journey's progress or start a pickup from where you are (see Location from your device), and the text you type into a place search with the area you're searching near. It receives no name, email or account identifier.
- Frankfurter provides currency exchange rates. It receives which dates we ask about, and nothing about you.
- ClickUp is where we track work. When a Help & feedback message becomes something to fix, its text, the screen it was sent from and its screenshot are copied into a task there. Your name and email address are not.
- Cloudflare fronts all traffic to constellations.li (DNS and security filtering), so requests pass through its network, and stores our encrypted-at-rest database backups (R2).
- Sentry receives a report when something in the app breaks, so we can fix it: the error, where in the app it happened and technical details of the request. Reports are not tied to your account. Your name, email, account identifier, cookies, network address and the content of what you sent are left out, though an error message can occasionally quote a detail of what was being processed. When a page fails to load, the app shows a short reference for that report. We only know a report was yours if you send us that reference, for example through Tell us what happened on the same screen.
- Stadia Maps serves the background of the map. Your device fetches the map images from Stadia directly, so Stadia sees your network address and which part of the map you looked at. It receives no account data and nothing about your trips.
- Microsoft and Apple, only when you choose to sign in with a Microsoft or Apple account.
- Apple, also when you turn on notifications in the iPhone or iPad app. They are delivered through the Apple Push Notification service, which receives the device token and the title and text of each notification, in order to show it on your device.
- Google, only when you opt in to Drive attachments, sign in with a Google account, or turn on notifications in the Android app. The app's notifications are delivered through Google's Firebase Cloud Messaging, which receives the device token and the title and text of each notification, in order to show it on your phone.
- Other users you choose to share with: constellation members, trip participants, and friend requests; the admins of a work account for any expense or trip you attribute to it; and anyone holding a public trip link you've chosen to create (which exposes only the itinerary skeleton: no names, notes, expenses, or documents).
- The operator of Constellations, only to diagnose a problem: the operator can view the service as your account sees it, read-only, and can't change anything as you. Every such view is recorded in the audit trail.
- Law enforcement when compelled by valid legal process.
We reserve the right to add further sub-processors, but only where necessary to provide or secure the service.
Each provider above handles this data under its standard terms of service and data-processing terms, which we have accepted.
Where data is stored
Primary application data lives on servers operated by us at constellations.li, behind Cloudflare's network. Database backups and copies of uploaded files are stored with Cloudflare (R2). A further encrypted copy of both is kept on storage we operate ourselves, so the service can be restored if Cloudflare becomes unavailable. The servers are in Singapore. Backups are held by Cloudflare (R2) and on our own storage in New Zealand. We may move to a managed cloud host as the service scales; if we do, we'll update this policy and notify users in advance.
Security
- Files are encrypted where they are stored. Attachments, receipts, avatars, and the documents on your travel profile are encrypted at rest by the storage holding them. Files in our object storage (Cloudflare R2) are encrypted with AES-256, as are our database backups. Files in a storage account you have connected yourself are covered by that provider's encryption. Our own backup copy is encrypted before it is written, with a key that is kept off both our servers and the storage holding the copy.
- Passwords are stored only as one-way hashes, which can't be read back, including by us.
- 2FA secrets and backup codes are encrypted with XChaCha20-Poly1305, and the access tokens for connected services such as Google Drive and company sign-in secrets with AES-256-GCM, before being stored. Each is decrypted in memory only for the request that needs it.
- Access tokens you create for the API are stored as hashes. The full value appears once, when it is created.
- Traffic is encrypted in transit. Browsers connect over HTTPS, and the link from Cloudflare's network to the server carries no plaintext and has no public entry point.
- Sign-ins, password changes, and administrative actions are recorded in an audit trail, and sign-in from a new device raises a signal if you've kept that category on.
Retention & deletion
You can delete your account at any time from Profile → Delete account, on the website or in the phone app. You confirm by typing your email address, and we email you a link that works for 30 minutes; the account is deleted when you open the link and confirm. If you're the only admin of a constellation that has other members, or the only owner or admin of a Work account, the app asks you to hand that over first. On deletion we remove your account, the trips you own, your files, your comments, your tokens and your sign-in details. Some things other people rely on are kept or handed to them: a flight you own that other passengers are on is handed to one of them, things you added to someone else's trip stay on it without your name, and settlement lines stay in other people's expense logs. The full list, and how to ask for deletion if you can't sign in, is in Deleting your account.
Our backups are separate copies. A backup made before you deleted something still contains it; backups are kept for up to 90 days and then removed, and aren't used for anything except restoring the service.
Audit logs and the source content of forwarded booking emails are retained for a maximum of 90 days and purged daily by an automated job. After that window the extracted details and the text source of any forwarded email are gone — along with any unfiled attachments from emails we couldn't recognise.
Help & feedback messages, their screenshots, and reports are deleted on the same cadence as audit logs. Things you delete go to the Trash, where you can restore them, and are removed for good on that cadence too.
The text of a conversation with Connie is cleared 60 days after each message, and within a day for anything you remove with Clear history. A record that the message existed, with what it cost to answer, is kept without its text.
Signals you've dismissed or acted on are deleted 90 days later; unread ones stay until you deal with them. A trip's activity history (who renamed it, added a booking, and so on) is kept for two years.
A position shared from your device is kept only as described under Location from your device.
Cookies
Constellations uses only cookies that are strictly necessary for the service to work: one that keeps you signed in, one short-lived cookie used during two-factor sign-in, one that remembers which work account you last viewed, and a few that remember how the app is set up on this device (theme, text size, spacing, app icon and the unread count shown as the page loads). The Android app adds one that tells the site a request came from the app. There are no advertising, analytics, or third-party tracking cookies, which is why you won't see a cookie banner.
Your data, on demand
A JSON archive of your portable data (profile, trips, constellation memberships, and signal preferences) can be downloaded at any time from Profile → Export your data, along with the attachments stored in Constellations' own backend.
Contact
Questions about this policy, or requests to see, correct, export or delete your information: [email protected].