A packing list doesn't sound private, but it says when you'll be away and who's coming — down to their names, kids included if they're on the trip. So here are the rules of the place, in plain words.
Every read and write is checked against trip membership in the database itself, not just in the interface. The one deliberate exception: an invite link shows the trip or event's name, dates and first names, so a friend can see what they're joining before telling us anything. Treat an invite link like a spare key — share it with the people coming, not the group chat of a thousand.
Your gear list is private unless you mark a specific item as shared. A shared item becomes visible to people you've actually been on a trip with — including trips other than your current one, so a new trip can start from what your crew already owns — never to anyone else. Only the item itself: its name, category and photo, never which trip it was on, your email, or anything else about you. Turn it off for an item and it stops being visible immediately.
No marketing, no newsletters, no “we miss you”. The people on your trip or event never see it either — they see the name you give, nothing more. Sign in with Google if you'd rather skip a password — we only ever ask it for your name and email, the same two things a password account gives us.
Only a trip or event needs a name. Dates can be as vague as “2027”, the location can be “somewhere in the Peaks”, and people can be on it as just a first name — an account is only needed when someone wants to tick things off themselves.
Saving a list as a template never shares your trip or event — sharing it with other people on the app is a separate step, and putting it on the open web (searchable on Google, no account needed to view) is a further, separate step you take deliberately. What goes out is the list itself — item names, categories, quantities, and a few frozen facts about its shape (nights, people, season) — never who was on it, who brought what, or anything else you typed into it.
There are no advertising or analytics scripts on any page — nothing watching how you use it, nothing following you afterwards. The only information here is what you typed into a list.
Remove an item and it's gone. Delete a trip or event and its lists, items, claims, meals and notes go with it, immediately — not hidden, not archived, gone. (We ask you to confirm first, for exactly that reason.)
Everything is stored in a Postgres database hosted by Supabase, and nowhere else. We don't sell it, share it or move it. Two services are involved beyond that, each doing one narrow job: Google, only if you choose to sign in with it — it tells us your name and email, nothing about your trips or events, and we tell it nothing back — and, if you've added a postcode, two free weather services (postcodes.io and Open-Meteo) that turn it into a forecast for the trip header. They see the postcode, nothing else — not the trip's name, dates, or who's on it.
Every trip and event has an Export link on its details page — everything on it, as a file you keep. And your account page has a real “delete my account”, not a support ticket — with one honest limit: if you own a trip or event other people have already joined, we ask you to hand it off or delete it first, so closing your account can't take their plans down with it.
Prefer it in formal shape? The privacy notice and terms say the same things the expected way.