What Stigma collects.

Effective April 19, 2026

Nothing. Stigma collects no user data of any kind. No accounts, no servers, no telemetry. Everything the extension does happens locally in your browser and stays on your device. This policy documents exactly what that means.

What we do not collect

No personal data, contact information, or identifiers
No browsing history, URLs, or page content
No analytics, usage metrics, or telemetry
No crash reports or diagnostic information
No sharing or selling of user data to third parties, because we do not have any
No accounts, emails, sign-ups, or profiles

Permissions Stigma requests, and why

Browser extensions run inside a permission system. Stigma requests the following permissions, each required for a specific piece of functionality. All processing happens locally in your browser.

activeTab: Gives Stigma access to the tab you are currently viewing, only when you interact with the extension. Used to read which trackers are active on the current page and display them in the popup.
storage: Saves your preferences on your machine. This includes which tracker categories you have chosen to block, which individual trackers you have blocked, and whether you have enabled Global Privacy Control opt-out signals. Preferences stay local and are never transmitted.
cookies: Used only by the "Clear Site Data" button, which clears cookies for the site you are currently viewing. Stigma does not read, store, or transmit cookie values.
browsingData: Used only by "Clear Site Data" to clear the broader set of data a site has stored on your device, including cache and local storage. Triggered by your explicit action.
declarativeNetRequest: The mechanism Chrome provides for extensions to block network requests. Stigma uses it to block tracker requests based on the categories you have chosen.
declarativeNetRequestFeedback: Lets Stigma see which of its own blocking rules matched, so the popup can show accurate counts of trackers blocked on the current page.
webNavigation: Used to detect when you navigate to a new page, so Stigma can reset tracker counts for that page.
webRequest: Used to observe tracker requests on the pages you visit so Stigma can identify and categorize them. Observations are not logged or transmitted anywhere.
tabs: Used to identify the currently active tab so the popup displays data for the correct site.
host_permissions: <all_urls>: Tracking can happen on any website, so Stigma must be able to observe network requests on any site you visit. This permission is scoped to the trackers it detects on your machine. Nothing leaves your browser.

Local storage

Stigma uses Chrome's storage.local API to save your preferences on your device. This includes blocked categories, blocked individual trackers, and your GPC opt-out setting. These preferences stay on your machine. They are never synced to any server and never transmitted off your device.

Third-party services

None. Stigma does not communicate with any third-party service, analytics provider, advertising network, or server of any kind. The extension ships with its tracker database built in and does not fetch anything over the network during normal operation.

Open source verification

You do not have to take our word for any of this. The full source code for Stigma is public at github.com/cpugs/stigma. The claims in this policy can be verified by reading the code, and we encourage you to do so or to have someone you trust do it for you.

Changes to this policy

If this policy changes, the updated version will be posted at this URL with a revised effective date. Substantive changes will be reflected in a new version of the extension itself, available through the Chrome Web Store or the GitHub repository. Minor corrections, such as typos, will not trigger a new version.

Contact

Questions about this policy, or about Stigma's behavior in any scenario this policy does not cover? Email cpugsley@usual.systems.