Platform
Built for data that cannot leak.
Everything on this page is a statement about how the platform works today. Where a control is in progress rather than finished, it says so.
PHI under BAA
Protected health information is permitted on the Team and Enterprise plans under a Business Associate Agreement. The Free plan is restricted to synthetic data — it exists so you can design, import and test without a contract, not so you can pilot with live patient records.
We describe the platform as HIPAA-ready: the technical and organizational controls required of a business associate are in place, and the BAA is what puts them under contract. There is no such thing as a HIPAA certification, and we do not claim one.
SOC 2 program
Our SOC 2 program is in progress — evidence collection is under way and a Type 1 assessment is scheduled.
We will publish the report when there is a report to publish. Until then there is no badge on this page, because a badge would be a claim we have not earned yet. If your procurement process needs the current status in writing, ask and we will send it.
Controls
What is in place today.
Encryption
- Message payloads and bundles are encrypted at rest in S3 using KMS-managed keys.
- TLS 1.2 or higher on every connection in transit; mutual TLS is available where a counterparty requires it.
- Ephemeral storage attached to running channel tasks is encrypted.
- Secret references are resolved at runtime and never rendered into logs or traces.
Isolation
- There is no shared filesystem between tenants.
- Each paid channel runs in its own dedicated task rather than a shared worker.
- Platform operators cannot read PHI payloads or message traces.
- Sandbox environments are ephemeral and torn down after their idle timeout.
Access control
- Single sign-on with Google and Microsoft on Team and above; OIDC and SAML on Enterprise.
- Workspace roles: owner, admin, editor and viewer.
- Organization membership with invitations and revocation.
- Audit logs on all mutating APIs — who changed what, and when.
Network controls
- Production listeners require an inbound allowlist.
- Dedicated ingress and egress address sets give the counterparty a stable IP to allowlist.
- Gateway addresses at
*.gw.intucloud.aiterminate TLS 1.2 or higher. - Hosted in AWS us-east-1 during the beta.
Retention
How long data is kept.
Free
7 days
Synthetic data only
Team
30 days
PHI permitted under BAA
Enterprise
365 days
Extended retention available as an add-on
Self-hosted intu-dev deployments set their own retention — the data never reaches us. Enterprise support for self-hosted deployments.
Explore the platform
Questions about compliance?
Talk to us before you fill in a security questionnaire — we would rather answer it properly.