ClearVue — Privacy Policy
Last updated: 29 July 2026 · Applies to all versions of the ClearVue browser extension
ClearVue collects nothing, transmits nothing, and contacts no server. It has no analytics, no accounts, no telemetry, and no advertising. Everything it shows you is read from the page you already have open in your own browser, and is displayed only to you.
What ClearVue handles
ClearVue is a developer tool. While its panel is open in your browser's DevTools, it reads:
| What it reads | Why | Where it goes |
|---|---|---|
| Network requests made by the inspected page — URLs, headers, request and response bodies, timings | To display them in the API Calls tab | Held in memory in your browser only; discarded when DevTools closes |
| The inspected page's component structure, props, and state | To display the Components tab | Held in memory in your browser only; discarded when DevTools closes |
| Authentication tokens present in that traffic | To report expiry and diagnose sign-in failures in the Auth tab | Decoded locally in your browser; never transmitted or stored |
| Console errors and warnings from the inspected page | To display the Problems tab | Held in memory in your browser only; discarded when DevTools closes |
| Your ClearVue preferences and whether you've seen the welcome guide | To remember your settings between sessions | Stored in your browser's local storage, on your own machine |
None of this data is transmitted anywhere. It is not sent to the developer, to Google, or to any third party. There is no server component to this extension. It cannot send data even in principle: it requests no host permissions, and its content security policy sets connect-src 'none', so the browser itself blocks any outbound network request from the extension.
Data collection disclosure
Under the Chrome Web Store's user data policy, ClearVue's disclosure is:
- Personally identifiable information — not collected
- Health information — not collected
- Financial and payment information — not collected
- Authentication information — not collected. Tokens appearing in traffic you are inspecting are decoded locally and shown to you on your own screen; they are masked by default and never recorded
- Personal communications — not collected
- Location — not collected
- Web history — not collected
- User activity — not collected
- Website content — read and displayed locally while the panel is open; never transmitted, and never stored beyond the DevTools session
ClearVue's data is not sold, transferred, or used for any purpose other than its single stated purpose: helping a developer understand the page they are inspecting.
Permissions
ClearVue's manifest declares an empty permissions array and no host permissions. It operates entirely through the browser's DevTools extension APIs, which function only while you have DevTools open, and only for the tab you opened it on.
Sensitive data on your screen
Because ClearVue displays real network traffic, request headers may include authentication tokens or cookies belonging to the site you are inspecting — the same information your browser's built-in Network panel shows.
ClearVue masks these by default, so a screen share or screenshot does not leak a live session. You can reveal any individual value with an explicit click. Nothing is ever recorded, and revealing a value does not persist it.
Children
ClearVue is a professional developer tool and is not directed at children under 13.
Changes to this policy
If ClearVue's data practices ever change, this policy will be updated and the change disclosed prominently in the extension itself and in its store listing before the new version ships. Continued use after such a change is not treated as consent; any new data handling would be opt-in.
Contact
Questions, concerns, or data requests: pross326@gmail.com
Because no user data is collected or stored remotely, there is no data to access, export, or delete on request. Local settings can be cleared at any time by removing the extension.