A profile is the minimum needed to identify a person to their constellations: a name, an avatar, and an optional manual location pin.
Travel paperwork lives on its own page: Settings → Travel profile holds passport details (with attached scans of the photo page and any other pages that matter), Known Traveller and redress numbers, seat and meal preferences, loyalty programs, and the personal-documents vault (visas, ESTAs, insurance). Documents there count for every trip's visa, eSIM and expiry checks; ones kept only on trips count for those trips (see Storing documents and passes). Everything there is private to the owner until they add a document to a trip, which shows it to the people on that trip; loyalty numbers can optionally be made visible to the people on your trips for booking convenience. On any flight you're on with an airline you have a number for, the flight's card shows that number, and a tap copies it for check-in. Sensitive numbers display masked until revealed, and passport scans are never shared or read automatically.
What other people see
Whether someone is a friend, in a constellation with you, or on a trip with you, the most they see about you is:
- Your name and avatar.
- Your effective location on the map, only through trips and constellations shared with them.
- Your participation in the trips they can see.
They don't see your email, your forwarding address, your other constellations, or any trips you haven't shared.
To stop someone seeing anything of yours, or to tell us about something they posted, see Reporting and blocking.
Avatar
Upload an image from the profile page. With a storage backend connected (see below), the file lives there; otherwise it lives in Constellations' default storage.
Location
By default, a person's location is computed from their most recent past-arrival travel visible to whoever's looking at the map: a flight, train, drive, or ferry, anything with an arrival point. To override it (living somewhere different from where the last trip ended, say), pin a location manually from the profile page. Remove it any time with Remove on the same card; you're then placed by your trips again.
Only you see exactly where you put a pin. Everyone else sees the town it's in, or, with no town within about 50 km, a spot rounded to about 40 km with no place name.
A manual pin wins as long as it's more recent than the last travel arrival. Landing somewhere new supersedes the pin, so a pin set today stops applying after the next arrival.
The same effective location is what lets a friend visiting your town see that you're around ("also here" on their trip). It follows the exact same visibility as the map: only people who can already see your location (a shared constellation, or a trip you're both on) ever see it, and only the location they're allowed to see.
Where you are also tells the jet-lag plan what clock you're on, so jet lag prep plans from where you actually are rather than from where your travel last landed. Pinning a location records the time zone of the device you pin it from; pins made before this, or from a device that can't report one, still show on the map but don't move the jet-lag baseline.
Home
Under Home on the profile page, add the towns you live in and your local airports. There can be more than one of each, for anyone who splits their time between places. Each one saves as you pick it, and the × on a place removes it.
Your homes do two things. Places near them are left out of "most visited" in your numbers on Home, and a trip back to one of them is greeted as heading home instead of as a trip to that place.
Storage backend
By default, files (booking PDFs, receipts, avatars) live in Constellations' own storage. To keep files on your own side, connect Google Drive from Settings → Storage: future files save there, and Constellations stores only references. The same screen disconnects Drive.
Switching backends doesn't migrate existing files; they stay where they were saved.
Export your data
A portable copy of the account is available any time from Profile → Export your data. The export is a zip containing a JSON dump of the profile, the travel profile, trips, constellation memberships, signal preferences, and what you've added on trips: expenses you made or paid, settlements you're part of, your payment methods, to-dos, checklists and comments. Alongside it are the files stored in Constellations' own backend and the postcards you've added, with their photos. Files stored in a personal Google Drive aren't bundled; they're already yours.
For a slice rather than a full dump (one trip's receipts, or every booking PDF from a single constellation), the Files and Expenses tabs both have a Select → Download as ZIP option that bundles just what's picked.
Forwarding aliases
The personal address below is the inbound endpoint that turns booking emails into trip items. It is unique per account. Tap it to copy it. To swap it for a fresh one, open the ⋯ beside it under Settings → Connie → Forwarding addresses and choose New address…; forwarding to the old address stops once you confirm.
Once you’re signed in, this section shows your personal contact card with the QR you scan to add Constellations to your phone’s address book. It encodes the personal forwarding address described above so you can forward booking emails straight from your contacts.
Approved sender aliases are the other email addresses forwards are accepted from. Without them, forwards from anything other than the primary email are silently rejected. Add the sender under Settings → Connie → Forwarding addresses before forwarding from it.