Loading...

Privacy Policy

Last updated: November 15, 2026

This policy explains how Magic Booking ("Magic Booking", "we", "us") collects, uses, stores and shares personal data when you use our website, our dashboard and the booking pages we host. It applies to business owners who create an account ("organizers") and to people who book through a booking page ("participants").

If you connect a Google account, the Google Calendar data section describes exactly what we access and what we do with it.

Your use of Magic Booking is also governed by our Terms of Service.

Contents

  1. Who we are
  2. Data we collect
  3. How we use data
  4. Google Calendar data
  5. Other connected calendars
  6. How we share data
  7. Cookies
  8. Retention and deletion
  9. Security
  10. Your rights
  11. International transfers
  12. Children
  13. Changes to this policy
  14. Contact us

1. Who we are

Magic Booking is an online service that lets businesses publish booking pages, show their availability from their own calendars, and receive reservations by email and in their calendars. Magic Booking is published by Baptiste Thomas Langlet, a sole proprietor based in Japan trading as b-t-l, at 2-12-1-405 Matsugaya, Taito, Tokyo 111-0036, Japan. For organizer accounts and for the operation of the service, Baptiste Thomas Langlet is responsible for your personal data. For participant data collected through a booking page, the business that owns the page decides why the data is collected, and we process it on its behalf to provide the service.

2. Data we collect

Organizers

  • Account data: your email address, used to sign in with a one-time link, and your name if you provide it.
  • Business data: business name, contact email, description, location, website and logo, and the content of your booking pages (titles, descriptions, prices, booking options and custom questions).
  • Calendar connections: the calendar links, CalDAV credentials or Google authorizations you add, the names and colors of the calendars you select, and the date and status of the last synchronization. See Google Calendar data and Other connected calendars.
  • Subscription data: your plan, its status, and the customer and subscription identifiers of our payment provider, Stripe. Card details are entered on Stripe's pages and never reach our servers.
  • Preferences: language, time zone, week start, time format and preferred currency.

Participants

  • Reservation data: your name, email address, the answers to the questions asked by the business, and the details of the reservation (date and time, event, seats, price and payment status).
  • Access data: the personal links that let you view or cancel a reservation. We store only a hash of their secret part.
  • Email requests: when you ask us to resend your reservation links, we record the request and a keyed hash of your email address to limit abuse.

Everyone

  • Technical data: for signed-in sessions, the IP address and browser user agent associated with the session, and the server logs needed to operate and secure the service.
  • Abuse limits: when you request a sign-in link, make a booking or ask for your reservation links, we record a keyed hash of your IP address network, and for sign-in links of your email address, to limit the number of requests. We never store the address itself.
  • Email delivery: our email provider tells us whether each email reached the recipient's mail server, bounced or was reported as spam. We record this delivery status with the reservation notifications. When an address does not exist or its owner reports our emails as spam, we add a keyed hash of the address, never the address itself, to a list of addresses we no longer send emails to.
  • Bot protection: the sign-in, booking and link recovery forms use hCaptcha, which processes device and interaction data to tell humans from bots.

We do not use advertising or third-party analytics trackers.

3. How we use data

  • To provide the service: create and display booking pages, compute availability from connected calendars, record reservations, and send confirmation, cancellation and sign-in emails.
  • To keep connected calendars working: we read the calendars used by booking pages again about twice a day when no visit has read them, and we email the business contact address when a calendar can no longer be read or reservations can no longer be written to it. The email names the affected calendars, accounts and booking pages, and the error.
  • To manage subscriptions and billing through Stripe.
  • To secure the service: authenticate users, prevent abuse and spam, and investigate incidents.
  • To answer the support requests you send us.
  • To meet legal and accounting obligations.

Where the law requires a legal basis, we rely on the performance of our contract with you, our legitimate interest in securing and improving the service, your consent (for example when you connect a calendar account), and our legal obligations.

4. Google Calendar data

Organizers can connect a Google account on the Calendars page so that booking pages show availability from their Google calendars and, if they choose, so that the reservations they receive are written to a Google calendar. Both are optional, and each happens only when you turn it on and approve access on Google's consent screen. We ask for each permission only when you use the feature that needs it.

What we access to read your availability (read only)

When you connect a Google account to use its calendars on your booking pages, we request only these read-only permissions:

  • Basic account information (openid, email): your Google account identifier and email address, to identify the connection and show you which account is connected.
  • Calendar list (calendar.calendarlist.readonly): the identifiers, names, colors and access level of your calendars, so you can choose which ones to use.
  • Events (calendar.events.readonly): for the calendars you select only, and only for the dates a booking page needs to display, each event's identifier, title, description, location, start and end times, status and whether it is marked free or busy.

With these permissions alone, Magic Booking cannot create, modify or delete anything in your Google account.

What we access to write your reservations (read and write)

If you choose a Google calendar to receive the reservations made on your booking pages, we ask you on Google's consent screen for an additional permission that allows writing. This access is not read only. Depending on the option you choose, we request:

  • A dedicated calendar (calendar.app.created): Magic Booking creates a separate calendar in your Google account, named after your business (for example "Yoga Studio · Bookings"), and manages the events in it. With this permission, we cannot see or change your other calendars.
  • A calendar you own (calendar.events.owned): Magic Booking adds reservations to a calendar you already own. This permission allows us to view, create, modify and delete events in the calendars you own, so we limit our own use as described below.

With write access, we only:

  • create one event for each reserved time slot in the calendar you selected. With the "Participant details" level, it includes the event title, date and time, location, the number of reservations, the participants' names and email addresses, their reservation references and answers, and a link to your dashboard. With the "Booked time slots only" level, it includes only the reserved times, shown as "Booked";
  • update that event when its reservations change, mark it as tentative while they are pending, and delete it when they are all canceled. When you stop writing to a calendar, we delete the upcoming events we created there and leave past ones;
  • keep the identifier of each event we create so we can find it again, and a private mark on it so your booking pages do not offer it as a bookable slot. We never modify or delete an event that Magic Booking did not create.

How we use it

  • Availability calendars: the events of the calendars you choose as availability calendars are shown on your public booking pages as bookable slots, with the title, description, location and times you entered in Google Calendar. Anyone who visits your booking page can see this information.
  • Unavailability calendars: for the calendars you choose as unavailability calendars, we use only the start and end times of busy events to block overlapping slots. Their titles, descriptions and locations are never shown to visitors.
  • Reservations: when someone books an event from an availability calendar, a copy of that event's title, description, location and times is saved with the reservation, so that the reservation, your dashboard and the confirmation emails stay accurate even if the event later changes.
  • Reservation calendars: if you turn on writing, the reservations you receive are added to the Google calendar you selected and kept up to date, so your schedule stays in one place. Anyone you share that calendar with in Google Calendar can see these events, according to your Google sharing settings.
  • Connection status: we record whether the last read or write succeeded, so the Calendars page can tell you when the connection needs attention. When the connection stops working, for example because access was removed, we email the business contact address once, naming the Google account and the affected calendars, and we read the calendars again about twice a day to notice it even when nobody visits your booking pages.

We use Google user data only to provide these user-facing features, and for no other purpose.

How we store and protect it

  • We store your Google account identifier and email address, the identifiers, names and colors of the calendars you select, and, if you turn on writing, the identifiers of the events we create for your reservations.
  • We store a refresh token so the service can access your calendars without asking you to sign in again. It is encrypted with AES-256-GCM before it is saved, is never sent to your browser, and is used only by our servers to call the Google Calendar API. Short-lived access tokens are kept in server memory only.
  • Event data is read when a booking page or the dashboard needs it and is kept in server memory for about two minutes to avoid repeated requests. It is not written to our database, except for the copy saved with a reservation described above.
  • All traffic between your browser, our servers and Google is encrypted with HTTPS.

How we share it

We do not sell Google user data and we do not transfer it to third parties, except as needed to provide the features described above (event details shown on your booking pages and included in reservation emails sent through our email delivery provider, reservation events written to the Google calendar you selected, and storage by the hosting providers that run the service), to comply with the law, or as part of a merger or acquisition with prior notice to you.

Limited Use

Magic Booking'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. In particular:

  • We do not use or transfer Google user data to serve advertisements, including retargeting, personalized or interest-based advertising.
  • We do not sell Google user data, and we do not use it to determine creditworthiness or for lending purposes.
  • We do not use Google user data to develop, improve or train generalized artificial intelligence or machine learning models.
  • No person at Magic Booking reads your Google user data unless you give us explicit permission for specific data (for example in a support request), it is necessary for security purposes such as investigating abuse, it is required by law, or the data is aggregated and anonymized for internal operations.

Disconnecting and deleting Google data

  • Disconnect on the Calendars page immediately deletes the refresh token, the Google account identifier and the Google email address, removes the account's calendars from your business and clears the cached events. Closing your account or deleting the business does the same for all its Google connections.
  • After you disconnect, Magic Booking can no longer change your Google calendars. Reservation events already written there stay in your calendar; you can delete them, or delete the dedicated Magic Booking calendar, in Google Calendar.
  • Only the names of the disconnected calendars remain in an archived record of the connection, and event copies remain with past reservations, so that your reservation history stays consistent. You can ask us to delete them at any time by contacting us.
  • Because the same Google account can be connected to several businesses, disconnecting does not revoke the authorization at Google. You can revoke Magic Booking's access at any time in your Google account permissions. After revocation, we can no longer read or write your calendars.

5. Other connected calendars

Organizers can also add calendar links (ICS URLs) and CalDAV accounts such as iCloud, Fastmail or Nextcloud. Calendar links and app passwords are encrypted with AES-256-GCM before they are saved and are never sent back to the browser; the dashboard shows only a shortened label in which secret parts are masked. Events from these calendars are used in the same way as Google events: shown as bookable slots for availability calendars, used only as busy times for unavailability calendars, and copied into a reservation when someone books. Calendar links are read only. If you choose a calendar of a CalDAV account to receive your reservations, or let Magic Booking create a new calendar in that account for them, Magic Booking also writes to it, with the same limits as for Google: it creates, updates and deletes only the reservation events it created. Disconnecting an account or deleting a calendar link erases its credentials; events already written stay in your calendar.

Reservation subscription links

Organizers can also create secret subscription links (ICS URLs) that publish the reservations of one booking page, or of all the pages of a business, so that calendar apps such as Google Calendar, Apple Calendar or Outlook can display them. Anyone who has the link can read the reservations it contains, from 30 days in the past onward, and the app subscribed to it copies them on its own servers. With the "Participant details" level, the link includes the event, the participants' names and email addresses, their reservation references and answers; with the "Booked time slots only" level, it includes only the reserved times, shown as "Booked". We store each link encrypted with AES-256-GCM and look it up by a one-way hash, and we record when it was last read. The organizer can change its level, replace it with a new link (the old one stops working) or delete it at any time; links are deleted with their booking page, business or account.

6. How we share data

We do not sell personal data. We share it only in these cases:

  • Between organizers and participants: when you book, the business receives your name, email address, answers and reservation details. Participants see the business details and event information published on its booking page.
  • Subscription links: the reservations included in a subscription link created by the business, with the people and calendar apps it gives that link to. See Other connected calendars.
  • Service providers that process data on our behalf, under contracts that protect it: our hosting and database providers, Resend for sending emails (it receives the recipient address and the content of each email, and keeps them for up to 30 days), Stripe for payments, hCaptcha for bot protection, and Google when you connect a Google account.
  • Legal reasons: when required by law, or to protect the rights, property or safety of our users, the public or Magic Booking.
  • Business transfers: in a merger, acquisition or sale of assets, with prior notice and under the protections of this policy.

7. Cookies

We use cookies needed to operate the service and an optional booking-contact cookie that you can enable. We do not use advertising or analytics cookies.

  • Session: keeps you signed in to your organizer account until you sign out or the session expires.
  • Preferences: your language, time zone, week start, time format and currency, kept for 30 days.
  • Optional booking details: only if you check "Remember my details on this device", a successful reservation saves your name and email address in a browser-readable cookie for 30 days. It prefills your name, email and email confirmation on this site's booking pages; the email is stored only once. The cookie is not an account or reservation-access credential. It is scoped to booking pages and is not used in Design Studio previews. Uncheck the option on a booking form to delete it immediately, or clear this site's cookies in your browser. Avoid enabling it on a shared device.
  • Active business: remembers which of your businesses you are managing.
  • Reservation access: lets a participant open their reservation page after following a personal link, until that link expires.
  • Security: short-lived cookies that protect the Google connection flow (10 minutes) and email address changes.

hCaptcha may set its own cookies when its challenge is shown.

8. Retention and deletion

  • Organizer accounts: kept while your account is active. When you close your account, your account, businesses and pages are archived, all sessions are revoked, and calendar credentials and Google account identities are erased. Records linked to reservations, billing and accounting are kept as long as needed for those purposes and our legal obligations. You can ask us to delete the remaining personal data where the law allows.
  • Participant data: personal management links stay valid until 30 days after the reserved event. The participant's name, email address and answers are anonymized 24 months after the end of the reserved event. Payment and accounting records are kept as required by law.
  • Calendar data: see Google Calendar data and Other connected calendars. Cached events expire after about two minutes.
  • Sign-in links expire after 15 minutes. The records of email requests used to limit abuse are removed after a short period, and the hashed addresses used to limit requests after one day. Hashed addresses on the list of addresses we no longer email are kept until the address is removed from it, for example at your request to our support team.

9. Security

We protect personal data with encryption in transit (HTTPS), encryption at rest for calendar credentials and tokens (AES-256-GCM), hashed access links, strict access control so that each organizer can only reach their own businesses and reservations, and limits against automated abuse. No system is perfectly secure; if a breach affects your personal data, we will notify you and the authorities as required by law.

10. Your rights

Depending on where you live, including under the EU and UK General Data Protection Regulation and Japan's Act on the Protection of Personal Information, you may have the right to access, correct, delete or export your personal data, to object to or restrict its processing, and to withdraw your consent at any time (for example by disconnecting a calendar). You can also lodge a complaint with your data protection authority.

Organizers can update most of their data in the dashboard. Participants should contact the business they booked with for requests about a reservation; we will help the business answer them. You can also contact us directly. We may need to verify your identity before acting on a request.

11. International transfers

Magic Booking is operated from Japan. Our service providers, such as Stripe, hCaptcha, Google and Resend, may process data in other countries, in particular the United States. Resend, Inc. is a United States company; our emails are sent from its Tokyo region. When personal data is transferred across borders, we rely on appropriate safeguards, such as adequacy decisions, standard contractual clauses, or the measures required by Japan's Act on the Protection of Personal Information for transfers to third parties in foreign countries.

12. Children

Organizer accounts are not intended for anyone under 16. Reservations for children should be made by a parent or guardian. If you believe a child has given us personal data without appropriate consent, contact us and we will delete it.

13. Changes to this policy

We will update this page when our practices change and revise the date at the top. If a change affects how we use data you already shared, in particular Google user data, we will notify you in the app or by email and, where required, ask for your consent before using the data in the new way.

14. Contact us

For any question or request about this policy or your personal data, contact us at …, or by mail:

Baptiste Thomas Langlet (b-t-l, Magic Booking)
2-12-1-405 Matsugaya, Taito, Tokyo 111-0036, Japan