Privacy

When you make an account: your email address, and then your name, date of birth and password. The password is stored only scrambled, in a form that cannot be turned back into it. Kabora 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 place, what you paid, any note you sent the host, and who else is coming if you tell Kabora.

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. Kabora also notes 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.

If you sign a host’s rental agreement: Kabora keeps what you signed on your trip page and the full name you typed. Kabora also keeps when you signed and the device and internet address you used. This is the host’s evidence that you agreed to their terms, kept for two years and then deleted.

If you fill in a host’s check-in form: when a host asks questions before you arrive, Kabora keeps your answers. That means the time you expect to arrive, the names of everyone coming, your car and its license plate, and anything else the host asked. Kabora also keeps when you answered, and the device and internet address you answered from. Your host reads them on your reservation. They are kept for two years after your last change, then deleted, and they are deleted with your account.

Security records: Kabora keeps each sign-in with the browser and device it came from, as your browser named them. That list is how you see where you are signed in and sign out of any of them. If you turn on two-step verification, Kabora also keeps 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 Kabora’s email — which means Resend handles your address and the contents of messages Kabora sends you. Stripe processes card payments, and Kabora never holds your card number. If you choose to verify your identity, Didit runs that check for Kabora: your ID photograph and selfie go to Didit, not to Kabora. Kabora keeps the outcome — verified or not, and the date — and never receives or stores the images. Didit keeps the face from your check so that a later selfie can be matched to it. Kabora asks for that selfie before your payout details can be changed. The face is kept until your account is closed or 3 years after your last check with Kabora, whichever comes first, and then deleted. If you give Kabora a phone number and ask for texts, Twilio delivers them. Your number and the words of that message go to Twilio, the way your email address goes to Resend. Kabora has writing helpers: a suggested reply, a translated message, the help assistant and a host’s assistant. When somebody uses one, the words it works on and the details of the stay it needs go to Anthropic, whose Claude model writes the answer. That can include a guest’s message and first name. Kabora’s Assistant also answers a guest’s question in the stay’s thread by itself, from what the host wrote on the listing, unless the host turns that off. The question and the listing’s words go to Anthropic the same way. A person’s own chats with the Assistant are kept for 30 days after the chat’s last message. When you talk to the Assistant in the Kabora app, your phone turns your voice into words itself. The app listens only while you talk to it and keeps no recording. The words go to Anthropic like anything else you ask the Assistant. A notification on the Kabora app goes through Expo, which hands its words to Apple or Google to show on the phone. The Kabora app asks Expo whether a newer version of its code is ready. If the Kabora app crashes, it sends a crash report to Google’s Firebase Crashlytics when it next opens. The report holds what failed in the app’s code, the phone’s model and system, the app’s version, and an identifier Firebase makes for that copy of the app. No name, account or anything you typed goes with it. When a host connects a smart lock, Kabora sets each stay’s door code through Seam, which runs the connection to the lock. Seam receives the code, the days it works, and a label with the stay’s code and the guest’s first name. Mail you send to a kabora.app address passes through ImprovMX on its way to Kabora. Kabora’s server logs, which can include an address or a page you visited, are kept for 30 days by Axiom; Kabora removes what it can before they are written.

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

Maps. On the website Kabora’s 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; Kabora never sends your name, your account or your bookings with it. When a host saves an address, or a search names a town Kabora has not looked up before, Kabora asks Google where it is. Kabora’s “what is nearby” lookups go to OpenStreetMap and send the place’s coordinates, never yours.

Kabora does not sell your data, and Kabora does not run advertising trackers.

Get a copy of it. There is a button in your account settings. It builds a file of what Kabora holds 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 Kabora 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 Kabora to stop. Tell Kabora which thing you want stopped. Kabora will either stop, or say plainly why it 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 Kabora would know you by, confirm it from the link Kabora sends, 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 Kabora. You do not have to ask Kabora 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. Kabora also does 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, and a short-lived one during a Google 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 Kabora.

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 verification 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; sessions that have ended. Each has a stated period, published with the rest of what Kabora keeps.

A record of what was done. Kabora keeps a log of actions taken in Kabora — who did a thing, and when. Most of it is Kabora’s 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 Kabora’s staff looked at a person’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 Kabora does 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 Kabora can show a deletion was honoured, which Kabora could not do if it deleted it too.

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

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

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