Consent
No consent, no delivery.
A tamper-proof consent engine runs alongside delivery. Opt-in terms are presented inside the publisher's own asset, choices are stamped and logged, and anything without consent is suppressed before it can be matched or served.
Consent coverage by publisheraudit logged
| Publisher | Opted in | Suppressed | Opt-in rate | Last audit |
|---|---|---|---|---|
| Bank Partner | 3.44M | 760K | 82% | 18 Aug 2026 |
| Telco Partner | 5.71M | 2.69M | 68% | 17 Aug 2026 |
| Airline Partner | 1.64M | 160K | 91% | 19 Aug 2026 |
| Retail Partner | 1.92M | 680K | 74% | 16 Aug 2026 |
If consent is present
The delivery microservice resolves matching local cluster definitions and returns your personalised offer.
Behavioural matching, reward attribution and conversion logging all proceed normally.
If consent is absent
The SDK suppresses your offer and renders a generic utility block or an opt-in prompt for ecosystem partner savings.
If the customer declines, the workflow halts. They are never counted in your reach.
What is recorded on every choice
—Hashed customer identifier (never PII)
—Publisher scope — consent is per publisher, never portable
—Cryptographic timestamp and consent text version
—Channel of capture: app, web, SMS or WhatsApp
—Withdrawal events with effective-from time
—Immutable audit trail available to the publisher's compliance desk