Privacy Policy

This site and the Pulse Observer browser extension are operated by Kenshiki, Inc., based in Tacoma, Washington, United States. Questions about this policy: hello@kenshikilabs.com. Last updated: July 10, 2026.

This site stores and sells none of the behavioral data captured here. Signals may be read and rendered during the current session so the site can show what a browser and interface can reveal, but they are not retained in a database, sold, transferred, or used to build a lasting profile.

The demo reads pointer movement, click precision, keystroke rhythm, and similar interaction signals while you're on the Demo page, purely to compute and display a session score.

Nowhere. Behavioral signals are captured and processed client-side, in memory, for the current session only. The network readout is requested once to show what a server can see on arrival.

This site does not use tracking cookies or third-party analytics to observe your behavior. Standard hosting logs, like any web request generates, may still apply at the infrastructure level.

If you're signed in, the app stores only the account information needed to authenticate you — it does not attach behavioral session data to your account.

Pulse Observer is our browser extension. It watches, on your device, which trackers and data brokers receive your data as you browse, and shows you evidence of it — who was watching, what they saw, and what your data is worth. The short version: your browsing history and every tracker observation stay in your browser, on your device. We cannot see them. We do not sell your data, and we will never sell your data — not raw, not aggregated, not “anonymized.” The extension exists to expose that trade, not to participate in it.

As you browse, the extension records tracker observations — which tracking companies were active on a page, what signals they used, and the page where it happened — in your browser's local extension storage. This necessarily includes a record of sites you visited. That record exists solely so the extension can show you your own report; it is never transmitted, synced, or readable by us. Observations are pruned automatically after a retention window (14 days by default), and removing the extension deletes all of it.

If you switch on “Observe browser cookie metadata” — off by default — the extension asks the browser for cookie permission at that moment and adds cookie names and their HttpOnly/SameSite/Secure flags to your local reports. Cookie values stay hidden unless you inspect them yourself, locally. Switch it off and the extension releases the permission. When you block a tracker, the blocking rule is installed inside your browser; no blocklist choices or browsing data are sent anywhere. Consent audits fetch the current site's own policy pages — the same fetch your browser would make if you clicked those links — and analyze them on your device.

Both run only when you click them; neither ever runs on its own. First, “Show me on a map”: one request to Kenshiki's session-profile service, which reads your IP address — the same way every website you visit already can — and returns the approximate location it implies, plus a static map image from Mapbox at those coordinates. That is the feature's entire purpose: to show you what your IP reveals. We use the request only to answer it; we do not build profiles from it. Second, the AI audit report, available on government (.gov) sites: at your request, the extension sends that page's address and a summary of its tracker observations to Kenshiki's audit service, which forwards it to a third-party AI model provider to generate the plain-language report shown to you. The summary is used only to produce your report; we do not store it, and it is never your browsing history — only the evidence summary you can see yourself with the report's copy button.

The extension has no account or sign-in, and contains no analytics, advertising, crash-reporting, or tracking code of any kind. We have no way to know who installed it, what sites you visit, or what your reports contain. Every observed tracker can be blocked or unblocked by you; cookie metadata observation is opt-in and reversible; the two network features run only at your click. To delete everything the extension has recorded, remove the extension — your browser erases its storage with it.

A later release may offer an opt-in way to contribute derived tracker observations to Kenshiki so we can expand tracker recognition and improve valuation accuracy for everyone. If we build it, it will be off by default, clearly labeled in the extension, limited to derived signals rather than raw browsing history, never sold, and this page will be updated before any such data is collected.

If how the demo or the extension handles data ever changes, this page will change with it.