Privacy

When you make an account: your email address, and then your name, date of birth and password. The password is stored only as a scrypt hash — we cannot read it, and neither can anyone who takes a copy of the database.

Your date of birth is used for one thing: confirming you are 18 or over, which you have to be to enter a booking contract. Hosts never see it.

If you add them: a phone number, a photo, a short bio, a city, a postal address, and the languages you speak. All optional, all editable, all deletable.

When you book: the dates, the property, what you paid, any note you sent the host, and who else is coming if you tell us.

What you agreed to when you booked: a copy of what the checkout showed you as you pressed the button — the price, the cancellation terms and the house rules. With it, the device and internet address you booked from. We also note each time your stay’s page is opened: when, from which device and address, and whether the door code was on the screen. They name nobody, and they are the host’s evidence if a payment for the stay is disputed. Both are kept for two years, then deleted.

Security records: each sign-in creates a session row holding the browser and device string your browser sent, so you can see and revoke your own active sessions. If you turn on two-factor authentication we store the secret that makes it work.

The host you book with. They get your name, your email, your phone number if you gave one, and the details of the stay. They are the other side of your booking, so this is the point rather than a side effect.

Companies that run parts of Kabora. Vercel hosts the site, Neon hosts the database, and Resend delivers our email — which means Resend handles your address and the contents of messages we send you. When card payments are switched on, Stripe will process them and we will not hold your card number at any point. If you choose to verify your identity, Didit runs that check for us: your ID photograph and selfie go to Didit, not to us. We keep the outcome — verified or not, and the date — and never receive or store the images.

Sign-in providers, only if you use them. Choosing Google, Facebook or Apple tells that company you signed in to Kabora. Not choosing them tells them nothing.

Maps. On the website our maps are Google’s, and in the iPhone app they are Apple’s. Loading a map asks for the part of it on your screen; we never send your name, your account or your bookings with it. When a host saves an address, or a search names a town we have not looked up before, we ask Google where it is. Our “what’s nearby” lookups go to OpenStreetMap and send the property’s coordinates, never yours.

We do not sell your data, and we do not run advertising trackers.

Get a copy of it. There is a button in your account settings. It builds a file of what we hold about you and gives you a link to download it. The file is JSON, so you can read it or hand it to somebody else's software. The link stops working after a while, and you can ask for a fresh one.

Correct it. Everything on your profile is editable from your account settings. If something is wrong that you cannot reach — a name on an old booking, say — email us and a person will fix it.

Delete your account. It is the last row of Sign-in & security in your account. Some booking records survive it. That is because a host has their own legal and tax reasons to keep a record of a stay that actually happened. Those are kept against the reservation, not against a profile.

Object, or ask us to stop. Tell us which thing you want stopped. We will either stop, or say plainly why we cannot — usually because a booking you made needs it.

No account? Ask anyway. A copy, a deletion, a correction or a stop can be asked for by anybody. A guest who booked elsewhere and stayed with a Kabora host has a record here too. Use the request form: type the address we would know you by, confirm it from the link we send, and a person answers within thirty days. Or email privacy@kabora.app.

Complain. If you are in the UK, the EU, or anywhere with a data protection authority, you can complain to them about us. You do not have to ask us first.

Nothing changes if you do. Using any of the above does not change your price, your booking, or how you are treated here.

Not to advertisers, not to data brokers, not to anybody. We also do not “share” it in the sense some privacy laws use — passing it to another company so they can advertise to you across other sites. Kabora has no advertising business and buys no audiences.

That is why there is no “do not sell my information” switch on this site. A switch turning off something that never happens would suggest it happens.

Kabora sets around twenty cookies and every one is its own. There are no advertising or analytics cookies at all, and no third party watching you here to switch off. That is why there is no cookie banner. A banner is for cookies that watch you. The law asks consent for those, not for the ones that sign you in or remember your screen.

Signing you in: your session, the device you are on, and a short-lived one during a Google, Facebook or Apple sign-in. Your session is kept for 30 days after your last visit. Each visit renews it, so you sign in again only after that long away. On the phone app it is 90 days.

The one exception, on the page where you type a card: Stripe, which processes the payment, sets two cookies of its own there. One is for the payment session and one lasts a year, and they are there to tell a real card from a stolen one. They are set on that page only, and they are Stripe’s fraud prevention, not anybody’s advertising.

Remembering how you like the screen: how wide your calendar bands are, whether the side panel is folded, which view a list opens in. Preferences, not a profile.

Making pages quick: small caches of things you just looked at, so a page can draw before the server answers.

Counting a listing view once: a cookie that remembers you already looked at a place in the last half hour. It holds no account id — the counting is done in a daily total per listing, so a host learns how many people looked and never which people. That is the whole design: the identity stays in your browser and never reaches us.

Your account and its contents stay until you delete them. Bookings and the payment records attached to them are kept for as long as tax and accounting rules require. A sign-in ends 30 days after your last visit, or when you end it yourself from Sign-in & security. A confirmation code dies after ten minutes or five wrong guesses, whichever comes first.

A few things are removed once they are dead. An invitation nobody accepted; a download link for your copy, once expired; the trust we gave a device you stopped using; sessions that have ended. Each has a stated period, published with the rest of what we keep.

A record of what was done. We keep a log of actions taken in Kabora — who did a thing, and when. Most of it is our own staff: signing in, opening a support ticket, or looking at a booking to answer a question about it. Money records are kept for seven years, because tax and accounting rules reach back that far. Records of who could get into an account and what settings were changed are kept for two years. So are records of when a member of our staff looked at somebody’s record, and of who uploaded a file. Sign-in activity is kept for one year, and anything carrying the network address a request came from is deleted after ninety days.

This log records that something happened, not the contents of it. It does not store email addresses, phone numbers, or the names people give their files, and a check refuses to write them. When you delete your account we do not keep the log intact. The entries stay, so the record of what happened is still whole, and your details are removed from them. Two things outlive that on purpose — the history of support tickets and incidents, and the receipt proving an erasure was carried out. The receipt names nobody; it exists so we can show a deletion was honoured, which we could not do if we deleted it too.

If this page changes in a way that matters, we will say so rather than quietly editing the date at the top.

Questions about any of it: privacy@kabora.app.

By post: Kabora, PO Box 868, Prosper, TX 75078.