Cookie consent for 1000 domains.
Free. With real blocking.

Can I really use it for free?

Yes. Free plan gives you full functionality for up to 1000 domains — no time limit. Only condition: banner shows a discreet "Powered by ConsentGuards" link. Register with a business email or one click via Google.

How can I register?

Two ways: with a business email (e.g. john@yourcompany.com — free mailboxes are not accepted in the form signup, this protects against spam) or with one click via your Google account. No credit card.

Can I remove "Powered by" link in free plan?

Not in Free plan. The link is the only "payment" for free usage — even on 1000 domains. Want no link? Starter ($12/mo) removes it for 100 domains, Agency ($49/mo) for 1000.

Why pay if free cookie plugins exist?

Because "free" plugins usually end at the banner — scripts load anyway. ConsentGuards is a technical gate: vendors load only after consent. You pay for control, not a banner.

Is this a cheaper Cookiebot?

No. Cookiebot is heavy compliance. ConsentGuards is a lightweight technical engine: blocking + API-first for networks. Different product, different use case. And we have a free plan.

Does it really block GA4 and Google Ads?

Yes — if tools are implemented via ConsentGuards/GTM after consent. Before consent, vendors are not loaded. Real blocking, not just a declaration.

Can I use it on many domains?

Free = up to 1000 domains with "Powered by" link. Starter ($12) = up to 100 domains WITHOUT the link. Agency ($49) = up to 1000 domains WITHOUT the link. You pay only to remove the link — features are the same. One panel, domain groups, bulk operations.

Do I need a yearly contract?

No. Monthly billing, no lock-ins. Free is free forever.

What if I stop paying?

Nothing "breaks". Account reverts to Free plan (up to 1000 domains, the "Powered by" link reappears in the banner). You can also disable the script entirely — site reverts to pre-implementation state.

Who is it NOT for?

If you need automated cookie scanning and compliance certificates — choose heavy platforms. ConsentGuards provides technical control, not paperwork.

What exactly is ConsentGuards?

ConsentGuards is a technical consent management and analytics/marketing tool blocking system until user consent. Works with Google Consent Mode v2.

What scripts are blocked?

ConsentGuards blocks tools implemented properly: GA4, Google Ads, GTM, Meta/Facebook Pixel, TikTok Pixel, LinkedIn Insight, Hotjar. List can be extended.

Does it block ALL cookies on the site?

No. It blocks analytics and marketing cookies. Technical cookies (sessions, security, login) don't require consent and aren't blocked.

Does it block manually inserted or plugin scripts?

Only if wired through ConsentGuards or GTM loaded after consent. Hard-coded HTML scripts need rewiring or extended protection mode.

Do I need Google Tag Manager?

No. ConsentGuards works with or without GTM, via dynamic script loading. You decide the architecture.

Does ConsentGuards block server-set cookies?

No. ConsentGuards works client-side (JavaScript). HTTP header cookies must be handled server-side.

Does it block localStorage and sessionStorage?

No global interference. Blocking applies to scripts trying to use them, if loaded after consent.

Does it block fingerprinting?

ConsentGuards doesn't detect fingerprinting. That's a legal/architectural issue requiring code audit.

Does it work with React / Vue / SPA?

Yes. Works framework-agnostic as a global JS layer. In SPA, trigger tracking events only after consent.

Does it support multiple languages?

Yes. System supports multiple language versions and per-domain content configuration.

Does it save user consent history?

By default, only saves current consent state in cookie. Consent history log requires separate solution (enterprise).

Does it meet Google Ads and GA4 requirements?

Yes — supports Google Consent Mode v2 and enables correct cookieless reporting.

Does it interfere with site appearance?

No. Banner and modal are injected dynamically, don't modify site structure or layout.

Is it WCAG / accessibility compliant?

Uses standard HTML elements, supports keyboard, doesn't block screen readers. Full WCAG compliance depends on final configuration.

Does it work in cookieless mode?

Yes. Supports cookieless analytics mode, Consent Mode v2, and data anonymization before consent.

Does it block external iframes (YouTube, maps)?

Not by default. Iframes require separate approach — available as additional feature.

Does it work with CDN (Cloudflare, Akamai)?

Yes. CDN compatible, works with cache, doesn't require disabling cache.

Does it work on subdomains?

Yes. Separate subdomain management or shared configuration possible.

Does it block A/B testing tools?

Yes — if wired as analytics tools. A/B tools may also require consent.

Can it work offline / locally?

Yes — in test environments. Production version requires API connection.

Does ConsentGuards guarantee GDPR compliance?

ConsentGuards supports technical compliance (consent/blocking), but is not legal advice. Ultimate responsibility lies with site admin. Industry standard.

Do you block all "other" scripts on the site?

We block what's wired through ConsentGuards (or GTM after consent). Hard-coded scripts need rewiring or extended protection mode.

Does ConsentGuards replace privacy policy?

No. It doesn't generate legal documents. Site still needs privacy policy and cookie policy.

Does ConsentGuards store user data?

Only stores consent information (cookie). Doesn't collect personal data, IPs, emails, or identifiers.

Does it generate cookies.txt files or logs?

No. Doesn't auto-generate documents or cookie lists. That's admin's responsibility.

Won't ConsentGuards lower my conversions?

Quite the opposite. No heavy scripts before consent = faster site. Simple interface without dark patterns. Many clients see better CWV.

Can I implement ConsentGuards myself?

Yes. One JS script + domain config + optional vendor wiring. For complex projects, we offer technical support.

How long does implementation take?

Standard site: ~15 minutes. Site network / agency: from 30 min to few hours (one-time).

Is it suitable for SEO agencies?

Yes — that's one of our main target groups. Agencies value scalability, API, no vendor lock-in, white-label option.

Can I resell ConsentGuards to my clients?

Yes. Agency packages, white-label option, and integration with your services available.

Can I test before buying?

Yes. We provide demo, test on chosen domain, and first implementation support.

Does it work on high-traffic sites?

Yes. System is light, cache-friendly, and ready for high traffic volume.

Is it suitable for e-commerce?

Yes. Doesn't block cart or payments, doesn't interfere with checkout, enables remarketing control.

Does it work with mobile apps / PWA?

Works in mobile browsers and PWA. Not an SDK for native apps.

Can I change plans mid-term?

Yes. You can increase or decrease domain count, billing is prorated.

What if I need custom configuration?

We offer custom configurations, client-specific integrations, and solutions for large networks.

Is ConsentGuards being developed?

Yes. Product is actively developed, adapted to Google and regulation changes, expanded with new modules.

Will I get technical support?

Yes. Scope depends on plan: email, consultations, onboarding.

Can I customize banner appearance?

Yes. Colors, texts, position, branding (white-label).

Is it suitable for small sites?

Yes, but greatest value is with many domains. For one site, still a professional solution.

Is ConsentGuards open-source?

No. ConsentGuards is a commercial product.

Can I expand features in the future?

Yes. Planned expansions: hard blocker mode, additional integrations, technical logs, client panel, agency automations.

Why is ConsentGuards a good investment?

Saves time, reduces risk, gives control, scales with your business. Organizes consent chaos technically, not declaratively.