Consent and compliance
Every resolution we make is gated on a recorded consent. Here is how that works and how you can check it.
What the visitor sees
The same thing you saw when you landed on this page.
| Step | What happens |
|---|---|
| Banner shown | A consent banner names the company collecting the data and links to the policy before anything is collected. |
| Global Privacy Control | A GPC signal from the browser is treated as a decline. No banner interaction is needed. |
| Decline | Nothing fires. No resolution is attempted. |
| Accept | The consent is recorded against a verifiable policy, then the resolution runs. |
| Opt out later | A standing opt-out is available and applies across our systems. |
This is the banner
An exact copy of what runs on this site. The one at the bottom of your screen is the live version.
The controller name is the business running the site, not Allsource. The policy link goes to that site's own consent policy. Nothing is collected until Accept is clicked, and a Global Privacy Control signal counts as Decline without the visitor touching the banner.
The policy is published, not described
You do not have to take our word for what a visitor agreed to.
Each pixel we provision gets its own consent policy at a public URL. The policy names the data controller, the contact methods the visitor authorised, and the effective date. It is machine readable, so a buyer, a partner or a regulator can fetch it directly.
The policy covering this website is published here:
View this site's consent policy
Every customer domain gets its own policy at its own URL, scoped to that domain. A partner's client accounts each get their own as well.
What the visitor authorises
Four contact methods, named separately.
| Method | Covered by the policy |
|---|---|
| Yes, named explicitly | |
| Telephone | Yes, named explicitly |
| SMS | Yes, named explicitly |
| Automated and AI agent outreach | Yes, named explicitly |
Automated and AI agent outreach is called out on its own rather than folded into a general marketing clause, because it is the method most likely to be disputed later.
What your legal and procurement teams usually ask
| Question | Answer |
|---|---|
| Is consent recorded per visitor? | Yes, against the policy version in force at that moment. |
| Do you honour Global Privacy Control? | Yes, as a decline. |
| Who is named as the controller? | The legal entity operating the site, not Allsource, on customer domains. |
| Is there an opt-out? | Yes, a global opt-out linked from every page of this site. |
| Where is this written down? | Our privacy policy section 1.2.5 and terms section 6.6, plus the per-pixel policy URL above. |
Compliance obligations sit with the business running the site. Nothing here is legal advice, and your counsel should review any tracking deployment.
Send this page to your legal team
If they have questions we have not answered, we will get on a call with them.