Privacy

Troll Guard scans visible YouTube comments only when the extension is enabled. It does not collect passwords, cookies, unrelated browsing history, or YouTube account tokens.

What is sent, and to whom

Most comments are handled on your device by local rules and cache and never leave it. When a comment is genuinely unclear, its text is sent to the Troll Guard scoring service to estimate toxicity. The scoring service uses server-side model providers and a deterministic local fallback. Provider keys stay in our backend, never in the extension.

Free comment scanner

The public scanner at /scan can fetch public YouTube comments when YouTube API access is enabled. When it is not, it shows a clearly labeled sample scan so visitors can see the workflow. It is an automated estimate, not a verdict, and it is imperfect.

Email and CRM

If you give us your email (waitlist, quiz, or scanner), we store it to contact you and may add it to our CRM (GoHighLevel). Every email we send includes a one-click unsubscribe that we honor.

What is stored locally

Settings, blocked phrases, approved text hashes, hidden comments, score cache, and correction events are stored in Chrome local extension storage during the MVP.

Correction events

Reveal, approve, keep hidden, block similar, and delete actions write local correction events using the comment hash, action, score, sensitivity, category, and timestamp. Cloud sync is not part of the MVP.

Delete data

Open extension settings and choose Clear Local Data to delete hidden comments, score cache, approved hashes, and correction events.