Privacy Policy
In plain English
We collect what a booking needs and what the law requires us to keep, and not much else.
Your card number never reaches us — Stripe handles payment and we see only the amount, the last four digits and whether it worked.
We do not sell your data. Operators get what they need to run your trip safely, and nobody else gets anything without a legal reason.
This summary is here to be read, not to be relied on. The numbered clauses below are what actually binds — where the two seem to disagree, the clauses win, and we would like to know about it so we can fix the summary.
What we collect
From your account: if you signed in with Google, GitHub, Facebook or Instagram, the name, email address and profile photo that provider holds for you. If you signed up with an email address instead, the name you gave us, that address, and a scrambled form of your password from which the password itself cannot be recovered — we never store or see the password you typed. Either way, anything you choose to add: a display name, a handle, a bio, a location.
From your bucket list: the journeys you save, the notes you write on them and whether you have ticked them off. Notes are private to you unless you publish your list.
From a waiver: the participant's name and date of birth, an emergency contact, and any medical or fitness information you tell us the operator needs to run the activity safely. Where the participant is a minor, the signing adult's name and their relationship to them.
From a booking or purchase: what was bought, when, for how much, and the email address the receipt goes to.
Automatically: your IP address and browser identifier at the moment you accept an agreement or sign a waiver, because a signature with nothing around it is not evidence of anything.
Why we hold it
To take and honour bookings, to give operators what they need to run an journey safely, to take payment and issue receipts, to answer you when you write in, and to keep the records that a marketplace handling money and waivers is required to keep.
Medical and fitness information is sensitive, and we treat it that way: it is collected only where the activity genuinely needs it, shared only with the operator running that activity, and never used to decide what to show or sell you.
Who else sees it
The operator running your journey, and only for that journey: the roster, the waiver, your emergency contact and anything you told us they need to know.
Stripe, who process payments. They receive your payment details directly and we never hold your card number. Their own privacy notice covers what they do with it.
Our hosting and database providers, under contract, to the extent that running a website requires it.
Anybody, if you publish your bucket list — that page is public by your choice, shows your name, photo, handle and list, and comes down the moment you switch it off.
We do not sell personal information and we do not share it for cross-context behavioural advertising.
How long we keep it
Your profile and bucket list, until you delete your account.
Signed waivers, acceptances of these agreements, and payment and invoice records, for as long as a claim could be brought and any period the law requires — typically several years, and longer for a waiver signed by or for a minor. Deleting your account does not delete these, and it should not: the point of a signed record is that neither side can make it disappear later.
Webhook and diagnostic logs, for a few months.
Your rights
You can ask us for a copy of what we hold about you, ask us to correct it, ask us to delete what we are not required to keep, and object to a particular use.
Write to hello@livabit.co and we will answer within one business day and act within thirty. We will not charge you for asking and we will not treat you differently for having asked.
Depending on where you live you may also have the right to complain to a regulator, and nothing here stops you doing that first.
Security, and being straight about it
You can sign in through a provider — Google, GitHub, Facebook or Instagram — in which case they do the identity work and there is no password of yours here at all. If you set a password with us instead, we store it scrambled by a one-way function, which means we cannot read it, cannot tell you what it is, and cannot hand it over. That is also why resetting it sends you a link rather than reminding you of the old one.
Data is encrypted in transit, access is limited to the people who need it, and payment details never touch our servers.
No system is perfect. If we ever have a breach that affects you, we will tell you what happened, what we know, and what to do — promptly, and without waiting to have a tidy story.
You accept this when you create an account, and again if a material change is published. The version you accepted and the date are recorded against your account.
Governed by the laws of the State of California. Livabit, Inc., hello@livabit.co.