effective September 24, 2026 — written to be read, not to hide things
This policy describes what data the Berdsy Chrome extension and its backend service
("Berdsy", "we") collect and how it is used. Berdsy is designed to know as little about
you as possible.
what we collect
The website you're viewing. To open the right chat room, the extension reads the
address of your current browser tab locally, and sends the site's hostname (e.g.
example.com) — and, if you choose page-level chat, the page path — to our
server. Berdsy never builds or stores a browsing history.
Optional background warnings (off by default). If you turn on
Warn me on risky sites in settings, the extension sends the hostname of each site you
visit (e.g. example.com — never the full address, page content, or your identity) to
our server to check whether Berdsy already has a warning for it. These checks are answered from
existing data, are not stored, and are not linked to you or your account. Turning the setting off
stops them immediately.
Your Google email address, only if you sign in. Signing in (required to post
reviews or report content) shares your email with our server once to issue a signed session.
We store only a salted, one-way hash of your email with your reviews and reports — the site
rooms and other users never see the email itself. We receive no other Google profile data.
Content you post. Chat messages, reviews, ratings, the nickname you choose, and
reports you submit. Chat and reviews are public — anyone using Berdsy on the same
site can read them.
A random install identifier. Generated by the extension for chat rate-limiting.
It is not linked to your Google account.
automated analysis
To warn people about likely scam sites and to help moderators prioritize reports, Berdsy
sends some public information to TypeSafe AI, which
runs an automated classification model on our behalf:
the text of public reviews, chat messages, and reports about a site — without
nicknames, email addresses, account identifiers, or IP addresses;
the public homepage of the site being discussed, which our server fetches itself, and the
public registration date of its domain (from the RDAP registry service).
This happens on our server, not in your browser, and only for sites someone has opened
Berdsy on. The results are used only to show automated warnings and to sort the moderation
queue. Automated analysis never removes or hides content; people make those decisions.
what we do not do
We do not sell your data. The only outside parties that process it are the service
providers that run Berdsy: Cloudflare (hosting), Google (sign-in), and TypeSafe AI
(automated analysis of public content, described above).
We do not show ads or use analytics/tracking of any kind.
We do not track your browsing across sites. Nothing is sent unless the side panel is in use,
or you have turned on the optional background warnings described above.
We never see your Google password. Sign-in happens on Google's own pages.
where data lives
Backend data is stored on Cloudflare's infrastructure (Cloudflare's privacy policy).
Sign-in uses Google OAuth (Google's privacy policy).
Your extension stores your nickname, session, server URL, and any site-owner keys in Chrome's
extension storage on your device (and your Chrome profile sync, if enabled).
retention and deletion
Chat rooms keep roughly the most recent 1,000 messages per room; older messages are deleted automatically.
Reviews remain until removed by moderation. Reviews removed by moderators leave an anonymous placeholder.
Signing out deletes your session from your browser. To request deletion of content or
data associated with your account, email jcesarg09@pagetalk.net
from the Google address you signed in with.
children
Berdsy is not directed at children under 13 and may not be used by them.
changes
We will update this page if the policy changes; the effective date above always reflects
the current version.