1Summary
By default, Comment Shield processes comment text entirely locally in your browser. There is exactly one exception: if you voluntarily add your own Perspective API key (see section 3), checked comments are additionally sent to Google. Without that key, no comment text ever leaves your device.
2What data is processed locally
The extension reads comment text on supported platforms (YouTube, Reddit, Instagram, TikTok, X, and Facebook) to locally determine whether a comment contains toxic language. This computation (word-list and pattern matching) runs entirely in your browser's memory and is not stored or logged anywhere. Flagged comments are only blurred or hidden client-side.
3Optional Perspective API integration (the one exception)
In the advanced settings you can voluntarily add your own Google Perspective API key to catch more subtle cases. If a key is set, the text of comments that pass the local check is additionally sent via our extension's background process to commentanalyzer.googleapis.com (Google) for analysis. Google's own privacy policy then applies to that transmission. Without a key entered, this transmission never happens — that's the default state.
4Warning before your own comment
Before you send a comment yourself, the extension optionally also checks your own draft text locally for toxic language and may briefly warn you before sending. This text also stays entirely on your device — unless you've enabled the Perspective API as described in section 3, in which case the same exception applies here too.
5Context menu (right-click)
If you select text on a page and choose "Mark as exception" or "Mark as toxic" via right-click, the extension reads only the text you selected and stores it locally in your word list. Nothing is transmitted to us or any third party.
6Stored settings
The following data is stored locally via Chrome's storage APIs:
- Settings (sensitivity, active platforms, display mode, custom word lists, whitelist/blocklist, context profiles, parental PIN, kids mode) — stored via
chrome.storage.sync, which syncs across your Chrome devices if you're signed in to Chrome. This sync runs through Google, not through us. - Statistics (number of hidden comments, 14-day daily history) — stored via
chrome.storage.local, stays only on your device.
7Permissions
The extension requests access to youtube.com, reddit.com, instagram.com, tiktok.com, x.com/twitter.com, and facebook.com in order to detect and blur comments there. If a Perspective API key is entered, access to commentanalyzer.googleapis.com is added (see section 3). The "context menu" permission enables the right-click feature described in section 5. The "keyboard shortcuts" permission (commands) allows toggling protection via a key combination, without access to page content. All permissions are used exclusively for the core functions described here.
8Connection with our website
getcommentshield.com (and potentially other voglair.com websites) can, if needed, check whether the extension is installed and retrieve a rough statistics snapshot (number of comments hidden today/in total) — technically via Chrome's own externally_connectable feature. This is used exclusively to show you the installation status on our own website. No comment content or personal data is transmitted in the process, and no other websites can make this query.
9No sharing with third parties
We do not sell, rent, or share data with third parties. No analytics or advertising SDKs are integrated into the extension. The only data transmission to a third party is the explicitly voluntary Perspective API use described in section 3 — and only if you enter your own API key.
10Changes to this policy
If this privacy policy changes, we update the date at the top of this page. For material changes, we also inform you via the extension's release notes.
11Contact
Questions about privacy? Reach us via voglair.com.