Privacy Policy

Meet Watchdog Chrome Extension — Last updated May 2026

Google API Services User Data

Meet Watchdog's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

OAuth scope used

The extension requests one Google OAuth scope: https://www.googleapis.com/auth/calendar.readonly — read-only access to Google Calendar. The extension cannot create, edit, or delete any calendar data.

Specific data fields accessed

The following fields are retrieved from the Google Calendar API (events.list endpoint) for calendar events occurring within a rolling ±2 hour window:

• summary (event title) — displayed in the alert notification so you know which meeting is starting.
• start.dateTime / end.dateTime — used to determine whether a meeting is currently active or starting soon.
• hangoutLink and conferenceData.entryPoints — the Google Meet, Zoom, or Teams URL used to open the call when you click Join Now.

No other Calendar fields (attendees, descriptions, locations, organiser details, recurrence rules, etc.) are requested or processed.

How this data is used

Google Calendar data is used exclusively to power the meeting alert feature. Specifically:

• Event titles and times are used to detect active meetings and compose the notification text shown to you.
• Meeting URLs are used solely to open the correct call link when you act on an alert.
• No Calendar data is used for advertising, analytics, user profiling, or any purpose other than alerting you to active meetings.

Data retention and storage

Calendar data is fetched live from the API each time the extension checks for meetings (once per minute). It is processed in memory and immediately discarded. The only information written to persistent storage (chrome.storage.local) is a record of which meeting IDs have already been alerted — no event titles, times, or URLs are persisted.

OAuth token handling

The Google OAuth access token is managed entirely by Chrome's built-in identity system (chrome.identity). Meet Watchdog never reads, stores, logs, or transmits the token value. The token never leaves your browser.

Data sharing and transfer

Google Calendar data is never sold, shared, transferred, or disclosed to any third party. It is never transmitted to any server operated by the developer or anyone else. The only outbound connection the extension makes is directly from your browser to https://www.googleapis.com/ using your own credentials.

What the extension accesses

Meet Watchdog requests read-only access to your Google Calendar in order to:

• Read the titles, start times, and video call links of your calendar events
• Determine which meetings are currently active or starting soon
• Check whether you have that meeting open in a Chrome tab

Access is granted through Google's OAuth 2.0 flow via Chrome's built-in identity API. The extension only requests the calendar.readonly scope — it cannot create, edit, or delete calendar events.

How your data is used

Calendar data is used solely to power the meeting alert feature. Specifically:

• Event titles and start times are used to identify active meetings and compose the alert notification text
• Video call URLs (Google Meet, Zoom, Teams) are used to open the correct call link when you click Join Now
• A small record of which meetings have been alerted or attended is stored locally in your browser (chrome.storage.local) so the extension knows when to stop alerting

Data storage and retention

All data stays on your device:

• No server. Meet Watchdog has no backend server. Nothing is transmitted off your computer.
• Local storage only. The only things written to storage are your settings (alert timing preferences) and a small state file tracking which meetings you've attended. Both are stored in Chrome's local extension storage on your machine.
• OAuth token. Your Google access token is managed entirely by Chrome's identity system. Meet Watchdog never reads, stores, or logs the token value itself.
• Clearing data. You can reset all meeting state at any time via the extension popup → Reset meeting state. Uninstalling the extension removes all stored data.

Data sharing

Meet Watchdog does not share any data with anyone. There are no analytics, no crash reporting services, no advertising networks, and no third-party SDKs. The only external connection the extension makes is directly to Google Calendar API (www.googleapis.com) to read your own calendar — using your own credentials.

Permissions explained

• identity — to sign in with your Google account via Chrome's built-in OAuth flow
• tabs — to check whether a meeting URL is already open in a Chrome tab (so it knows you've joined)
• notifications — to show the meeting alert pop-up
• alarms — to check your calendar once per minute in the background
• storage — to save your settings and meeting attendance state locally
• offscreen — to play the alert sound using the Web Audio API

Children's privacy

Meet Watchdog is a productivity tool intended for adults. It does not knowingly collect any information from children under 13.

Changes to this policy

If this policy changes materially, the updated version will be posted here with a new "Last updated" date. Continued use of the extension after a change constitutes acceptance of the updated policy.

Contact

Questions about this privacy policy can be directed to the project's GitHub Issues page.