AppsSecurity & Compliance

How the security controls are themselves protected

Data handling, permissions and audit for Autessa Security & Compliance

The controls that protect your Autessa company are protected the same way: they live inside your company boundary, they are encrypted with your company’s own keys, the most sensitive changes require a person in the browser, and every change leaves a record.

Start free
Layers around your dataNorthwindSample

Company scope

Storage encryption

Per-company AES-256 key

Connector credentialsConversation historyTrigger payloadsWebhook detailsJob run historyMCP credentialsPhone configsApp sign-in material

Company scope: Every request is scoped to one company first

Storage encryption: All storage encrypted at rest at the infrastructure level

Per-company AES-256 key: Keys derived per company, unique to you

Data handling

What is stored, and how?

DataHow it is handled
Secret valuesEncrypted, never returned by any read. Filled in only inside outgoing HTTPS requests to allowed hosts.
Authenticator setup keysShown once at setup; the QR code is drawn in your browser.
Model provider keysEncrypted with your company key, write-only, last four characters shown.
Connector credentials, history, payloadsAES-256 with keys unique to your company, inside encrypted storage.
Masked columnsStored encrypted; every reveal logged as DECRYPT.
Card and account numbers in chatHeld for the conversation only, never saved; the AI sees placeholders.
Evidence sealsWrite-once storage; COMPLIANCE seals locked until their retention date.

Permissions

Nobody can grant more than they have

Every place access is handed out, the giver is checked against their own access: invitations, roles, share levels, API key scopes, app permissions and table roles. Keys are re-checked against their owner on every request, and runs act as the person behind them.
  • Inviters cannot grant permissions they lack
  • Share levels never exceed your own
  • Keys never reach beyond their owner
  • Only Admins can assign the Admin role
Who a run acts asfollows into sub-agents and toolsSample
Started by a personRuns as that person
Started by an API keyThe key’s limits, never more than its owner
A visitor of a public or sign-in appThat visitor, within the app’s permissions
Triggers, scheduled jobs, webhooksThe person who set them up
Inbound Slack, text or callThe person who connected the channel
toolConfig.runAs: "OWNER" · invokableBy: "OWNER_TOOLS"

Simple data tools only. Turns itself off when anyone else edits or publishes.

Audit

Every security change leaves a record

Secrets record every change, share, use and reveal. The data access log records every read and change of protected data on a verified hash chain. Evidence seals keep their own chain of custody.
stripe-live · audit lognewest firstSample
10-31 14:02USECharge card · api.stripe.com · run 8f2c
10-31 13:40USE_DENIEDExport orders · no Use access
10-28 09:15ROTATEsam@northwind.example · v2 → v3
10-27 16:30SHARETeam Payments · Use
10-02 11:04CREATEsam@northwind.example · SEALED

Reports, policies and questionnaires

Autessa’s compliance reports, security policies and subprocessors are on the Trust Center. Platform availability is on the status page.

FAQ

Security questions

Where are Autessa’s audit reports and policies?

On the Autessa Trust Center at trust.autessa.com, where you can request reports and answers to security questionnaires.

Can Autessa staff see our secrets?

No for Sealed secrets: nobody can view them, including support. Revealable secrets need a request approved by a manager in your company, and machine identities can never reveal.

Can a single compromised script mint new credentials?

No. API keys, OAuth clients and SSO are administered only in the web app, behind a person’s session.

Review Autessa with your security team

Walk through the controls, the audit trail and the Trust Center with us.

Start free

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