Introduction
If you publish a Gamma site to your own custom domain, you may need to know what cookies or tracking run on it so you can write accurate privacy and cookie notices for your visitors. Here's the short version: Gamma itself doesn't set any.
What Gamma sets on your site
Gamma doesn't set any cookies on sites published to custom domains.
Gamma doesn't run any non-essential tracking on these sites, so there's nothing that needs to be blocked until a visitor consents.
Because of this, Gamma doesn't show a cookie consent banner on your site by default.
🔷Note: This applies to tracking introduced by Gamma. If you add your own tools, those may set cookies (see below).
Tracking you can add yourself
Gamma sites support Google Tag Manager and Meta Pixel integrations. If you connect either of these, they can set cookies on your visitors' browsers, and you're responsible for configuring them and disclosing them in your own privacy and cookie notices.
Adding a cookie consent banner
Gamma doesn't provide a built-in consent banner. If you need one, you can set it up through Google Tag Manager, which supports most popular consent management tools. Configure your tags to fire only after consent is granted.
💎 Pro Tip: External links to services like Spotify, Calendly, or Google Forms don't place cookies on your Gamma site. Embedded content from third parties can, so check each provider's cookie policy if you embed rather than link.
FAQs & Common Issues
Does Gamma set cookies on my custom-domain site?
No. Gamma doesn't set any cookies on sites published to custom domains.
Do I need a cookie banner on my Gamma site?
Not for anything Gamma does. If you've added Google Tag Manager, Meta Pixel, or embedded third-party content, you may need one depending on your local regulations.
Does Gamma offer a cookie consent banner?
No, but you can add one through Google Tag Manager.
Where can I find Gamma's own cookie policy?
Gamma's privacy policy and cookie policy cover gamma.app itself, not sites you publish.