Start
Turn on selected protections before ordinary page scripts begin.
How Cloak works / desktop Chrome
Turn on selected protections before ordinary page scripts begin.
Stop selected tracking and ad-tech requests before they finish loading.
Reduce selected clues used to recognize a browser or measure behavior.
Show a local receipt of what Cloak observed or changed.
The customer version
Cloak 0.1.14 focuses on tracking that desktop Chrome can see or change. It protects the shopping path, helps with clear consent choices, keeps price checks and receipts local, and preserves tested shopping actions.
Cloak stops requests that match its named tracker and ad-tech rules. It does not block every tracker, every ad, or activity that happens only on a company's servers.
Cloak removes common campaign, click, and referral tags while keeping useful search terms, filters, variants, carts, and checkout state intact.
Cloak reduces selected graphics, audio, device, language, font, and hardware clues. This can make recognition harder; it is not an anonymity guarantee.
Cloak limits how often covered scrolling, pointer movement, and visibility signals are delivered. Deliberate clicks and ordinary shopping actions still work.
When enabled, Ray can select recognizable reject-optional, necessary-only, or opt-out choices on likely consent banners. It avoids accept-all and ambiguous controls, but cannot interpret every consent interface.
On protected shopping sites, Cloak makes a best-effort attempt to rewrite recognized tracking cookies with Secure, stricter same-site, and partition boundaries. Sites may reject or replace them.
Cloak can send Global Privacy Control and Do Not Track signals. The receipt can show that the preference was sent; it cannot prove that every site honored it.
Tests cover search, filters, variants, carts, currency, sign-in, and checkout state. Stores can change, so compatibility exceptions are still possible.
Cloak keeps window, monthly, and all-time protection counts in the extension. The receipt reports browser-visible actions; it does not guess what happened on a hidden server.
Run a Cloak Check on a supported product page to save its clean URL, visible title, price, and observation time locally. Repeated checks show the lowest, highest, latest, and visible variance for that exact clean offer.
If the current visible price is above a lower local observation for the same clean offer, Cloak can flag the difference. That comparison does not prove personalization, price discrimination, or guaranteed savings.
When enabled with a customer-supplied Gmail address, Cloak can derive a stable merchant-specific plus address and offer it in an empty checkout email field. It is not an external forwarding service, and some merchants or email providers may not support sub-addressing.
Sites save cookies and other data in Chrome so they can remember sign-in, carts, and past activity. With confirmation, Cloak can clear covered saved data for one store now. You may be signed out and your cart may be emptied.
You can choose this separately for each store. It stays off unless you turn it on, runs only after a full Chrome restart, and does not delete the store's account or server records.
The seven-day trial uses rate-limited reminders and local protection totals. After checkout, an opaque entitlement token verifies paid access with cloak.build; ordinary browsing history is not sent with that check.