Credentials
We connect through official OAuth and platform APIs and never ask for your passwords. You can revoke our access from each platform at any time.
Security and responsibility
We make the boundaries, access questions, data paths, and review points explicit so your team can decide whether the engagement fits its own requirements.
Clear boundaries first
MetricMaven can help operate the agreed measurement layer. We do not replace your organization’s security, privacy, identity, or governance responsibilities.
MetricMaven is responsible for
Your organization is responsible for
Before and during the work
The specific controls depend on your architecture and requirements. These are the operating conversations we expect to have, not a certification claim.
Agree who can see and change what. Access is scoped around the systems and work required for the engagement. We document the owners, destinations, and approval points with your team before implementation.
Move only the data the work calls for. Data destinations and handling expectations are part of the engagement scope. We work with your team to define what belongs in marketing systems and what should remain out of them.
Review before a repair becomes relied upon. Tracking, pipeline, and reporting changes have a reason, an expected effect, and a validation path. Findings that affect your business definitions stay visible for your approval.
Close the loop with a documented handover. At the end of an engagement, your team can revoke access, receive the agreed documentation, and confirm the remaining owners and operating procedures.
Data handling
Where measurement data is stored during an engagement and how it is handled.
We connect through official OAuth and platform APIs and never ask for your passwords. You can revoke our access from each platform at any time.
Marketing data is modeled in a managed Google BigQuery warehouse. Qualified portfolio and agency engagements can transfer modeled data into a warehouse your organization owns.
Data is encrypted in transit over TLS. Data in the BigQuery warehouse is encrypted at rest by Google Cloud.
Available on request as part of the engagement paperwork.
We are actively pursuing SOC 2 Type II. We are not certified today, and we do not claim to be. Ask us for our current status and a security overview.
Retention periods, subprocessor lists, and incident-notification terms are set per engagement and confirmed in writing before work begins.
Book a 20-minute call with the person who will answer it.