Customer Data Governance

Customer data governance that puts you in control

Q: How does Amperity control access to customer data?

Policies define the actions a user can take, and resource groups scope access to Customer 360 databases. Additional policy options can restrict downloads, exports and, for supported policies, visibility of fields marked as PII. Administrators configure these controls to fit each user's responsibilities.

Q: Is Amperity the source of truth for email consent?

No. Amperity can use the consent data you supply to filter audiences, but consent may change between an audience update and message delivery. The sending platform must verify current consent immediately before sending an email.

Q: Can Amperity help process privacy-rights requests?

Yes. Configured workflows can discover records for data subject access requests and process supported deletion requests. Customers remain responsible for interpreting requests, providing them to Amperity and coordinating required changes in other systems. These capabilities support your compliance process; they do not establish compliance on their own.

Q: What activity can teams review?

Amperity records supported user activity, including configuration changes, PII views and destination configuration. Activity logs identify the user, time, action and object, and can be filtered and downloaded. The audit-events API provides programmatic access. AI Assistant conversations have a separate administration view.

Q: Do the same data-handling terms apply to every AI connection?

No. Amperity's AI Assistant and an external AI client connected through MCP have different data flows. The AI Assistant Privacy FAQ describes its provider processing and conversation storage. For MCP, your organization must approve the connected client's data handling and retention under its agreement with that provider.

Make customer data usable with clear controls for access, privacy processing and change. Amperity helps teams build trusted customer context and govern how it's used.

Request a demo Visit the Trust Center

Make governance part of how customer data gets used

Customer data governance defines who can access customer information, how it may be used, and how changes and activity are reviewed. Those controls help teams make customer data useful while respecting the responsibilities that come with it.

Amperity is the Customer Context Platform. Its identity resolution and unified profiles help teams work from a shared understanding of the customer. Policies, privacy workflows and operational controls help govern access and use.

Match access to each team's responsibilities

Let marketers build audiences and analysts explore customer data within the access you assign. Amperity policies define the actions available to each user; resource groups scope access to Customer 360 databases.

Scope access by team or brand

Use custom resource groups to associate users with the databases they need. This supports brand-specific access within a tenant, alongside the actions allowed by each user's policies.

Control PII visibility and data movement

For supported user policies, restrict visibility of fields marked as personally identifiable information (PII). Separate policy options restrict downloads of query and segment results or prevent campaign and orchestration exports.

Connect sign-in to your identity provider

Configure SAML single sign-on and map identity-provider groups to Amperity policies. Amperity also enforces multi-factor authentication for users who sign in with a username and password.

Carry privacy requirements into customer workflows

Build audiences from the consent information you supply and configure workflows to respond to privacy requests. Your team defines the request process, applicable requirements and follow-through across connected systems.

Use consent data when selecting audiences

When configured, the Email Opt Status table lets you filter audiences using consent data by email address, brand, region and email program. Consent can change after an audience is built, so verify it again in the sending platform immediately before email delivery.

Respond to access and deletion requests

Configure privacy-rights workflows to discover records for data subject access requests or process supported deletion requests. Review the resulting compliance tables and use those results to coordinate the required work in source and downstream systems.

Real-time activation

Review changes before they reach production

A change to source data, identity configuration or a customer database can affect the teams using it. Sandboxes give operators a separate environment to test configuration changes and inspect the results before promotion.

Test and validate

Run updated workflows in a sandbox and review validation results. Resolve configuration conflicts and inspect added, changed or removed objects before an authorized user promotes the changes.

Review the identity behind your decisions

Use Stitch summaries, benchmarks and record-level exploration to review how source records are grouped into profiles. Investigate unexpected matches or profile changes as part of your identity review.

Trace recorded activity

Review recorded activity by user, time, action and affected object. Filter and download activity logs, or retrieve audit events through the Amperity API for your security review workflows.

Apply controls to the AI workflow you enable

Keep AI use connected to the controls your team has defined. Enablement, permissions and data handling depend on the specific feature, region and connected systems.

Manage AI Assistant access

Authorized operators can enable or disable AI Assistant features for a tenant, and user-level policy options restrict access. Supported workflows vary by region and configuration. Authorized administrators can review AI Assistant conversation records.

Keep connected AI clients within scope

Amperity MCP applies the connected user's Amperity policies and database resource groups. Your organization chooses the AI client and approves its handling of returned data under your agreement with that provider. MCP session safety modes limit write operations in addition to the user's permissions.

Explore intelligence

Bring security evidence into your evaluation

Governance also depends on how a platform is built and operated. Amperity's security program addresses information risk, operational resilience and protection of customer data. Review the supporting reports and documentation in our Trust Center.

Discuss hosting, data residency and deployment requirements with our team as part of your architecture review. The appropriate configuration depends on your cloud environment, region and required capabilities.

Lakehouse deployment Visit the Trust Center

ISO27001 Certified

International standard for information security management systems. The scope of the ISMS implemented by Amperity includes the following products: DataGrid, AmpID, Amp360, AmpIQ, and Support Services.

Make the next customer-data workflow accountable

Bring us a customer-data workflow you want to improve. Evaluate who needs access, which privacy requirements apply and how changes will be reviewed, so your team can act with clear responsibilities.

Customer data governance that puts you in control

Make governance part of how customer data gets used