Private calendar availability

Your calendar connection

Privacy policy

This policy describes the private scheduling connector called Private calendar availability, used by its owner and invited users.

Effective November 1, 2026

What the connector accesses

With your authorization, the connector requests only https://www.googleapis.com/auth/calendar.events.freebusy. It reads busy start and end times for the calendar selected privately in its configuration.

It does not request event titles, descriptions, locations, attendee lists or permission to create, change or delete calendar events.

How availability is used

Busy periods are used to display availability in a private scheduling system and, if enabled by the operator, to prevent conflicting bookings. Calendar availability is not sold, used for advertising or used to train AI models.

The connector obtains calendar data directly from Google APIs. This public information site does not receive calendar data, OAuth grants or calendar credentials.

Storage, access and retention

Busy snapshots are stored in a temporary, nonpersistent application cache with a 15-minute freshness limit. Stale or failed connections are identified in the private system; the operator must review those indicators.

Calendar identifiers and OAuth credentials are kept in access-controlled private connector files, separate from this website and its source. Authorized operators administer the connection. Access to availability in the scheduling system is controlled by application permissions.

Persistent application records retain connection metadata, health information and internal scheduling review references. They do not store Google event titles, descriptions or locations. Disconnecting a calendar does not automatically delete existing connection metadata or internal review history.

Disconnecting and removing credentials

You may revoke the app's access through Google Account connections. Revocation prevents future authorized reads from that account.

To stop use in the private system, contact the operator who invited you. The operator disables the connection and removes its private credential file. Existing temporary snapshots age out within the freshness limit; retained metadata and review references are handled separately by the operator.

Support and privacy requests

Contact the operator who invited you for access, disconnection or credential-removal requests. The Google authorization screen also identifies the app's support contact.

This policy covers the calendar connector. It is not a patient privacy notice or a statement about clinical services.