Privacy policy

Breez supports calendar providers such as Google Calendar and Outlook and may support additional providers over time. When you connect a supported provider, Breez may access and store the provider account details needed to identify and maintain the connection, such as a provider user ID, email address if supplied by the provider, linked account identifiers, and token expiry metadata.

Breez also stores the OAuth credentials needed to maintain an active provider connection, such as access tokens, refresh tokens, and token expiration times. For Google, Breez currently requests read-only calendar access together with basic account identity scopes used to complete OAuth and identify the connected Google account.

For each linked calendar, Breez stores calendar metadata such as the provider name, external account ID, external calendar ID, and external calendar name.

To build your Breez availability surface, Breez reads and stores event data from the calendars you link. Depending on what a provider returns, this may include event IDs, event status, recurrence data, original start times, start and end times, summary or title, description, location, and attendee information.

Breez uses connected provider data to authenticate linked accounts, discover the calendars available to you, refresh OAuth access when needed, synchronize linked calendars, maintain your Breez calendar, render owner views, enforce share-link visibility settings, generate iCal feeds, troubleshoot reliability issues, and prevent abuse.

Breez stores synced event data in its own service so it can render owner and shared availability views without fetching the same provider event data on every request.

Breez does not use connected calendar content for advertising and does not sell connected provider data.

Breez shares connected provider data only as needed to operate the service, as you direct it, or as required by law. Breez does not publish your source calendars directly as standalone calendars.

If you create a share link or use an iCal subscription feed, Breez may disclose availability derived from linked calendars to anyone who has that link. Depending on the visibility settings you choose for each linked calendar, viewers may see either busy-only entries or fuller event details such as titles, descriptions, locations, and attendee display names.

Breez may also disclose connected provider data to service providers that host, store, secure, authenticate, and monitor Breez on our behalf, such as cloud hosting, managed database, authentication, and logging or monitoring providers. These providers may process data only to provide services for Breez.

Breez may disclose data when required to comply with law, enforce our terms, or protect the rights, safety, and security of Breez, its users, or others.

OAuth credentials, linked-account metadata, linked-calendar metadata, share-link configuration, and synced event data are stored server-side. Breez uses access controls to limit access to account-owned records and keeps service credentials on the server side only.

Breez stores share-link tokens as hashes rather than storing raw share tokens in the database, and Breez is designed to redact sensitive values such as access tokens, refresh tokens, and event content from application logs where feasible.

Breez uses technical and organizational safeguards designed to protect connected provider data in transit and at rest, but no method of transmission or storage can be guaranteed to be completely secure.

Breez retains linked-account metadata, linked-calendar metadata, OAuth credentials, share-link configuration, and synced event data for as long as they are needed to provide the service, maintain active linked calendars, and support the share links or iCal feeds you keep active.

If you disconnect a linked account, delete a linked calendar or share link, or ask Breez to delete your data, Breez will stop using the affected data for future syncs and will delete or clean up associated Breez records, subject to limited retention needed for security, fraud prevention, legal compliance, dispute resolution, or backup recovery.

Breez sync processes also update or remove copied event data when linked source events or linked calendars are removed from the provider or from Breez.

Breez uses cookies and similar session storage to keep you signed in and to protect authentication flows.

Breez also records privacy-safe product analytics for launch and reliability work, such as page views, CTA clicks, auth outcomes, and performance or friction signals. These analytics are designed to avoid raw share tokens, calendar event contents, and direct personal details in event properties.

For support, privacy questions, or deletion requests, contact Breez at support@breezcal.com.

When contacting Breez about deletion, please include enough information for Breez to identify the relevant account, linked provider, and linked calendars so the request can be verified and processed.

Breez may update this page as the product changes. Material updates will be reflected by the last updated date above.