Your agent's session is yours.
BrowserAI is built so that what your agent does in a browser stays between your agent and the sites it visits. Here is how, with nothing left out.
Isolated
Every session is a separate Chromium process with its own profile directory held in memory. Sessions share nothing: no cookies, no cache, no storage. Each one reaches the web through an egress filter that refuses private and internal addresses, so a page cannot reach our machines or another session.
Wiped
When a session closes, for any reason, its process group is killed and its profile is deleted. Nothing about the pages it opened survives the session.
Not logged
The gateway writes no request log. It does not record the URLs your agent opens, what it types, the content it reads or the IP it connects from. Errors are logged without any of that.
Off unless you ask
The live view streams frames only to holders of its view token and stores none. Replay keeps frames in memory for one hour after the session closes, only when you turned it on. The cookie vault stores ciphertext encrypted with a key only your agent's wallet can derive.
What we keep
| Data | For how long |
|---|---|
| Session record: id, payer address, start, end, seconds, amount | 30 days |
| Deposits and total spent per address | While the balance exists |
| Replay frames, when turned on | 1 hour after close, in memory |
| Cookie vault ciphertext | 90 days after last write, or until you delete it |
| Signature nonces | Up to 10 minutes, in memory |
No account
There is no sign-up, no email and no API key. A wallet signature authorizes spending and a session token authorizes the browser connection. The only identifier we see is the paying address, and USDG transfers are public on chain, like any onchain payment.