Your data, plainly explained.

You can reach me at [email protected] for anything in this policy — a question, a data request, or a concern.

Business owners — the studio, salon, or gym owners who run their schedule on GettingBooked — provide: their name and email address (used to sign in and receive notifications), their business name and public booking-page settings (timezone, cancellation policy, appearance choices).

Members — the people who book a class or appointment — provide: their name, and an email address and/or phone number, either when they book for themselves or when a business owner adds them manually. Their booking and attendance history is recorded automatically, and a business owner can add private notes about a member (visible only to that business, never to the member).

We also automatically see standard connection information any web request carries — IP address, browser type, pages requested — handled at the infrastructure level by Cloudflare (see Section 05), not separately logged or analyzed by us beyond what's needed to run and secure the service.

We use industry-standard AES-256 encryption for those fields. To still let the app check "does this email already have a booking?" without ever decrypting data just to compare it, we keep a separate one-way cryptographic fingerprint of each email/phone alongside the encrypted value — it can confirm a match but can't be reversed back into the original.

A member's name is kept as plain text on purpose — business owners need to see, sort, and search it directly to run their day-to-day, the same way a paper sign-in sheet would work.

• Running the service: letting a business manage its schedule and members, and letting a member book, cancel, or join a waitlist.
• Signing you in: passwordless sign-in works by emailing a one-time 6-digit code — that's the entire purpose of collecting an email address at sign-in.
• Notifications: booking confirmations, cancellation notices, waitlist offers, and — for business owners — automatic 30/90/365-day "how's it going" stats reports.
• Keeping things running: diagnosing bugs and errors (Section 05) and understanding traffic patterns so pages load well on the phones most visitors actually use.

We do not sell member or business data, and we do not use it for advertising.

Google Analytics (GA4) only runs, and only sets its cookies, after you choose "Accept" on the cookie banner shown on your first visit. Choosing "Decline" — or just not choosing — means it never loads at all. You can change your mind any time by clearing your browser's site data for this domain, which brings the banner back.

Sentry can capture a masked video-like replay of the ~60 seconds before a crash to help fix it — by default it blurs all text and blocks all images/media, so it's built specifically to avoid capturing member details, but it's worth knowing it exists. It isn't gated by the cookie banner since it isn't a tracking/advertising cookie.

Where you arrived from is remembered for the current browser tab only (session storage, gone when you close it): the site or campaign tag that brought you here, such as "google" or "instagram", and the first page you opened. If you create a studio, that is saved with it so we can tell which pages bring new studios. It is not personal data, it never goes to Google Analytics on its own, and it is never a full web address.

Signing in stores a session token in your browser's local storage (not a tracking cookie) so you don't have to re-enter a one-time code on every visit. It expires automatically after 24 hours.

Email open and click tracking. Emails GettingBooked sends contain a tiny invisible image and links that pass through track.gettingbooked.app, run by Resend. When the image loads or a link is clicked, Resend records that it happened, when, and the IP address and device or email app it came from. We use this to check that important emails, like a waitlist offer with a deadline, actually reach people in time. It's never used for advertising or shared with anyone else. Most email apps let you block remote images, which stops the open record; links still work either way.

• One-time codes are single-use and expire after 15 minutes, whether or not they're used.
• Session tokens expire automatically after 24 hours.
• A business owner can permanently delete their entire business at any time, from Settings → Danger zone — every member, booking, and setting goes with it, and it can't be undone.
• Businesses that go quiet (no owner sign-in and no scheduled sessions for a while) are flagged internally and, after a warning period, may be removed to keep the platform tidy.
• A member who wants their information removed can ask the business they booked with — an owner can remove any member from their roster at any time — or write to us directly at [email protected].
• Telegram alerts, if a business owner has connected Telegram, are kept by Telegram in the owner's chat. Deleting a member or a business in GettingBooked doesn't remove alerts already delivered; the owner can delete them in Telegram.

For a member's own data, the business you booked with is usually the fastest route — they can see and edit it directly from their Members tab. For anything platform-level, or if you'd rather go straight to the source, write to [email protected] and we'll handle it directly.

GettingBooked isn't directed at, and doesn't knowingly collect information from, children under 16. If a business runs classes for minors (kids' swim lessons, junior gymnastics, and so on), that business — not GettingBooked — is responsible for getting whatever parental consent applies before entering a child's details, exactly as they would for a paper sign-up sheet.

Cloudflare, Resend, Google, Sentry, and (if a business owner connects it) Telegram all run global infrastructure, so information may be processed in countries other than where your business or its members are based. Each maintains its own security and privacy commitments, which is part of why they were chosen; you can read their respective privacy policies for details on their own practices.

No online service can honestly promise to be unbreakable — least of all one built and run for free by a single independent developer rather than a company with a dedicated security team. Real care has gone into the parts that matter most: encrypting member details at rest, expiring codes and sessions automatically, rate-limiting sign-in attempts, and using industry-standard encryption (TLS) everywhere data moves. That's a genuine effort, not an absolute guarantee, and it's better to say so plainly than to imply otherwise.

The date at the top always reflects the latest version. If a change is material — a new third party, a new use of member data — we'll flag it in the in-app "What's New" changelog the same way a new feature would be announced, not just quietly bump the date.

Questions, requests, or concerns about this policy: [email protected].