Consent Mode HQ publishes independent, implementation-focused analysis of consent management, cookie compliance and web tracking. This page sets out how that work is produced, so you can judge what you read here.
Where our facts come from
We work from primary sources: the text of a regulation, a supervisory authority’s own publication, a court’s own document, a vendor’s own documentation, or the source code of the library being discussed. Where a claim comes from somewhere weaker — a case tracker, a trade publication, a secondary summary — we say so in the article rather than presenting it with the same confidence.
This matters more than usual in this field. Pages generated at scale in the privacy niche routinely invent regulations that do not exist; we have caught fabricated guidance being cited as real. If we cannot trace a claim to a source you could check yourself, we cut it or we mark it as unconfirmed.
How we handle things that are still moving
Much of what we cover is unfinished: bills in trilogue, enforcement actions mid-flight, frameworks between versions. A proposal is not law, a council position is not a parliament position, and an announcement is not an outcome. We name the stage a file has reached and date anything that changes, so a reader arriving in six months can tell what has aged.
Corrections
When we get something wrong we fix it in place and say what changed, with the date, on the article itself. We do not quietly edit and move on. If you find an error, write to us at contact@consentmodehq.com with a source — corrections are the email we most want to receive.
Independence and money
Some outbound links to vendors are affiliate links, marked as sponsored where they appear. They never affect an assessment: no vendor has ever been moved up, softened, or left out because of a commercial relationship, and we do not accept payment for a review or a placement in a comparison. The site also carries advertising, handled separately from editorial. Our privacy policy covers what that means for your data.
We write about tools we have used or read the source of. Where we have not tested something ourselves, the article says so.
What we do not do
We do not give legal advice, and nothing here is legal advice. We cannot tell you whether your specific configuration is compliant in your jurisdiction — that is a question for a lawyer who can see your implementation and your contracts. What we can do is explain how the technology behaves, where implementations usually break, and what regulators have actually said and done.
Who writes this
Articles are published under the Consent Mode HQ editorial byline. Contributions from practitioners with hands-on consent, analytics or compliance experience are welcome — see about for what we look for and how to get in touch.