Privacy policy
Effective November 18, 2026
In short: Knock Knock reads your calendar so it can ring you before meetings. That data stays in your browser. It is never sent to us or to anyone else, and there are no servers, analytics or ads.
What Knock Knock is
Knock Knock is a browser extension for Chrome, other Chromium browsers, and Firefox. It rings you shortly before Google Meet meetings on your calendar, with buttons to join or snooze.
Data the extension accesses
If you sign in with Google, Knock Knock asks for read-only access to your calendar events (the https://www.googleapis.com/auth/calendar.events.readonly scope). It reads events on your primary calendar from about 15 minutes ago to 24 hours ahead, and uses:
- each event's ID, title, start and end time, status and type;
- the event's Google Meet link, and its description and location, which are read only to find a Meet link;
- attendee names or email addresses, and your own response (accepted, declined and so on), so declined meetings don't ring;
- the calendar's email address, shown in settings so you know which account is connected.
If you use a secret iCal address instead, Knock Knock reads the same kinds of fields from that feed, and the address itself is stored as a setting.
Knock Knock can't change your calendar, and it doesn't access email, contacts, files or any other Google data.
How the data is used
Only to provide the extension's single feature: work out which meetings to ring for and when, show the meeting's title, time and attendees in the ring window and settings page, and open the meeting link when you click Join.
Where the data is stored
- On your device only. Upcoming events, ring state (for example "snoozed") and your settings are kept in the browser's extension storage.
- The Google access token is kept in session storage, held in memory and cleared when the browser closes. It's never written to disk by the extension.
- Only events between about 15 minutes ago and 24 hours ahead are kept. Older ones are removed at the next calendar check, which happens every 5 minutes.
Sharing
None. Knock Knock has no backend server. Calendar data is never sent to the developer or to any third party, and it's never sold, used for advertising, or used to train AI models. The only network requests the extension makes are to Google, to sign in (accounts.google.com), read your calendar (www.googleapis.com or calendar.google.com) and revoke access when you sign out (oauth2.googleapis.com). It opens meet.google.com when you click Join.
Google API Services User Data Policy
Knock Knock's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Your choices
- Sign out in Knock Knock's settings to disconnect your calendar, revoke the extension's access token and clear the stored events.
- Revoke access at any time at myaccount.google.com/permissions.
- Uninstall the extension to delete everything it stored. Browsers remove an extension's storage when it's uninstalled.
Children
Knock Knock isn't directed at children under 13 and doesn't knowingly collect their data.
Changes
If this policy changes, the new version will be posted on this page with a new effective date. Material changes to how data is used will be announced in the extension's store listing.
Contact
Questions about privacy: knock-knock.gerbil269@passmail.com.