Skip to main content

Data Privacy

Volv Analytics is designed to help your team work with customer and revenue data without losing control of who can access it or how connected systems are used. Our approach is customer-facing and practical: keep data scoped to the right workspace, limit access by role, and let customers decide which external systems are connected.

Privacy by Workspace Scope​

Volv uses organization-scoped, tenant-aware data boundaries so analytics configuration, synced records, and processing context stay associated with the correct customer workspace. In practice, that means the product is built around logical separation between customer environments rather than treating all customer data as a shared pool.

We describe this as logical isolation and workspace scoping. That is intentional, bounded language: it reflects application-level separation and access enforcement without implying dedicated customer infrastructure.

Access Is Scoped and Role-Based​

Access to workspace data is governed by authenticated sessions, tenant-aware request checks, and role-based permissions. Sensitive settings areas such as integrations, user management, user assignments, and role management are restricted to users with elevated workspace permissions.

This helps keep day-to-day visibility aligned to the role a person has inside your organization, while limiting higher-impact administrative actions to the people you designate to manage the workspace.

You Control Connected Systems​

Volv only connects to the external systems you choose to authorize. Customers manage those connections through workspace settings, including OAuth-based provider connections and API key-based integrations.

That means your team controls:

  • which systems are connected
  • who can manage those connections
  • when a connection should be updated or disconnected

We use connected-system data to power the analytics, reporting, and workflow features you have enabled in your workspace.

Practical Privacy Boundaries​

For a platform like Volv, privacy is closely tied to access boundaries:

  • Workspace/org scoping keeps customer context associated with the right organization
  • Role-based access limits sensitive actions to authorized users
  • Authenticated session controls help block access when session requirements are not met
  • Security-relevant logging and trace context support review and investigation of important access activity

Our goal is to provide strong operational boundaries and clear customer control without overstating what the product does. When we talk about privacy on this page, we mean scoped access, logical separation, and customer-managed integrations grounded in how the product is built.