Technical stuff,
handled.

Cloak reduces selected browser-side inputs that can feed profiling and pricing systems. It cannot reveal why a merchant chose a price or guarantee a lower one.

Cloak removes known tracking parameters while keeping search, product, filter, cart, and checkout state that a page needs.

Cloak strips known click IDs when it can do so without breaking the destination.

Cloak blocks known tracker and ad requests it can identify in the browser.

Cloak counts ad requests separately from tracker requests when the browser evidence distinguishes them.

Cloak recognizes bounded patterns including Google Analytics _ga, _gid, _gat, and _gac keys; Shopify _shopify_s, _shopify_y, campaign, analytics, and referrer keys; TikTok _ttp, ttcsid, and _pangle keys; Klaviyo __kla_id and klaviyo-prefixed storage; Adobe AMCV, s_ecid, s_vi, s_fid, s_sq, and demdex keys; and host-scoped Microsoft Clarity identifiers. It cannot read HttpOnly cookies or server-side records.

Cloak reduces selected active and passive signals where Chrome allows it; it does not make a browser anonymous or impossible to recognize.

Paid Cloak protection starts before normal website scripts can collect the covered signals. A page can still interfere with MAIN-world code, and compatibility exceptions can apply.

Cloak avoids cumulative noise during a page visit, then rotates the seed for a new document so the same modified output is less reusable across visits.

Cloak withholds the covered high-entropy values from page scripts and removes selected Sec-CH-UA request headers. Basic browser brand, mobile status, and platform can remain.

Cloak removes and intercepts a narrow set of fingerprint-named identifiers while preserving ordinary cart, product, login, and preference storage.

Cloak strips them by default, but lets you keep a trusted creator code for a site when you choose.

Cloak records what was visible. A warning is not proof that a price, availability, or outcome was manipulated.

Cloak clears supported merchant session cookies and local site state, cleans tracking context, and applies its selected browser defenses. This can reset sign-in, cart, or preference state on some sites.

Shopping Mode clears only supported state for the selected merchant session. Cloak does not read or delete server-side account records.

After confirmation, Cloak asks Chrome to clear that store's cookies, local storage, IndexedDB, Cache Storage, service workers, site file-system storage, and WebSQL. This signs the user out and may empty carts. It does not delete the merchant's server-side account or order history.

Automatic forgetting is off by default. When enabled for one store, Cloak clears that configured store when Chrome next starts, not while the user is ordinarily shopping. Chrome must fully exit before a later startup event can run.

Cloak supplies only the selected store origin family. Chrome documents that cookies are broader than other origin storage and can be removed across the registrable domain, which is why Cloak confirms the sign-out and cart risk first.

Cloak recognizes common recently-viewed key patterns, including viewedProducts, while its ordinary tracking-state cleanup preserves tested cart, login, checkout, currency, locale, and product-selection state. A full store reset intentionally clears all covered storage for that store.

Cloak removes or limits selected referral context during protected shopping flows so less of the previous page travels with the request.

Cloak sends the GPC preference when enabled. Its legal effect and a website’s response depend on jurisdiction and implementation; it is not a deletion request.

Cloak can send DNT as a compatibility signal, but does not present it as an enforceable or universally honored protection.

Cloak adds bounded, stable per-document noise to selected Canvas and Web Audio readbacks and normalizes WebGL debug vendor and renderer values. It reduces selected recognition signals rather than preventing fingerprinting entirely.

Cloak standardizes the covered signals, withholds the local font list, returns generic microphone, speaker, and camera entries, and reports a full battery state to covered page scripts. Sites can still observe many signals Cloak does not cover.

Cloak limits covered window and document callbacks to at most one delivery every 250 milliseconds. It does not invent clicks, promise a particular intent score, or stop every first-party behavior measurement.

Cloak blocks a defined set of exchange domains and OpenRTB paths. It does not block every ad auction, and it does not claim that every matched vendor handles identical data.

Cloak stores up to 500 valid observations in Chrome local extension storage and can show the visible difference on a later check. It does not upload the record, claim a refund automatically, or guarantee every variant, fee, or retailer page can be matched.

Cloak keeps this assessment in the browser and shows what it changed. It is scoped evidence, not a claim about hidden server-side activity.

Cloak can raise a careful local alert when these signals pile up. The alert is a reason to look closer, not proof of price discrimination or manipulation.

When enabled, Cloak prefers unambiguous privacy-preserving choices and avoids accept-all or unclear controls. Consent interfaces vary, so customers should still review the result.

Cloak applies this only to recognized tracking cookies on protected shopping sites. Sites can reject or replace cookies, and the feature does not control HttpOnly or server-side records.

Cloak Check creates a private browser-side observation only when it can find a clear price. It does not purchase, monitor a merchant server, or prove why a price changed.

Cloak shows the lowest, highest, latest, and visible variance from observations saved in that browser, with search and sorting. It is not live market-price intelligence.

The alert reports a comparison between local observations. It does not prove personalization or price discrimination and cannot guarantee a future price or saving.

Cloak can ask for honest feedback after a few days and show local protection totals near the end of the trial. Dismissals persist, prompts are rate-limited, and paid customers do not receive trial prompts.

Cloak stores the token locally and sends it only to cloak.build for customer-initiated access checks. It is not a hardware fingerprint or Google-profile identifier.

Cloak does not automatically upload or download these summaries. The customer decides whether and where to paste them.

The feature is off by default and only offers or fills an empty checkout email field when enabled. It is not a forwarding or relay service, and support depends on the customer's email provider and the merchant accepting plus-addressed email.