Quiet Browse support
Help without tracking.
Before opening an issue
Include the Quiet Browse version, Chrome version, operating system, affected hostname, the enabled Quiet Browse setting, what happened, and what you expected. Remove names, account details, messages, payment information, and other private page content from screenshots.
Common fixes
A control says the page must be reloaded
Reload the affected website tab once. Chrome cannot attach a newly installed or updated content script to some already-open pages until they reload.
A site changed after an update
Use Show original page for the current tab, or turn Quiet Browse off for that host. Platform interfaces change, and a previously supported selector can stop matching correctly.
List choices changed after disabling the adult content filter
Current versions remember list checkboxes while removing active block rules. Reload the
extension from chrome://extensions if an older build is still installed, then
choose the desired lists once.
A regional list will not update
Confirm that Chrome granted access to raw.githubusercontent.com. The packaged
starter set works without that permission. An unavailable or malformed source keeps only its
own last working rules.
The protection password was lost
Quiet Browse has no password recovery. Chrome still permits disabling or uninstalling the extension and clearing its data. The password provides friction, not administrator-grade enforcement.
Delete local extension data
- Open Quiet Browse.
- Select Sites & privacy.
- Choose Delete all Quiet Browse settings.
- If password protection is active, enter that password.
Uninstalling the extension through Chrome also removes its extension storage and rules.
Report a security concern
Use GitHub's private vulnerability reporting. Do not disclose an unpatched vulnerability in a public issue, and do not include passwords, authentication cookies, private messages, or payment information.