Support Center

We use several lightweight signals to estimate your data usage. Along with reading the Content-Length header, we apply carefully controlled patches to APIs like fetch, XHR, WebRTC, WebSocket, SSE, Beacon, native video/audio, and certain workers. These patches run quietly inside the page context and never alter how the site behaves.

No. The instrumentation is minimal, non-intrusive, and designed to leave the website’s functionality completely unchanged. The site works exactly as it normally does; we simply provide helpful metrics in the background.

Due to the dynamic nature of the internet, some complex site structures require significant development effort to ensure accuracy. We prioritize popular sites and are continually working to expand compatibility.

No. We do not log credentials or browsing history. While we measure request payloads for bandwidth estimation, we do not read, log, or store any of the data contained within those payloads.

Chrome's tool is global and "all-or-nothing". Our cleaner is a surgical instrument: it lets you inspect and clean data for a single website. This means you can reset the state of one site without being logged out of everything else.

Never. The extension only reads metadata (like key names and sizes) for analysis. It never reads the actual content of your localStorage or databases. All operations happen locally on your browser.

This is expected as IndexedDB often holds essential app data. Deleting it is like a "hard reset". Simply reloading the page will allow the site to rebuild its database and return to normal.

No. We are obsessed with performance. The extension is extremely lightweight and uses smart throttling to ensure monitoring does not impact your browsing experience.

To calculate the size of storage or clear the cache for a specific site, we need technical access to those browser APIs. We use these permissions responsibly and only for sites you choose to inspect.