Privacy and data use

Scheduler stores these data categories:

• Identity data: your Google subject, name, email address, profile image, and authentication sessions.
• Scheduling poll data:poll details, candidate times, invited participants, participation, and the organizer's chosen time.
• Response data: the availability you explicitly submit for each candidate time.
• Calendar configuration: connection status, private Calendar identifiers and labels, and the calendars selected for conflict checks.
• Credential data: encrypted OAuth credentials needed for authorized Google Calendar operations.
• Security and operations data: authentication session metadata such as IP address and user agent, HMAC-derived rate-limit identifiers and counters, and restricted operational records containing identifiers, actions, outcomes, timing, and error categories.

An unfinished create-poll form may be saved in your browser's session storage so it can survive a sign-in or a recoverable error. It is scoped to your account in that browser session and cleared after successful creation.

Calendar busy intervals are transient assistance data. They are never stored, logged, or shared. Scheduler does not request or store Calendar event titles, descriptions, locations, or attendees during availability checks. Only your submitted responses are shared with other participants.

Google processes identity sign-in and authorized Google Calendar operations. Cloudflare hosts Scheduler and processes application requests and stored application data on Scheduler's behalf. Scheduler remains responsible for how these services are used.

On Scheduler's current Cloudflare Workers Free plan, Workers Logs containing request and response metadata and restricted application operational logs are retained for up to three days. Workers Logpush is not enabled, so Scheduler does not export those logs to a separate log store. Cloudflare separately makes aggregate Worker metrics, such as request counts, errors, and performance measurements, available for up to three months; those metrics are not individual log events.

Choose Download my data in Account settings to export JSON containing your Scheduler profile, Calendar configuration without credentials, created polls, claimed participation, and submitted responses.

You can correct poll details you control and replace or withdraw your availability while a poll is open. Contact us to request a correction you cannot make in the application. You can withdraw Google Calendar access by disconnecting Calendar, revoke access in your Google Account, and continue responding manually.

You can delete your account. Scheduler removes sessions, OAuth credentials, Calendar configuration, and live direct identifiers during local deletion processing; cancels open polls you organize; and de-identifies shared records until their normal deletion date. A confirmed request that cannot finish is safely reapplied. Finalized Google Calendar events remain intact.

Deleting Scheduler data or disconnecting Calendar does not remove a Google Calendar event that Scheduler already created. Google and the event organizer or attendees control that external record. If an in-progress Calendar operation cannot be reconciled during account deletion, you may need to manage the Google Calendar event directly.