Security

Your work stays in your workspace

AI agents get their own cloud computers, your sign-ins stay on the server, and nothing leaves without your yes. Here's how.

One workspace, walled off

Every workspace has its own computers, files, memory and sign-ins. Nothing a bot sees or saves crosses into another workspace.

A computer per bot

Each bot works on its own cloud computer. A long task on one never sees the files or browser of another, and a computer can be wiped at any time.

Your yes before it leaves

Emails, messages, payments and anything else that leaves the workspace wait for an approval. You set what needs a yes, per bot and per kind of action.

Every step in the audit log

What a bot opened, typed, sent and who approved it is written to the workspace's audit log, kept read-only and exportable for admins.

Controls under the hood

The details security teams ask about first.

Compliance roadmap

Where we are today. We'll publish reports here as each one is done.

  • SOC 2 Type IIn progress
  • SOC 2 Type IIPlanned
  • ISO 27001Planned
  • GDPR data processing agreementIn progress
  • Independent penetration testIn progress

Responsible disclosure

Found something? Email us the steps to reproduce. We reply within two working days, keep you posted while we fix it, and won't act against good-faith research.

security@plany.space

Security questions

Short answers about isolation, sign-ins and approvals.

Ask us something else