Spoiler Guard

Privacy Policy

Privacy Policy

Spoiler Guard for YouTube consists of a browser extension and a sharing site to protect your viewing experience from spoilers. This page details how data is handled.

Extension Data Processing

The extension reads comment, live chat, and chat replay text on YouTube pages inside your browser to match them against community lists or your personal rules. This process is used strictly for blurring or hiding potential spoilers.

Data Transmission

The extension fetches published official blocklists from the Spoiler Guard website for supported video IDs. Comment and chat text is matched inside your browser; personal rules and curation candidates are stored locally.

Chrome Web Store User Data Policy

The extension's use of information, and any transfer of information, will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. See the official policy.

Local Storage

The extension stores block settings, presentation styles, personal block rules, and curation candidates inside local extension storage (Chrome Storage). You can clear this data at any time by uninstalling the extension or clearing extension data.

Website Data

This website is hosted on Vercel and uses Vercel Analytics and Google Analytics 4 (with Google Signals and ad personalization disabled) to measure page usage. Request metadata (time of access, browser agent, region) and page-view events may be recorded. You can opt out of Google Analytics on this browser via Google's official opt-out add-on or by setting localStorage key gussuri_ga_opt_out to 1.

Excluded Uses

We do not use collected or stored information for advertising, user tracking, selling to third parties, or identifying YouTube accounts.

Third Parties

We use Vercel for website hosting and analytics, Google Analytics 4 for aggregated traffic analytics, and GitHub links for source code. Using these services applies their respective privacy policies.

Inquiries

For privacy questions, please open an Issue on our GitHub repository or contact via our distribution pages.

Effective Date: August 6, 2026