# Security and trust

This page is an overview for a first conversation. For a security questionnaire
or a detailed review, [contact us](/contact).

## What is in place

- **Tenant isolation.** Each customer's data is separated by the database
  itself, not only by application code.
- **Your keys.** Provider keys and integration tokens are encrypted per tenant
  and decrypted only in memory when needed. With Gateway and AGDK, provider keys
  stay on the platform side and never enter the agent's process.
- **Human approval.** Agents can be required to pause for a person before a
  consequential action.
- **Audit trail.** General, secret-access, tool-server and governance events are
  all logged, and Governance adds a tamper-evident record.
- **Access control.** Owner, Admin, User and Viewer roles.
- **Single sign-on.** SAML 2.0 is verified against a live provider.
- **Data rights.** Export and deletion for personal data, and configurable
  retention.
- **Stop controls.** Per-agent suspension, and a workspace-wide Emergency Stop
  in Governance.

## What we do not claim

- **No third-party certification today.** Matimo does not yet hold SOC 2 or ISO
  27001 as a vendor. Our compliance exports help you build your own evidence.
  They are not a certificate. Vendor certification is on our roadmap.
- **Encryption at rest.** Encryption at rest for the platform database and cache
  is not yet in place.
- **OIDC and LDAP sign-in.** Built, but not yet verified against a live provider
  or directory.

We would rather tell you this now than have you find it in due diligence.

## Open source

The tool and governance library (Matimo OSS) and the AGDK are open source, so
your engineers can read the code that enforces the rules.