Privacy
What the software stores, why it stores it, and what it deliberately does not.
This is not the privacy policy — it is a description of how the system behaves
Audonomics is pre-release and the formal privacy policy has not been published. What follows is an accurate account of what the software does with data today, written so you can check it against the product rather than take it on trust. It creates no obligations and is not legal advice. The binding document will be published, drafted by counsel, before general availability.
Two different kinds of person
Audonomics holds data about two groups, and they are not treated alike. Users are the people who sign in to run a workspace. Audience members are the people a workspace knows about — their customers, not ours.
For audience members, the workspace is the controller and Audonomics is the processor. We do not decide what is collected about them, we do not use their data to build a profile across workspaces, and we do not sell it.
What is stored about a signed-in user
Email address, display name, a password hash — never the password — and, if two-factor is enabled, a TOTP secret and recovery codes. Sessions are stored as a hash of the session token, with the user agent and IP recorded so you can review and revoke them.
Every action that changes state is written to an audit log with who did it and what changed. That log is deliberately append-only: it exists so a workspace can answer “who approved this” about money and contracts.
What is stored about an audience member
Whatever the workspace imports or connects: typically name, email, approximate location, and a history of events — purchases, attendance, engagement, referrals. Value scores and predicted lifetime value are derived from those events and labelled as modelled wherever they appear, because they are estimates rather than facts.
Rollups are rebuilt from the event ledger rather than edited in place, so a correction to the underlying events corrects everything computed from them.
What is not stored
Card numbers and bank details never reach Audonomics. Payment credentials are handled by the payment provider; the platform holds only the provider’s reference, the amount and the status.
There is no cross-workspace analytics product. One workspace’s audience is never used to inform another’s recommendations.
Who inside a workspace can see what
Access is role-based and enforced on the server for every request, not hidden in the interface. Counterparties are isolated by design: a vendor sees its own quotes and contracts and never a competitor’s, and a sponsor sees its own deal and never the workspace’s wider pipeline.
Security describes the enforcement in more detail.
Requests about your data
Access, correction, deletion and portability requests go to privacy@audonomics.com. If you are an audience member of a workspace, we will route your request to that workspace as controller and tell you we have done so.
Deleting a workspace — a control its owner holds in Settings — deletes its audience, events, orders and derived intelligence. Financial records required for accounting are the exception, and the retention period for those will be stated in the published policy.