Security and data

What AI Coworker can see, when it acts, where your text goes and what we keep. Written so your IT team can approve it in ten minutes. Last updated 7 November 2026.

The short version

QuestionAnswer
Does it act on its own?Only when asked. Summaries and drafted replies are shown to you first, and you click send. It posts by itself in one case: when someone writes @AI Coworker in a comment (answered by the extension in the browser, or by the server in a Basecamp project you connected). Every answer starts with "✦ AI Coworker" so nobody mistakes it for a person.
What does it read?Only what you point it at: the thread, card or page you ask about (and its console errors if you ask). Nothing in the background, no browsing history unless you turn that on.
Where does the text go?From your browser to our server, then to the AI model provider that answers. With your own AI key, to the provider you chose. It is passed on, not stored.
What do you keep?Your account, counts of AI tasks (time, tool, model, token numbers), and tokens you connect (encrypted). Not your prompts, not the AI's answers, not your boards.
Is it used to train AI?By us: never. The providers work under their own API terms (see below).
How do I turn it off?Switch the view off, or remove the extension. Basecamp connection: Disconnect on your account page removes the tokens and the project webhooks. Account deletion: write to [email protected] from your account email; done within 7 days.

What the browser extension can access

Permissions the extension asks for when you install it: storage (your settings), scripting and activeTab (to show the side panel on the page you open it on), contextMenus (the right-click "Send to a task"), sidePanel, and identity (Google sign-in for Drive, only if you use it).

Sites it can read without asking again: our own site, googleapis.com (Drive, only if you connect it), and the project tool it was made for. The single-tool editions (Basecamp, Trello, Jira and so on) ask for that tool only. The all-tools edition asks for the 14 tools it supports: Basecamp, Trello, Jira, Asana, ClickUp, monday.com, Notion, Linear, Wrike, Smartsheet, Airtable, Zoho Projects, Teamwork and Microsoft Planner. Everything else, including "all sites" for the side panel on any page and your browsing history, is an optional permission that the browser asks you about at the moment you turn the feature on, and that you can revoke in the browser's own extension settings.

What leaves your browser, and when

The optional Basecamp connection (no install)

Code tasks

Website and code changes run in your own GitHub Actions, not on our servers. You give a fine-grained token (stored encrypted); one pull request adds the workflow file to your repository, which your team reviews and merges. Each task runs with your build and secrets inside your own runner, proves itself to our server with GitHub's short-lived identity token, and ends in a branch, a pull request and a preview link. We store the instruction, the branch name, the build status, the last lines of the build log and the links, so the card can show them.

What we store

DataHow it is kept
AccountEmail, optional name, company and main tool, plan. Password only as an Argon2 hash. Account keys only as a hash.
UsageTime, kind of task, tool, model, token counts, success. No text.
ConnectionsCode-host tokens, your own AI key and Basecamp tokens, encrypted with ChaCha20-Poly1305. Removed when you disconnect.
Code tasksInstruction, branch, build status, log tail, links.
PaymentsRazorpay handles the card; we keep the plan, amounts and Razorpay's reference numbers. We never see card numbers.
Waitlist and challengeEmail and the answers you typed in the form; challenge progress and the reflections you wrote.

Who else is involved

Checklist for your IT team