Privacy policy

Who we are

khloe is operated by [[ LEGAL ENTITY NAME ]], [[ REGISTERED ADDRESS ]], established in [[ COUNTRY OF ESTABLISHMENT ]]. For anything in this policy, including a request to see or delete your data, write to [[ PRIVACY CONTACT EMAIL ]].

Two different relationships

This matters for knowing who to ask about what, so it comes first rather than buried at the end.

• If you are a business using khloe, we are the controller of your account data — your email, your settings, your billing status. You deal with us directly.
• If you booked an appointment through a business that uses khloe, that business is the controller of your booking, your questionnaire answers and any rating you leave. We only process it on their instructions, as their supplier. Ask them first — about what they hold, why, or to have it deleted. We will help them answer, and we will not use their data for our own purposes.

What we collect, and why

From people making a booking: your name, email address, anything you type into the notes field, your answers to the screening questions the business set, and the time you booked. This is what makes the appointment exist and lets us email you a confirmation you can use to reschedule or cancel. If you cancel, we keep the reason you give, if any. If the business asks for payment when you book, the card payment is taken by Stripe (see below); we keep only whether it was paid or refunded, never your card details.

After a session: the business can mark whether it took place. If it has chosen to, we send you one short email afterwards asking how it went; the score from one to five and any comment you write go to that business. You can ignore the email — nothing follows it up.

From businesses using khloe: the email address of each team member (used to sign in), the business's name, address for its booking page, time zone, opening hours and booking settings, and its client list where it chooses to keep one. When a business signs up, we email it a link to confirm the address before the account exists. Subscription billing is handled by Stripe.

Automatically: when someone opens a business's booking page we count the visit — a time and a short label for where it came from (for example “instagram”, taken from the link or the referring site). The count holds nothing that identifies the visitor: no IP address, no cookie, no device fingerprint. So that a reload is not counted twice, your browser remembers the visit for that tab only, and forgets it when the tab closes. Your IP address is counted against a short-lived rate limit when you submit a booking or start a questionnaire, so the page cannot be flooded. It is stored as a counter, not attached to your booking, and is deleted within about a day. We do not use advertising or analytics cookies, and there is no tracking pixel anywhere in this app.

Google Calendar data

This section applies only to a business that chooses to connect its Google Calendar. Nothing here affects people booking appointments.

With permission, khloe requests three scopes and uses each for one thing:

• calendar.freebusy — to read which times are already committed, so a busy slot is never offered to a client. We read busy/free periods, not the contents, titles or attendees of existing events.
• calendar.events — to create an event for each booking with a video-conferencing link, and to update or delete it when the client reschedules or cancels.
• userinfo.email — to show which Google account is connected, so a business can tell whether it connected the right one.

Access and refresh tokens are encrypted before they are stored (AES-256-GCM), so a copy of the database is not a set of usable calendar credentials. Disconnecting a calendar in settings deletes the stored credentials and asks Google to revoke them.

khloe's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide the scheduling features above. It is never sold, never shared with other businesses using khloe, never used for advertising, never sent to the AI assistant described below, and never used to train any model.

Who else processes this data

We use a small number of suppliers, each for one job:

• Supabase — hosts the database and handles sign-in for business accounts.
• Vercel — hosts and serves the application.
• Google — only for businesses that connect a calendar, as described above.
• Stripe — takes subscription payments from businesses, and, for a business that asks clients to pay when they book, takes that payment on the business's own Stripe account. Stripe receives the payer's card details directly; they never pass through khloe.
• Our email provider — delivers sign-up links, booking confirmations, reminders, reschedule and cancellation notices and rating requests. It necessarily sees the recipient address and the contents of those emails.
• Anthropic — provides the AI assistant, used only when a business asks for it, in two places. When a business asks for help drafting its screening questions, it receives only what that business typed to describe its own work. When a business asks for a written summary of its Reports, it receives the period's figures (bookings, hours, visits by source, cancellations), the text of the business's own questions with counts of how they were answered, cancellation reasons, and rating comments — without any client's name, email address or booking details attached. Anthropic does not use this to train its models.

We do not sell personal data, and we do not share it with anyone else for their own purposes.

How long we keep it

Bookings, clients, questionnaire answers, ratings and visit counts are kept for as long as the business that collected them keeps its account, because that business needs its own history. A business can delete individual clients and cancel bookings from its dashboard at any time, and can ask us to delete its account and everything in it.

Rate-limiting counters holding IP addresses are deleted within about a day. We are honest that automated export and bulk-deletion tooling is still being built: until it ships, these requests are handled by writing to the address above, and we will not refuse one because the button does not exist yet.

Your rights

If you are in the UK or the European Economic Area, you have the right to ask for a copy of your data, to have it corrected or deleted, to restrict or object to how it is used, and to have it sent to another provider. You can exercise any of these by writing to [[ PRIVACY CONTACT EMAIL ]].

If you booked through a business using khloe, that business is the one to ask — see “Two different relationships” above. You can also complain to the data-protection authority in [[ COUNTRY OF ESTABLISHMENT ]] or in the country where you live.

Security

Data is encrypted in transit. Calendar credentials are additionally encrypted at rest. Each business's data is isolated from every other business's at the database layer, and that isolation is enforced structurally rather than left to individual queries to remember. Links that let a client manage a booking, rate a session, or book without signing in are unguessable tokens generated from a cryptographic random source — treat one like a password, and tell the business if you think yours has been seen by someone else.

Changes to this policy

If we change how data is handled in a way that affects you, we will update the date at the top of this page, and tell businesses using khloe directly where the change is material.