5 items
Blocks trackers, sends Global Privacy Control, and shows each site a different device profile so most trackers can't link you. Nullecho blocks the ad networks, analytics scripts, social pixels, and known fingerprinting vendors that follow you across sites, using static rule lists built from DuckDuckGo Tracker Radar, EasyPrivacy, and AdGuard, evaluated by the browser's own declarativeNetRequest engine. It sends Global Privacy Control, a do-not-sell/share signal legally recognized in California, Colorado, and several other states if you live there — the duty attaches to your residency, not the site's location. Instead of trying to make you invisible, Nullecho gives each site a different, internally consistent device profile, drawn from a pool of real, common hardware/software configurations and held stable per site. This breaks the cross-site fingerprint join for trackers that hash the signals Nullecho covers, verified against the FingerprintJS and ClientJS libraries. It does not break the join against a library that detects spoofed values, discards them, and keys on what's left; CreepJS does exactly that. On pages that display a price, Nullecho watches for the exact disclosure sentence New York law now requires when a price was set by an algorithm using your personal data. When it finds one, it tells you and lets you keep a local, on-device copy of what the page displayed — the words on the page, never a compliance judgment. Nullecho collects nothing about you: no telemetry, no accounts, no analytics, no crash reporting, nothing synced. A build-failing test enforces this against any network call to anywhere but the extension's own bundled files. What it does not do, stated plainly: it does not hide that it's installed — it is detectable, by design. It does nothing about your IP address or TLS fingerprint; both sit below any layer an extension can reach. It will not get you a lower price. It does nothing against state or government surveillance. Firefox's resistFingerprinting/fingerprintingProtection and Brave's built-in protections are genuinely stronger, because they work below the JavaScript layer; Nullecho's niche is Chrome, where neither exists. Known limits: the device profile does not cover Web Workers, and screen size, pixel density, and color depth are reported honestly rather than spoofed, since a contradiction is worse than a leak. A page that wins the loading race before Nullecho's script runs can, in narrow cases, read the real machine through a constructed frame. Open source, MIT licensed: github.com/ZJHeepfixer/nullecho. Every claim above is a measurement recorded in the repository — run the same measurement yourself, on your own browser, at nullecho.org.
Oct 6, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.