Acceptable use

Scope

A workspace is a machine we pay for, running an agent you briefed, with network access and a volume. That is why this page exists and why nothing like it exists for Fleet for Mac: on your own Mac the agent runs with your privileges on your own hardware, and what it does is between you and your employer.

What you may not do on a workspace

• No mining. No cryptocurrency mining, no proof of work, and nothing else whose purpose is to convert our compute into a token.
• No exfiltration.Do not use a workspace to move data you are not entitled to, out of anywhere. That includes using it as a relay for someone else’s repository, and it includes bulk-copying a repository you were given read access to for a different purpose.
• No running services for third parties. A workspace is a development machine. It is not a web host, a proxy, a VPN exit, a game server, a bot, or a scraper on a schedule. A dev server you are looking at is fine. A dev server the public is looking at is not.
• No reaching another workspace.Workspaces are on a private network. Do not probe, scan, or attempt to connect to another one, to the control plane beyond the endpoints your own workspace uses, or to our provider’s infrastructure.
• No attacking anyone. No denial of service, no credential stuffing, no unauthorised scanning of hosts you do not own, and nothing illegal where you or we are.

None of the above is aimed at ordinary work. Installing packages, running a test suite, calling an API you have a key for, pushing a branch and opening a pull request are the entire point.

The limits, as numbers

• Idle stop: 10 minutes. A workspace stops after 10 minutes with nothing running. A turn in flight is never interrupted by this, even with the browser closed.
• One run: 6 hours. A workspace stops 6 hours after it starts, busy or not. Start it again whenever you want.
• Outbound transfer: 50 GB a month, included. Past that we will tell you, on your workspace activity page, and past it by a lot we will stop the workspace and write to you. Ordinary development is nowhere near this: it is the number at which something is being moved rather than built.
• Spend cap: yours to set. Every workspace has a monthly compute budget you control. At 80 percent you get a banner. At 100 percent a running workspace stops after a 15 minute grace period so a turn can finish, and a stopped one will not start until you raise it.

Those figures are compute: the machine, the volume and the transfer. Model usage is billed to your own Anthropic account, because credentials are bring your own, and we neither resell nor subsidise nor see it.

What we do about it

We meter compute and outbound transfer per workspace, hourly. We do not read the contents of your volume, and we do not have your prompts or your transcripts: the section on what we hold is specific about this.

If a workspace crosses a line here we will stop it and tell you why, on your own activity page, which is the log of everything that workspace has done. Repeated or deliberate breaches suspend the account. Anything unlawful, or anything actively harming somebody else, we will suspend immediately and without notice, because the alternative is leaving it running.

A suspension is not a deletion. Your volume stays until you delete it or until we tell you a date, and you can always get your work off it.

Telling us about a problem

If a workspace is doing something it should not, including one of ours, write to [CONTACT EMAIL]. Security reports go to the same address and we will not argue about disclosure timelines with somebody doing us a favour.

Changes

We may update this page. The limits above come from the same constants the service enforces, so this page and the running system cannot disagree about a number. If a limit changes in a way that affects you, you will hear about it before it applies.

Contact

[CONTACT EMAIL], [LEGAL ENTITY], [REGISTERED ADDRESS].