{chat} privacy notice
Updated 2026-11-20
Who operates {chat}
{chat} is an independent beta maintained by its project maintainer. It is not affiliated with Google, Zillow, Wikipedia, IMDb, ESPN or other websites where conversations appear. Use Help & privacy → Support in the extension to contact the maintainer.
Page context and public conversations
After you choose Continue on the first-run notice, the extension checks supported tab URLs locally. For approved public pages, it sends a normalized page URL or an integration item ID to the conversation API to select a room. Tracking parameters are removed from generic page URLs. Unapproved or private page URLs are not sent by the normal extension flow. The website registry request does not contain your current page URL. We do not scrape page content or keep a browsing-history feed.
Posts, replies, display names and conversation scores are public. Do not post private information or anything you do not want others to read or copy. A hashed room ID is not a secrecy guarantee. The API receives the approved normalized URL to verify generic page access; the rooms table stores its hash, not the full URL.
Google sign-in and account data
Google verifies your sign-in. The backend checks your verified email and uses a stable Google account identifier to link your account. We store that identifier, an application account ID, display name, account status, permissions, contributions and votes. Your email, password and Google access token are not saved in the application database. Google access tokens remain managed by Chrome; expiring application sessions are stored on your device and only their hashes are kept in the database.
Google API data and Limited Use
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Reports, support and safety
Reports include your account ID, the target content ID and the selected reason. Reports and support messages are visible to moderators, not the public. Support requests may contain information you choose to send; do not include passwords, tokens, payment details or other unnecessary sensitive information. Website requests contain the domain you submit and your account ID.
Rate limiting uses account counters and secret-keyed hashes of network IP addresses. Raw IP addresses are not saved in these application counters. Hosting providers process network information to deliver the service. Moderator actions are logged without copying removed content into the audit log.
Retention and deletion
Account data and contributions remain until you remove them, delete your account, or a moderator removes them. Deleting a post also deletes its replies and votes. Delete account removes your account, Google mapping, sessions, contributions, votes, website requests and support requests from the live database. Reports you submitted and reports targeting your removed contributions are deleted. Audit records are de-identified where they refer directly to your deleted account.
Recovery copies may retain previously deleted data until the provider’s recovery window expires or a temporary migration copy is retired by the maintainer. Contact Support for deletion help. Live deletion does not recall copies other people have made. Moderators can remove content and suspend accounts; contact support to appeal.
Providers and your choices
Google provides identity verification. We do not sell personal data, run advertising analytics, or load remote fonts. Device preferences and local development/offline data remain separate from shared forum data.
You can decline or pause page-context sharing, read this notice and the community rules, delete individual contributions, sign out, or use Delete account. Appearance preferences may remain on your device after account deletion; uninstalling the extension removes its local storage. Future material changes to page-context disclosure will prompt a new acknowledgement.