Trust
Data & consent
Every signal in the platform is tied to an explicit, scoped consent record. Revoking a source stops future processing for that customer.
| Customer | Data source | Scope | Granted | Status | Action |
|---|---|---|---|---|---|
Maya Reynolds cus_2847 | Transactions | Merchant, date, amount, category | Aug 18, 2026 | Active | |
Maya Reynolds cus_2847 | Receipt uploads | Receipt image, merchant, total, line items | Aug 18, 2026 | Active | |
Dev Anand cus_2851 | Transactions | Merchant, date, amount, category | Aug 11, 2026 | Active | |
Lena Okafor cus_2862 | Receipt uploads | Receipt image, merchant, total, line items | Aug 4, 2026 | Active | |
Priya Nair cus_2884 | Personalized rewards | Affinity scores used for offer selection | Jul 22, 2026 | Active | |
Tomas Berger cus_2870 | Transactions | Merchant, date, amount, category | Jul 19, 2026 | Active |
How permissioning works
- · Consent is captured per source in the embedded module before any data is collected.
- · Scope is recorded with the grant and shown back to the customer.
- · Revocation disables future processing for that source and removes the customer from audience refreshes.
- · Encrypted transport and storage where provided by the platform. No compliance certifications are claimed.