Privacy policy

Draft, pending legal review

This is a working draft written alongside the product, not legal advice. It describes what Advoro actually does with data today, which is the useful starting point for a solicitor to turn into the final policy. Do not publish it as-is.

Who is responsible for what

Ascendz operates Advoro and is the data controller for account data: the people who sign in to run a workspace, their email addresses and their activity in the product. For the leads, customers and partners a business tracks inside Advoro, that business is the controller and Ascendz is a processor acting on their instructions.

What is stored about a lead

When someone opts in through a referral link, Advoro records their email address, an optional first name and phone number, which partner referred them, which programme it belonged to, the source label, and whether they gave marketing consent along with the exact wording they agreed to. A salted hash of their IP address is stored to spot abuse. The raw IP address is never stored.

What a partner can see

The business owns the lead, the partner earns from it. A partner sees that they generated a lead, its first name, a masked email such as b...@example.com, its source and its status. Full email addresses and contact details stay with the business. A partner can also opt out of the public leaderboard and appear as Anonymous to other partners, while the business always sees who they are.

Payment data

Advoro never sees or stores card details. It connects to a business’s own Stripe account to read the sales it needs to attribute, and Stripe remains responsible for processing. In this version Advoro also never moves money to partners: a partner raises an invoice and the business pays it directly.

Cross-account access

Businesses are isolated from one another by row level security in the database, so one cannot read another’s data. Ascendz staff can open a read-only support session against a workspace to troubleshoot. Every such session is time-boxed, is recorded in the operator audit log, and is also written into the affected business’s own audit log so they can see that someone looked and when.

Retention

Commission entries are kept for as long as the business needs them for their accounts, because the ledger is append-only and is the record both sides rely on. Leads and customers are deleted when the business deletes them or closes their workspace. Requests to access, correct or delete personal data should go to the business running the programme first, since they are the controller for that data.

Contact

clientsupport@ascendz.co