Privacy Policy
MemTab does not collect, transmit, or sell any data. There is no server, no analytics, no telemetry, and no third-party service of any kind.
What MemTab reads
Everything below stays on your machine.
| Data | Why | Where it goes |
|---|---|---|
performance.memory — the JavaScript heap size of the page you're on |
To pick a colour | Kept in memory in that tab. Never written anywhere, never leaves the tab. |
The <link rel="icon"> elements in the page's <head> |
To draw the site's own favicon inside the indicator | Used immediately, then discarded. |
| The current tab's URL, in the extension's service worker | To look up that page's favicon in the browser's local database | Used for the lookup; the resulting image is cached in memory. |
MemTab does not read page text, form fields, passwords, cookies,
localStorage, browsing history, or anything you type.
What MemTab stores
Your settings — thresholds, colours, indicator style, poll intervals, and
the list of sites you've asked it to skip — go in chrome.storage.sync. Your
browser syncs that across profiles you are signed into, using your own account. MemTab has
no access to it beyond your own browser. No browsing data is stored there.
Cached favicons go in chrome.storage.session, which lives in
memory and is cleared when the browser closes. Tabs in private/incognito windows are never
cached at all, so no record of private browsing is created.
You can export or delete everything from the options page at any time. Uninstalling MemTab removes it.
Network requests
MemTab makes no network requests.
The only fetch() in the codebase targets
chrome-extension://<id>/_favicon/, which is MemTab's own origin and a
lookup against a local database the browser already maintains. It does not touch the
network.
An earlier design fetched favicon URLs from the pages you visited. That was dropped: the URL is page-controlled, so fetching it from the extension's privileged context would let a hostile page use MemTab to read cross-origin and intranet URLs on its behalf.
Permissions
Each requested permission and what it is used for is documented in docs/PERMISSIONS.md.
Verifying this
MemTab is open source and has no build step — the published package is exactly what is in the repository, with no bundling, minification, or dependencies. You can read all of it. Releases are built reproducibly and carry a build-provenance attestation, so you can check that a published package was built from the tagged source:
gh attestation verify memtab-0.1.1.zip --repo councilOfNine/memtabChanges
Any change to this policy will be published on this page with an updated date, and called out in the changelog.
Contact
Questions: github.com/councilOfNine/memtab/issues