Question 1

How long does setup take?

Accepted Answer

A simple head installation can be quick. Add your website, configure the banner and install the complete snippet. Allow time to check tag order, visitor choices and returning visitors. Platform restrictions or an existing consent tool may require extra work.

Question 2

Do I need a developer?

Accepted Answer

You can often install the banner using your platform's custom-code settings or the WordPress plugin. A developer or tag specialist may be needed for custom applications, restricted checkout pages or tracking configuration. Check the guide for your platform before choosing an installation method.

Question 3

Can I try ConsentEase first?

Accepted Answer

The standard offer includes a 7-day free trial. Trial checkout requires a payment method and shows when paid billing will begin. Check the dates and terms displayed at checkout; creating an account alone is not proof that checkout has completed.

Question 4

Can I replace an existing cookie banner?

Accepted Answer

Yes, but plan the change so two consent tools do not run together. Remove the old banner and its consent initialization when switching, install the complete ConsentEase snippet and test existing tracking configuration. A previous tool's stored choice is not automatically a ConsentEase choice.

Question 5

What is the difference between my website ID and an API key?

Accepted Answer

The public website ID identifies the banner configuration and is used in your embed snippet. It is not an API credential. API keys authorize scoped access to website data and operations: keep them out of public browser code and revoke exposed keys.

Question 6

Does ConsentEase make my website GDPR compliant?

Accepted Answer

ConsentEase provides technical consent controls, scan findings and consent records. These do not certify legal compliance. Your tracking configuration, purposes, notices, policies and wider data practices still need review.

Question 7

Does ConsentEase support Google Consent Mode v2?

Accepted Answer

Yes. The complete embed snippet sets Google consent defaults, and the banner sends updates when a visitor saves a choice. The defaults must run before Google Tag Manager or other Google tags. A correct snippet does not fix tags that load too early or have incorrect consent settings.

Question 8

Does the banner automatically block every tracker?

Accepted Answer

No. Consent signals and script blocking are different. Google tags need an appropriate Basic or Advanced Consent Mode configuration; Advanced mode may send cookieless pings before consent. Other trackers need their own consent-aware loading or blocking configuration. Verify actual cookies and requests after refusal.

Question 9

Do you provide consent records for audits?

Accepted Answer

Yes. ConsentEase records timestamped consent choices and provides dashboard filtering and CSV export for authorized users with the required access. A record supports review; it is not proof that every tag behaved correctly or that the whole website is compliant. A single dashboard CSV export is limited to 10,000 records.

Question 10

Does a successful scan mean my website is compliant?

Accepted Answer

No. A scan reports what was observed in its tested pages and time windows. Trackers behind login, interactions or untested pages may not be observed. Read the findings and verification coverage, and treat incomplete or failed checks as missing evidence rather than a pass.

Question 11

Does geographic detection automatically switch the legal consent model?

Accepted Answer

No. Geographic context can support a regional badge and language context, but it does not automatically rewrite banner controls or persist a legal jurisdiction in every consent record. Choose the appropriate setup for your audience and obligations.

Question 12

How does pricing work?

Accepted Answer

Public pricing is graduated per website: the first 10 websites cost €9 each per month or €90 each per year. From website 11, only the additional websites cost €7 per month or €70 per year. The lower rate does not apply retroactively to the first 10 websites. Prices exclude VAT; existing or agreed agency pricing may differ.

Question 13

What happens when I add or remove websites?

Accepted Answer

For supported per-website subscriptions, ConsentEase attempts to synchronize the billable website quantity and applicable pricing with Stripe. Proration may apply. Legacy subscriptions and agreed partner pricing have separate rules; removing the last website is not a subscription cancellation. Check your billing summary or contact support if a change is not reflected.

Question 14

Are there pageview or traffic limits?

Accepted Answer

Public pricing is based on websites, not visitors, sessions or pageviews. There is no pageview-based price tier. This does not mean every operation is unlimited: scans, API requests, policy generation and exports have their own limits.

Question 15

Is annual billing discounted?

Accepted Answer

The public annual rates are €90 for each of the first 10 websites and €70 for each additional website, excluding VAT. These are annual charges, not monthly payments. Confirm your billing interval and total at checkout.

Question 16

Do you offer strategic agency pricing?

Accepted Answer

Agencies managing 50 or more websites can request a strategic offer. Any additional discount depends on an agreed site, term or revenue commitment; it is not an automatic discount for every agency account.

Question 17

Is there a free plan?

Accepted Answer

There is no permanent free plan. The standard trial offer lasts 7 days. Review the checkout terms and billing start date before activating it.

Question 18

Does the pricing page mean every planned feature is available now?

Accepted Answer

No. Roadmap and future product positioning are not the same as a released feature or a purchased entitlement. Check current availability, usage limits and your account access before relying on a feature.

Question 19

Will ConsentEase slow down my website?

Accepted Answer

The banner runtime loads asynchronously, but it still uses network, CPU and rendering resources. The small consent-default block runs before tracking tags. Measure your own page with and without the integration rather than relying on a zero-impact promise.

Question 20

Does it work with single-page applications?

Accepted Answer

Yes, provided you install it once in the persistent application shell. Do not reinsert the banner or reset consent on each route change. Framework-specific loading order, browser-only execution and navigation should be tested in your deployed application.

Question 21

Can I use Google Tag Manager?

Accepted Answer

Yes. A direct head installation is preferred when available. If you install through GTM, consent defaults must still be established before Google tags run, and consent-related tags need the correct triggers and settings. Installing a template or connecting a Google account is not automatic publication of your container.

Question 22

Can I connect my application or AI agent to ConsentEase?

Accepted Answer

The public REST API and MCP endpoint use scoped API keys and website authorization. MCP supports the documented website and cookie operations and aggregate consent statistics; it cannot invent visitor choices or change banner design and publication. Check client compatibility and the documented remote or local installation options.

Question 23

Where is my data stored?

Accepted Answer

Storage and processing locations depend on the hosting infrastructure and services used. If you require EU-only residency or specific transfer safeguards, request the current hosting locations and subprocessor details before signing. This FAQ does not promise EU-only processing.

Question 24

Who can access my consent data?

Accepted Answer

Customer-facing dashboard access depends on website ownership and authorized agency or team access. REST and MCP access requires a scoped API key and authorization for the website. Review invitations and credentials when granting or withdrawing access; service-provider processing is a separate matter covered by the applicable privacy and processing terms.

Question 25

Are consent records anonymous?

Accepted Answer

Do not treat consent records as anonymous. They can contain visitor identifiers, hashed IP addresses, user-agent information, timestamps and choices. Hashing or pseudonymization does not remove every identification risk. Limit access and handle exports as potentially personal data.

Question 26

Is consent renewal the same as deleting old consent records?

Accepted Answer

No. Banner renewal controls when a visitor may need to choose again. Record expiry, evidence retention and deletion are separate concepts. Changing a renewal setting is not an automatic log-deletion policy. By default, ConsentEase keeps each consent record until its scheduled renewal date plus 24 months (never shorter than recording time + 365 days + 24 months); after that, it becomes eligible for removal by a daily cleanup. The website owner is the controller and should export records that must be kept longer.

Question 27

Can visitors change their consent later?

Accepted Answer

Yes. Provide the revisit control or a visible cookie-preferences link or button so visitors can reopen their choices. Opening preferences alone does not save a new choice. After a visitor saves a change, consent signals update; cookie cleanup is limited to what the browser and integration can access.

Frequently asked questions

Getting Started

GDPR & Compliance

Pricing & Billing

Technical

Security & Privacy