Privacy

Your account

• Your name, as you typed it or as Google or Apple gave it.
• Your email address. You prove it when you join, with Google, Apple or a code we email you. We use it to sign you in and to write to you about your account, never for marketing.
• If you made a passkey: its public key and id. The private key stays on your device, and we never see it.
• For each agent token: its name, when it was made and when it was last used. The token itself is stored only as a hash.
• Your sign-in cookie, stored only as a hash. It lasts 30 days.

We have no password for you. WorkOS, a US company, runs the Google and Apple sign-ins and sends the sign-in codes for us, so it sees your email address and, with Google or Apple, your name.

Your browsers

Each browser is Chromium running on our server with a profile of its own. The profile holds what any browser keeps:

• Cookies and logins, history, and site data (local storage, IndexedDB, caches).
• The list of open tabs, so the browser can reopen them after it sleeps.
• Passwords and passkeys you save in the browser. These are encrypted on disk with a key kept on the server.
• Pictures of the pages, for the console: the latest one for each browser, up to 120 earlier ones, and one for each sleeping tab.
• An activity log of what agents and you did in the browser: actions, page addresses, the agent's name and the reasons it gave when it asked for you. The last 1,500 entries per browser are kept.
• An outbound proxy's password, if your browser has one, encrypted.
• A usage log, so we can tune when idle browsers sleep: for each agent call, the time, the browser and tab number, the tool and its action (such as "click" or "screenshot"), how long it took, how much data went each way, the CPU and memory the browser used around it, whether the browser and tab were awake or asleep, whether you were watching, and the agent's name. Also when the browser and its tabs slept and woke, and when you opened and closed it. It holds no page text, addresses, typed text or tokens; a site appears only as a scrambled code, the same for every visit to that site, that doesn't name it. Kept 30 days, then deleted.
• A backup of each browser's profile, made while the browser is awake (every minute when something changed, and within seconds of a new login). Backups go to OpenFS storage on Cloudflare R2, sent encrypted in transit. A backup holds the same profile as above, cookies and the encrypted vault included. Old backups are thinned out: every backup is kept for an hour, then one an hour for 30 days, until you delete the browser.

Cookies and site data are not encrypted separately from the profile. Someone with access to the server's disk can read them.

Where it is

The hub and your browsers run on a server we rent from Hetzner in Germany. Backups are stored in Cloudflare R2, in a bucket in Western Europe.

Who can see your browsers

• You, signed in, and the agents you gave a token to.
• Other accounts can't. To them, your browsers answer as if they don't exist.
• Anyone you give a hand-off link to can use that one tab until you tap Done, or for 30 minutes at most.
• The operator. We run the server and have admin access to it. The hub's owner key opens every browser, yours included, and anyone with admin access to the server can read the files listed above. We only open a browser or its files to help you when you ask, or to fix a fault or stop abuse.

Others who handle your data

• Cloudflare carries all traffic to and from this site through a Cloudflare Tunnel, which decrypts it at Cloudflare's edge before it reaches our server.
• Phone alerts, if you turn them on, go through ntfy.sh. Each alert has your browser's name and the reason the agent gave. Anyone who knows your topic name can read your alerts, so keep it to yourself.
• The live video in the viewer finds its connection through Cloudflare's STUN server, which sees your IP address.
• If a browser has an outbound proxy, its traffic goes through that proxy provider.
• Sites you and your agents visit see the browser as they would any browser.
• What your agent reads from pages goes to your agent and its AI provider, under your own agreement with them.

What we don't do

No ads. No analytics or tracking on these pages, and no third-party scripts, fonts or images. We don't sell or rent your data. The only cookie is your sign-in cookie, set when you sign in.

Deleting things

• An agent token: revoke it in the console's account menu. It stops working at once.
• Signing out ends your sign-in cookie.
• A browser: open it in the console, then Settings, then Delete. Your account: Delete account in the account menu, which deletes all your browsers too. Either one erases the profile (logins, cookies, history, site data), saved passwords and passkeys, pictures and activity, and its backups in OpenFS, at once and for good. Agent tokens stop working, and nobody can sign in to the account again. If the backup service can't be reached, the browser is still deleted and we keep retrying until the backup is gone.

Questions

Hotkey is run by the team behind Hotkey. Write to [email protected].