Privacy Policy

Understand how VeridataOps handles personal data across public and hosted surfaces.

This public privacy policy describes scope, controller and processor roles, data categories, sharing, retention, security, transfers, and rights routing for public websites, hosted service operations, and customer-facing support paths.

Public host: https://veridataops.com. Use these pages for customer-safe evidence and policy review on the live marketing surface.

Understand how VeridataOps handles personal data across public and hosted surfaces.

Scope

This policy covers public sites, hosted service use, and customer-facing support paths.

  • VeridataOps public websites and product pages.
  • Hosted VeridataOps application environments operated by VeridataOps.
  • Customer communications, account administration, and support interactions.
  • Customer-facing documentation and review packets that explain how data is handled.

Roles

Controller and processor roles depend on the service surface.

  • VeridataOps generally acts as controller for website visitors, sales contacts, billing contacts, and support contacts whose data it collects directly.
  • VeridataOps generally acts as processor or service provider for tenant data processed inside the hosted service on behalf of a customer.
  • Customer-managed and OEM deployments shift more processing control to the operating customer or partner outside VeridataOps-hosted support or release work.

Data Use

VeridataOps uses data only for documented service purposes.

  • Providing and securing the hosted service.
  • Authenticating users and enforcing tenant access controls.
  • Collecting, reviewing, and presenting customer-authorized operational evidence.
  • Providing support, release, billing, security, and service communications.
  • Meeting legal, contractual, security, accounting, or audit obligations.

Next Step

Use the live public surface as the review artifact.

When a customer or reviewer needs product-safe wording, point them at these URLs on veridataops.com and then attach deployment-specific evidence separately.

Talk to an Implementation Reviewer

Next Step

Pair this doc page with proof, fit, and one scoped follow-up.

A documentation page should answer its question and then route the visitor to the proof artifact, coverage page, or reviewer path that finishes the evaluation.

Proof

Inspect the corresponding artifact Use the proof library to connect the written explanation to a real product surface or public-safe sample. Browse Proof Library

Coverage

Validate support and caveats Use the coverage pages to confirm what is modeled already and where scope still matters. Open Coverage Hub

Contact

Route the next technical question Escalate to an implementation reviewer only after this page made the remaining blocker explicit. Talk to an Implementation Reviewer