broccoli

Privacy Policy for broccoli

Last updated 19 November 2026

This policy covers the broccoli extensions for Chrome and Firefox and the backend at api.anti-brainrot-blocker.fyi. broccoli checks YouTube videos against your allowed categories and blocks videos that do not match.

Accounts and information we handle

The developer approves email addresses for registration. Users with an approved address can create an account in the extension. Members sign in with their broccoli account email address or their existing username.

How we use information

We use information to authenticate users, recover access to accounts, save category preferences, check and block videos, cache decisions, troubleshoot failures, secure the service, and respond to requests.

We do not sell user data or use it for advertising. Our use and transfer of information received through the Chrome extension follows the Chrome Web Store User Data Policy, including its Limited Use requirements.

Storage and security

The extension saves the email address or username you enter in temporary browser session storage so it can restore it when you reopen the popup. The popup holds passwords and recovery codes in memory while you use the forms. Signing out clears the saved email address or username.

The extension keeps both access and refresh tokens in temporary browser session storage. They keep you signed in while the browser is open. Signing out or closing the browser clears them. The extension also clears them if the server rejects a refresh token as invalid or expired. When updating from an older version, the extension removes saved password drafts and moves any saved production refresh token into session storage.

The backend stores approved email addresses, account records, saved categories, authentication sessions, and password reset records in PostgreSQL. It stores passwords as bcrypt hashes and refresh tokens as hashes. Each reset record contains your account ID, a keyed hash of the code, its expiry time, and the number of attempts remaining. Redis stores video IDs and decisions by account.

The extensions communicate with the production backend over HTTPS. The backend uses HTTPS to communicate with its API providers.

Service providers and data sharing

When the backend needs a fresh decision and you have saved allowed categories, it uses YouTube API Services to look up the video and the OpenAI API to classify it.

Each provider handles the information it receives under its applicable terms and data practices.

Retention

Your controls and deletion requests

You can change your allowed categories in the extension. Sign out or uninstall the extension to stop it from sending video checks. To remove your server-side account or data, send a deletion request to the developer.

The developer handles requests to access, correct, or delete your data manually and may ask for information to verify account ownership. Keep your password, reset codes, and authentication tokens private. Send privacy requests by email to b.frolikov@gmail.com.

Account deletion removes the account, password hash, saved categories, authentication sessions, and password reset records from the database. The registration approval list, cached decisions, and existing logs follow the retention described above. You can ask the developer to remove your approved email address and address any remaining cache or log entries in the same request. Information already sent to service providers is subject to their retention and deletion practices.

Changes to this policy

We will update this page and its last-updated date when our data practices change. Material changes will also be communicated through the extension’s listing or directly to users before new processing begins where notice or consent is required.

Contact

The developer operates broccoli. For privacy questions, account registration, or deletion requests, contact b.frolikov@gmail.com.