Privacy Checkup
30-second document privacy checkup.
Six yes-or-no questions to see whether your document workflow may need governed collection, audit trails, and retention controls.
General operational guidance. Not legal, regulatory, compliance, or data protection advice.
30-second check
1 / 8
Signals
General operational guidance only. Not legal, regulatory, compliance, or data protection advice.
What the check looks for
Governance signals that ordinary collection channels miss.
The result is based on operational indicators: sensitivity, collection channel, auditability, retention, external submitters, and review expectations.
Document custody
Document custody is the accountable handling of a sensitive record from request through receipt, access, review, retention, and lifecycle action.
Governed document collection
Governed document collection means sensitive files enter through a controlled workflow rather than through ad hoc inboxes, chat threads, or unstructured folders.
Audit trail
An audit trail is the record of who requested, submitted, accessed, reviewed, changed, retained, or deleted a document during its lifecycle.
Retention enforcement
Retention enforcement connects document lifecycle actions to policy instead of relying on staff to manually clean up attachments, downloads, and shared folders.
FAQ
Common questions about the privacy checkup.
Is this a GDPR compliance assessment?
No. The check provides general operational guidance about document collection risk signals. It is not legal, regulatory, compliance, or data protection advice.
Can CVOR make my organization GDPR compliant?
No software can make an organization compliant by itself. CVOR is designed to support governed collection, access control, auditability, and retention workflows, while the organization remains responsible for its legal basis, policies, and obligations.
When is email not enough for document collection?
Email is usually not enough when sensitive records need controlled requests, scoped access, document-level audit trails, retention enforcement, and a defensible lifecycle record.
What evidence should a governed document workflow produce?
A governed workflow should help show what was requested, who submitted it, who accessed or reviewed it, what changed, and how retention or deletion expectations were handled.
What should we do after completing the check?
If the result shows a strong or possible fit, review the workflow with CVOR so document types, submitters, access boundaries, audit expectations, and retention requirements can be assessed before onboarding.