Slotcheck Privacy Policy

Last updated: 20 July 2026

Slotcheck shows your Google Calendar beside meeting scheduling pages so you can check your availability without switching tabs. It has no servers. Your calendar data never leaves your browser.

Who we are

Slotcheck is a Chrome extension published by Gravity Zero Labs. Questions about this policy or your data can go to contact@slotcheck.app.

What Slotcheck accesses

When you connect a Google account, Slotcheck requests read-only access to:

Your calendar list — calendar names and display colours, so you can choose which ones to show.
Calendar events — title, start time, end time, and your own response status, for the dates you view.
Basic profile information — your email address, name, and profile picture, used to label connected accounts in the settings screen.

The only Google scope requested is https://www.googleapis.com/auth/calendar.readonly, alongside standard email and profile scopes. Slotcheck cannot create, edit, move, or delete anything in your calendar. The access is read-only by design, and the extension contains no code that writes to the Calendar API.

How your data is used

Calendar data is used for exactly one purpose: rendering your events on a timeline inside the extension's side panel, and showing a count of events on the date you have selected on a scheduling page. That is the entire feature.

Slotcheck does not:

Send your calendar data to any server operated by us or anyone else
Use your data for advertising, profiling, or building any user model
Sell, rent, or share your data with third parties
Use your data to train machine-learning models
Run analytics, telemetry, tracking pixels, or third-party scripts of any kind

Where your data is stored

Everything stays on your computer, in your browser's local extension storage (chrome.storage.local). This includes your access token, your account's email, name, and profile picture, your calendar list and which calendars you enabled, your preferences, and a short-lived cache of recently viewed events.

There is no Slotcheck backend. We operate no servers, no database, and no logging infrastructure. There is no account to create and no data for us to hold, because your information is never transmitted to us. The only network requests Slotcheck makes are directly from your browser to Google's own APIs.

Cached events

To avoid re-requesting the same information, Slotcheck briefly caches events you have already viewed. Cached entries expire after five minutes, and entries older than seven days are deleted automatically. The cache lives only in local extension storage.

Pages Slotcheck runs on

Slotcheck activates on scheduling pages from Calendly, Cal.com, HubSpot Meetings, and SavvyCal. On those pages it reads only the date you have selected, so the calendar view can follow along.

Because scheduling widgets are frequently embedded in other websites, the extension requests access to all sites. This is used solely to place its button on a page that contains an embedded scheduler. Slotcheck does not read, collect, transmit, or store the content of pages you visit, and it takes no action at all on pages without a supported scheduler.

Google user data and Limited Use

Slotcheck's use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Your control and how to delete data

Disconnect an account — open Slotcheck's settings and choose Remove. Its stored token and data are erased immediately.
Remove everything — uninstall the extension. Chrome deletes all of its local storage, leaving nothing behind.
Revoke access at Google — visit myaccount.google.com/permissions and remove Slotcheck. This invalidates its access independently of the extension.

Children

Slotcheck is a workplace productivity tool and is not directed at children under 13.

Changes to this policy

If this policy changes materially, the updated version will be published at this URL with a revised date above. Any change expanding how data is used would require your renewed consent through Google's permission screen.