Browser Guide Privacy Policy

Browser Guide is built so that the honest answer to "where does my data go?" is short. This page is that answer in full.

Summary

• No servers of ours. Browser Guide has no backend, no analytics, no telemetry, and no accounts. We never see your data.
• One recipient. Page evidence, questions, and voice audio go directly from your browser to OpenAI's Realtime API, using your own API key, only when you ask a question.
• Credentials in a private local file. Your OpenAI credential (pasted key, or one imported from your existing Codex/Claude Code sign-in) is stored by the local helper in ~/.config/browser-guide/credentials.json with user-only (0600) permissions — the same pattern Claude Code, Codex, and gh use. It never enters Chrome storage, sync, source, or logs.
• Memory stays local. Per-site memory (the last few Q&A pairs, so follow-ups have context) lives in a private local file, is strictly bounded, and is clearable from the panel in one click.

What the extension accesses

• Page snapshot — captured only after you click the toolbar icon on a page and ask something. It is a bounded accessibility outline (roles, names, visible text; ~12,000 characters max). Input values, passwords, cookies, storage, network traffic, and hidden form values are always excluded.
• Screenshots — only when you enable the Visual toggle, and omitted entirely (fail-closed) when a visible input field, code block, or likely-sensitive content is present.
• Microphone — only while you are speaking to the guide after pressing the voice beacon. Audio streams to OpenAI over WebRTC and is never recorded or stored by the extension.

What is stored, and where

• Credentials — ~/.config/browser-guide/credentials.json (0600), written and read only by the local native helper. Removable anytime with the key button in the panel or by deleting the file. Sign-ins imported from Codex or Claude Code stay fresh by re-reading those tools' own credential files on this Mac — Browser Guide never calls sign-in servers itself.
• Site memory — ~/.config/browser-guide/memory.json (0600), also local-only. To make follow-up questions useful, the helper keeps the last few question-and-answer pairs per site: at most 10 short notes per site and 50 sites, trimmed and oldest-out. Memory never leaves your Mac, is shown to the model only as explicitly untrusted history, and the clock button in the panel clears the current site — or everything — at any time. Deleting the file works too.
• Agent-eyes snapshot (opt-in) — ~/.config/browser-guide/eyes.json (0600) exists only while you keep the Eyes toggle on. It holds the same sanitized page outline the guide itself sees (origin, title, accessibility outline, capture time — never input values, passwords, or screenshots) so local MCP clients like Claude Code can read it. The toggle is off by default, a visible badge shows while it is on, and turning it off — or uninstalling — deletes the file.
• Session state — which tab you shared, kept in Chrome's in-memory session storage and gone when Chrome closes. Conversations exist only in the open panel; the only things persisted from them are the local site memory and, while enabled, the agent-eyes snapshot described above.

Third parties

The only third party is OpenAI, which receives your questions, the sanitized page evidence, optional screenshots, and voice audio under your own API key and OpenAI's own terms and privacy policy. Nothing is sent anywhere else — the extension has no network client of its own and its pages declare connect-src 'none'.

Verify it yourself

Browser Guide is open source under Apache 2.0. The claims above are enforced by an automated forbidden-capability guard and end-to-end tests you can run yourself: github.com/Crawlio-app/browser-guide.

Questions or concerns: rashid.azarang.eg@gmail.com.