Access
Access set per party
Bidders, advisers, opposing counsel and internal reviewers can be admitted to the same room and given different views of it. Access is set per participant and changes as the transaction moves.
CVOR for Enterprise
Request, track and govern
sensitive documents in one place.
Every request is a named item with its own status, so your team can see what is still outstanding without reading a thread — and explain who accessed a passport or payroll file long after the work closed.
Between the person sending and the team receiving.
CVOR separates the personal side of a document exchange from the enterprise side. Submitters interact with a controlled portal designed for clarity and trust. Enterprise teams operate inside a tenant-scoped environment where access, review activity, retention, and audit evidence are governed by the platform — not by inbox conventions.
01
Invite
A scoped invitation is issued for a specific workflow. Access is explicit before any documents are requested.
02
Request
The platform issues a structured document request — specific document types, clear requirements, governed intake.
03
Upload
The submitter uploads through the governed portal. Files are encrypted at the application layer on receipt.
04
Review
The enterprise team reviews within the platform. Every access event is recorded in the immutable audit trail.
05
Govern
Retention rules, access controls, and lifecycle governance are enforced automatically from point of receipt.
CVOR Data Room
When the exchange has more than two sides.
Some workflows are not one requester and one submitter. A transaction brings in bidders, opposing counsel, advisers and internal reviewers, each of whom should reach a different part of the same file. CVOR Data Room applies the same custody model to that shape: a room scoped to the transaction, where documents are requested from participants and released to them under one set of controls.
Room administrators decide who is admitted and what each party can reach. A legal firm acting for one side does not see what another side submitted, and an invited bidder sees only the material released to them.
Direction
Documents move both ways
A room collects evidence through named requests and releases material back to participants. Both halves carry the same access boundary and produce the same record of who did what.
Attribution
Every release stays attributable
Material released from a room can carry recipient watermarking, so a document that travels beyond its intended reader remains traceable to the participant it was issued to.
Lifecycle
The room closes, the record does not
Transactions end. Access can be withdrawn, material retained under policy, and the account of who saw what kept after the room itself is no longer active.
The Data Room uses the same request, access and retention model as the rest of CVOR, with the boundary drawn around a transaction and every party in it.
Several layers of control, each with its own record.
Each layer governs a different dimension of risk. Together they form a system you can walk an auditor through.
Invite-only
Access that starts with an invitation.
Every workflow begins with a scoped invitation to a named person. There is no open registration link and no shared upload URL. Before a single document is requested, access is explicitly granted to the right person for the right workflow. Per-tenant authorization keeps every organization's records entirely separate. No document from one tenant is ever visible to another.
- Invite-only onboarding
- Per-tenant isolation
- Role-scoped access
- No open registration
AES-256-GCM
Encrypted before it reaches storage.
Sensitive personal information is encrypted at the application layer using AES-256-GCM before it reaches object storage. Documents, signed agreements, and personal data are never stored in plaintext. The platform acts as a governed control layer between the submitter and the storage system — not a pass-through.
- Application-layer encryption
- Encrypted object storage
- No plaintext personal data
- Encrypted signed agreements
Immutable logs
Every action recorded. Nothing disappears.
Every upload, document view, status change, forwarding event, and lifecycle action is captured in an immutable, append-only audit log. Failed asynchronous events are isolated in a dead-letter system for controlled recovery — they do not silently disappear from the workflow record. When an auditor asks what happened, the answer is already there.
- Append-only audit capture
- Dead-letter recovery
- View and access logging
- Full lifecycle trail
Automated
Retention enforced by the system on a schedule.
Document retention policies are enforced automatically through scheduled retention sweeps, so no one has to remember to delete records. Session expiry controls reduce standing access. Lifecycle decisions are governed by policy, not inbox management.
- Scheduled retention sweeps
- Policy-driven lifecycle
- Session expiry controls
- No manual deletion required
Mandatory MFA
MFA is not optional.
Every platform access point requires multi-factor authentication. Password hashing uses modern adaptive algorithms. Rate limiting on sensitive endpoints reduces exposure from automated attack attempts. Security headers and browser hardening are applied across the application.
- Mandatory MFA on all access
- Adaptive password hashing
- Rate-limited sensitive endpoints
- Security headers applied
Designed to support audit conversations.
CVOR's governance model maps technical controls to the questions procurement, compliance, and legal teams ask during review.
ISO 27001
Controls aligned to ISO 27001 across access, cryptography, logging, retention, monitoring, and incident response.
GDPR
Architecture follows GDPR Article 5 principles: purpose limitation, data minimisation, storage limitation, integrity, and accountability.
Audit-Ready
A traceability matrix connects controls to implementation evidence — designed to support procurement review conversations.
The platform includes an ISO 27001-aligned governance pack with a traceability matrix that connects controls to implementation evidence across access control, cryptography, logging, retention, monitoring, and incident response. This language describes architecture and governance intent — it does not claim a certification.
Review the full security posture →What do you need to know first?
CVOR is usually assessed alongside existing channels, internal repositories, generic portals, and workflow-specific operating requirements.
Problem context Why email and WhatsApp fail document workflows
Use this when the team needs to align on why ordinary channels cannot provide document-level governance.
Category fit Compare CVOR with file sharing and portalsUse this when buyers are evaluating Dropbox, Google Drive, shared drives, email attachments, or generic client portals.
Software evaluation What to look for in a secure document collection portalUse this when the team is comparing intake portals, upload links, and governed collection requirements.
Two sides of the same exchange.
CVOR serves both sides of the document exchange — the enterprise governing what it receives, and the individual controlling what they send.
Enterprise
How organizations use CVOR
- 01 Issue a scoped request
Name the document types, workflow purpose, and submitter requirements through the governed platform.
- 02 Receive through the portal
Accept documents through the governed intake flow — no email attachments, no consumer messaging channels.
- 03 Review with full audit trail
Every review action is recorded. Access is scoped. The audit trail is immutable from point of submission.
- 04 Govern the lifecycle
Retention, access controls, and lifecycle rules apply automatically once documents are in custody.
Individual
How individuals experience CVOR
- 01 Receive a clear invitation
A specific invitation for a specific workflow — not an ambiguous request to email sensitive files.
- 02 Submit through a governed portal
Documents are uploaded with clear context around what is required and why it is being collected.
- 03 Track what was sent
A clear record of what documents were submitted, to which organization, and when.
- 04 Receive confirmation
Receipt is confirmed — no uncertainty about whether a sensitive document arrived safely.
Assess the workflow before onboarding.
CVOR onboarding is sales-led so governance, document types, and operational constraints are understood before rollout.