Privacy Policy
Last updated: June 11, 2026 · Applies to Jewell Made browser extensions, including Advertisement Ends Here!
The short version
Advertisement Ends Here! is a local-only tool. It has no backend, no telemetry, no analytics, no accounts, and no cloud sync. Nothing the extension records ever leaves your device unless you explicitly export a report file and share it yourself.
What the extension processes on your device
To block trackers and record evidence of tracking attempts, the extension processes, locally:
- Network request metadata (URLs, hosts, resource types) to match requests against its registry of known tracker endpoints and its behavior-based detector.
- Page tracking API calls (for example
fbq,gtag,dataLayer.push) observed in pages, with arguments redacted before storage. - Cookie names and consent-manager storage keys on sites you visit, to record your privacy and consent state.
- Search form submissions, recorded as a hashed label (the search text itself is not stored unless you explicitly enable plain-text evidence).
What the extension stores
Evidence events are stored locally in your browser's extension storage. Values are redacted by default before storage: email addresses, phone numbers, and long opaque tokens are replaced with hashes; credit-card-like numbers are removed entirely; page URLs are stored without query strings. Plain-text evidence is off by default. Stored events are capped (oldest pruned) and can be erased at any time with the Clear button.
What the extension transmits
The extension sends no data about you anywhere. It makes one kind of network request of its own: when it blocks a known tag-manager loader (for example Google Tag Manager), it may fetch that same public script file — without cookies or credentials — solely to tell you which tracking companies the blocked loader would have installed. This request contains no information about you beyond the request itself, is cached, and never includes your browsing history.
Outbound effects you configure are performed locally by the browser: blocking requests, removing tracking
parameters, removing tracker cookies, and attaching the Sec-GPC: 1 (Global Privacy Control) header
when that setting is on.
Permissions
declarativeNetRequest,webRequest— block tracker requests and observe outcomes for evidence.cookies— remove known tracker cookies when you start a recorded test.storage— store settings and the local evidence log.activeTab— read the current tab's address when you open the popup, to show that site's card and offer per-site disable.- Host access — required to observe and block tracker requests on the sites you browse.
Data sharing and sale
No data is shared with, sold to, or transmitted to anyone. There are no third-party analytics or advertising services involved — that would be ironic.
Exported reports
When you download a report or diagnostics file, a JSON file is saved to your device. These files can contain the redacted evidence described above. Treat exported files as sensitive and share them only deliberately.
Paid plans (planned)
A paid tier is planned. When it launches, payments will be handled by a payment processor (you would buy on their checkout page, not inside the extension), and the extension would validate an anonymous license token — never your browsing data, never the evidence log. This policy will be updated with specifics before any paid plan goes live, and the local-only promise above will not change.
Changes
Material changes will be reflected here with a new "Last updated" date and in the extension's store listing.
Contact
Questions or concerns: [email protected]