Examples inside the current scope
Cloak can block selected known tracker and analytics requests when they match its browser rules. That includes selected session-replay, measurement, pixel, retargeting, ad-delivery, exchange, OpenRTB, FingerprintJS delivery and API, and narrowly identified interaction-telemetry requests where blocking can be done safely.
It also removes common campaign and referral parameters from supported URLs, canonicalizes supported Amazon, Walmart, eBay, AliExpress, and other marketplace routes, and reduces selected browser-recognition inputs where Chrome permits. Search terms, filters, variants, carts, and checkout state are preserved when the cleaner recognizes them as functional.
When a page exposes attribution-like cookies or storage to the browser, Cloak can name what it found and clear supported readable state. The receipt separates trackers from ads and keeps this-window, monthly, and all-time totals in cumulative scope.
Why some ads may disappear
Some advertising systems depend on requests that overlap with Cloak's selected ad-tech rules. Blocking those requests may mean fewer visible ads on some sites. Broad or universal ad removal is not Cloak's product promise, and aggressive publishers or platforms may still serve ads.
What remains outside the extension
Cloak does not make you anonymous, change your IP address or network route, scan for malware, or replace a VPN or antivirus product. It cannot protect activity inside native mobile or rideshare apps, stop every first-party or server-side data flow, erase records another company already holds, reveal why a price changed, or guarantee lower prices.
Cloak deliberately avoids blanket-blocking broad fraud systems such as DataDome, PerimeterX, and ThreatMetrix because that can break login, checkout, and CAPTCHA flows. It reduces covered browser signals instead.
A blocked browser request is evidence of that action. It is not proof that all tracking stopped or that a merchant changed an offer because of tracking.
How to verify the result
The local receipt shows selected browser-visible actions in the current window: trackers blocked, ads blocked, URL tags removed, readable tracking state cleared, and selected fingerprint checks reduced. Monthly and all-time views use longer cumulative scopes rather than inventing different event definitions.
Cloak can also send GPC and DNT preference signals and warn about visible checkout pressure. A preference signal is not proof a site honored it, and a pressure warning is not proof of deception or price discrimination.
Primary sources