Privacy Policy

Last updated: August 6, 2026

Pagehand (“the Extension”) is a Chrome extension that helps you read and automate the current page using the Chrome DevTools Protocol. This policy explains what data the Extension handles and what it does not do.

1. Two ways Pagehand reaches a model

Which one you use decides whether Pagehand’s servers see anything at all. In both, the agent loop and every page tool run inside the Extension, and your chat threads are stored only on your device.

• Hosted (the default) — you sign in with an email address, and model calls go from the Extension to Pagehand’s API at pagehand.app, which forwards them to the model router (OpenRouter) and on to the provider serving that model.
• Your own API key — you supply a provider key, and requests go from your browser straight to that provider. Pagehand operates no server on this path and receives nothing.

2. Account data (hosted mode only)

If you never sign in, none of this exists. Signing in creates an account that holds:

• Your email address — used to send the sign-in link and to identify the account. Authentication and the account database are provided by Supabase.
• Session tokens — issued on sign-in and stored on your device (see §3), so the Extension can call the hosted API without re-authenticating each time.
• Usage records — for each hosted request: account id, the model asked for, a timestamp, and what the request cost. Used for metering, quotas, and abuse prevention. The content of your messages is not part of this record and is not stored.

You can sign out from the side panel at any time, which removes the session from your device. To have the account itself deleted, contact us (§9).

3. Data stored on your device

The Extension stores the following locally in your Chrome profile:

• LLM settings — provider choice, model name, base URL (if custom), and API key, in chrome.storage.local. Keys are stored unencrypted in the browser profile and are not synced to your Google account via Chrome Sync.
• Hosted session — the access and refresh tokens for your account, in chrome.storage.local, with the same exposure as the keys above.
• Chat threads — conversation history (including any screenshots kept in the thread) in IndexedDB on this device.
• Locale preference — your UI language choice.

4. Data sent over the network

When you chat with the agent, prompts, page-derived context (for example accessibility snapshots, console/network excerpts, and screenshots you ask it to take), and tool results are sent to a large-language-model provider — the one you configured, or the one serving the hosted model.

In hosted mode that traffic passes through Pagehand’s API on its way to the router and the provider. It is forwarded in transit and not written to a database by us; only the usage record in §2 is kept. With your own key, nothing is routed through us at all.

Those providers’ own privacy policies govern data once it reaches them — as does OpenRouter’s on the hosted path.

5. Permissions and page access

Pagehand uses Chrome’s debugger permission (Chrome DevTools Protocol) to inspect and control the page it is attached to. While attached, Chrome displays a persistent banner: “Pagehand is debugging this browser.” That banner is a Chrome safety feature and cannot be suppressed by the Extension.

Default host permissions are limited to the built-in provider API hosts. Broad site access (https://*/*, http://localhost/*) is optional and requested only when needed (for example a custom provider base URL).

6. What we do not collect

• No storage of your chats, page content, or screenshots on Pagehand’s servers
• No crash reports or usage analytics sent to Pagehand
• No advertising identifiers
• No sale of personal information

Server logs for the hosted API record request metadata — time, account id, model, size, and cost — not message content.

7. Children

The Extension is not directed at children under 13, and we do not knowingly collect personal information from children.

8. Changes

If this policy changes in a material way, the “Last updated” date above will be revised. Continued use of the Extension after an update means you accept the revised policy.

9. Contact

Questions about this policy, or a request to delete your account: email horizon05140@gmail.com, or open an issue on GitHub.