From Community: Inquiry on Cookie Consent Compliance Timeline
Liz Ngonzi
Hey team! Following up on my previous question regarding native cookie consent banners / GDPR tools for our custom domains (like <http://lizngonzi.ai|lizngonzi.ai>, <http://aiforhumanity.io|aiforhumanity.io> and <http://aiforimpact.io|aiforimpact.io> ). I really need to have full compliance without having to build hacky iframe wrappers or reverse proxies. Do we have an updated timeline or an official ETA on the website feature roadmap for native consent widgets or header script injections?
Nik Payne (Gamma design)
Hey Liz Ngonzi, appreciate you following up and for the super clear context (and the examples). Totally hear you on not wanting to ship hacky iframe/reverse-proxy workarounds just to be compliant. I’ll pass this to the team, but I don’t have an official ETA I can share from the forum side right now.
Quick question so we can make this actionable: is your must-have (a) a native consent banner + preference management, or (b) the ability to inject your own scripts in the header (so you can use something like Cookiebot/OneTrust), or do you need both for your setup?
Liz Ngonzi
Nik Payne (Gamma design) Hey Nik, thanks for the quick response!If I had to prioritize, (b) the ability to inject our own scripts in the header is the immediate must-have.Since we already use tools like Termly to manage our policies and compliance globally, simply being able to paste our container snippet into a <head> field would instantly solve the problem for us and give us full control. Long-term, a native toggle (a) would be an amazing no-code addition for standard users, but script injection gives professional creators the flexibility we need right now. Appreciate you taking this back to the team! - Liz