Privacy policy

Data we handle

• Your chosen name and membership: the name you enter, room and member identifiers, owner/member role, membership status, and access-management records.
• Authentication and invitations: a signed membership credential stored in Chrome's local extension storage; credentials sent to the access service to obtain short-lived Ably tokens; invitation identifiers, hashed invite codes, creation time and used/revoked state.
• Messages and coordination: messages you send, their sender names and identifiers, timestamps, claims, claim acknowledgements, and presence information identifying connected members.
• Meet call identifier: the meeting path from the active Google Meet URL, used to put members on the same call into the same conversation channel. The extension does not collect your general browsing history.
• Service connection information: Cloudflare and Ably process information necessary to operate their services, such as IP addresses, request or connection metadata, and service logs, under their respective policies.

The extension does not record meeting audio or video, transcribe calls, read Google Meet chat, or collect unrelated page content. It does not use your Google account to determine your name. There are no advertising or analytics SDKs added by this extension.

How data is used

Data is used to establish and recover membership, redeem or revoke invitations, manage access, connect collaborators on the same Meet call, relay messages and claims, show presence and retained message history, and maintain the service. It is not sold or used for advertising, creditworthiness or lending decisions. Collection and sharing are limited to the coordination purpose described here.

Where data goes

• Your browser: Chrome stores your saved membership profile, service URL and signed credential locally for this extension. Recent messages and connection state are held in memory while the extension is running. Clicking Copy invite places that code on your clipboard.
• Cloudflare Workers and D1: the access service processes names, membership credentials, invite requests, member-management actions and Meet identifiers. D1 stores the permanent room, member and invite records. Message text is relayed directly through Ably and is not stored in D1.
• Ably: connects clients and processes names, client and channel identifiers, messages, claims, acknowledgements and presence. The channel identifier includes the room and Meet call identifier. Ably provides retained message history.
• Your collaborators: members connected to the same room and Meet conversation can receive your messages, chosen name, claims and presence. The owner can view membership names and manage member access.

See Cloudflare's privacy policy and Ably's privacy policy. If you configure another access-service URL, its operator also processes the access data sent to that service; review that operator's practices before using it.

Retention and deletion

Your room and memberships do not expire automatically. Names, membership records and invite metadata remain in D1 while the service is maintained, unless deleted or anonymized by its operator. Unused invites stay valid until used or revoked. Removal revokes access but retains the membership record; it does not automatically erase past messages.

Messages and coordination events stored by Ably are retained according to the app's configured Ably retention policy. Displaying the latest five messages does not limit how many events Ably retains. Provider logs and backups may follow separate provider retention schedules. The extension does not maintain another message archive.

Use Remove setup from this browser to clear the extension's locally saved membership profile and credential. Uninstalling the extension also removes its local extension storage. These actions do not delete server records or revoke credentials held elsewhere. Contact the publisher below to request deletion or anonymization of your identifiable service records. Requests involving provider-retained messages are subject to the provider's available retention and deletion controls.

Security and your choices

The hosted service and Ably use encrypted transport. Messages are not end-to-end encrypted; the relay provider can process them. The full Ably API key and signing secrets remain on the access service. Content scripts receive short-lived tokens and profile metadata rather than the permanent membership credential.

Only share an invite with its intended recipient. The owner can revoke unused invitations and remove members. Membership credentials do not expire automatically. Ably tokens expire after one hour and renew automatically while membership remains valid. Member removal denies renewal and attempts immediate token revocation; if live revocation fails, an already issued token may remain usable until expiry.

HTTP access-service URLs are supported only for localhost development. The Meet strip is visible if you share that Meet tab/window or a full desktop where it is visible. It does not provide capture protection.

Changes and contact

This policy will be updated when the extension's data practices change. The latest version will show its update date here.