GDPR cookie consent
without the bloat.
Fast, predictable consent management for SaaS, stores, and modern websites.
The setup assistant scans your site, classifies every script and cookie, and builds blocking rules for what it actually loads. No universal dictionaries, no ad-tech runtime: the entire loader is ~10 KB. You see what gets blocked, why, and can change it. Most sites go live in minutes.
14-day free trial · No credit card required
We use cookies to enhance your browsing experience, serve personalized content, and analyze our traffic. Please choose your cookie preferences.
Built for / Not built for
Built for
- SaaS websites
- Marketing sites
- Ecommerce stores
- Agencies managing client sites
- Blogs and portfolios
- Teams that want direct control
Not built for
- Ad-tech publishers needing IAB TCF
- Vendor-list-driven consent models
- Enterprise privacy suites
LiteConsent deliberately excludes ad-tech infrastructure. If your site runs programmatic ads and needs IAB TCF, there are CMPs built for that. We are built for everyone else.
Consent enforcement without the ad-tech stack
Many CMPs are built around ad-tech ecosystems and vendor-driven consent models. LiteConsent focuses on consent enforcement with a small, predictable runtime.
What they really sell you
You're buying an ad-tech control panel, not consent enforcement.
- IAB TCF v2.2 integration · built for programmatic ads, not most product sites
- Google CMP Partner / AdSense tooling · useful only if you run ad inventory
- Vendor-driven consent model · built around large vendor ecosystems
- Autoblocking dictionary (1,000+ signatures) · rules and patterns to guess categories at runtime
- Black-box auto-blocking · heuristics decide what to block; hard to debug when something breaks
- 100+ KB JavaScript bundle · extra weight that can hurt PageSpeed / Core Web Vitals
- €19 to €49/month · paying for ad-tech features you'll never use
What you actually need
Full consent management, explicit control, predictable footprint.
- Consent banner flow · Accept / Reject / Customize (equal-weight actions)
- Real script + iframe blocking · enforced before execution
- Explicit, readable rules · auto-generated for your site, reviewable before going live
- Consent logs + export · audit-ready records (server-side)
- ~10 KB loader · no ad-tech runtime, no signature dictionaries
- No render-blocking layer · the page renders immediately
- Google Consent Mode v2 · works with GA4 and GTM, no extra bundles
- From €7/month · pay for what you use
Why teams switch
Cookiebot got too expensive
Predictable usage-based pricing. No surprise bills when traffic spikes.
We don't need IAB complexity
If you do not run programmatic ads, you do not need a framework built for them.
We want GTM to keep working
Resource rules intercept scripts by domain, so your existing GTM setup keeps working.
We need proof of consent
Every consent choice is logged server-side with timestamps, categories, and exportable records.
We don't want a slow banner script
The loader is ~10 KB gzipped, with no vendor lists or ad-tech runtime weighing down your pages.
Auto-setup discovers everything
The setup assistant scans your site and creates blocking rules automatically, so many sites can start without re-tagging scripts.
Try it on your site in 5 minutes
14-day free trial with full Pro access. No credit card required.
What LiteConsent handles
Script + iframe blocking
Non-essential scripts and iframes are blocked until the visitor gives consent. Blocking is domain-based and category-aware.
Consent logging + export
Every consent decision is logged server-side with timestamps and categories. Export as CSV. EU-hosted storage.
Region-based behavior
Region-aware consent adapts to the visitor's jurisdiction. EU visitors see opt-in banners. US visitors see CCPA notices. Configurable per region.
Customizable banner UI
Colors, text, layout, toggle style, fonts, and border radius. Edit in the visual editor or write custom templates.
Category controls, Google Consent Mode v2, GPC support, Auto setup, Multi-language, Cookie policy page
Your banner, your design
Start from a ready-made template or clone one and make it fully yours. Customize visually or go deeper with HTML and CSS.
- Choose from 5 built-in templates: bottom bar, popup, floating widget, and more
- Customize colors, fonts, position, overlay, animation, border radius, and icons in the visual editor. No code needed
- Clone any built-in template to get a working HTML structure with all required elements, then customize the markup and styles however you want
- Upload your own fonts to match your brand typography exactly
- Step-by-step docs explain every element, so you know what each part does before changing it
All plans include 5 built-in templates with visual customization. Pro adds 5 custom templates and 5 custom font uploads. Business includes 20 of each.
How the numbers break down
The loader stays small because your config contains only rules for your site. There is no universal dictionary to download and no ad-tech framework to initialize.
Two ways to deploy
CDN or self-hosted, both use the same two scripts. c.js is a config compiled specifically for your site: only your rules, categories, and display settings, nothing extra. lc.js is the lightweight runtime that enforces consent.
Automatic updates, zero maintenance
Add two script tags. Your compiled config auto-updates when you save changes in the dashboard. Fast global delivery via our CDN.
- Config updates instantly when you save
- Fast global delivery, no hosting needed
- Works on any website or framework
Full control, your servers
Download both files and host them on your own server. You control the delivery and can inspect every byte. Re-download c.js after each config change.
- Full control over script delivery
- Inspect the source, nothing is hidden
- Works in air-gapped or restricted environments
Setup takes three steps
Add two script tags
Paste two lines into your HTML head. Your compiled config and the consent runtime load together.
Run the setup assistant
Browse your site to discover cookies and third-party scripts. We classify them and create blocking rules automatically.
Go live
The banner appears for visitors in regions that require consent. Scripts are blocked until they choose.
That's it. Rules update automatically when you save changes in the dashboard.
Auto setup, based on your site
The setup assistant scans your live site, classifies every cookie and third-party script, and compiles a config with only the rules your site needs. You review every rule before going live — nothing runs that you haven't approved.
- Discover cookies and third-party scripts from real browsing
- Classifies each resource into consent categories
- Match your site's colors and detect languages
- Auto-create resource rules for dynamically loaded scripts
- Generate integration hints for statically embedded scripts
The result is a blocking config built from your actual site. If a script isn't covered, add a rule in the dashboard.
Supports implementation of major privacy regulations
LiteConsent adapts behavior by region and legal model.
GDPR (EU/EEA)
Opt-in consent with script blocking, equal-choice actions, and server-side logging.
UK GDPR / PECR
The same opt-in model as the EU, with scripts blocked until consent.
CCPA / CPRA (California)
Do Not Sell / Share notice, GPC detection, and an opt-out model.
LGPD (Brazil)
Category-based opt-in with clear purpose disclosure.
PIPEDA (Canada)
Notice-based consent with an opt-out path where appropriate.
Global Privacy Control
Detects the browser signal and respects it automatically.
How it works by region
| EU / EEA | Opt-in required, with scripts blocked until consent |
| United Kingdom | Opt-in required, with scripts blocked until consent |
| California (CCPA) | Do Not Sell / Share notice with GPC support |
| Rest of world | Simple notice or no banner, configurable by region |
Every rule is visible in your dashboard. Every consent action is logged.
How LiteConsent treats user data
No third-party tracking
LiteConsent does not send visitor data to external services. Consent records are stored on EU-hosted servers.
Minimal data collection
Only the data needed for consent management is collected: consent choices, timestamp, and anonymized metadata.
You control the data
Export or delete consent records at any time. Data retention is configurable per plan.
Privacy by design, not an afterthought.
Pricing that scales with your traffic
No hidden tiers. No artificial feature limits. Pay based on usage.
€5.83/mo · billed annually
billed monthly
1 domain · 20K consents/mo
- Unlimited page views
- Script + iframe blocking
- Region-aware behavior
- Analytics dashboard + CSV export
- Cookie policy page
- Auto setup
- Google Consent Mode v2
€12.50/mo · billed annually
billed monthly
3 domains · 100K consents/mo
- Everything in Basic
- 42 languages
- 5 banner templates
- 5 custom fonts
- Custom consent renewal period
- Subdomain consent sharing
- Up to 3 team members
€32.50/mo · billed annually
billed monthly
10 domains · 2M consents/mo
- Everything in Pro
- Up to 10 team members
- Scheduled compliance scans
- 20 banner templates
- 20 custom fonts
- 3-year consent log retention
Common questions
Is LiteConsent enough for GDPR compliance?
LiteConsent covers the technical consent layer: banner display, script and iframe blocking, consent storage, logging, and withdrawal. We also provide a DPA and store consent data in the EU. Full GDPR compliance still depends on your privacy policy, your data processing practices, and how you configure the third-party tools you use.
Do I need to manually configure every script?
No. The setup assistant discovers cookies and scripts on your site automatically, classifies them, and creates blocking rules. You review and adjust, then go live. For scripts embedded directly in your HTML, the assistant generates integration hints showing which tags to update.
Why don't you support IAB TCF?
IAB TCF is built for sites that participate in programmatic advertising and need to pass consent signals through ad networks and vendor lists. Most SaaS sites, stores, and company websites do not need that complexity. LiteConsent is designed for those sites.
What about CCPA, CPRA, and other US state laws?
LiteConsent supports region-aware consent flows, including CCPA and CPRA-style opt-out behavior, Do Not Sell or Share notices, and Global Privacy Control support. You can configure the behavior by jurisdiction instead of showing the same banner to everyone.
Is LiteConsent a full CMP or just a banner?
It is a full consent system. LiteConsent includes banner UI, script and iframe blocking, jurisdiction-aware behavior, consent storage, proof-of-consent logs, and export. The loader stays small because it avoids ad-tech overhead, not because key features are missing.
Does LiteConsent support Google Consent Mode v2?
Yes. LiteConsent supports Google Consent Mode v2 and works with Google Analytics, GTM, and Google Ads without requiring a separate heavy runtime.
Will it slow down my site?
LiteConsent is built to stay lightweight. The loader is about 10 KB gzipped and avoids the large client-side bundles common in heavier CMPs. The page still loads normally while LiteConsent controls scripts and iframes based on consent.
What if I cannot edit every script tag on my site?
Most scripts are handled automatically by resource rules, which block dynamically loaded scripts and iframes by domain. For scripts hardcoded in your HTML, the setup assistant generates integration hints showing exactly which attributes to add.
Will this work with GTM, SPAs, and dynamically injected scripts?
Yes. LiteConsent handles GTM, single-page apps, and dynamically injected scripts through resource rules that intercept network requests by domain. The setup assistant detects these automatically during the discovery session.
Where is consent data stored?
Consent records are stored in the EU. Data is encrypted in transit and at rest, and every account includes a DPA.
Can visitors change their consent later?
Yes. You can expose a persistent Cookie Settings entry so visitors can reopen the dialog and update their choices at any time.
Do you track people across websites?
No. LiteConsent does not build advertising or analytics profiles across websites. It only stores what is needed to manage and remember consent within your own setup.
What data does LiteConsent collect?
Only what is needed for consent management: consent choices, timestamps, and limited technical metadata. You can export or delete consent records, and retention can be configured by plan.
Why is the loader only about 10 KB?
Because LiteConsent compiles a site-specific config that contains only the blocking rules your site actually needs. There are no universal dictionaries, no IAB TCF vendor lists, and no ad-tech frameworks bundled in. The loader ships the consent UI and enforcement layer, nothing else.
What happens if something is not blocked?
LiteConsent only blocks what is explicitly covered by your resource rules or markup tags. That keeps behavior predictable and avoids false positives. If something still loads, you can add a rule in the dashboard or tag it directly.
Do I need a developer to set it up?
Not always. The setup assistant discovers scripts and creates rules automatically. Many sites can go live after reviewing the auto-generated setup. A developer is helpful for sites with custom script injection, advanced GTM setups, or heavily dynamic apps.
Can't find your answer? Email us
Full consent management. Simple pricing.
14-day free trial with full Pro access. No credit card required.