Compliance
Compliant by construction, not by policy.
Quantiv was designed around GDPR and HIPAA from the first line of its architecture. The controls are part of how data moves through the platform, so they hold whether or not anyone remembers to apply them.
Egress filter · purchase
→ Meta CAPI
- order_idforwarded
- order_valueforwarded
- emailPIIhashed
- gclidforwarded
- condition_codePHIblocked
A property classified PHI is not forwardable. Not by policy, not by a reviewer remembering - the filter has no path that lets it leave.
Illustrative data
Foundations
The controls, and where they live.
A dedicated database per brand
Each brand runs in its own workspace with its own database. Isolation, residency, and deletion are properties of the deployment, not filters on a shared table.
Classification on every property
Every property in the taxonomy is classified as none, PII, or PHI. The classification travels with the data.
Classification-gated egress
Outbound payloads are filtered by classification. Only allowlisted identifiers leave, hashed. PHI is never eligible.
Consent signals with every event
Consent captured by your consent platform is carried in the context envelope of each event and recorded with it.
Person-level deletion
Deleting a person removes their events and identities from the event store in a single operation, scoped by environment.
Retention you control
Test and stage keep short fixed windows. Production retention is set by your organisation, and enforced automatically.
Access audit logging
Access to person-level data is logged, alongside every configuration change and every agent action.
Encryption
Data is encrypted in transit and at rest. Ad network credentials are held in an encrypted vault.
The forwarding problem
Conversion forwarding and health data do not mix.
Meta and Google prohibit health and other sensitive data in conversion uploads, and regulators have acted against brands that sent it. A platform that forwards whatever it receives turns a measurement tool into a liability.
In Quantiv, what can leave is decided by the classification in your taxonomy, enforced on every payload. Health-adjacent brands get the benefit of server-side conversions without the exposure.
- Forwarding constrained by classification, not by review
- PHI-classified properties have no outbound path
- Every delivery recorded in the ledger
Egress filter · purchase
→ Meta CAPI
- order_idforwarded
- order_valueforwarded
- emailPIIhashed
- gclidforwarded
- condition_codePHIblocked
A property classified PHI is not forwardable. Not by policy, not by a reviewer remembering - the filter has no path that lets it leave.
Illustrative data
Governance
Sensitivity is decided by people, and recorded.
The instrumentation agent can flag a property that looks sensitive, but only a person can classify it. Every classification change is versioned and written to the audit log.
Event definition
v4 · Active
purchase
Norvelle Web
| Property | Type | Required | Class |
|---|---|---|---|
| order_id | string | yes | none |
| order_value | number | yes | none |
| currency | string | yes | none |
| string | no | PII | |
| condition_code | string | no | PHI |
Events that do not match an Active definition are rejected in prod and flagged in test and stage.
Illustrative data
For your review
What we provide during evaluation.
- 01
Security brief
Architecture, data flows, encryption, and access controls, in writing.
- 02
Data processing agreement
Our standard DPA for review by your legal team.
- 03
Data flow walkthrough
A session with your security or privacy lead on exactly what leaves your workspace, and how.
Questions
Common questions.
Where is our data stored?
In a dedicated database for your brand. Hosting region is agreed during onboarding.
Can you sign a BAA?
Talk to us about your requirements. We will confirm what applies to your deployment before any regulated data is sent.
How do we handle a deletion request?
Deleting a person is a single operation that removes their events and identities from the event store, and is recorded in the audit log.
Request the security brief.
Tell us about your data and your obligations, and we will send the security brief and DPA ahead of a walkthrough with your team.