Data protection
Tenant isolation and encryption
Each Autessa company is its own isolation boundary for people, resources, data and encryption keys. Every request is scoped to one company before it touches data, and sensitive data is encrypted at rest with AES-256 using encryption keys unique to your company, inside storage that is itself encrypted at the infrastructure level.
The problem
What problem does it solve?
In a multi-tenant platform, a single bug in a query filter can expose one customer’s records to another. Logical separation alone puts all of that weight on code being perfect.
How it works
- 1
One company at a time
You always work in one company, your active scope. Switching re-scopes the whole builder and every API.
- 2
Nothing crosses the boundary
A resource in one company cannot see, call or reference another’s. Credentials minted in a company reach only that company.
- 3
Per-company keys
Keys are derived per company, so the key material protecting your data is not the key material protecting anyone else’s.
- 4
Explicit exchange only
When two companies need to exchange something, the Marketplace provides an explicit, reviewed packaging step, never ambient access.
Every option
Tenant isolation and encryption: settings and options
| Setting | What it does |
|---|---|
| Connector credentials | OAuth tokens and secrets behind every connected account. |
| Conversation and execution history | Agent and multi-agent logs, copilot sessions and transaction records. |
| Automation payloads | Trigger history, webhook execution details and scheduled-job run history. |
| Feature secrets | MCP server credentials, phone configurations, e-signature verification codes and app authentication material. |
Permissions
Who can do what?
| Who | What they can do |
|---|---|
| Members | See only the companies they belong to. |
| Everyone, including Autessa systems | Reach your data only through a request scoped to your company. |
What to know
- The tenant key is the innermost of several layers, not the only one.
- For reports on infrastructure controls, see the Trust Center at trust.autessa.com.
Connections
How Tenant isolation and encryption connects to the rest of Autessa
Reports, policies and security questionnaires are on the Autessa Trust Center.
FAQ
Tenant isolation and encryption: questions
Is my data encrypted at rest?
Yes. Sensitive data is encrypted with AES-256 using keys unique to your company, and all storage is also encrypted at rest at the infrastructure level.
Can another company’s agent call my tools?
No. A resource in one company cannot see, call or reference a resource in another.
Who manages my encryption keys?
Autessa derives and manages keys unique to your company, so your data is isolated by encryption with nothing extra for you to run.
Get started with Tenant isolation and encryption
Every Autessa company is cryptographically separated: sensitive data is encrypted at rest with AES-256 using keys unique to your company, inside storage that is itself encrypted.
Reports, policies and questionnaires live on the Autessa Trust Center.
100% customizable, code and all
Make Autessa Security & Compliance fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours