Security
How Enact keeps work separate.
Workspaces are boundaries
Every request, job and file operation is scoped to one workspace.
- Files and conversations are stored and authorised per workspace, and access across workspaces is denied.
Isolated cloud work
In Enact's managed cloud, each assistant session runs in its own container, which mounts only its workspace's files.
- Each container mounts only its own workspace's files.
Choose where work runs
Choose where work runs.
- Run conversations on your own Mac, or in Enact’s managed cloud.
Sign-in through Enact Auth
Enact Auth issues every credential the app and Enact's cloud services accept.
- Accounts are never linked by email address alone.
Assistants act within permissions you set
Instructions and permissions are configured per workspace.
- Give each assistant its own instructions, and choose which tools assistants may use in workspace settings.
Data protection
How Enact handles data in transit, at rest and across workspaces.
- Encryption in transit and at rest: Data moving between Enact and your browser or engine accounts is encrypted with TLS 1.2 or later. Stored data is encrypted at rest with AES-256.
- EU data residency option: Teams that need to keep data in the EU can choose an EU data location for their workspace.
- Customer data is not used to train models: Your channels, files and Memory Graph are not used to train Enact's or any AI engine's models.
Compliance roadmap
Enact is working towards ISO/IEC 27001 certification and a SOC 2 Type II report, and is building for GDPR and the EU AI Act.
ISO/IEC 27001
In progressAn information security management system covering how Enact protects customer data.
SOC 2 Type II
In progressAn independent report on Enact’s security, availability and confidentiality controls over time.
GDPR
In progressData protection and privacy requirements for handling personal data of people in the EU.
EU AI Act
In progressEU requirements for how AI systems are built, documented and operated.