Security and trust
Pluto Coach Ltd ("Pluto", "we") makes Warden. This page is for whoever reviews Warden before your company adopts it. It says what Warden does today, and nothing more. For the data we collect, see our privacy policy; for the agreement, our terms.
At a glance
| Question | Answer |
|---|---|
| Does our code go to Pluto? | On the free edition, no: it goes from the developer's computer to the model provider your company chooses. On Warden Team, the chats your company shares, including the code the agent read or wrote, are stored in your company's Team portal, which we host on AWS in the EU (Ireland): secrets removed on the developer's computer and again on the server, any chat can be marked Private, your company can turn the log off, records are kept 90 days by default (a manager can set 7 to 730) and can all be deleted at once. Separately, prompts pass through us only through Warden Team's hosted model gateway, which keeps no content and runs for demos only: it is off the rest of the time. |
| Do you train models on our code? | No. We never use your code, prompts or data to train models. |
| Who decides what an agent may do? | Your rules, checked on the developer's computer. A model never decides. |
| Single sign-on | Your own identity provider over OpenID Connect (tested with Okta; Microsoft Entra, Google Workspace and others speak the same standard), or Google sign-in. You can require your own provider for everyone. |
| Joiners and leavers | SCIM 2.0: assign someone to Warden in your identity provider and they get a seat; remove them and the seat is revoked. |
| Where Warden Team data lives | Amazon Web Services in the EU (Ireland), or a dedicated instance for your company alone. |
| Encryption | HTTPS in transit. Stored records encrypted at rest; secrets sealed with AES-256-GCM under a key only the service holds. |
Your code and prompts
- The Warden desktop app runs on the developer's computer. Code and prompts go to the model provider your company chose, on your company's own account.
- The app sends us no usage data: telemetry is switched off in its code, with no setting to turn it on.
- Warden Team holds your company's rules, skills, plans and specs, and the activity log: on by default, a company can turn it off, and a member can mark any chat Private. Never your repository.
- Warden Team can route prompts through a model gateway so your company can set budgets and allowed models. The supported path today is your company's own LiteLLM proxy, set in the Team portal: prompts and code go from the developer's computer to your proxy and never reach us. Our hosted gateway is for demos and is off the rest of the time; while it runs, prompts pass through it on their way to the provider and we do not keep their content.
Who can sign in
- Your identity provider. The Warden Team portal signs people in through your company's own OpenID Connect provider, with PKCE. Only people who already hold a seat in your company get in; a working email at your domain is not enough.
- Require SSO. Once a sign-in through your provider has worked, a manager can require it: passwords and Google sign-in then stop working for your company, so your provider's multi-factor and session rules apply to everyone. The Warden mobile app signs in with a password today, so it is refused for a company that requires SSO.
- SCIM 2.0 provisioning. Tested with Okta. Your identity provider adds and removes Warden seats as people join, move and leave. Members of one group you name become managers; everyone else is a developer.
- Seat licences. Each developer's Warden app holds a licence signed with Ed25519 and bound to their seat and email. A revoked seat is refused on every call to Warden Team at once.
- Roles. Managers set company rules, skills and seats. Developers read company rules and cannot change them.
What agents may do
- Tool calls an agent makes in Warden are checked against your rules: deny blocks it, ask waits for a person's yes, the rest runs. With API-key and local models every call is checked before it runs. With Claude Code, its built-in tools and the MCP servers Warden adds are checked before they run; in the current release a tool it runs without asking (an MCP server from your own Claude settings, a command one of your Claude allow rules covers, or Bash its own sandbox allows) is checked only as it starts, and the next release closes this. For other agents, see the docs for exactly when each call is checked.
- A rule set by your company cannot be waived on a developer's machine.
- Secrets kept in Warden stay on the developer's computer, in the operating system's keychain (on Linux without one, an encrypted file). An agent refers to a secret by name; Warden puts the value into a command only when your rules allow that command, and scrubs it from what the agent reads back.
- Approvals can be answered from the desktop, the Warden mobile app, Slack or Microsoft Teams. Each answer is recorded, with where it was given.
Where Warden Team runs
- On Amazon Web Services in the EU (Ireland), with its databases in the same region.
- Our hosted demo gateway keeps its own records (keys, budgets, allowed models; never prompt content) in the UK.
- Cloudflare sits in front of the service and this website. Emails are sent from the UK.
- We share the full list of sub-processors on request, and our privacy policy names them.
A dedicated instance is a separate copy of Warden Team for one company, run by us in the same places, with its own database, its own keys and its own address at <your-name>.wardenofpluto.com.
Records, audit and deletion
- Secrets are removed from activity on the developer's machine before it leaves, and again on the server.
- Every active member of your company can read its activity log of agent work (on by default; chats marked Private are not shared). Managers also see an identity log of who was added, removed or promoted and who signed in through your provider, and the record of approvals.
- Your company's managers control retention (90 days by default for the activity log) and can delete records.
- When a seat is removed, by a manager or by your identity provider, their portal sign-in, phones and Warden licence stop working at once, and their personal work store is erased.
For your security review
- Certifications
- Warden does not hold SOC 2 or ISO 27001 certification yet. We answer security questionnaires directly: email us and we reply with what Warden does, not a template.
- Data protection
- For Warden Team records we act for your company (it is the controller, we are its processor), under UK and EU data protection law. See the privacy policy.
- Reporting a vulnerability
- Email ace@wardenofpluto.com with the subject "Security report", and please give us time to fix it before telling anyone else. Found a way past a rule instead? Report it on our issue tracker.
- Who we are
- Pluto Coach Ltd, London, United Kingdom.