Confidencial runs in your cloud, on your own infrastructure, or hosted by us. When you host the protection engine, no content reaches Confidencial. In every deployment, encryption keys live in your key management service.
keys · your KMS
content · never leaves
ISO 27001 · SOC 2
Your environment
Encryption keys
Generated and held in your KMS, including AWS KMS, and Azure Key Vault
Protection engine
Signed containers in your cloud or on-prem, in self-hosted mode
Your content
Protected in place, at the field level
keys never cross
Confidencial
Classification summaries
Counts and file names during discovery, not content
Ciphertext, if anything
Computationally inaccessible without your keys
Your encryption keys - never
Not in any deployment mode, not at any time
Encryption keys are generated and held in your key management service in every mode. During discovery, access is a read-only key scoped to the storage targets you select, and we receive classification summaries rather than content.
Maximum control
Signed containers in your own cloud or on-premises. No outbound internet access by default. Deployed with Terraform or Helm.
Balanced
Protection engine in your environment, management plane hosted. You choose which components sit where.
Fastest to stand up
We run the infrastructure. Your keys still live in your key management service and are never transmitted to us.
Tell us which mode you are evaluating and we will walk your team through the architecture for it.
Request a security reviewProtection is applied at the data layer, and the keys that reverse it are held in your key management service. An attacker who compromised Confidencial’s infrastructure would not obtain those keys, because they are never transmitted to us.
Protected content without the corresponding keys is computationally inaccessible. That is a property of where the keys sit, not a promise about our controls.
A breach of the platform is not a breach of your data. When you host the protection engine, there is no content on our infrastructure to breach.
What an attacker leaves with
exfiltrated.dat
a8f3d29c14e7b6205fa14d0983cc27e1
7b21e64fa093d8c25e1170ab34ff92dc
c04e91b7723da8f6e50c19b428d7360a
f13b807ce6a92d45107bf3ea9c2d5481
2e7ca41d90b3f8e6·······
Confidencial integrates with your existing key management service, including AWS KMS and Azure Key Vault. Keys are generated and held there. Access policy is embedded in the protected object itself rather than in a separate system that stops applying when the file moves.
Revocation
Pull access after a file has already left. The object stops opening.
Rotation
Rotate on your schedule, in your KMS, without touching Confidencial.
Identity binding
Access tied to identity, enforced cryptographically rather than by policy engine.
Third-party certified information security management system. Covers risk management, access control, incident response, and supplier security. Certificate available on request.
Independent auditor verification that security controls operated as designed over a sustained period, not at a single point in time. Report available under NDA.
Assessed against PCI DSS v4.0 as a service provider. Attestation of Compliance available on request.
Protected health information can be encrypted at the field level rather than only in transit and at rest. Business associate agreements available for covered entities and business associates.
Independent penetration testing at least annually. Executive summaries available under NDA.
The platform also aligns to GDPR, the NIST AI Risk Management Framework, ISO/IEC 42001, Executive Order 14117, and FIPS 140-3. Alignment is not certification and we do not claim it as one.
Selective encryption protects the sensitive parts of a document and leaves the rest readable. A salary figure, a patient identifier, a drug formulation, a deal value. Everything around it stays usable for search, editing, collaboration, and AI.
This means non-sensitive content is intentionally readable to authorized users and authorized systems. Plaintext exists where your policy allows it, and nowhere else.
Any vendor claiming that no plaintext exists anywhere is either encrypting whole files, which breaks the workflows you are trying to protect, or is describing something other than what their product does.
Your policy defines the boundary. The cryptography enforces it.
Learn more about selective encryption →One document
When you host the protection engine, no. It runs inside your environment, and no content or keys reach our infrastructure. Keys are generated and held in your key management service. In Confidencial-hosted deployments, we operate the key service on your behalf.
An attacker who compromised our infrastructure would leave with ciphertext. The keys that would reverse it live in your environment. When you host the protection engine, there is no customer content on our infrastructure to take.
In your environment, hybrid, or hosted by us. Self-hosted runs as signed containers in your cloud or on-premises, deployed with Terraform or Helm, with no outbound internet access by default.
No. Recovery is layered, and you hold the layer that matters most. You keep a recovery key offline, in your own custody. Confidencial never holds it and cannot use it. Your root key lives in a key management service and is backed up by your cloud provider under their standard durability guarantees. Group keys are captured in database snapshots, so shared access survives a group-level failure. Losing any one of these does not lock you out.
No. Customer data is never used for model training, product improvement, or any purpose outside delivering the service. We use commercial AI tools internally for productivity, testing, and research, never with customer data.
During a data assessment, we collect file and folder names and summary counts of detected sensitive data types. No file content is stored, only volume metrics. The assessment database is deleted within ten business days of the completed scan.
As you store your data, you will always retain access. The customer holds a recovery key offline. An API/CLI tool can be used to remove all protection. For any SaaS service, we will offer a data take-out service, at the expense of the data owner.
Walk through the architecture with our CISO. Pick your deployment model. Get the documentation your reviewers need.
Available on request