Privacy policy
Cleared is a Chrome extension that checks your web app for security, privacy, legal and quality problems before you launch it. This page explains exactly what it reads, what it keeps, and what it never does.
Effective 9 October 2026. Applies to the Cleared extension, version 1.0 and later. Published by Moses Afolabi.
Scans run on your computer. Nothing Cleared reads is sent to us, and we have no servers that receive it.
- Sent to us
- Nothing. Cleared has no account, no backend and no analytics.
- Kept on your device
- Your latest scan results, your scan preferences and your verification code.
- When it reads anything
- Only after you press Scan, and only on the site in that tab.
- Sold or shared
- Never.
AWhat Cleared reads during a scan
Cleared installs with access to no websites. It does nothing until you open it on a tab and press Scan, and the first time you scan a site, Chrome asks you to allow access to that site only. During a scan, inside your own browser, it reads:
- The page you're on and, if you choose Whole site, up to 25 other pages of the same site, loaded in a background tab with your existing sign-in.
- The requests those pages make and any errors they log, recorded inside the page, to find failed requests, trackers that load before consent, and broken code.
- The JavaScript files the site sends to every visitor, to look for secret keys that shouldn't be public. Any key found is shown to you masked (for example
sk_live_•••1234) and is not stored anywhere. - Links, buttons and forms on the page, to test links and to press buttons that can't change data. While buttons are tested, Cleared blocks every request from that tab that could save, delete, send or pay for anything.
All of this happens in your browser, the same way the site would load for you normally. It is used only to produce your report.
BThe database check
If a site's code includes a Supabase or Firebase connection, Cleared can check whether strangers could read its data. It does this only on localhost or on sites where you've added your personal verification code, which proves the site is yours.
The check uses only the public key that the site already gives every visitor. It requests at most one row from each table, keeps the column names to show you which kinds of data are exposed, and discards the values immediately. It never writes, changes or deletes anything.
CWhat's stored, and where
- Scan results for each tab are kept in your browser's session storage for the extension. They're removed when you close the tab or quit the browser.
- Your verification code (a random code made when you install Cleared) and your scan mode (this page or whole site) are kept in the extension's local storage until you remove the extension.
- Reports you download are saved where you choose. Fix prompts go to your clipboard only when you press a copy button.
None of this is sent to us or to anyone else.
DWhat we never do
- Collect, transmit or store your browsing history, page content, passwords, form entries or personal information.
- Use analytics, tracking pixels, advertising or fingerprinting in the extension.
- Sell, rent or transfer user data, or use it for anything other than the scan you asked for.
- Load code from the internet. Everything Cleared runs ships inside the extension.
The use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
EWhy Cleared asks for each permission
| Permission | Chrome's name for it | What Cleared uses it for |
|---|---|---|
| Site access, on request | optional host permissions | Cleared installs with access to no sites. When you press Scan, Chrome asks whether Cleared may access that one site. It can only scan sites you've allowed, and you can remove access anytime. |
| activeTab | Active tab | Reading the address of the tab you opened Cleared on, so it knows which site to ask permission for. |
| scripting | Scripting | Running checks inside a site you've allowed, recording that page's own requests and errors, showing the progress card and highlighting issues. |
| declarativeNetRequest | Block content | Blocking requests that could change data while buttons are tested. Removed when the test ends. |
| sidePanel | Side panel | Showing scan progress and results beside your page. |
| storage | Storage | Keeping results and settings on your device, as described above. |
FThird parties
No third party receives data from Cleared. The accessibility checks use axe-core, an open-source library bundled inside the extension that runs locally. The only network requests a scan makes go to the site you're scanning and its own database, the same places your browser already talks to when you use that site.
GYour choices
- Close a tab or quit Chrome to clear that tab's results.
- Remove the verification tag from your site at any time to stop database checks on it.
- Remove Cleared's access to a site from its details page in
chrome://extensions(Site access). - Remove Cleared from
chrome://extensionsto delete everything it stored.
Cleared isn't directed at children under 13.
HChanges and contact
If a future version adds accounts or anything that sends data off your device, we'll update this policy and the date above before that version is released, and explain the change in the release notes.
Questions about privacy?
Email the publisher using the contact address on Cleared's Chrome Web Store listing.