# Construct Computer security

> How Construct Computer keeps your work safe: what agents do without asking, how keys are encrypted, where data lives and how to report a problem.

Construct's agents work in your inbox and your apps, so the limits on them are written into its code, where a web page or an email can't talk them out of it. This page says what an agent may do without you, what we keep and who can reach it.

Checked against Construct's code on November 14, 2026.

## What an agent does on its own

Each agent has a setting for each app you connect: Off, Read only, Ask first or Auto. Whichever you pick, some things always wait for you.

| Where | On its own | Asks first, or can't |
| --- | --- | --- |
| Apps | Reads, and on Auto creates and updates | Sends, posts, deletes, pays, shares or changes who has access, every time |
| Email | Reads its own mailbox | Every email, shown as it will go, and three at most in one turn |
| Files | Reads, writes and moves to Trash | Emptying Trash, which only people can do |
| Computer | Runs commands, five minutes each at most | Reaching more than package registries and code hosts, until an owner or admin allows it |
| Browser | Opens pages you gave it or a search returned | Using your logins, and anything on a page that takes a payment |
| Workflows | Runs saved steps on their schedule | A new workflow stays a draft until you save it |
| Chat apps | Answers your team in Discord, Telegram and Slack | Anyone else gets a guest that only searches, reads pages and replies, 20 questions a day |

On Auto, Construct still reads what each change would do. One that throws something away or reaches other people, like a calendar invite with guests, is treated as a delete or a send and asks. So do an MCP tool whose definition changed since it last ran, a file handed to an MCP server, and a turn that has already made 200 changes.

## Text from outside

Pages, files, email, app results and command output reach an agent marked as untrusted, and it's told to treat what's inside as information, never as instructions. An agent only opens links you gave it or a search returned, which shuts the easy way to send your data to someone else's address.

Email from a sender whose domain doesn't vouch for them is held, and agents never read it unless you let it in. A memory saved after outside text came into a chat waits for you to keep it.

Our tests plant instructions in pages, memories and skills to check that agents ignore them. Prompt injection isn't solved anywhere, though, and when planted text gets through, the approval before a send or a delete is what stops the damage. Our post on [prompt injection](https://construct.computer/blog/ai-agent-prompt-injection/) covers the attacks and these guards in detail.

## Your keys and sign-ins

Model keys, mailbox passwords, MCP tokens and bot tokens are encrypted with AES-256-GCM under a key made for your workspace and that kind of secret, so a sealed value copied anywhere else won't open. A key is opened only for the call that needs it, and never inside your agents' computer.

Sign-ins to apps like Gmail, Notion or HubSpot are held by Composio, our integration provider, under an identity of your own, and Construct keeps the connection's ID, never its token. You can disconnect an app in Settings at any time.

A key pasted into a chat is hidden from the agent, and memory takes out anything that looks like a password, an API key, a card number, an IBAN or a passport number before it's saved. Card details go into Dodo Payments' own checkout, and Construct never receives the card number.

## Where your work lives

Construct runs on Cloudflare. Each workspace has a database of its own, each chat another, and files sit in storage under the workspace's own prefix. Our [sub-processors list](https://construct.computer/sub-processors/) says where each company we use handles data.

Each workspace gets its own computer, a container that holds no secrets. Its web traffic passes through a proxy we run, which lets it reach only what the workspace allows and never a private address. After 10 idle minutes it's shut down and wiped, apart from its workspace folder, which is saved for next time.

## AI and your data

Construct doesn't train AI models on your work. Your messages, the chat so far and what tools return go to the model answering, at one of the providers on our [sub-processors list](https://construct.computer/sub-processors/), under business terms that don't let them train on it.

Our own AI gateway doesn't log your requests. On your own key, the provider you chose handles them under your account with it.

## Who can get in

There are no Construct passwords to steal. You sign in with Google or with a code we email, which lasts 10 minutes and allows 5 tries. A session lasts up to 30 days, Settings lists every device that's signed in, and Sign out everywhere else ends the rest at once.

In a team, owners and admins run the workspace, and only the owner can hand it over, delete it or end its plan. An app account you connect stays yours, and you choose who in a team can use it: nobody, only you, everyone after asking you, or everyone.

Our own admin tools sit behind Cloudflare Access and a one-time code, and anything destructive asks for a second code by email.

## Deleting your data

Export everything, in Settings, downloads your chats, memory, agents and workflows as one file. Delete account stops every workspace you own at once and erases its chats, memory, files, agents, workflows, email, browser logins and app connections, which are removed at Composio too.

We keep payment records for tax, no longer tied to you, a keyed hash of your email so the free trial isn't given twice, a keyed hash of the IP address you signed up from for 30 days, and your agents' email addresses, so nobody else can take them.

## Report a security problem

Write to security@construct.computer.

Tell us what you found, how to repeat it and what someone could do with it, and keep it private until we've fixed it.

We won't take legal action over research done in good faith that stays inside your own account, leaves other people's data alone and gives us time to fix what you found. Agents following planted instructions count too, and we'll thank you on this page if you'd like.

---

The Markdown copy of https://construct.computer/security/. Everything Construct Computer publishes is listed in https://construct.computer/llms.txt.
