ConsentModeHQ is an independent, technical publication about cookie consent, Google Consent Mode, pre-consent tracking and privacy law as it actually plays out on websites. We are looking for editors and contributors who want to be part of it.
The bar is simple to state: every claim traces back to something you can open — a regulator’s decision, an official spec or vendor doc, the actual repository, a network request you captured. If that is how you already work, we would like to hear from you.
Editors
Editors review drafts before they go live. In practice that means:
- checking each factual claim against its primary source, and cutting or flagging what cannot be traced;
- spotting the difference between a proposal and law, a beta and a stable release, a vendor’s marketing and its documentation;
- tightening structure and language so a developer or a DPO can act on the post;
- keeping older posts honest when the facts move — enforcement files, library versions, browser behaviour.
A background in privacy engineering, analytics implementation, web development or data protection law all fit. Being precise matters more than being senior.
Contributors
We publish technical, practical articles grounded in real implementations. Topics we are especially interested in:
Google Consent Mode and tagging
- Correct versus broken implementations, and how to tell them apart from the network tab
- GA4, Google Tag Manager and server-side tagging with consent
Cookie banners and CMPs
- Implementation and migration guides, including open-source and self-hosted CMPs
- Configuration issues that lead to non-compliance
- UX, dark patterns and what makes consent valid
Tracking and audits
- Pre-consent tracking and how to detect it
- Storage and identifiers that are not cookies
- Auditing a site from a technical privacy perspective
Privacy and regulation
- GDPR, ePrivacy, UK PECR, US state laws and their practical effect on websites
- Enforcement decisions, explained for the people who have to implement them
How we write
- Educational and vendor-neutral. No sales pitches, and no vendor-versus-vendor reviews.
- Primary sources only. Links to the regulator, the spec, the repo or the court document, not to someone’s summary of them.
- Show the mechanism: code, requests, measurements and screenshots are welcome.
- Explain how the technology behaves. We do not give legal advice.
You do not need to have published before. You do need to care whether it is true.
Get in touch
Send a DM to @ConsentModeHQ on X — DMs are open — or email contact@consentmodehq.com.
Tell us briefly who you are, whether you are interested in editing, writing or both, and one topic you would want to cover or one claim you have seen repeated that you think is wrong. For examples of the kind of post we publish, see what a UK audit of 624 gambling sites actually measured or Safari turning consent cookies into session cookies.