Privacy Policy

What this page covers

This Privacy Policy covers the Cloak website, the beta request flow, and the current Cloak browser extension build.

Website and beta request information

If you request pilot access, we may collect the information you submit, such as your email address, role or use case, optional page URLs for the flow you want us to inspect, and notes about where tracking or pressure feels most relevant to you.

We also use basic site telemetry and server logs for performance, traffic, and reliability.

Extension data the current build processes

The current extension processes browser data that is necessary for its user-facing privacy and security features. That includes page URLs, page titles, page timing/session context, page text and links needed to detect pressure or tracking patterns, form targets and related page content needed to scrub tracking-heavy destinations, readable cookie/storage state the extension can access from the page, and local proof/setting state stored in the browser.

The current build also reacts to some on-page activity that is directly tied to its protection features, such as navigation, clicks on tracked destinations, and form submissions, so it can clean URLs or show warnings at the right moment.

How Cloak uses that data

Cloak uses this data to provide its single purpose: protecting people from tracking, profiling, and deceptive pressure on the pages they visit. In the current build, that means blocking known tracking requests, cleaning tracking-heavy URLs, reducing some fingerprinting signals, clearing readable tracking state the extension can access, and showing local warning UI when relevant patterns appear.

The current build is designed to process this protection data locally in the browser for the feature itself, not to sell it, profile users for advertising, or use it for unrelated purposes.

How we share information

We do not sell personal data collected through the website or the current extension build.

For the current extension build, browser data used for protection features is intended for the extension's user-facing function. We do not describe it as a general analytics feed or an advertising asset. We may share limited information with service providers only when needed to operate the website or support people who explicitly contact us, or if disclosure is required by law or necessary for security.

Retention and control

Website submissions may be kept for pilot review, follow-up, research, legal compliance, and record-keeping.

Extension settings and local proof state stay in the user's browser storage until the user clears them, resets them, or removes the extension. Because some protection logic acts on live pages, users should review the extension's current behavior and settings before using it on sites that matter to them.

Chrome Web Store disclosure

Cloak requests only the permissions needed for its current user-facing privacy features. The use of browser data by the current extension build is limited to providing or improving those disclosed protection features, consistent with the Chrome Web Store User Data Policy.

We do not sell user data, use it for advertising, or use or transfer it for creditworthiness or lending decisions. We do not let humans read extension-processed browser data unless a user explicitly asks for support on specific material, or access is necessary for security or legal reasons.

The packaged extension does not use remotely hosted extension code.

Your choices

If you want us to update or delete beta request information you submitted through this site, contact us through the current beta request path and ask us to remove it.

Changes

We may update this Privacy Policy as the site or extension changes. If we make material changes, we will update the date at the top of this page and publish the revised version here.