Security
How we keep your business safe.
Security at Operator AI is not a checklist. It is how the product is built: humans stay in control, access is limited, and every action is visible.
Security principles
Control first. Transparency always.
Eight principles shape how we design, operate, and support your AI roles.
Built-in approval gates
Operator AI never acts on its own for anything that matters. You decide which actions need a human yes, and Operator AI stops and asks before it proceeds.
Scoped access per tool
We connect each tool with the minimum permissions needed. No broad account takeovers. Tokens are revocable and stored encrypted at rest.
Full visibility, every action
Every decision, every message and every tool action is logged with reasoning. You can see what happened, why it happened, and roll it back if needed.
Understand model data use
Confirm the model providers and their data-use terms for your workflow before sharing sensitive information. Training terms need to be checked for your configured services.
Encrypted in transit and at rest
All traffic is protected with TLS 1.2+. Backed data is encrypted at rest. We use short-lived tokens and rotate keys as part of regular maintenance.
Isolated VMs, per business
Each role runs on its own dedicated virtual machine with its own kernel, network stack, and storage. Your machine is never shared with other customers, and our developers cannot reach into it.
Private knowledge, per business
A retrieval (RAG) system grounds each role in your own business documents, so answers come from your context. That knowledge is stored separately per customer and never merged or shared.
Human oversight by default
New workflows start with approval on everything. You loosen the leash per process as trust builds, never the other way around.
What we do
Practices, not promises.
Security is a daily practice. Here is how we put the principles into action.
Least-privilege integrations
- Each tool gets only the permissions required for its role.
- OAuth tokens are scoped and never shared across customers.
- Integrations can be paused or disconnected in one click.
Clear data boundaries
- Each business runs in its own isolated VM, separate from every other customer.
- A RAG system retrieves business knowledge per customer, never across customers.
- Context from one business is not used for another.
- Retention periods are agreed during onboarding and configurable.
Reliable infrastructure
- Roles run in isolated virtual machines with their own kernel and storage.
- Hosted on a managed cloud provider with regional redundancy.
- Regular backups and environment separation.
- Monitoring and alerting for unusual activity or failures.
Contact
Talk to us about security.
We answer questions, review concerns, and take vulnerability reports seriously.
Questions about security?
Email us at security@operatorai.dev and we will respond as soon as possible.
Contact security teamReport a vulnerability
Found something we should know? We review every report and move quickly to fix real issues.
Report a vulnerabilityOperator AI security guides
Operator AI FAQs
- Is my data used to train AI models?
- Ask the team to confirm the model providers and their data-use terms for your workflow before connecting sensitive information. Provider-specific training terms need confirmation for your setup.
- Where is my data stored?
- Storage locations depend on the configured runtime and connected services. Ask for the locations relevant to your workflow before sharing data with residency requirements.
- Is Operator AI GDPR compliant?
- This page is not a compliance certification. Ask the team to confirm the applicable data-processing terms and safeguards for your intended use, and review them against your business obligations.