Privacy

Draft — last updated October 26, 2026. This page describes plainly what Noa 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 Noa, our cloud keeps your account, your cloud TODO tasks and your usage, so it can run them and bill you. It keeps your chat history and memory too, so your other computers have them (you can keep memory on this computer only), and your bookmarks if you choose to sync them.
• Turn on end-to-end encryption and your chats, memory and the pages Noa remembers are sealed on your computer before they're sent. We store only ciphertext and can't read it.
• 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 and memory while you are signed out, the activity log, and documents you attach to a chat. (Pictures you send in a chat go to your account with the chat once you sign in, below. 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%\Noa).

End-to-end encryption

If you sign in, you can turn on end-to-end encryption in the extension's settings (Privacy). Noa shows 12 recovery words, and your computer derives an AES-256 key from them. From then on, every chat, memory entry and remembered page is sealed on your computer before it reaches us, and only your computers that have the words can open it. Our servers, our database and anyone with admin access see ciphertext. We keep only a fingerprint of the key, so your computers can tell the account is encrypted, and while it is on we refuse anything sent readable. The words never reach us, so we can't recover them: if you lose them, the encrypted copies in your account can only be deleted.

What stays readable to us: when each item changed, its size, and for memory, scrambled tags of its key so we can cap how much is kept. While encryption is on, memory search runs on your computer instead of ours. It does not yet cover your cloud TODO list or files kept in your account, and it does not hide what the AI must read to do a task (below).

Your phone

If you pair a phone, it talks to your computer through our relay over an end-to-end encrypted channel (X25519 and ML-KEM-768 for the handshake, so it is designed to resist future quantum computers, then AES-256-GCM). The relay passes messages along without being able to read them. We keep each paired device's name, public keys and, for a phone, where to send its notifications, so your phone can find your computer. Push notifications say only that a job needs you or is done.

What the AI sees

While it works on a task, Noa 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.
• Noa 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 and images

Voice is on paid plans. Which service hears you depends on the voice engine you pick in the extension's settings. We don't keep your audio.

• Standard: each clip you record goes through our server to Cloudflare Workers AI to be turned into text. Replies are read aloud by your own browser. We record the clip's length for billing.
• Deepgram: your speech is transcribed the same way. The text Noa says back goes through our server to Deepgram's voice on Cloudflare Workers AI, which returns the audio. We record the text's length for billing.
• Realtime and Realtime mini: while a voice session is open, your microphone audio streams through our server to OpenAI's Realtime API, along with the rest of the conversation, including what the agent reports about the task and the pages it works on. OpenAI's replies come back the same way. We record each response's token counts and cost, not what was said.
• Image generation: when you ask Noa to make a picture, your description goes through our server to OpenAI, which returns the image. We record the cost, not the description or the image.

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.noa.bot, 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.
• Memory, unless you keep it on this computer (Settings > Memory; syncing is on by default for a signed-in account): the facts, preferences and task notes the agent keeps, so your other browsers have them. So that memory can be searched by meaning, our server has Cloudflare Workers AI turn each entry into a list of numbers (an embedding) and stores that with it. With end-to-end encryption on, entries arrive sealed and get no embedding.
• Your chat history: each conversation's title, request and what happened in it (the agent's replies and the steps it took, with what it read on the pages), so signing in on another computer brings your chats back, and the pictures you sent in them. Other files you attach stay on your computer. Chats you had before signing in are added when you sign in. Deleting a chat in the extension deletes it from your account too. With end-to-end encryption on, all of this arrives sealed.
• Bookmarks, if you sync them between computers: each bookmark's title, link and folder.
• Phone calls Noa makes for you: the number called, when, how long, what it cost and the transcript of what was said, so the chat can show the call. During the call its audio passes between Twilio (the phone line), our server and the voice model you picked (OpenAI or Google Gemini). We don't keep the audio.
• 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.

Our customer records

We keep track of who uses Noa in RunHQ, the tool we use for sales and support: your email address, name, when you signed up, your plan, and the amount and date of each payment. It does not receive your chats, memory, tasks or anything Noa read on a page.

This website

noa.bot has no ads. Each page loads RunHQ's visit counter, which records page views, the page you came from and time on the page, and sets a cookie for it. 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, chat history and its pictures, keys, sessions, linked phones, call records, synced memory and bookmarks, usage records and the account itself, and removes you from our customer records. To delete only your synced memory, choose Forget everything in the extension's memory settings.

Contact

Questions, or a request about your data: support@noa.bot.