Effective date: 31 October 2026
Last updated: 31 October 2026
ClassesBook ("ClassesBook", "we", "our", "us") provides the ClassesBook website and web application for studios to publish classes and for members and instructors to book and teach them. The marketing site is classesbook.com. The application is app.classesbook.com. ClassesBook is owned and operated by Alessandro Cusenza, a self-employed entrepreneur, who is the data controller for the personal data described in this policy. VAT number: MT 3006 6012. Postal address: Flat 7, Triq Il-Barrakki 68, Qormi, Malta QRM1054.
If you have questions about this policy, or you want to exercise your privacy rights, contact us at info@classesbook.com.
This policy describes how we collect, use, store, share, and retain personal data when you use ClassesBook, including Google Sign-In and the optional Google Calendar connection. It is the policy we submit for Google OAuth verification.
When you create or sign in to an account we process the identifiers Firebase Authentication holds for you: a Firebase user id, email address, and sign-in method (email and password, email link, or Google).
If you choose Google Sign-In, Firebase Authentication uses Google's sign-in flow. The app requests Google's default profile scope and does not request Google Calendar at sign-in. We receive your Google account email. If Google provides a display name and profile photo, we store those on your ClassesBook profile when the account is first created. Firebase Authentication also keeps the Google account identifier for that sign-in (used later so Calendar can be linked only to the same Google account). We do not receive your Google password.
You and your studio may store name, phone, address, photo, role, studio name, timezone, class and booking settings, instructor profiles, and similar account fields in Firestore, and photos or documents in Firebase Storage.
We store class templates and sessions, bookings, waiting-room entries, packages and credits, instructor assignments, referrals, and related studio records so the product can run.
If a studio collects a waiver or intake form, the answers are stored for that studio and may be emailed to the studio.
Card numbers and similar payment-method secrets are collected and stored by Stripe, not by ClassesBook. We store Stripe identifiers we need to operate billing (for example Stripe customer id, Connect account id, Checkout session or payment-intent ids), amounts, currency, package purchases, and subscription status. Studios can connect a Stripe Connect account so members pay the studio. Studios may also record manual (offline) payments and optionally upload a proof-of-payment file to our Storage.
We send transactional email through Resend from no-reply@classesbook.com (booking confirmations, waitlist, payment notices, instructor invites, signup notices, and similar). Signup notices to studio administrators can include the new user's name, email, user id, signup method, and IP address when we have it.
For email-link signup, our server stores the caller IP in a short-lived signup session (up to 7 days) and may copy it onto the user profile after verification. On the login page, the browser may look up a public IP via api.ipify.org; that value is stored only if a new account is created from that Google Sign-In. We use IP addresses for abuse rate-limits and those signup notices—not for advertising.
Where the in-app Studio Assistant is enabled, your message, recent conversation memory, on-screen context, and a schedule snapshot (class names, times, locations, instructor names and profile ids, and similar fields needed to plan a request) are sent to Google Cloud Vertex AI (Gemini) so the assistant can propose actions. Proposed writes are stored as short-lived plans (15 minutes). Studio-visible audit rows record who ran which assistant action, not the full prompt.
The MCP connector lets a signed-in user authorise an external AI client to call the same studio tools. We store MCP OAuth client metadata and hashed secrets, short-lived authorisation codes, and refresh-token hashes. Tool calls run on our backend. We do not send MCP tool traffic to Gemini; the external client is chosen by the user and has its own privacy policy.
Described in the Google Account and Google Calendar data section below. Used only if you connect Google Calendar.
We use Firebase App Check with Google reCAPTCHA to reduce abuse. Cloud Functions write operational logs (including error messages) to Google Cloud Logging. We do not load a third-party product-analytics or advertising pixel on the app.
We are established for this service in Malta / the EU. We process personal data to:
We do not sell your personal data and we do not use Google user data for advertising.
We use processors that are required to run ClassesBook:
An MCP client you authorise (for example a ChatGPT-style connector) receives whatever that client's tools return while it is connected. Stripe Checkout and Google's sign-in, Calendar consent, and reCAPTCHA pages are hosted by those providers.
We may disclose data if required by law or to protect the rights, safety, or security of ClassesBook, our users, or the public. If we ever transfer the business, this data would move with it under this policy.
We keep account, profile, class, booking, payment-metadata, and similar Firestore and Storage records for as long as your account is active or as needed to provide the service and meet legal obligations.
Some items are removed or expire sooner in our systems:
Cloud logs, Resend's copies of email, and Stripe's copies of payment data follow those providers' retention. To ask us to delete what we hold, email info@classesbook.com (section 7).
If EU/EEA or UK GDPR applies, you may request access, correction, erasure, restriction, portability, and objection to processing based on legitimate interests, and you may withdraw consent where we rely on it.
There is no self-serve account deletion in the app. You can correct much of your profile by signing in and using Profile or studio settings. For access, correction, deletion, or other requests, email info@classesbook.com. We may need to verify that the request comes from the account holder.
You also have the right to complain to the Information and Data Protection Commissioner (IDPC) in Malta: https://idpc.org.mt — or to your local supervisory authority.
ClassesBook does not set a first-party advertising or analytics cookie, and the app does not include a cookie-consent banner.
We (and Firebase) use browser storage that is strictly necessary so you stay signed in and so short-lived product flows work:
emailForSignIn, displayNameForSignIn, referralIdForSignIn, subReferrerIdForSignIn, signUpIPAddressForSignIn, widgetModeForSignIn, signUpDisplayNamesByEmail); pending instructor invite classesbook.pendingInvite (48 hours). classesbook.returnUrl (1 hour), classesbook.activeStudioOwnerId, ai-assistant-session-v2:<uid> (assistant transcript on this device when the assistant is enabled), widgetMode. mcp_oauth_pending: only during MCP Google sign-in, to finish that authorisation. Third parties may set their own cookies when you use their pages or scripts: Google Sign-In, Google Calendar consent, reCAPTCHA, Stripe Checkout, Google Fonts, and the Bootstrap and icon CDNs loaded in the app shell. You can clear site data in your browser. That will sign you out.
Access to Google Calendar tokens, AI plans, MCP secrets, and similar backend collections is denied to the browser by Firestore rules; only our Cloud Functions (Admin SDK) read them. Calendar tokens are stored as Firestore fields and are not accessible from the browser. Google Cloud storage uses Google's default encryption at rest. Client secrets (Stripe, Resend, Google Calendar OAuth client) sit in Google Cloud Secret Manager. HTTPS is used on the hosted app. No method of transmission or storage is 100% secure.
ClassesBook is not directed to children under 16, and we do not knowingly collect personal data from children under 16. If you believe a child has provided personal data to us, contact info@classesbook.com.
Our Cloud Functions run in us-central1 (United States). Google, Stripe, and Resend may process data in the United States and other countries outside the EEA. Where GDPR requires appropriate safeguards for such transfers, we rely on the safeguards offered by those providers (which may include Standard Contractual Clauses). Connecting Google Calendar or the Studio Assistant necessarily sends the data described in this policy to Google.
We may update this policy. The new version will be posted on this page with a revised effective and last updated date.
If you sign in with Google, we receive your Google account identifier (the provider account id Firebase Authentication stores), your email address, and—when Google provides them and we are creating your ClassesBook profile—your display name and profile photo. We use these to create and recognise your ClassesBook account. Google Sign-In does not grant ClassesBook access to your calendar.
Connecting Google Calendar is optional and separate. We request these OAuth scopes: openid, email, and https://www.googleapis.com/auth/calendar.events. We ask Google for offline access (access_type=offline) and a consent prompt so we can keep a refresh token.
We use that access only to create, update, and delete class-session events that ClassesBook puts on your primary Google Calendar (classes you book, classes you teach, or studio templates the owner chose to sync). We do not import your existing calendar, and we do not read, import, or display your other events. We do look up upcoming events that ClassesBook previously created on your calendar (by our event identifiers) so we can update or remove them. We do not use Calendar data for advertising.
After you connect, our servers store a Google OAuth refresh token and a short-lived access token (plus expiry, Google account id, email, and granted scope) in the Firestore document googleCalendarTokens/<your Firebase user id>. Those documents are not readable or writable by the browser (Firestore rules deny all client access). They are used only by Cloud Functions on the server. We also store link status and the linked Google email on googleCalendarLinks/<your Firebase user id>, which you can read while signed in; that document does not contain the tokens.
We keep the tokens until you disconnect in ClassesBook, until Google tells us the grant is no longer valid (for example you revoked it at Google), or until you connect a different Google account. The Google Calendar OAuth client secret is in Secret Manager; it is not your token.
We do not sell this information, we do not use it for ads, and we do not share it except with the service providers needed to run the feature (Google Calendar API and Firebase / Google Cloud hosting this backend).
ClassesBook's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.
Members and instructors can disconnect in ClassesBook using the Google Calendar control on the Home page (the link-off control next to the Google Calendar switch). That removes upcoming ClassesBook events from the calendar, revokes the grant with Google (best effort), and deletes our stored tokens. Past ClassesBook events stay on the calendar. Studio owners connect Calendar from the class form and do not see that Home-page control; they can revoke at Google or email us.
Anyone can revoke ClassesBook's Calendar access at https://myaccount.google.com/permissions, or by emailing info@classesbook.com. If you revoke at Google, we delete our stored tokens the next time we try to refresh access. We cannot remove events from the calendar after Google has already cut off access.
Use the contact in section 1: info@classesbook.com.
Questions about this Privacy Policy: Alessandro Cusenza, Flat 7, Triq Il-Barrakki 68, Qormi, Malta QRM1054 — info@classesbook.com.