1. What Meet Knock Does
Meet Knock is a Chrome extension that provides presence and interruptibility features for Google Meet calls. It lets team members mute and unmute their Meet tab and send knock signals to teammates.
2. Data We Collect
| Data | Source | Purpose | Stored where |
|---|---|---|---|
| User handle (self-chosen pseudonym) | User input during onboarding | Displayed to teammates in the participant list | Chrome sync storage (local) and Firebase Realtime Database (shared with meeting participants) |
| Mute state (speaker on/off, mic on/off) | Extension reads from Chrome tab state and Google Meet DOM | Displayed to teammates so they know who is available | Firebase Realtime Database, deleted when user leaves the meeting |
| Presence / last-seen timestamp | Generated by the extension every 30 seconds | Shows teammates who is currently in the meeting room | Firebase Realtime Database, deleted when user leaves or within 5 minutes of disconnection |
| Meeting code (from the Google Meet URL) | Read from browser URL bar on Meet pages only | Used to group participants in the same meeting room | Firebase Realtime Database, deleted when all participants leave |
| Anonymous auth token | Generated by Firebase Anonymous Auth on first install | Secures database reads/writes | Firebase Auth (managed by Google), Chrome sync storage |
| Knock signals (nudge/unmute events) | Generated when a user clicks Nudge or Unmute | Delivers the knock to the target user | Firebase Realtime Database, deleted immediately after delivery |
3. Data We Do NOT Collect
- Real names, email addresses, or any personally identifiable information
- Browsing history or activity on any site other than meet.google.com
- Audio, video, or screen content from meetings
- Google account information
- Cookies or tracking identifiers
- Analytics or telemetry data (no Google Analytics, no Mixpanel, no tracking pixels)
4. How Data Is Used
All collected data is used exclusively to provide the extension's core functionality: showing teammates' presence and mute status, and delivering knock signals. Data is never used for advertising, analytics, profiling, or any purpose unrelated to the extension's features.
5. Data Sharing
Firebase (Google Cloud): Meeting presence data, mute states, handles, and knock signals are transmitted to and stored in Firebase Realtime Database, a service operated by Google. Google's data handling for Firebase is governed by the Firebase Terms of Service and Google Cloud Privacy Notice.
No other third parties. We do not sell, rent, or share your data with advertisers, data brokers, or any other third party.
Other meeting participants: Your chosen handle, mute state, and presence are visible to other Meet Knock users in the same Google Meet call. This is the core function of the extension.
6. Data Retention & Deletion
- Presence and mute state: Automatically deleted from Firebase when you leave the meeting, or within 5 minutes if your connection drops unexpectedly.
- Meeting rooms: Automatically deleted from Firebase when all participants have left.
- Knock signals: Deleted from Firebase immediately after delivery (typically within seconds).
- User handle: Stored in your Chrome sync storage indefinitely until you change or uninstall the extension. The handle is only written to Firebase while you are actively in a meeting and is removed when you leave.
- To delete all your data: Uninstall the extension. This removes all locally stored data. Any Firebase records associated with your sessions are ephemeral and auto-delete as described above.
7. Data Security
- All data in transit is encrypted via HTTPS/WSS (Firebase Realtime Database uses secure WebSocket connections by default).
- Firebase database access is restricted by security rules: users can only write their own records, signals can only be read by the intended recipient, and all access requires authentication.
- No data is stored on any server we operate. Firebase (Google Cloud infrastructure) handles all server-side storage.
8. Permissions Explained
| Permission | Why it's needed |
|---|---|
sidePanel |
Renders the Meet Knock UI alongside Google Meet |
offscreen |
Plays the knock alert sound even when the Meet tab is muted |
storage |
Saves your handle and preferences locally in Chrome |
notifications |
Shows desktop notifications when a teammate knocks |
alarms |
Sends periodic heartbeats to maintain your presence status |
scripting |
Injects a helper script into the Meet page to control audio (defense-in-depth muting) |
host_permissions: meet.google.com |
Allows the extension to interact with Google Meet tabs only — no other websites |
9. Children's Privacy
Meet Knock is not directed at children under 13. We do not knowingly collect data from children.
10. Changes to This Policy
We may update this policy as the extension evolves. Changes will be posted at this URL with an updated "Last updated" date. Continued use of the extension after changes constitutes acceptance.
11. Contact
For privacy questions or data deletion requests, contact: privacy@meetknock.xyz