- Workspace Areturns nothing
- Your workspacereturns your rows
- Workspace Creturns nothing
Enforced in Postgres, not in application code
What's in place
Named mechanisms, not intentions
Tenant isolation enforced by the database
Postgres row-level security keeps every workspace's rows apart, below the application.
Per-workspace encryption for connected credentials
Calendar and CRM credentials are sealed with a key that belongs to your workspace alone.
Multi-factor authentication
Authenticator-app codes with recovery codes, on every account.
Bot protection on the public endpoint
A challenge that adapts to traffic, so scripted abuse can't burn your credits.
Outbound requests are guarded
Every URL a tool calls is validated and pinned, so it can't be pointed at an internal address.
Errors do not leak internals
Failures return a request id — never a traceback, a query or a file path.
Your content is not training data
What your assistant reads and your visitors type is used to answer, and for nothing else.
Idempotent writes
A retry after a timeout returns the original result instead of a duplicate.
Read this first
What we're not certified for
Listed as plainly as what we are. If one of these is a requirement, we won't pass your review — better to know now.
- SOC 2 Type IINoNot yetNot certified and no audit is in progress. If your procurement process requires it, we will not pass, and we would rather say so now than in week six.
- HIPAANoNot yetNot certified, and we do not sign BAAs. Do not put protected health information into an assistant here.
- ISO 27001NoNot yetNot certified.
- GDPR — data processing termsPartlyIn partA DPA is available and the subprocessor list is published. We are a processor for the conversation data your visitors generate; you remain the controller.
- Data deletion on requestYesYesWorkspace data can be deleted, and deletion removes it from the primary database and object storage.
- Encryption in transitYesYesTLS everywhere, with HSTS on the public surfaces.
- Encryption at restYesYesAt the storage layer, plus per-workspace envelope encryption for connected-account credentials specifically.
- Penetration test reportNoNot yetNo third-party test has been commissioned yet. When one is, the summary will be published here.
More detail
Written for whoever has to sign it off
Architecture
How isolation, encryption and key management actually work, including their limits.
/security/architecture
Compliance
What we hold, what we do not, and what we would need to do to get there.
/security/compliance
Data residency
Which region your data sits in, and why there is no choice of one today.
/security/data-residency
Incidents
What we commit to telling you, how quickly, and the history so far.
/security/incidents
Reporting a vulnerability
How to report one, and our commitment not to pursue researchers acting in good faith.
/security/disclosure
Vendor questionnaire
The answers to a standard security review, published in advance.
/security/questionnaire
Subprocessors
Every third party that may touch customer data, and what each one does.
/legal/subprocessors
Data Processing Agreement
The contract, including the Standard Contractual Clauses and both annexes.
/legal/dpa
Need an answer this page doesn’t give? Write to security@integrable.cloud.