# Gatelamp

> Gatelamp scans all your sites, tells you which ones need a cookie banner, and gives those an honest one in their own style, with one dashboard for every site. Status: in development, waitlist only. Features, plans and prices can change; nothing on the site is an offer or guarantee. Gatelamp helps you follow the published rules on cookies and consent; it isn’t legal advice.

Key facts:
- Planned pricing per workspace, never per pageview: Free (one site, honest banner and cookie page, a scan every month, proof of consent, a “consent by gatelamp” label), Maker (monthly, for a handful of sites, every feature) and Studio (monthly, for portfolios and agencies: many sites, scans after every deploy, team members with roles; client access per site planned). Exact prices follow before Gatelamp opens; waitlist members get the early price. Details: https://gatelamp.com/pricing
- The banner: accept and reject side by side with the same weight, nothing ticked in advance, clear button text, a fixed “Cookie settings” button, choices kept six months by default. Built on the Dutch Data Protection Authority’s published rules.
- The scanner: a real browser visits each site three times (before a choice, after “Reject all”, after “Accept all”) and lists cookies, storage and requests to other domains, with the script that caused each.
- Privacy: consent records stored in the EU, no IP addresses or user agents kept, one cookie on your domain with the visitor’s choice, no tracking of its own.
- Install: a script tag served from your own domain (a web component of around 12 kB in Shadow DOM), an npm package and an Astro component at launch. WordPress, Shopify, Webflow, Framer and Google Tag Manager are planned. Google Consent Mode v2 at launch; IAB TCF not at launch.
- Made by Frank Spin, an independent product designer and developer in the Netherlands (KvK 01129853), building software since 2007: https://gatelamp.com/about
- Waitlist: https://gatelamp.com/join · Contact: https://gatelamp.com/contact (hello@gatelamp.com)

## Features at launch
- [Honest banner](https://gatelamp.com/features/honest-banner): A cookie banner with accept and reject side by side, nothing ticked in advance and clear button text. The editor won’t publish one that breaks the rules.
- [Your site’s style](https://gatelamp.com/features/your-brand): Give each site a cookie banner that looks like the site built it: its own colours, font, corners and shadow, as a bar, a corner card or a dialog.
- [Script blocking](https://gatelamp.com/features/script-blocking): Hold back Google Analytics, Google Ads, the Meta pixel and other tags until a visitor says yes: one attribute per script, Consent Mode v2 and a small API.
- [Click to load](https://gatelamp.com/features/click-to-load): Show YouTube, Vimeo and Google Maps behind a placeholder in your style. Nothing loads until a visitor clicks, and YouTube comes from youtube-nocookie.com.
- [Every language](https://gatelamp.com/features/languages): Run one cookie banner in every language your site speaks: banner, settings and declaration per language, picked from the page, with starter text to review.
- [Accessible](https://gatelamp.com/features/accessible): A cookie banner people can use with a keyboard or a screen reader, with focus kept in the dialog and contrast checked against WCAG AA before you publish.
- [Site scanner](https://gatelamp.com/features/scanner): A real browser visits your site three times: before a choice, after reject and after accept, and lists every cookie, storage item and request it finds.
- [Alerts](https://gatelamp.com/features/alerts): Get an email when a scan finds a new cookie or tool, something that runs before consent, or a site that suddenly needs a banner. Quiet when all is well.
- [No-banner advice](https://gatelamp.com/features/advice): Gatelamp shows which of your sites can do without a cookie banner and what to change: self-host fonts, load videos on click, count visits without cookies.
- [All your sites](https://gatelamp.com/features/all-sites): Every site in one dashboard: a status lamp per site, a switcher at the top and one to-do list across all of them. Built for makers, studios and agencies.
- [Describe once](https://gatelamp.com/features/vendor-library): Describe each tool and cookie once, with its purpose, provider, duration and where data goes, and every site that uses it points to the same description.
- [Shared presets](https://gatelamp.com/features/shared-presets): Share banner text, categories and settings across your sites as a preset. Change it once, see which sites it touches and publish them all in one go.
- [Cookie declaration](https://gatelamp.com/features/declaration): A cookie page built from what the scanner finds, per language, as plain HTML on your own site. Add a tool and every declaration that uses it updates too.
- [On your domain](https://gatelamp.com/features/first-party): Gatelamp’s script and every call run from your own domain: a web component of around 12 kB in Shadow DOM, so a strict Content Security Policy can stay.
- [Proof of consent](https://gatelamp.com/features/consent-records): Keep a record of every cookie choice: a random consent ID, the choice per category, when it was made and which banner version the visitor saw. No IPs.
- [Consent stats](https://gatelamp.com/features/consent-stats): See how visitors answer your cookie banner: accept, reject or their own mix, per site, per category and per banner version. Counted from the records.
- [Privacy by default](https://gatelamp.com/features/privacy-by-default): Gatelamp stores consent records in the EU, keeps no IP addresses or user agents, saves the choice in one cookie on your domain and tracks nobody itself.

## Planned features (not built yet)
- [Rules per region](https://gatelamp.com/features/regions): Planned: show the cookie banner in the countries that need one and keep it off elsewhere, with its own choice period per region. No IP address is stored.
- [Across domains](https://gatelamp.com/features/cross-domain): Planned: one cookie choice for a site and its subdomains, carried to your other domains by link, without third-party cookies or a tracking ID.
- [Edge mode](https://gatelamp.com/features/edge-mode): Planned for sites behind Cloudflare: a Worker rewrites known tracker tags before the page leaves the edge, so they reach the browser already blocked.
- [Platforms](https://gatelamp.com/features/platforms): At launch: a script tag for any site, an npm package and an Astro component. Planned next: WordPress, Shopify, Webflow, Framer and Google Tag Manager.

## Who it’s for
- [Gatelamp for agencies](https://gatelamp.com/for/agencies): Cookie consent for every client site from one dashboard: a banner in each client’s style, a scan of what each site loads, and proof when a client asks.
- [Gatelamp for makers](https://gatelamp.com/for/makers): Scan all your small sites and see which ones need a cookie banner. Describe your analytics and other tools once, and hear when a new embed sneaks in.
- [Gatelamp for web shops](https://gatelamp.com/for/web-shops): A cookie banner for your shop that holds back GA4, Google Ads and the Meta pixel until a customer says yes, with Consent Mode v2 and a banner per language.
- [Gatelamp for blogs and content sites](https://gatelamp.com/for/content-sites): Find out if your blog needs a cookie banner at all: load YouTube on click, self-host fonts, count visits without cookies and keep the cookie page current.

## Comparisons (other tools’ facts as shown on their own sites on the date given)
- [Gatelamp vs Cookiebot](https://gatelamp.com/compare/cookiebot): Gatelamp vs Cookiebot: free plans, pricing per domain or per workspace, scanning, IAB TCF, Consent Mode v2, where the script loads and proof of consent. Checked 2026-10-21.
- [Gatelamp vs CookieYes](https://gatelamp.com/compare/cookieyes): Gatelamp vs CookieYes: free plans, pricing per pageview or per workspace, scanning, IAB TCF, Consent Mode v2, where the script loads and consent records. Checked 2026-10-21.
- [Gatelamp vs Complianz](https://gatelamp.com/compare/complianz): Gatelamp vs Complianz: free plans, yearly licences or a monthly workspace, scanning, IAB TCF, Consent Mode v2, platforms and proof of consent compared. Checked 2026-10-21.
- [Gatelamp vs iubenda](https://gatelamp.com/compare/iubenda): Gatelamp vs iubenda: free plans, paying per site and pageview or per workspace, cookie scans, IAB TCF, languages and what each keeps as proof of consent. Checked 2026-10-21.
- [Gatelamp vs Usercentrics](https://gatelamp.com/compare/usercentrics): Gatelamp vs Usercentrics: free plans, paying by sessions and domains or per workspace, many sites in one account, cookie scans, IAB TCF and languages. Checked 2026-10-21.
- [Gatelamp vs Termly](https://gatelamp.com/compare/termly): Gatelamp vs Termly: free plans, paying per website or per workspace, cookie scans, consent logs, IAB TCF, languages and where the script loads from. Checked 2026-10-21.

## Guides (general information, not legal advice)
- [We audited our 39 sites](https://gatelamp.com/guides/we-audited-our-39-sites): What our 39 websites load before a visitor chooses: four clearly need a banner, 27 depend on the country, and Cloudflare added a script we never put there.
- [Do I need a banner?](https://gatelamp.com/guides/do-i-need-a-cookie-banner): When an EU website needs cookie consent and when it doesn’t: what the ePrivacy rule covers, common cookies and tools, national exceptions and a checklist.
- [Banner rules](https://gatelamp.com/guides/cookie-banner-rules): A fair EU cookie banner: reject next to accept, nothing pre-ticked, clear buttons, easy withdrawal and proof of each choice. With a do and don’t list.
- [Cookie policy](https://gatelamp.com/guides/cookie-policy): What a cookie policy lists for each cookie and tool: name, provider, purpose, duration, first or third party and data leaving the EU. With a template.
- [Google Fonts](https://gatelamp.com/guides/google-fonts-gdpr): Loading Google Fonts from Google’s servers sends each visitor’s IP address to Google. What a Munich court ruled, and how to host the fonts yourself.
- [Video embeds](https://gatelamp.com/guides/youtube-embeds-without-cookies): A YouTube embed contacts Google as soon as the page loads. What privacy-enhanced mode changes, and how to load videos and maps only after a click.
- [Consent Mode v2](https://gatelamp.com/guides/google-consent-mode-v2): Google Consent Mode v2 for site owners: the four signals, denied defaults, basic or advanced mode, when Google requires it and why you still need a banner.

## Free tools (no account; general information, not legal advice)
- [Cookie banner checker](https://gatelamp.com/tools/cookie-banner-checker): Enter a web address and see if the page likely needs cookie consent: the trackers, embeds and fonts it loads, and the cookies its server sets.
- [Google Fonts checker](https://gatelamp.com/tools/google-fonts-checker): Check whether a page loads Google Fonts from Google’s servers, which families it uses and whether they look self-hosted. With a step-by-step fix.
- [Consent Mode checker](https://gatelamp.com/tools/consent-mode-checker): Check whether a page loads Google tags and sets Consent Mode v2 defaults: all four signals, denied before the tags fire, and a consent platform.
- [Video embed generator](https://gatelamp.com/tools/youtube-privacy-embed): Turn a YouTube or Vimeo link into embed code that loads nothing from YouTube until a visitor clicks, plus the youtube-nocookie and dnt=1 versions.
- [Google Maps embed generator](https://gatelamp.com/tools/google-maps-embed): Turn Google Maps or OpenStreetMap embed code into a placeholder with your address that loads nothing from Google until a visitor clicks Load map.
- [Cookie declaration generator](https://gatelamp.com/tools/cookie-declaration-generator): Pick the tools your site uses or scan a page, add your own cookies, and copy a cookie table by category as HTML or Markdown, from vendors’ own docs.
- The cookie banner checker, the Google Fonts checker and the Consent Mode checker fetch one page on our server and read only its HTML (the cookie banner checker also reads the cookies the server sets). No JavaScript is run, so fonts, tags and consent settings added later by scripts or inside a Google Tag Manager container aren’t seen. Nothing about the address or the result is stored. The video and Google Maps embed generators run in the browser and their code doesn’t load anything from gatelamp.com; the map code accepts only Google Maps and OpenStreetMap embed addresses. The cookie declaration generator lists only vendors whose cookies we could source from the vendor’s own documentation (checked 28 October 2026, sources on the page); its optional scan uses the same server check as the cookie banner checker to tick the tools a page loads.

## Pages
- [All features](https://gatelamp.com/features): every feature in four groups (ask, watch, manage, prove)
- [How it works](https://gatelamp.com/how-it-works): from the first scan to lamp off in four steps
- [Pricing](https://gatelamp.com/pricing): the plans and questions about pricing
- [Roadmap](https://gatelamp.com/roadmap): what is in Gatelamp at launch and what comes after
- [Who it’s for](https://gatelamp.com/for), [comparisons](https://gatelamp.com/compare), [guides](https://gatelamp.com/guides) and [free tools](https://gatelamp.com/tools)
- [About](https://gatelamp.com/about): who builds Gatelamp and why
- [Privacy policy](https://gatelamp.com/privacy): what the waitlist on this site stores
- [Cookies](https://gatelamp.com/cookies): the cookie declaration for this site, generated by Gatelamp itself
- [Countries](https://gatelamp.com/countries): the countries where Gatelamp isn’t available; visits from there are blocked