Privacy Policy — Sodium
Chrome extension · Effective 31 August 2026 · Version 3.4
Sodium collects nothing. The rules run inside Chrome, it never reads the pages you visit, and it has no network access of its own.
What it does#
Sodium's blocking is a list of rules handed to Chrome. Chrome matches them itself, inside the browser, and refuses the requests. The extension is not in the path of a request and never sees one.
That is the whole design, and it is why there is no data to describe: an extension that matched requests in its own code would have to be told about every request in order to block any of them.
Data we collect#
None. The categories below are the ones Google's extension policy asks a developer to declare, used here as a checklist for every product rather than only the ones it applies to. Sodium collects, transmits and stores none of them.
| Category | Collected? |
|---|---|
| Personally identifiable information (name, address, email, age, ID numbers) | No |
| Health information | No |
| Financial and payment information | No |
| Authentication information (passwords, credentials, tokens, PINs) | No |
| Personal communications (emails, texts, chat messages) | No |
| Location (region, IP address, GPS, place names) | No |
| Web history (pages visited, page titles, URLs, timestamps) | No |
| User activity (clicks, scrolls, keystrokes, mouse position) | No |
| Website content (text, images, videos, hyperlinks, files) | No |
Permissions and why they exist#
- Declarative request rules. The rule engine is Chrome's. Sodium supplies the list; Chrome does the matching and the refusing, and the extension is never told what was requested.
- Access to the pages you visit. Only to collapse the empty containers, sticky bars and overlays that a blocked advertisement leaves behind. That script changes layout; it does not read text, form fields or anything you type.
Sodium requests nothing else.
Data sharing and sale#
Because no data is collected, none is shared, sold, rented, transferred or disclosed to anyone — including us. There are no third-party services, SDKs, libraries or analytics providers of any kind. No data is used to determine creditworthiness or for lending purposes.
Remote code#
The extension executes no remotely hosted code. All of its code is in the package the Hub loads into the browser, where it can be inspected.
Children#
Sodium is not directed at children and, since it collects no data, it collects no data from children.
Changes to this policy#
If a future version of Sodium ever handles data differently, this policy will be updated before that version ships, and the effective date above will change. Material changes are noted in the changelog.
Contact#
Questions about this policy or the product: calyndrae@gmail.com
This policy applies only to Sodium and not to any website you visit while it is running.