Frequently askedquestions

Cookielet is a Cookie Consent Management platform built to handle compliance for your website, so you don't have to think about it. It scans your site and finds every cookie and tracking script running in the background. Then it shows visitors a consent banner that actually matches the privacy law in their region — GDPR if they're in the EU, CCPA if they're in California, and so on. Anything non-essential stays paused until someone actually says yes to it, and every response gets logged with a timestamp so you've got a record if you ever need one.

If your site uses analytics, ad pixels, or any kind of tracking technology, and visitors come from places like the EU, UK, or California, you're already dealing with rules that require proper consent. That's true for online stores, SaaS tools, blogs, agencies — basically anyone collecting visitor data. Cookielet figures out which law applies to which visitor automatically based on location.

Once installed, it scans your entire site to map out cookies, pixels, and third-party scripts. It then detects where each visitor is coming from and displays the right banner — an opt-in style for EU traffic, an opt-out style for California visitors. Every choice gets saved to a secure log with a timestamp attached.

One script, added to your site's header — that's really the whole process. No manually hunting down every cookie yourself, no code overhaul. The script triggers an automatic scan and starts showing location-based banners right away, whether your site runs on WordPress, Shopify, or something custom-built.

Usually just minutes. Once the script is live, scanning, detection, and banner display all happen automatically, so there's very little manual configuration standing between you and being compliant.

No. Cookielet loads in the background so your pages continue loading smoothly. Until a visitor gives consent, non-essential cookies, analytics, and advertising pixels stay blocked, reducing unnecessary requests during the first page load.

GDPR, UK GDPR, the ePrivacy Directive, CCPA/CPRA, PIPEDA, LGPD, POPIA, PDPL, and other major data protection regulations. Based on each visitor's location, Cookielet automatically displays the correct banner and applies the appropriate privacy settings.

It covers the major ones, and that list keeps growing as new regulations show up worldwide. Updates happen regularly to keep pace with changing legal standards.

Yes — a visitor in Germany sees a banner requiring active opt-in before any tracking starts. A visitor in California sees CCPA/CPRA-style options, including a "Do Not Sell or Share My Personal Information" toggle where required. The geo-based logic handles it automatically.

Yes. You can adjust colors, logo placement, and wording so the banner feels like a natural part of your site instead of a bolted-on legal notice. The underlying consent logic stays exactly the same.

Yes. Cookielet can display the consent banner in the visitor's own language automatically, based on their location or browser settings, so people actually understand what they're agreeing to.

CookieLet offers four plans: Free, Starter ($11/month), Pro+ ($27/month), and Ultimate ($57/month). Each account includes one Free website; additional websites require a paid plan. Choose annual billing to receive 2 months free. VAT/GST is added based on your billing location.

No hidden fees. If you go over your pageview limit, you'll pay a small extra amount per 1,000 views. Taxes like VAT or GST may apply based on your location.

Have a blog or personal site? Choose Starter. Running a growing business? Pro+ is a great fit. Already getting lots of traffic? Go with Ultimate.

Free scans 100 pages per check and covers 5,000 pageviews a month. Starter scans 800 pages, covers 150,000 pageviews, and runs automatic monthly scans. Pro+ scans 6,000 pages, covers up to 700K pageviews, and adds geo-targeted banners. Ultimate scans 10,000 pages, covers unlimited pageviews, scans weekly, and removes CookieLet's branding.

Yes. There are no contracts. Cancel whenever you want, or upgrade instantly when your traffic grows.

Yes. Each website needs its own consent management plan, since pricing works per domain.

Pro+ works well for most online stores. If your store gets heavy traffic across countries, choose Ultimate to stay GDPR and CCPA compliant everywhere.

No. Signing up is free. You'd only add a card if you later choose a paid plan.

Click "Sign up," add your email and a password, and that's it. You'll be in your dashboard right away, ready to add your site.

No. Signing up is free. You'd only add a card if you later choose a paid plan.

Log in, click "Add site," and enter your domain. CookieLet scans it and gives you a short code to paste into your site's header. Once it's pasted, your cookie banner shows up on your site.

Yes. You can add several sites to one account. Each site has its own banner and its own consent records.

Click "Forgot password" on the login page and enter your email. A reset link will land in your inbox in a couple of minutes. If you don't see it, check spam.

First, check spam — it's usually there. If not, log in and click "Resend verification email" on your dashboard. Still nothing? Contact support and they'll help you sort it out.

CookieLet is built for websites, not native mobile apps. It works wherever you can add a script to your site's header — WordPress, Shopify, or custom-built. For app-based cookie consent, check with support first.

It's just one small piece of code. Sign up, add your site, and CookieLet gives you a script. Paste it near the top of your site's header, save, and refresh — your cookie banner will show up right away. No coding needed.

No. You just copy the code and paste it once. That's the whole setup, no matter what platform your website is built on.

No, not really. The script is small and loads quietly in the background. If you see a small dip in analytics afterward, that's usually because visitors who reject cookies aren't being tracked anymore — not your site slowing down.

No, each website needs its own script. This keeps your scans and consent records accurate. But you can still manage all your sites from one CookieLet account.

Yes, take the old one out first. Two tools running at the same time can cause your banner to glitch, show twice, or block cookies incorrectly.

No. CookieLet only controls tracking and marketing cookies, holding them back until a visitor agrees. Your checkout and payment system won't be touched at all.

GDPR (EU/UK), the ePrivacy Directive, CCPA/CPRA, and a growing list of US state laws (Virginia, Colorado, Connecticut, Utah). It also covers Canada's PIPEDA and Quebec's Law 25, Brazil's LGPD, South Africa's POPIA, Switzerland's nFADP, Australia's Privacy Act, and several Middle Eastern and Latin American data laws. Your banner automatically shows the right consent options depending on where the visitor is browsing from.

Yes. Cookielet follows core GDPR requirements — visitors get clear opt-in choices before non-essential cookies load, consent is broken down by category (analytics, marketing, functional), and every choice is logged securely with a timestamp.

Yes. IAB Europe's Transparency and Consent Framework (TCF) is the standard ad-tech partners use to check whether a visitor has actually consented to data sharing. Being a registered CMP means Cookielet's consent signals are recognized and trusted by ad networks.

Yes. The ePrivacy Directive says you need permission before storing cookies, not after. Cookielet blocks non-essential scripts automatically until a visitor makes a choice.

Yes. Place links to both in your banner's footer text so visitors can quickly reach whichever answer they are after.

Yes. Cookielet runs automated cookie scans on your site on a recurring schedule, identifying new trackers and categorizing them so your cookie policy and consent banner stay accurate.

Continuously — not once a year, but every time a law actually changes. The moment GDPR guidance shifts, a new US state law kicks in, or regulators tighten enforcement, Cookielet's banners and policy templates get updated to match.

That's built in. There's a proper "Do Not Sell or Share My Personal Information" opt-out for CCPA and CPRA. Visitors from California — or from a state with similar rules — automatically see the right version of that opt-out.

Yes — colors, logo, corner rounding, even the wording. A live preview lets you tweak without guessing and reloading your site fifty times.

Depends on your setup. If tracking scripts fire before someone clicks anything, that's actually a compliance issue. A properly built cookie consent website blocks analytics and ad scripts until someone actually says yes.

At the moment, CookieLet does not provide an option to change the button order. The default layout aligns with applicable privacy regulations and provides a consistent, compliant user experience.

It's in your dashboard under language or localization settings. Turn on auto-detect if you get international traffic, so visitors see the banner in their own language automatically.

Paste a short code snippet or shortcode into your footer widget. It reopens the same preference panel visitors saw on their first visit, so they can change their mind anytime.

At the moment, CookieLet does not provide an option to customize the font style used in the consent banner. The banner uses our standardized, legally reviewed styling for a consistent, compliant experience.

Usually one of three things: the consent cookie isn't saving (browser privacy settings), your site loads under both www and non-www without a redirect, or another script is overwriting your consent settings. Incognito mode will always re-show it — that's normal.

No, one good cookie consent platform usually covers both. It should detect visitor location and switch rules automatically — opt-in for GDPR in the EU, opt-out style for the CCPA in the US.

Yes. A cookie policy explains which cookies your site uses; a privacy policy covers your broader data practices. Add both links to your banner's footer text.

Yes, probably more than most sites. Stores run heavier tracking — analytics, retargeting, cart abandonment tools — exactly what consent laws target.

Yes, but only the consent choice itself — accept, reject, or customize — plus a timestamp. It's not profiling visitors, just proving consent was given.

The consent choice, a timestamp, a consent ID (so people aren't re-prompted), and basic technical info like IP and browser type used to detect which privacy law applies. It also scans your site for trackers.

No. The consent ID is tied to a browser, not a person. Names and emails only exist for your own Cookielet account — completely separate from visitor data.

Encrypted, on secure servers, with retention length set by you. The retention window is built into your published policy automatically.

Not by Cookielet. It blocks tools like Google Analytics or Meta Pixel until consent is given — it's a processor, not an advertiser.

No. The consent ID is scoped to your domain only — no cross-site tracking.

Your site's cookies (analytics, ad pixels) are what Cookielet detects and blocks until consent. Cookielet itself sets just one cookie — the one remembering the visitor's choice.