Privacy policy

Your calendar stays yours.

Calendar Check: Highlight Time Conflicts on Gmail, Handshake & Eventbrite | Last updated August 4, 2026

Short version. Calendar Check has no developer backend, advertising, analytics, or telemetry. Page and email text are processed in the browser to find times. Calendar information is requested read-only from the provider you choose, and the developer does not receive that data.

What this policy covers

This policy covers the Calendar Check Chrome extension, including its Gmail, Handshake, Eventbrite, JSON-LD event, Google Calendar, Outlook Calendar, and Apple or iCloud ICS features. It explains what the extension handles, why it handles it, where it is stored, and when it is sent directly to a service you choose.

Information the extension handles

Web pages and email content

On supported HTTPS pages, the extension reads the page text, structured event data, and relevant page metadata needed to find event times. When Gmail highlighting is enabled, it reads the scheduling text displayed in the Gmail message or thread you open. This processing happens in the browser. Raw page or email content is not sent to Calendar Check or stored as a message copy.

Calendar information

When you connect a calendar, the extension requests only the read-only information needed to compare event times:

Settings and time-zone choices

The extension stores your preferences, selected calendars, time-zone overrides, connection state, synchronization status, and a derived busy-time index so highlights can work without a server. An unsupported-page warning may retain the current page URL locally so the popup can identify the affected page. The extension does not build a browsing history or collect mouse, keyboard, scroll, or click analytics.

Authentication information

Google sign-in is handled through Chrome's Identity API. Outlook uses an authorization flow and stores its access and refresh tokens in the extension's private Chrome storage. These tokens are not sent to Calendar Check's developer or any analytics service.

How information is used

Information is used only to highlight time slots, determine whether they conflict with connected calendar availability, show optional event names, interpret time zones, refresh the local index, and support the extension's settings and error messages. The extension does not use user data for advertising, profiling, credit decisions, or unrelated product research.

Gmail reading and event-name tooltips are user-controlled features. The extension asks for the relevant consent or permission when those features are enabled.

When information leaves the device

Calendar Check has no server that receives page content, email content, calendar data, or authentication tokens. The extension makes direct HTTPS requests only to services required for a feature you chose:

Those services handle requests under their own policies: Google Privacy Policy, Microsoft Privacy Statement, and the policy of the ICS provider you choose.

No data is sold, rented, used for personalized advertising, or shared with the developer. Provider requests are limited to the calendar feature you activate.

Storage, security, and deletion

Settings and derived calendar data are stored in Chrome extension storage. Google manages its OAuth token cache through Chrome. Outlook tokens, the selected ICS URL, time-zone choices, and the derived busy index are kept in the extension's private storage. Network requests use HTTPS.

Disconnect a provider in the popup to remove its connection information. Removing the extension removes its extension storage under Chrome's normal extension-storage behavior. You can also remove the pasted ICS calendar URL by disconnecting Apple or iCloud.

Your choices

Policy changes and contact

If the extension's data practices change, this page will be updated before or when the change takes effect. The updated date above will show when the policy was last revised.

For privacy questions or deletion requests, open an issue in the Calendar Check GitHub repository.