ReportsVault holds sensitive legal, vendor, financial, and HR information. Access is role-based, every action is logged, and your organization's Administrators govern how data is used.
Your data is never used to train a model.
Overview
How ReportsVault holds your data
ReportsVault holds sensitive legal, vendor, financial, and HR information. Access is role-based, every action is logged, and your organization's Administrators govern how data is used.
Each claim below names what enforces it and who holds control.
Access and identity
Who can reach what, and how
Access is granted by role, not by person, so leavers and movers are handled by changing a role rather than hunting permissions.
Single sign-on through your identity provider (SSO).
Automated provisioning and deprovisioning (SCIM).
Role-based access control, configured by your Administrators.
Record-level permissions for sensitive matters and cases.
Data handling
Retention and purge, on your terms
Data is encrypted in transit and at rest. Retention periods are configured per record type, and purge runs on that schedule rather than on request.
Retention periods set by your Administrators.
Scheduled purge, with the action written to the audit log.
Export of your data on request and at exit.
AI processing
Contract Intelligence, and the two modes
Contract Intelligence, AI-assisted contract review, checks contracts against your organization's own standards and returns grounded, cited findings for human review.
It runs in two modes. Full Analysis uses the complete document context. Extra Privacy keeps more of the work inside your environment and reduces analysis depth. Your Administrators choose the mode per workflow.
Your data is never used to train any AI model. That is guaranteed by enterprise agreements with our AI providers, and your organization controls its data and how it is used.
AI assists the review. Every final decision rests with your team. Contract Intelligence provides workflow support, not legal advice.
Auditability
Every action, on the record
Workflow history is attached to the record rather than reconstructed from mailboxes. An auditor sees who did what, when, and on what version.
Tamper-evident activity logs.
Approval decisions recorded against the request.
Document versions retained with the record.
Independently audited each year.
Deployment
Cloud or on-premise
Deployment models are aligned to your requirements rather than to ours. The control model is the same in both.
Cloud hosting in an enterprise-grade environment.
On-premise deployment where required.
Environment separation between production and testing.
