Scripts before a choice
A theme, plugin, app or GTM tag can load a service without going through the banner.
Law 195/2024 · EU GDPR
We set up GDPR and consent for your website: cookies, forms, analytics, pixels and external services. We start with an audit, agree the scope, then verify the result.
Get a setup plan for my websiteWhat the service includes
For an assessment, send:
After reviewing the project, we agree the scope and cost of the work. The proposal depends on the platform, the number of integrations and the markets.
Where declarations and reality often diverge
Sometimes the Reject button only changes text on screen. You need to check both the interface and what happens to requests, cookies and events after the click.
A theme, plugin, app or GTM tag can load a service without going through the banner.
A quote request and a marketing subscription need separate bases and separate choices.
A map, video, chat or widget can send data before any interaction.
A fixed GTM does not prove that the theme, apps and checkout behave the same way.
Scope
We agree the scope after reviewing the project. These are the base stages, adapted to the platform and markets.
A map of forms, cookies and other identifiers, analytics, pixels, chat, maps, video, CRM and newsletters. Server-side transfers and checkout are marked separately.
Banner and categories, reopening preferences, the tag firing scheme, forms and agreed documents in the website languages.
Scenarios before a choice, after rejection, partial choice, acceptance and withdrawal. We check network requests, cookies, repeat visits, desktop and mobile.
A report on findings and limitations, the change list and a short guide: what to recheck after new apps, forms and pixels.
We configure the website and connected tools. Legal bases, HR, supplier contracts, DPO, DPIA and internal procedures are agreed separately with the data protection contact and, where appropriate, a lawyer. Technical setup does not certify the compliance of the whole company.
Platforms
We check the banner and what the platform does on its own.
Theme, plugins, caching, third-party embeds and script order. We check whether the CMP duplicates what the theme already loads.
Customer Privacy, regional settings, apps, web pixels and checkout. The theme does not control every platform pixel.
Custom and hybrid projects: server-side transfers, CRM, call tracking and non-standard forms are checked within the agreed scope.
Acceptance
Acceptance relies on observable scenarios and a report, not on a scanner score.
| Scenario | What we check |
|---|---|
| Before a choice | Optional tools do not start when blocking is selected. Text and links are available. |
| Rejection | The choice is stored, preferences can be reopened, and events do not fire under optional categories. |
| Partial choice | Analytics and marketing are controlled separately, without hidden defaults. |
| Acceptance | Required tags fire once, without duplicate events. |
| Withdrawal | Preferences change without a reload or after one, and later requests follow the choice. |
| Repeat visit | The stored choice applies and the banner does not reset it. |
| Languages and devices | Buttons and text are clear in each language and usable on a phone. |
The report records what was tested, in which browsers and regions, and what limitations remain. No events for a short period does not prove that all transfers have stopped.
How to start
Cost depends on the CMS, languages, markets and the number of integrations.
Send the URL, platform, markets and the list of tools. We clarify the task and its boundaries.
We describe what to check and configure, what stays outside the scope, and which licences and work are billed separately.
We agree a release and rollback plan, configure the site, test the scenarios and hand over the report.
The number of forms and languages, apps and pixels, display regions, server-side integrations, checkout, and whether a lawyer needs to be involved. CMP licences and post-launch support are agreed separately.
FAQ
Short answers to the decisions that come up before agreeing the scope.
No. The banner collects a choice, but compliance also depends on which services start, on what basis, and what happens after rejection. The website's actual behaviour has to be tested.
No. Advanced mode can send cookieless requests before consent. A denied status alone does not prove that no data is transmitted. We choose the approach after reviewing purposes and requirements.
Legal bases, contracts, retention periods and internal procedures go beyond technical setup. We prepare the technical information; the client approves the legal part with the data protection contact or a lawyer.
It depends on the chosen approach. We do not promise to keep the full previous data volume. The proposal states which events remain, which become limited, and how to verify them.
After a new app, pixel, form or change of purposes, old settings can stop working. Rechecking is part of support when support is agreed.
We take Law 195/2024 into account and consider whether EU GDPR applies based on markets and the nature of processing. The concrete legal scope depends on the company's activities; technical setup does not replace legal assessment.
Useful before you request
A review of Law 195/2024, the data map, banner limits and Consent Mode. With links to primary sources.
Request
Give us the website address, platform and markets. We clarify the task and prepare a proposal: what to check, what to configure and how to accept the result.
Do not send passwords or access credentials. A public URL is enough for the initial assessment.