ComplyWise holds compliance evidence: KYB records, identity documents, screening results, signed contracts. This page explains the controls that protect that data, whether you are a customer today or evaluating us.
Workspace isolation
Every record belongs to exactly one workspace, and that boundary is enforced in the database itself through row-level security, not just in application code. Every query a user makes is filtered at the database layer, so one workspace's data is structurally invisible to another's, even in the event of an application bug.
Access scoping inside a workspace
Roles (Workspace Admin, Editor, Contributor, View Only) control what members can do. Beyond roles, members can be restricted to specific entities: a restricted member never sees out-of-scope companies, their people, their documents, or their files, and this scoping is enforced at the database and file-storage layer, including in search results and notifications.
AI privacy
When you use ComplyWise's AI features, your data is not training material:
- Model requests are routed only through zero-data-retention routes, enforced fail-closed: if a zero-retention route is unavailable, the request is refused rather than sent anywhere else.
- Your documents and conversations are never used to train models.
- Document embeddings (the search index behind grounded answers) are generated under a no-training policy with our embedding provider.
External links that stay under control
Share links, document-collection links, and signing links are how your counterparties reach ComplyWise without an account. Each one is protected the same way:
- The link carries a one-time token; ComplyWise stores only a hash of it, never the token itself.
- A share link can be gated: the reader confirms the address it was sent to, and, when you ask for it, enters a one-time code emailed to that address. Codes are six digits, expire in 10 minutes, work once, allow five attempts, and are stored only as a hash. A verified reader holds a session for 12 hours and then verifies again.
- Re-copying a link rotates it, and so does emailing a share link again; the old link dies either way.
- Every access is rate-limited and logged, with time and network details recorded.
- Link recovery emails go only to the address the sender recorded, never to an address a visitor types, and the recovery flow answers neutrally so it cannot be used to probe who is party to a document.
Document integrity
- Signed documents are pinned by checksums computed server-side over the actual stored bytes.
- E-sign activity (opens, consent, signatures, declines) is written to an append-only evidence trail that application users cannot edit or forge.
- Completed envelopes produce a certificate summarizing the evidence, generated alongside the final signed document.
Encryption and platform hardening
All traffic is encrypted in transit with TLS, with strict transport security enforced. The application ships with a strict content security policy and modern browser security headers.
Reviewed account access
There is no self-serve signup. Account requests are bot-protected and reviewed by a person before any workspace is created, so every account on the platform was deliberately admitted.
Terms and privacy
The platform agreement every account holder is on, and how personal data is handled, are published at /legal/terms and /legal/privacy (linked from the sign-in page and from the footer of every external link page). They cover the platform itself; services you buy from the operator are governed by their own engagement terms.
Questions, or need our security details for a vendor review? Contact support@complywise.io.
Related articles
- Screening overview: how risk screening works
- Upload documents into your KYB record: where your evidence lives