Docs Hub

Choose the VeridataOps doc path that matches the question you need answered.

The public docs are split by evaluation intent so technical reviewers can find workflow proof, install detail, coverage caveats, and audit evidence without digging through one long reference page.

Prefer direct contact? Email info@veridataops.com. Include the page you reviewed and the blocker; the first reply will route you to the right reviewer or documentation path.

Illustration routing technical reviewers to the install, operate, assurance, and decision pages they need.

Docs Paths

Each page answers one evaluation question.

Start with the page that matches your role, then move to contact only after you know which technical path or proof artifact matters.

Evaluation Workflow

What proof should we expect from a first serious evaluation? For technical evaluators who need to understand the review boundary, proof artifacts, and the exact evidence a first session should leave behind. For: Technical evaluators, implementation leads, and security reviewers. Open page

Product Installation

What has to be in place to stand up the VeridataOps control plane? For teams preparing the main application environment, image strategy, and first control-plane startup. For: Platform engineers and deployment owners. Open page

Collector Deployment

How do collectors enroll and operate inside the customer network? For teams planning outbound collection, enrollment, runtime persistence, and reachability to source systems. For: Implementation owners and source-system operators. Open page

Supported Coverage

Which sources, destinations, and pack behaviors are in scope today? For buyers comparing pack coverage, semantic fit, and what still depends on scope, credentials, or follow-through. For: Solution architects, integration owners, and technical buyers. Open page

Security And Audit

What evidence should exist for controls, releases, and formal reviews? For security, compliance, and operator stakeholders who need the evidence boundary spelled out clearly. For: Security reviewers, audit stakeholders, and release owners. Open page

Evaluation Path

What a serious public evaluation should let a visitor do next.

1. Understand the review boundaryStart with the evaluation workflow page to see what is reviewed before anything is published.
2. Validate deployment fitUse the installation and collector pages to confirm where the control plane runs and how sources are reached.
3. Check coverage and caveatsUse the coverage page to see what the packs support today and where scope still matters.
4. Inspect assurance evidenceUse the security and audit page to prepare the controls and release evidence a real review requires.

Policy Documents

Direct links for privacy, data protection, and regulated-readiness review.

Use these published policy-document pages when a reviewer needs customer-facing privacy, GDPR, data protection, supplier, or audit-evidence material without digging through the longer assurance page first.

Regulated Evidence

Privacy, GDPR, DORA, and supplier review Routes privacy, data protection, GDPR, DORA, supplier, and framework-readiness questions to the live assurance guidance already published on veridataops.com. Open regulated customer evidence

Audit Evidence

Customer-facing report and policy packet Routes reviewers to the live audit-report section covering tenant/data/collector controls, release evidence, hosting evidence, and open-gap handling. Open reports and audit evidence

Policy Set

Privacy, data protection, GDPR, cookies, and subprocessors Start with the policy index when the reviewer needs the full main-domain policy set and then move directly into the exact page they asked for. Open policy set

Privacy Policy

Controller, processor, retention, and rights routing Use the full privacy page when the review needs personal-data scope, handling, retention, sharing, and request-routing detail. Open privacy policy

Data Protection

Access, encryption, provenance, and shared responsibility Use the full data-protection page when the review needs the customer-facing control boundary instead of a short assurance summary. Open data protection policy

GDPR Policy

EEA and UK review detail Use the full GDPR page when the review needs controller and processor roles, lawful bases, transfers, and rights-routing detail. Open GDPR policy

Cookie Notice

Browser storage and optional analytics Use the full cookie page when the review needs the browser-side storage and optional measurement detail on the public and hosted surfaces. Open cookie notice

Subprocessors

Supplier-category and purpose detail Use the full subprocessor page when the review needs the supplier categories, purpose, and typical exposure detail without internal evidence. Open subprocessor notice

Next Step

Push the reviewer from navigation into proof, fit, or implementation review.

The docs hub should move visitors to the proof artifact, coverage discussion, or reviewer path that completes the evaluation.

Proof

Match docs to proof artifacts Use the proof library when the reviewer wants the product artifact behind the written explanation. Browse Proof Library

Coverage

Check source and destination fit Use the coverage hub when the next question is source support, collector reach, or destination modeling. Open Coverage Hub

Contact

Escalate one technical blocker Route the exact implementation question once the reviewer can name the remaining blocker clearly. Talk to an Implementation Reviewer