AIRYVL

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.

Demo data
CustomerData sourceScopeGrantedStatusAction

Maya Reynolds

cus_2847

TransactionsMerchant, date, amount, categoryAug 18, 2026Active

Maya Reynolds

cus_2847

Receipt uploadsReceipt image, merchant, total, line itemsAug 18, 2026Active

Dev Anand

cus_2851

TransactionsMerchant, date, amount, categoryAug 11, 2026Active

Lena Okafor

cus_2862

Receipt uploadsReceipt image, merchant, total, line itemsAug 4, 2026Active

Priya Nair

cus_2884

Personalized rewardsAffinity scores used for offer selectionJul 22, 2026Active

Tomas Berger

cus_2870

TransactionsMerchant, date, amount, categoryJul 19, 2026Active

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.