be2ween — Privacy Policy

Effective: 2026-06-27 · Publisher: workingrobot.com · Contact: d@workingrobot.com

The short version: be2ween never reads your prompts or the AI's responses. It has no accounts and no user database. Nothing you type, and nothing the AI says, ever leaves your browser. The only network request it makes is fetching our house programming — and that request carries no information that identifies you.

What be2ween does

be2ween is a Chrome extension that notices when an AI web app (Gemini, Claude, or ChatGPT) is "thinking" and fills the wait with house content — station cards, trivia, short interactive bits — then hands you back when the AI is done. No backend for your data, no sign-in.

How it detects "thinking" — without reading anything

To know when the AI is working, be2ween looks only at interface chrome: the presence of a stop/cancel button, the model-name label, whether an attachment chip is present, and the rate of page changes (counted, never inspected). It does not read, store, or transmit the text of your prompts or the AI's responses — ever. This is enforced in the code itself, not just by policy: the detector is built so message text cannot enter it.

What stays on your device (and is never uploaded)

These live in your browser's local storage and are never sent anywhere:

If you use Chrome's built-in account sync, Chrome may sync your extension settings across your own devices. That is Chrome's sync, under your Google account — be2ween has no separate account and never receives that data.

The one thing that leaves your device: fetching our programming

About every 30 minutes (and on startup), the extension fetches our house programming feed from workingrobot.com. This is a normal web request for a file. It includes the extension's version number (the same for everyone on that build) so we can see which versions are in use. It carries no user identifier, no account, and nothing about what you typed or which AI you used.

Because it is a web request, our server can see the network metadata any web server sees — your IP address, browser user-agent, and the time. We do not retain it as a per-user record. We aggregate these requests into counts only — roughly how many active installs there are, an approximate country breakdown, and the version split — and we discard the raw IP addresses. We do not build profiles, track individuals, or follow you across sites.

The programming we send you is data, not code

The feed is signed (Ed25519) and validated before anything is shown, and it contains only data — text cards, channel definitions, and detector configuration (which interface elements to look at). It never contains executable code; the extension runs only the code packaged in it (its security policy forbids remote scripts). The detector configuration can tune which on-screen elements be2ween looks at, but it can never make be2ween read your messages, and the extension always falls back to its built-in baseline if the feed is absent or invalid.

What be2ween never does

Permissions, and why

Children

be2ween is not directed to children and does not knowingly collect data from anyone — it collects no personal data at all.

Changes

If this policy changes, we'll update this page and its effective date. Material changes will be reflected in the extension's listing.

Contact

Questions: d@workingrobot.com.