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
| Question | Answer |
|---|---|
| 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 hello@maitreyalabs.com 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
- Your project tool's data is read and written by your browser directly with the tool, using your existing sign-in. It does not pass through us.
- An AI request (summarise, draft, list action items, a page question, an @mention) sends the text you typed plus the context you chose to our server over HTTPS. The server passes it to a model provider and returns the answer. We do not write it to our database or logs.
- Your own AI key is stored encrypted (ChaCha20-Poly1305) and used only for your requests. The server refuses private and local addresses so it cannot be pointed at an internal network.
- monday.com and ClickUp tokens (only if you use those chat views): you paste a personal access token in the extension's settings. It is kept in this browser only (never sent to us) and is added to requests to the tool's own API address,
api.monday.comorapi.clickup.com, by the extension's background worker. Web pages and the extension's page scripts cannot read it. Remove it in the same settings page. - Google Drive: your Google sign-in stays in your browser. AI Coworker asks for one permission (files it creates and the folder you pick) plus your email.
The optional Basecamp connection (no install)
- You sign in at Basecamp's own page and allow AI Coworker. We never see your Basecamp password; we receive a token that is stored encrypted and renewed automatically.
- For each project you switch on, we add one Basecamp webhook for new comments. A comment that does not contain @AI Coworker is ignored immediately.
- On a mention, the server reads that one item: its description and its last 40 comments (up to 24,000 characters), sends them to the model, and posts the answer as a comment from your Basecamp account. Basecamp only lets project admins add webhooks, and AI Coworker can see only what your own account can see.
- Disconnect removes the webhooks and deletes the tokens.
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
| Data | How it is kept |
|---|---|
| Account | Email, optional name, company and main tool, plan. Password only as an Argon2 hash. Account keys only as a hash. |
| Usage | Time, kind of task, tool, model, token counts, success. No text. |
| Connections | Code-host tokens, your own AI key and Basecamp tokens, encrypted with ChaCha20-Poly1305. Removed when you disconnect. |
| Code tasks | Instruction, branch, build status, log tail, links. |
| Payments | Razorpay handles the card; we keep the plan, amounts and Razorpay's reference numbers. We never see card numbers. |
| Waitlist and challenge | Email and the answers you typed in the form; challenge progress and the reflections you wrote. |
Who else is involved
- AI model providers that answer requests on the default route (currently OpenCode, DeepSeek and OpenRouter-hosted models), or the provider you connect. Each works under its own API terms.
- Razorpay for card payments. Cloudflare for the public address. Google only if you connect Drive. GitHub only if you connect code tasks.
- No other customer can see your account, usage or connections: every request is checked against your own account key.
Checklist for your IT team
- Install per person, not per workspace. No admin rights in your project tool are needed, except that Basecamp lets only project admins add the optional webhook.
- The extension has no remote code: it ships with its own scripts and loads nothing from other sites.
- Network destinations: our site and API,
googleapis.com(if Drive is on), your tool, andapi.monday.comorapi.clickup.com(only with those tokens). A provider address only on the server side. - Want a data-processing agreement, or found a security problem? Write to hello@maitreyalabs.com. See also the privacy policy and terms.