Lil Bro Wipe – History Cleaner privacy policy

Last updated: 19 September 2026

Lil Bro Wipe – History Cleaner deletes chosen entries from your browsing history. Everything happens on your device. There is no server behind it.

What it accesses

• Your browsing history, to find the entries that match your rules and delete those, and, only when you press the button for it in the advanced controls, to work out which sites you visit most often that no rule covers so you can add one. That read is worked out on the page and nothing from it is stored. A rule marked never delete keeps its sites out of every wipe, and the list it goes by is this extension's own: it cannot read the allow list in your browser settings.
• Extension storage for your rules, your settings, an optional local log of what was cleaned, and the count shown on the settings page.
• A PIN you set yourself, if you switch the list lock on. It is stored on your device as a hash and never sent anywhere, and it does one thing: it hides your rule list from other people using the same computer. It does not encrypt anything, and anyone who can reach your browser settings can still remove the extension. Forgetting it has a way out: type the word lilbro and the PIN goes, and so does everything the extension saved, your list included. None of that comes back.
• Cookies, if you use the cookie features. It reads cookie names and domains to delete the ones you did not keep, and keeps the site of an open tab in session storage (memory, gone when the browser closes) so a closed tab's cookies can go with it. Tab access is an optional permission, asked for only when you switch that feature on.
• Other stored browsing data: cache, download history and saved form text, cleared through the browsing-data permission and only with those switches on.

What it does not do

• Nothing is collected, sold or shared. No analytics, no account, no third party.
• It makes no network requests of its own. The settings page carries one link out, to the page where you can support the project, and your browser opens that in a new tab only if you click it. The extension itself sends nothing, at any point.
• Everything it runs ships inside the package. There is no remote code, no eval, and nothing fetched at runtime.
• It does not read page content, and it does not touch passwords: Chrome removed password deletion from extensions, so there is no such switch.

Cookies, cache and the rest

Clearing is off by default. With it on, cache, cookies, site storage, download history and saved form text go for the span you pick, when you press a button, and at startup if you ask for that. Cookies are removed for the whole site, so being signed out of it is the normal result. The keep list is the exception: those sites are never touched. Chrome cannot narrow history, download history or form text to one site, so those are all-or-nothing for the span you choose.

Where your data lives

Your settings, the PIN and the optional log of what was cleaned stay on your machine, in your browser's local extension storage. They are never uploaded anywhere. The log can be cleared at any time from the extension's settings page, and removing the extension deletes all of it.

So does your rule list. It is held in local extension storage, the same place as everything else this extension saves, and it is not put anywhere the browser would upload. The extension makes no network requests of its own, so there is no account, no server and no transfer between your devices on the path, whether or not browser sync happens to be switched on. Exporting the list writes a file on your own computer, which stays there until you move it.

Changes to this policy

If this policy ever changes, the date at the top of the page changes with it. Continued use of the extension after an update means you accept the current version.

Contact

Questions about this policy or the extension: open an issue on GitHub.