Verify the wiring

Every AI extension says it respects your privacy. Ours is the rare claim you can check yourself — in about 60 seconds, with tools already built into Chrome.

Watch the traffic yourself

1. Open the SideZero side panel, then go to chrome://extensions and switch Developer mode on (top right).
2. On the SideZero card, click Inspect views → sidepanel.html. A DevTools window opens — this is the extension's own traffic, nothing else mixed in.
3. Pick the Network tab in that DevTools window.
4. Back in the panel: send a message, summarize a page, generate an image — use anything.
5. Read the Domain column, then click any request → Headers to see exactly what was sent, and to whom. What you'll see depends on which mode you used:
   • Your own key (BYOK): the request goes straight to that provider — api.anthropic.com, api.openai.com and so on. No sidezero.app anywhere. We are not in the path, at all.
   • Zero (the free / $12 managed plan): you'll see exactly one request to sidezero.app/api/v1/ai/chat. That one is us — it has to be, because we're paying for those replies. Open it: it carries your message text and a random install id (or your sign-in token), and nothing else — no page URL, no browsing history, no identity beyond the account you chose to create. We pass it to the model and stream the answer back. We store the token counts for your quota; the text itself is never written down. The database that records usage has no column for it — see "What we store" below.
   Both modes are honest, but they're different, and this page would be worthless if it pretended otherwise.

The complete list of domains

This is every network destination in the extension. Not the highlights — the whole list.

That's the whole list. A request to any other domain would be a bug — we'd genuinely like to hear about it: support@sidezero.app.

One thing that is not in the table, because it isn't ours to make. When you dictate, SideZero uses the speech recognition built into Chrome. Chrome sends that audio to Google to turn it into text — exactly as it would for any website that asks for your microphone. That request comes from the browser, not from the extension, so you will not see it while you watch our traffic, and we'd rather tell you than let you assume the microphone works offline. Your audio never passes through SideZero, and a note is stored only when you press Save. If you would rather it didn't go to Google, don't use the mic — every other feature works without it.

What you will never see

• No calls to sidezero.app. The extension never phones home. You only land on our site when you click a "get a key" link in Settings (a plain redirect), or when Chrome itself opens our feedback page after an uninstall — carrying nothing but your browser type and the extension version, never an identifier.
• No analytics or telemetry domains. There is no tracking library in the extension. We don't know who you are, what you browse, or what you asked.
• No error reporting. Diagnostics stay on your device; the Support card lets you copy a scrubbed debug summary and email it — or not. Key-shaped strings are removed from it before it's even written to disk.
• No key sync. Keys are stored with chrome.storage.local — the variant that never syncs to your Google account or other machines.

Why this works as proof

A browser extension can't hide its traffic from its own browser. DevTools sits below the extension, not beside it — if SideZero called anywhere else, it would appear in that Network tab, timestamped, with the payload attached. That's why we'd rather show you the wiring than ask you to trust a policy page.

English · Deutsch · 日本語 · Français · Español · Português