The security behind your AI employee.
Built so your credentials never touch the AI, risky actions wait for approval, and your data never trains a model.
- ISO 27001 aligned
- GDPR aligned
- EU data residency
- ChatGPTChatGPT in Slack: Search, write, summarize and get work done.
- ClaudeAnthropic's AI agent for any task — think, write, and code with Claude.
- SpinrunYour AI employee in Slack
Built to the standard.
Honest about the audit.
Our controls follow ISO 27001 and the GDPR. We are not certified yet, and this page says so until we are.
ISO 27001StatusAlignedCoverageAn information security management system built on ISO/IEC 27001:2022. No certificate has been issued yet.DocumentationControls overview on request; the certificate is shared once issued.
GDPRStatusAlignedCoverageA Romanian company under the GDPR and the ANSPDCP, processing your data under an Article 28 DPA.DocumentationDPA and subprocessor list published.
EU data residencyStatusEUCoverageThe database, authentication and the agent runtime run in EU regions. Providers outside the EEA are named, and transfers rest on SCCs where no adequacy decision applies.DocumentationSubprocessor list published, with where each one runs where confirmed.
What Spinrun does.
What Spinrun does not.
Here's exactly what Spinrun touches — and what it never does.
Encrypts your data
TLS in transit, and the API keys and model keys you add sealed with AES-256-GCM, out of the model's reach.
Logs every tool call
Each gateway call — the tool, the action, the outcome, how long it took — goes to the activity log, with payload capture under your control.
Keeps core data in the EU
The database, authentication and the agent runtime run in EU regions. What is not region-pinned, we name on the subprocessor list.
Revokes on demand
Admins can disconnect any integration, remove any member, or stop a running agent.
Train on your data
Your conversations and files never enter our training set, and the providers we route through are not permitted to train on them.
Read your secrets
API keys and tokens are injected at execution time by the tool gateway; the model never sees them.
Act without approval
Writes and destructive actions you put behind approval wait for a person to approve them before they run.
Share across workspaces
Every workspace is isolated at the database row level. No cross-tenant access.
AI Safety
AI brings new risks, and we know how to handle them
Your credentials are invisible to the AI
A backend tool gateway injects your API keys and OAuth tokens at execution time. The AI model itself never sees them.
Not a policy. The architecture.
model-context-preview- Task
- Sync HubSpot MQLs to Salesforce
- OAuth token
- [Redacted]
- API key
- [Not Available]
tool-gateway- Credential
- Injected server-side
- Vault
- AES-256-GCM sealed
- Audit
- Access logged
Enforced in code.
AI brings new risks, and we know how to handle them
AI employees introduce attack surfaces traditional SaaS does not have. Three controls keep the surface small.
Prompt-injection defense
Untrusted content is rendered as data, not commands. High-risk tools sit behind human approval, so an injection can't trigger gated actions like moving money on its own.
Named model providers, no training
Model calls go to providers named on our public subprocessor list by default, and none is permitted to train on your content.
Skills, the persistent memory
Memory is scoped to your workspace, never used to train models, and exportable or deleted on request.
Credentials & secrets
Every tool you connect.
Zero secrets in chat.
OAuth-first
Every major tool connects via OAuth with the narrowest scopes that get the job done. No passwords stored.
Encrypted vault
API keys you add for native integrations, and your own model keys, are sealed with AES-256-GCM, isolated from model context, and read only when a call needs them.
Admin scope control
Admins decide which integrations are connected, who can use them, and what an agent may do with each. Disconnect any integration at any time.
Vulnerability disclosure
If you believe you have found a security vulnerability in Spinrun, we want to hear from you. Email legal@spinrun.ai with enough detail to reproduce the issue: affected URL or component, steps, impact, and any proof-of-concept. Please do not include customer data in the report.
Scope
spinrun.ai, runtime.agents.spinrun.ai, the /mcp gateway, the spinrun CLI, and our code repository. Third-party services we integrate with are out of scope; report those to the vendor.
Our commitments
- Acknowledgement within 5 business days of receiving your report.
- Triage result and status update within 30 calendar days, and further updates at least every 30 days until resolution.
- Confirmed critical vulnerabilities fixed within 90 calendar days of confirmation; other severities according to our internal remediation targets, which are stricter than this.
- We coordinate public disclosure with you once a fix is released, and we credit reporters who want credit.
What we ask of you
give us reasonable time to remediate before public disclosure, do not access or modify data that is not yours, do not degrade the service (no DoS, spam, or social engineering of staff or customers), and stop and report immediately if you encounter customer data.
Safe harbor
research that follows this policy is authorized, and we will not pursue or support legal action against you for it. If a third party takes action against you for activity conducted in accordance with this policy, we will make it known that you acted in good faith.
Recognition
we do not run a paid bug bounty today. Meaningful reports receive a thank-you, public credit if wanted, and Spinrun credits.
FAQ
Email legal@spinrun.ai. We acknowledge within 5 business days, provide triage status within 30 days, and fix confirmed critical issues within 90 days. Full policy under Vulnerability disclosure on this page; machine-readable contact at /.well-known/security.txt.
One hire. The output of a team.
Spinrun works nights, remembers every decision, and connects to the tools you already use. Start free, then Pro from €20 a month.