Privacy Policy

Account information. When you create an account we store your email address, a Cadence handle (the public username in your booking links), your display name and time zone. Passwords are handled by our authentication provider and are never stored in readable form.

Scheduling data. The details you configure in Cadence: availability rules, event types, custom booking questions, buffers, notice periods and team settings.

Bookings. For every booking we store the event type, the chosen time, the invitee's name, email address, time zone and their answers to your custom questions, plus reschedule and cancellation history.

Calendar data. Described in detail below under "Google Calendar access".

When you connect a Google Calendar, Cadence asks Google for permission to access your calendar through Google's official OAuth sign-in. You approve this on a Google page — Cadence never sees or stores your Google password.

What Cadence requests and why:

• Read your calendars' free/busy information — so Cadence can hide time slots where you are already busy and offer only genuinely free times on your booking pages. Cadence reads event time ranges for connected accounts, not their full contents or attendee lists.
• Create and update events — so a confirmed booking is written into the calendar you designate, and so a reschedule moves that same event instead of creating a duplicate.
• Delete events Cadence created — so a cancelled booking is removed from your calendar. Cadence does not delete events you created yourself.

You can connect more than one Google account. Busy times from every connected account are checked against bookings, but events are written only to the single calendar you designate as the write target.

Use and limitation. Calendar data is used exclusively to operate scheduling: computing availability, preventing conflicts, creating, moving and removing booked events. We do not sell calendar data, use it for advertising, train AI models on it, or share it with third parties except the infrastructure providers needed to run the service.

Disconnecting. You can disconnect a Google account at any time from the Integrations page. Disconnecting removes Cadence's stored access to that account and deletes its cached busy-time data. You can also revoke Cadence's access from your Google Account security settings at any time.

Calendar connections are stored with their access keys encrypted, and those keys are only readable by Cadence's server — never by your browser or anyone else's. Access to your data inside the app is protected by row-level database policies, so one account can never read another account's bookings, contacts or connections.

All traffic to Cadence is encrypted in transit. Access to scheduling operations is logged, and booking creation is validated inside the database to prevent duplicate bookings even under concurrent requests.

Your data is retained while your account is active. You can delete individual bookings, contacts, event types and calendar connections from within the app at any time.

To delete your account and all associated personal data — including calendar connections, cached busy-time data, bookings and contacts — email jeanlucandrenavarro@gmail.com and we will process the deletion. Disconnecting a calendar account removes that account's tokens and cached busy data immediately.

If you book time with a Cadence host, the host receives your name, email, time zone and your answers to their booking questions in order to run the meeting. The host is the controller of that information. Cadence processes it on their behalf, and invitees can reschedule or cancel their own bookings through the link in their confirmation.

We will update this page when the policy changes and note the date above. Questions or deletion requests: jeanlucandrenavarro@gmail.com.