Security and data handling
How devlin.ai protects simulation content and learner conversations, in plain language, for your security, IT, and governance teams.
Independently audited against the Security Trust Services Criteria. The report is available under NDA through our Trust Center.
Our AI providers operate under no-training terms. Simulation content and learner conversations are not used to train models.
The application, database, and AI serving run in United States regions.
Row-level security in Postgres keeps each customer's data separate, enforced by the database itself, not only by application code.
TLS 1.2+ with HSTS for every connection, and AES-256 encryption at rest.
Connect your own identity provider over SAML, such as Microsoft Entra ID or Okta, and require SSO for your whole organization.
devlin.ai stores what a simulation needs to run and what a designer needs to review it. Nothing more.
Each learner session gets a random identifier. Learner identity collection is off unless a workspace owner or admin turns it on, and identity values are never included in AI prompts.
In voice simulations, speech is processed in real time and never recorded or stored, by devlin.ai or by our voice provider. The text transcript is stored like any other conversation.
devlin.ai is built for practice scenarios that instructional designers write. It is not designed to process patient data, customer records, or other regulated data.
Designers can request export or deletion of their data. Account deletion removes simulations, conversations, messages, and credit history.
Each subprocessor maintains its own security program. The current list with links to their trust centers is available on request.
Request the SOC 2 Type 2 report and our detailed security overview through the Trust Center, or email devlin@devlin.ai for questionnaires and DPAs.