Privacy policy
Last updated 4 October 2026
The short version
- We only collect what is needed to take and manage bookings.
- Customer booking data belongs to the business you booked with. We process it for them.
- We never sell data, show ads, or use your data to train AI models.
- Our database is in the EU (Frankfurt).
- You can ask us to see, correct or delete your data at any time.
1. Who we are
OpenBooking (openbooking.sh) is a booking system that lets appointment businesses take bookings on their own booking page and through AI assistants such as ChatGPT, Claude and Gemini. The hosted service at app.openbooking.sh is run by Skøien Holding AS (organisation number 936 680 267, Persbråtan 5, 0770 Oslo, Norway) ("we", "us").
Questions about privacy: johanshelleve@gmail.com.
This policy covers the hosted service. If a business runs the open-source OpenBooking software on its own servers, that business alone decides how your data is handled.
2. Our two roles
- Business owners (our users): for your account and your business profile, we are the controller.
- Customers who book an appointment: the business you book with is the controller of your booking data, and we are its processor. We handle that data only to run bookings for the business, as set out in our data processing terms. For questions about a booking, contact the business first; we will help it answer you.
3. What we collect
From business owners
- Name, email address and password (stored only as a salted scrypt hash).
- Business details you enter or import: name, address, phone, opening hours, services, prices, staff names and booking rules.
- If you use Import from your website: the public pages of the website address you give us, read once to fill in your setup.
- If you connect Google Calendar: see section 6.
From customers who book
- First and last name, email address and/or phone number.
- The appointment: service, time, staff member, price, any notes you add, and its status.
- How the booking was made (for example "booking page", "Claude" or "ChatGPT"), so the business can see where bookings come from.
When you book through an AI assistant, the assistant sends us the details you gave it for the booking. What the assistant itself stores is covered by its provider's privacy policy (for example OpenAI, Anthropic or Google), not this one.
Technical data
- IP address and request details, used briefly for security and to limit abuse (for example too many login attempts). Rate-limit records are deleted within 24 hours.
- Anonymous usage statistics via PostHog, without cookies: which pages are visited, the site or campaign a visit came from, which buttons are clicked, how far pages are scrolled, and how far people get in sign-up. Customer booking pages are not tracked.
- When someone visits openbooking.sh, our team gets a short notice with the page, the site or campaign they came from and an approximate location (city and country, from the IP address), and, when they leave a page, how long they stayed, how far they scrolled and which buttons they clicked. The IP address itself is not stored.
- We set no advertising or tracking cookies. Studio keeps your login in your browser's session storage.
4. Why we use it
| Purpose | Legal basis (GDPR) |
|---|---|
| Running your account and the booking service | Contract (Art. 6(1)(b)) |
| Taking, confirming and cancelling bookings, and sending booking emails | Contract, on behalf of the business |
| Security, fraud and abuse prevention | Legitimate interest (Art. 6(1)(f)) |
| Account emails (email confirmation, password reset, important service notices) | Contract |
| Keeping records the law requires | Legal obligation (Art. 6(1)(c)) |
We do not sell personal data, use it for advertising, or use it to train AI models.
5. Who we share it with
We use a small number of service providers (sub-processors) to run OpenBooking:
| Provider | What for | Where |
|---|---|---|
| Vercel | Hosting the app | EU region (Frankfurt); US company |
| Neon | Database | EU (Frankfurt) |
| Resend | Sending booking and account emails | US company |
| Calendar sync, only if the business connects it | US company | |
| PostHog | Usage statistics for our website and the owner pages (sign-up, setup, Studio), without cookies; and counts of sign-ups and bookings per business. Never customer details. | EU (Frankfurt) |
| Sentry | Error reports, so we can fix problems. Personal data is filtered out. | EU (Frankfurt) |
| Slack | Internal alerts to our team (for example "a business signed up"). Business names only, never customer details. | US company |
| Anthropic | Reading a business's public website during setup, only if the owner uses Import. No customer data is sent. | US company |
Transfers outside the EU/EEA rely on the EU Standard Contractual Clauses or the EU-US Data Privacy Framework. We also share data when the law requires it.
The business you book with sees your booking in its OpenBooking Studio. If it has connected Google Calendar, the appointment also appears in that calendar.
6. Google user data
If a business owner connects Google Calendar, OpenBooking asks Google for permission to:
- See free/busy times (
calendar.freebusy), so we never offer a time when the owner or staff are busy; - Create, change and delete the booking events it makes (
calendar.events), so every booking shows up in the calendar; - List the owner's calendars (
calendar.calendarlist.readonly), so each staff member can be matched to a calendar; - Know the Google account's email address (
openid,email), to show which account is connected.
We store the access token Google gives us and the IDs of the events we created. We do not read the titles, descriptions or attendees of the owner's other events; free/busy data tells us only when time is taken. We use Google data only to provide these booking features, never for advertising, and we do not sell it or use it to train AI models. Humans at OpenBooking do not read it, except with the owner's permission for support, for security reasons, or where the law requires.
OpenBooking's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Owners can disconnect Google Calendar at any time in Studio Settings, which deletes the stored token, or revoke access at myaccount.google.com/permissions.
7. How long we keep it
- Accounts and business settings: until the account is deleted.
- Bookings: for as long as the business keeps its account, so it can see its history. When an account is deleted, its bookings are deleted within 30 days.
- Temporary holds that were never confirmed lapse after minutes.
- Retry records (used so a repeated request never books twice): 24 hours.
- Security records (rate limits): up to 24 hours.
- Backups: deleted data can remain in backups for up to 30 days.
8. Your rights
Under the GDPR you can ask to access, correct, delete, restrict or receive a copy of your personal data, and object to processing based on legitimate interest. Business owners can write to johanshelleve@gmail.com. Customers should contact the business they booked with; if you can't reach it, write to us and we will help. We answer within one month.
You can also complain to the Norwegian Data Protection Authority, Datatilsynet, or the authority where you live.
9. Security
All traffic is encrypted (HTTPS). Passwords are hashed, owner sessions are signed and expire, logins are rate-limited, and each business can only see its own data. No system is perfectly secure; if a breach affects your data, we will tell the affected businesses and the authorities as the law requires.
10. Children
OpenBooking is not meant for children under 16 to use on their own. A parent or guardian should book for them.
11. Changes
If we change this policy in a way that matters, we will email business owners before it takes effect. The date at the top shows the latest version.