GDPR - banner for cookies, Youtube videos, etc
F
Félix Domingo Tirado
Facilities for inserting the cookie privacy policy.
Nik Payne (Gamma design)
Merged in a post:
From Community: Inquiry on Cookie Consent Compliance Timeline
Elizabeth 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 Elizabeth 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?
Elizabeth 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
Nik Payne (Gamma design)
Elizabeth Ngonzi: Thank you!
Nik Payne (Gamma design)
Merged in a post:
Cookie-Zustimmungsbanner wie Cookiebot integrieren oder anbieten
Grit Hallal
In der EU muss jede Seite einen Kecks-Fress-Button, den eigentlich keiner liest, haben, sonst frisst Dich der Abmahnanwalt. Es istwenig hilfreich, dass es diese Funktion nicht gibt, jedoch eine Anbindung der Domain: sinnvoller und rechtlich sauber ist es dann, dieses Anbinden nicht zu ermöglichen, sondern nur ein Integrieren in andere Webseiten oder eben eine rechtssichere Lösung anzubieten.
Ich habe mir jetzt mit einer Karte beholfen: doch das ist keine saubere Lösung.
O
Oliver
This is a must!
O
Oliver
This needs to be addressed.
Nik Payne (Gamma design)
Hey Grit Hallal, danke für die super konkrete Rückmeldung. Total nachvollziehbar, dass ein EU-konformes Cookie-Consent-Banner (Cookiebot etc.) bei einer eigenen Domain Pflicht ist und die aktuelle “Karte als Workaround” sich nicht sauber anfühlt. Ich geb das ans Team weiter.
Damit wir das richtig einordnen: 1) Nutzt du Gamma mit eigener Custom Domain oder über eine gamma.app URL? 2) Was wäre für dich die ideale Lösung: native Consent-Lösung in Gamma, oder die Möglichkeit, ein eigenes Script (zB Cookiebot) im Head einzubinden?
Grit Hallal
Nik Payne (Gamma design) ich nutze Gamma mit eigener Custom Domain. Sogar mehrfach, weil es wirklich leicht geht. zu 2. native Consent-Lösung in Gamma ist einfacher. Habe heute den Nachmittag mit Recherchen verbracht, wo die Cookies eigentlich herkommen, und als ich die hatte, bin ich an Gamma gescheitert.
Grit Hallal
Nik Payne (Gamma design)wie weit ist Eure Umsetzung?
Nik Payne (Gamma design)
Merged in a post:
German legal audit failed on Goolge fonts download, tags, consent banner,..
Fernand Schroell
I maintain my website using the Gamma platform. During a legal audit I discovered several issues that I cannot address through the visual editor but which are essential for compliance with EU/German law and for search engine optimisation:
Google Fonts / external fonts – The generated HTML code loads fonts from https://fonts.googleapis.com, meaning visitor IP addresses are transmitted to Google. Under the GDPR this requires user consent. Please provide an option in the editor to disable remote fonts and instead host fonts locally, or otherwise offer a way to prevent external font loading.
Meta tag noindex, nofollow – The code includes <meta name="robots" content="noindex, nofollow">, which prevents search engines from indexing my pages. I cannot control this in the editor. Please allow users to choose between index and noindex settings.
Consent banner / cookie management – The page currently loads Google Tag Manager and analytics scripts automatically, and there is no built‑in option to display a consent banner that blocks these scripts until the user opts in. A consent management solution or the ability to embed a custom banner would be very helpful to meet GDPR and TDDDG requirements.
Additional meta tags – It would also be useful to edit meta tags (canonical tags, Open Graph tags, robots directives) via the editor to improve SEO and compliance.
I would appreciate hearing whether and when these features will be available, as they are critical for legal compliance and for the professional presentation of my website.
Nik Payne (Gamma design)
Merged in a post:
Cookie Banner
EverConnect null
It would be good if we can add a cookie banner for the website for GDPR compliance and for buttons to be icons as an option.
Nik Payne (Gamma design)
Merged in a post:
Cookie acceptance, Dataprivacy and webpage ownership
A
Andreas andreas@toth-
dear team, it would be nice to get more EU and German Laws covered by having cookie acceptance when opening the site, data privacy pages and webpage of ownership supported.
Alison (Design @ Gamma)
Merged in a post:
GDPR/Web Regulation
Galit Rosenblatt
Webesite or landing pages require GDPR features currently not available in Gamma sites, like cookies consent pop up window, causing users to break the law if a website is published. This is not a nice to have, it's a very basic must have.
Load More
→