Data processing

For audience data, the workspace is the controller — it decides what is collected and why — and Audonomics is the processor, acting on the workspace’s instructions. For the accounts of people who sign in to Audonomics itself, Audonomics is the controller.

Audience records and their event history, orders and their financial records, and the derived intelligence computed from both — value scores, segments, predicted lifetime value. Processing happens to deliver the product: scoring, segmenting, ranking opportunities, modelling economics, selling and delivering experiences.

Derived figures are labelled as modelled wherever they appear, so a workspace can tell an estimate from an observation when answering its own subjects.

Every query is scoped to a workspace and enforced on the server. Counterparties are isolated further: a vendor sees only its own quotes and contracts, never a competitor’s amount or negotiation stage, and a sponsor sees only its own deal.

Security sets out how that is enforced.

Both controls exist in the product today: Settings exports every record the workspace holds — audience, events, orders, payments, contracts and the audit log — as one file, and the owner can delete the workspace from the same page, which removes its audience, events, orders and derived intelligence by cascade. Deleting a single audience member erases their events, identities and scores; orders keep their financial records with the personal link severed. The retention period for financial records will be stated in the signable agreement.

Report a suspected vulnerability or breach to security@audonomics.com. Notification timelines to controllers will be committed in the signable agreement rather than described loosely here.