Privacy

Draft — last updated September 25, 2026. This page describes plainly what browsertodo does with your data, based on how the software works today. It is not legal advice and not yet a reviewed legal policy.

The short version

• The extension works in your own Chrome. Your cookies and the sites you're signed in to stay in your browser.
• To do a task, the AI has to see the pages it works on. That page content goes to the AI you choose.
• If you sign in to browsertodo, our cloud keeps your account, your cloud TODO tasks and your usage, so it can run them and bill you.
• We don't sell your data and don't show ads.

What stays on your computer

These are kept by the extension in Chrome's own storage and never sent to us:

• Your settings, including the Anthropic API key or Jev key you paste in.
• Your chats, the activity log, and files you attach to a chat. (Tasks you added before signing in stay here too, until you move them into your account.)
• Site logins you save. They are encrypted with a passphrase you choose, and unlocked only for the current browser session.

If you use the local helper with your own Claude Code, the helper also keeps its logs of each run on your computer (%LOCALAPPDATA%\browsertodo).

What the AI sees

While it works on a task, browsertodo reads the pages it acts on: their text, a list of the page's buttons and fields, and screenshots. It sends these, with your instructions, to the AI that runs the task:

• Your own Claude Code or Claude API key: the content goes straight from your computer to Anthropic, under your own Anthropic account and terms. It does not pass through us.
• Jev with your own key: the step to perform and the page's list of elements go to TypeSafe, which runs Jev.
• browsertodo AI: the same content goes through our server to Anthropic (for Claude) and TypeSafe (for Jev). Our server records what each request cost (model, token counts, price) to charge your usage credit. It does not save the content of the request.
• Voice input (paid plans): the audio clip you record goes through our server to Cloudflare Workers AI to be turned into text. We don't keep the audio; we record its length for billing.

When the agent signs in to a site with a saved login, that site's username and password are given to the AI so it can type them. Saved logins are never used for X.

What our cloud stores when you sign in

Signing in is optional. The extension works without an account when you bring your own Claude. When you do sign in with Google, our service at app.browsertodo.com, which runs on Cloudflare, stores:

• Your account: your Google account ID, email address, name and profile picture link. We ask Google only for these (the openid email profile scopes).
• Sign-in sessions for the extension and the dashboard.
• Your cloud TODO list: each task's instructions, attached files, schedule and status, its result (a summary, a link and a final screenshot of the page) and a log of what happened to it.
• API keys you create for your scripts. We store only a hash of each key.
• Billing and usage: your plan, your usage credit and how it was spent, and a record of each hosted AI request's cost.

Payments

Stripe handles subscriptions and top-ups. Your card details go to Stripe, never to us. We keep the Stripe customer ID and the status of your plan.

This website

browsertodo.com has no analytics, trackers or cookies. Its fonts load from Google Fonts, so Google receives your IP address when the page loads.

Deleting your data

Everything in the extension can be removed by uninstalling it. To delete your account, open the dashboard's Account page and choose Delete account. That cancels any subscription and deletes your tasks, files, keys, sessions, usage records and the account itself.

Contact

Questions, or a request about your data: support@browsertodo.com.