Xaere
Xaere Codes stores the organisation, project, code lifecycle, access credentials and operational audit data needed to issue and resolve codes. XR Audience is a separate service: it accepts only verified, minimised interaction events when an integrator has established a lawful consent flow. The technical data-boundary notice lists each current input, exclusion and deletion path.
The Flutter receiver SDK does not create a persistent device identifier and contains no publisher or Audience secret. Audience reporting is optional and starts only after host consent. Advertising and personalization are separate host choices and have no SDK data flow. A random in-memory measurement token rotates every 30 minutes by default, is never stored on disk and disappears when the receiver is disposed.
Audience retention is configured per integration. An organisation owner can permanently close a tenant from the Console after MFA and explicit confirmation. This removes its Core workspace data and transactionally purges its verified events, replay state, integration secrets and legacy aggregates from the separate Audience database. Provider accounting or support records that must be retained externally remain governed by that provider and applicable law.
Access, correction or deletion requests can be sent through the contact page. This page is a product notice; before commercial launch, Xaere will publish the controller identity, processing locations and the final legal notice for each supported market.