Cookie vault

Keep an agent signed in to a site across sessions without leaving its cookies readable on our side.

How the key is made

The SDK asks the agent's wallet to sign the fixed message BrowserAI cookie vault key v1 followed by its address. Wallet signatures are deterministic, so the same wallet always produces the same signature. Its SHA-256 is the AES-256-GCM key. The signature and the key never leave the agent.

What is stored

The cookies are exported from the browser, encrypted on the agent's side with a fresh 12 byte IV, and uploaded as bai1.<iv>.<ciphertext> under a name you choose, keyed by your address. Reading, writing or deleting an entry requires a fresh signature from that address. Entries are deleted 90 days after their last write, or when you delete them.

What we can see

While a session is open, its cookies live inside that browser, as they would in any browser, and travel over TLS during export and import. At rest we hold only ciphertext we cannot decrypt.