Privacy policy

Breez uses managed Neon Auth for Google sign-in or email verification codes. Account information includes your account ID, email address, display name, Google profile information if you use Google sign-in, and verification and session information. Google sign-in does not connect a calendar; calendar access requires a separate authorization and source selection.

When you connect Google Calendar, Outlook, or ICS calendar subscriptions, Breez stores provider account identifiers, access credentials needed to maintain the connection, calendar names and identifiers, and sync status. For ICS subscriptions, this includes the subscription URL. Provider calendar access is read-only.

Breez stores events from selected source calendars, including event identifiers, titles, times, locations, descriptions, recurrence information, attendees, and free/busy status when supplied by the provider. It also stores your View settings, Visibility and Sharing choices, and Busy blocks. If you contact support, we receive your email address and the information you send.

Breez uses this information to sign you in, connect and sync source calendars, maintain your Breez Calendar and Views, apply Visibility settings, deliver shared Views and Calendar subscriptions, and keep the service reliable and secure. Breez does not create, change, or delete events in your source calendars.

Breez does not sell personal information, use calendar content for advertising, or use calendar content to train generalized AI models. Breez uses OpenAI's ChatGPT Ads Measurement Pixel to measure completed account registrations attributable to advertising, as described below.

When you enable Sharing, anyone with the Sharing link can view or subscribe to that View. Your Visibility choices determine whether a source shows generic Busy time, titles and times, or full details. Attendee lists, account identifiers, provider credentials, and private Busy-block labels are not included in shared Views.

Review the preview before sharing: titles, locations, and descriptions can contain information about other people. Recipients can forward the link or save copies. Disabling Sharing or resetting access stops future access through the affected link, but cannot remove copies already saved by recipients or their calendar apps.

Breez uses Neon for database storage and authentication, Vercel for the website, and Google Cloud for backend services, Calendar subscription delivery, and monitoring. These providers process information needed to deliver those services. We may also disclose information when required by law or necessary to protect the security of the service.

Breez's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Breez stores account and calendar data in Neon, uses owner access controls, and keeps provider credentials on the server. We use safeguards designed to protect data in transit and at rest, but no service can guarantee complete security.

Human access to identifiable calendar content requires your affirmative permission for the specific data, a necessary security purpose, or compliance with applicable law.

Breez retains account and calendar data while needed to provide the service. Removing a source calendar deletes its copied events and View memberships. Disconnecting a source account also removes its stored credentials and source calendars. Revoking access through Google or Microsoft stops future authorized reads but does not itself delete data already stored in Breez.

You can request account deletion through support. After verifying the request, we delete your sign-in identity and stored account and calendar data, including active Sharing. Deleted data may remain in backups until they expire, and records needed for security or legal compliance may be retained only as necessary.

Breez uses cookies and session storage for sign-in and calendar authorization. Hosting and authentication services receive the technical request and session information needed to deliver the service. Breez records aggregate product actions and load times to understand use and reliability; analytics do not include calendar event content, account identifiers, or raw Sharing links.

On the production landing and sign-in pages, Breez loads OpenAI's ChatGPT Ads Measurement Pixel. The pixel uses first-party attribution and browser-reference cookies (__oppref, up to 30 days; __obref, up to 365 days) and sends technical request information to OpenAI to measure ad performance. After a new Breez profile is created, Breez sends a registration_completed event from its server through OpenAI's Conversions API, using those existing attribution references without delaying access to the Calendar. Server events require a valid pixel browser-reference cookie. Breez does not load the pixel on private Calendar pages or Shared Views, and does not pass calendar content, source names, Sharing links, contact information, or account identifiers in conversion events.

If automatic advanced matching is enabled for the pixel in Ads Manager, OpenAI's SDK can detect supported contact information on pages where it runs and hash it in the browser for conversion matching. Breez does not manually supply contact information to the pixel. Registration events opt out of future user-level personalization. Stored measurement-consent denials are respected by the pixel, which removes its attribution cookies when consent is denied. Registrations without a valid browser-reference cookie are not forwarded by the server. Breez does not change its cookie or analytics behavior in response to a browser's Do Not Track signal. Google and Microsoft process information under their own privacy policies when you use their services.

You can review your calendars and events, change View Visibility, disable Sharing, and remove sources in Breez. Correct source events in the original calendar; Breez receives those changes during sync. Contact support to request access to, correction of, or deletion of your personal information. We verify requests before releasing or deleting account information.

Breez is not intended for children under 13. We do not knowingly collect personal information from children under 13. Contact support if you believe a child has provided personal information so we can investigate and remove it.

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

Breez is operated by Kevin Liu in California. For a privacy request, include your account email address and a brief description of the request.

This policy is effective September 30, 2026. Updates will be posted here with a revised date. Material changes will be announced in the service or by email. We will obtain your consent before using Google user data for a new purpose.

For the rules governing use of Breez, see our Terms of Service.