Enterprise compliance, built into the architecture.
Xail's zero-knowledge encryption and compliance module meet the requirements of regulated industries. Your organization holds the keys. We never see plaintext.
Xail's architecture provides the technical controls that compliance frameworks require. Not bolted on after the fact.
HIPAA Ready
Substantial compliance with the Security Rule. Encryption, access controls, audit logging, and integrity verification built in.
SOC 2 Aligned
8 of 12 Trust Services Criteria met. Partial on 3 with clear roadmap. Cryptographic integrity, audit trails, and change management.
Zero-Knowledge
No plaintext on any server. Messages split client-side via XorIDA threshold sharing. Reconstruction happens only on the recipient's device.
Published Algorithm
XorIDA provides information-theoretic threshold sharing over GF(2). Known-answer test vectors. 100% test coverage. Patent-protected.
Enterprise features
Every feature compliance officers ask for.
Xail's enterprise module gives organizations the visibility and control they need without compromising zero-knowledge architecture.
eDiscovery + search
Audit + compliance
eDiscovery
Compliance officers decrypt copies under legal process. Search across all compliance copies with full-text and metadata queries. Export with chain-of-custody documentation. Legal hold prevents deletion.
search + export + legal hold
Data Loss Prevention
Pre-split scanning blocks sensitive patterns before they leave the client. SSN, credit card numbers, and custom regex rules. Integrates with Proofpoint and Mimecast for enterprise DLP policies.
pre-split scanning
Audit Logging
Append-only logs for every action. Who accessed what, when, and from where. Tamper-evident. No PHI in logs. Exportable for external SIEM integration and regulatory review.
append-only + tamper-evident
SSO Integration
SAML and OIDC enterprise authentication. Centralized identity management. Single sign-on with your existing IdP. Assertion validation with 5-minute max age for replay protection.
saml + oidc
Delegation Management
Executive assistant access with explicit, granular permissions: read, reconstruct, export. Time-limited with automatic expiry. Revocable at any time. Self-delegation blocked for security.
time-limited + revocable
Retention Policies
Configurable retention windows with minimum and maximum day limits. Legal hold prevents premature deletion of compliance copies. Auto-expiry removes data after the retention period. All policy changes audit-logged.
legal hold + auto-expiry
R
Ask Ren
Here to help
Have a question about Xail for enterprise? I can help.
Ask Ren to set up a call with a live person · contact@xail.io
How compliance works
Zero-knowledge encryption with organizational oversight.
The compliance module generates an encrypted copy for the organization without breaking the zero-knowledge guarantee for the sender.
User composes
Plaintext on device
DLP scan
Block sensitive patterns
XorIDA split
Threshold sharing
Shares sent
Via email providers
Compliance copy
Encrypted to org key
Organization holds the keys. Compliance copies are encrypted with the organization's public key (RSA-4096-OAEP + AES-256-GCM hybrid encryption). Only the compliance officer with the private key can decrypt. Xail never sees plaintext.
Instant delivery
Sub-second delivery. Audit trail intact.
P2P acceleration doesn’t weaken the compliance layer. When both sender and recipient are online,
Xail delivers in under a second — without bypassing the compliance copy, the audit log, or the
delivery proof. Speed and oversight are not a tradeoff.
speed
Sub-second delivery
P2P acceleration when both parties are online. Email shares arrive seconds later as the
cryptographic backup and permanent organizational record.
compliance
Audit trail unchanged
The compliance copy and audit log are generated before shares leave the device.
P2P transport doesn’t affect organizational oversight — the log entry is identical
whether delivery was instant or delayed.
evidence
Proven reconstruction
The delivery acknowledgment is only sent after successful XorIDA reconstruction on the
recipient’s device — not after delivery to a server. Exportable as legal evidence.
Stronger than a read receipt.
Why this matters for legal hold:
A delivery acknowledgment that proves the recipient reconstructed the message is stronger evidence
than a server delivery receipt that proves shares reached a mailbox. The distinction matters in
discovery when recipient denial is at issue.
Deployment options
Your infrastructure, your rules.
Choose the deployment model that matches your organization's security requirements and operational capabilities.
Self-Hosted
Corporate Xail Server on your infrastructure. You control the hardware, the network, and the keys. Full isolation. Meets the strictest data residency requirements.
Managed Enterprise
Xail hosts the compliance server. You hold the encryption keys. We see nothing. Reduced operational burden with the same zero-knowledge guarantee.
Hybrid
Mix of self-hosted and managed for different business units. High-security divisions self-host. Standard teams use managed. One organization, flexible deployment.
Regulatory readiness
Controls mapped to the frameworks you're audited against.
Xail's architecture provides technical controls that map directly to regulatory requirements. Here's where we stand.
Healthcare + HIPAA
Legal + eDiscovery
HIPAA
Security Rule
Substantial Compliance — technical safeguards built into the architecture
Access Control — RBAC with admin, compliance officer, user roles. OAuth 2.0 + SSO. Delegation with expiry.
Audit Controls — Append-only logs for all PHI access, creation, modification, deletion. No sensitive data in logs.
Encryption — AES-256-GCM at rest. XorIDA threshold sharing in transit. No plaintext on servers.
Integrity — HMAC-SHA256 verification on every share. Share index + UUID validated before reconstruction.
Transmission Security — Messages split across providers. No single channel carries the full message.
Contingency Plan — Reconnection with exponential backoff exists. Formal DR plan on roadmap.
SOC 2
Trust Services Criteria
8 of 12 criteria met — partial on 3, clear roadmap for remainder
Change Management (CC8) — Feature branches, signed commits, automated checks before merge.
System Operations (CC7) — Automated testing and retry logic in place. Incident response plan on roadmap.
Trust boundary
Enterprise compliance is transparent, never hidden.
When a consumer Xail user messages an enterprise recipient, they know. Trust is structural, not assumed.
Consumer user
Personal Xail account
notification shown
Enterprise recipient
Corporate Xail server
How it works
Visible notification
When composing to an enterprise Xail recipient, the sender sees a clear notification: "This recipient is on a corporate Xail server. Their organization may retain copies per their compliance policies."
Explicit acknowledgment
The user must acknowledge the notification before the message sends. No silent retention. No surprises.
Structural trust
Enterprise compliance works because the boundary is visible. Organizations get oversight. Individuals get informed consent. The architecture enforces both.
Get started
Talk to our enterprise team.
Custom deployment. Compliance review. Pilot program. Whatever you need to evaluate Xail for your organization.
