Security fixes are accepted for the current main branch and the latest Chrome Web Store release.

Do not open public issues for sensitive vulnerabilities. Use the repository owner's preferred private contact method if one is listed, or request a private disclosure channel through the issue tracker without including exploit details.

Useful reports include:

• Affected version or commit.
• Steps to reproduce.
• Impact and affected permissions or data.
• Suggested fix, if known.

Browser Guard stores data locally in Chrome extension storage. It does not run a backend service. Features that need access to tabs, page content, or active-tab audio should stay narrowly scoped and documented in PRIVACY.md and Chrome Web Store privacy disclosures.