Privacy

Your data,
treated calmly.

Plain-language privacy. No third-party tracking. No data sales. Just what we collect, why, and how to remove it.

01

What we collect

When you sign up, we collect your email and a password hash. When you complete onboarding, we add your display name, username, bio, and timezone. That's it on the account side.

When someone books with you, we collect their name, email, timezone, and any notes they include. This is the bare minimum needed to send confirmation emails and manage the event.

We also generate unique confirmation and cancellation tokens for each booking so attendees can manage their appointments without logging in. A temporary lock token is used to reserve a time slot for up to 5 minutes during the booking flow.

If a meeting URL or location detail is provided (e.g. Google Meet, Zoom, in-person address), we store it with the booking so both parties can join.

We log standard request metadata: IP address, user agent, request path, and response time. These are kept for 30 days for debugging and abuse prevention, then deleted.

02

Booking status & history

Each booking has a status: pending, confirmed, cancelled, rescheduled, no-show, or completed. We store this status and, where applicable, the reason for cancellation or the original booking a reschedule replaces.

This history is visible to the host in their dashboard and helps manage scheduling accurately. Guests see only their own booking status.

03

Invoices & payments

When you create an invoice, we store business details, client information, line items, amounts, and payment status. Invoice data is linked to the booking it relates to, if applicable.

Payments are processed through Stripe. We store the payment transaction ID, amount, currency, and status (e.g. paid, failed, partially paid). Payment activity is logged alongside the invoice for auditing.

We do not store full credit card numbers or bank details — those are handled entirely by Stripe.

04

What we don't collect

No third-party tracking. No advertising pixels. No behavioral profiling. No cross-site analytics.

We don't sell, rent, or share your data with anyone. There is no data broker arrangement.

05

How we store it

Passwords are bcrypt-hashed before storage; we never see your plaintext password.

Database is PostgreSQL with at-rest encryption. Backups are encrypted and rotated weekly.

Sessions are httpOnly, Secure cookies with CSRF protection. Tokens are never exposed to JavaScript.

Cancellation and confirmation tokens are UUIDs stored in the database. Lock tokens are stored temporarily in Redis and expire automatically within minutes.

06

Data retention

Account data is kept for as long as your account is active. If you delete your account, all associated data is permanently removed within 7 days.

Booking records are kept for the lifetime of the account to provide accurate scheduling history. After account deletion, booking data is anonymised.

Request metadata logs are deleted after 30 days. Lock tokens in Redis expire after 5 minutes automatically.

Invoice records are retained for accounting purposes. You can delete draft invoices at any time; paid invoices are retained as part of your financial records.

07

Calendar integrations

When you connect Google Calendar, we receive an OAuth token scoped to read and write calendar events. We use it only to detect conflicts and create booking events on your calendar.

We do not read events outside of conflict detection. We do not store the contents of your existing calendar events.

You can disconnect calendar integrations at any time from Dashboard → Settings → Calendars. Disconnection revokes the token immediately.

08

Cookies

We use only essential cookies for session authentication and CSRF protection. These are Strictly Necessary cookies — no consent is required for them to function.

No analytics cookies, no tracking cookies, no third-party ad cookies are placed on your browser.

You can configure your cookie preferences at any time using the cookie banner in the footer of the page.

09

Email

Transactional emails (booking confirmations, cancellations, reminders, invoices) are sent via Resend. They store the email address and message body for delivery purposes.

We do not send marketing emails to attendees. We do not add you or your guests to any newsletter.

10

Your rights

Export: contact us and we'll send you a JSON export of your account, event types, availability, invoices, and bookings.

Deletion: contact us and we'll permanently delete your account and all associated data within 7 days. This includes bookings made by guests, anonymized after deletion.

Correction: most fields are editable in Dashboard → Settings. For anything else, contact us.

11

Changes

If we make material changes to this policy, we'll notify you by email at least 30 days before they take effect. The current version is dated below.

Last updated: May 28, 2026. Questions? Contact us.