Skip to main content

​
Overview

Provalytics is designed to work with structured client data in a controlled, scoped, and operationally repeatable way. Because many clients use warehouse connections, recurring file delivery, exports, and MCP access, security and governance matter alongside measurement quality.

​
Scoped access

Where possible, Provalytics uses scoped, purpose-built access rather than broad shared credentials. Examples include:
  • dedicated Snowflake service accounts
  • scoped warehouse roles
  • managed storage destinations
  • client-specific MCP keys
  • client-specific connector and export settings

​
Structured delivery

For custom data workflows, the platform is built around structured repeatability. That means clients typically provide data through:
  • warehouse tables
  • storage destinations
  • recurring files
  • shared sheets
  • managed export routes
This reduces ambiguity and makes ingestion more reliable over time.

​
Connection security

Different connection types use different security controls. Depending on the route, that may include:
  • read-only roles
  • key-pair authentication
  • IP allowlisting
  • managed buckets
  • scoped API keys
Your CSR can help confirm the required controls for your specific integration path.

​
MCP and downstream access

MCP access is designed to be controlled through client-scoped keys that can be created, rotated, and revoked. For teams using exports or warehouse delivery, Provalytics can also support downstream operational workflows without requiring users to rely only on the in-app UI.

​
Why this matters

The goal is not just to get data into the platform. The goal is to make sure the data arrives through a process that is:
  • structured
  • secure
  • repeatable
  • appropriate for the sensitivity and operating model of the client