Cookie Policy: Automating GDPR & ePrivacy Compliance

Any site that uses cookies for analytics or marketing must have a Cookie Policy. This is required by <cite>GDPR (Articles 5, 7)</cite> and <cite>the ePrivacy Directive</cite>, and it's also a condition for running ads via Cookie Consent and Facebook. Without this document, you risk a fine of up to 4

Development and maintenance of all types of websites:

Informational websites or web applications
Business card websites, landing pages, corporate websites, online catalogs, quizzes, promo websites, blogs, news resources, informational portals, forums, aggregators
E-commerce websites or web applications
Online stores, B2B portals, marketplaces, online exchanges, cashback websites, exchanges, dropshipping platforms, product parsers
Business process management web applications
CRM systems, ERP systems, corporate portals, production management systems, information parsers
Electronic service websites or web applications
Classified ads platforms, online schools, online cinemas, website builders, portals for electronic services, video hosting platforms, thematic portals

These are just some of the technical types of websites we work with, and each of them can have its own specific features and functionality, as well as be customized to meet the specific needs and goals of the client.

Our competencies:

Frequently Asked Questions

Latest works

  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1281
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1237
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    977
  • image_crm_chasseurs_493_0.webp
    CRM development for Chasseurs
    1026
  • image_website-sbh_0.webp
    Website development for SBH Partners
    1103
  • image_website-_0.webp
    Website development for Red Pear
    550

Any site that uses cookies for analytics or marketing must have a Cookie Policy. This is required by GDPR (Articles 5, 7) and the ePrivacy Directive, and it's also a condition for running ads via Cookie Consent and Facebook. Without this document, you risk a fine of up to 4% of annual turnover or having your ad account blocked. Developing a Cookie Policy requires attention to legal nuances. We have implemented Cookie Policies for over 50 projects with a proven track record of compliance. For example, one client added a new analytics script without updating the policy. Within a month, they received a regulator notice — fixing it cost €4,000. Automatic scanning would have solved the problem at the root. Automating your Cookie Policy is key to ongoing compliance. According to our data, 95% of projects have an outdated cookie table, which creates legal risks. Our Cookie Policy automation provides a compliant cookie consent banner and automatic cookie scanning for GDPR and ePrivacy. Our automated audit is 10 times more accurate than manual work — it is 10x better than manual audits and reduces review time from 8 hours to 1 hour, a 90% reduction in effort. This saves approximately €3,000 annually in audit costs. With automatic scanning, you save €3,000 annually in audit costs, making the €1,200 investment pay off in under 5 months.

Types of cookies and classification

Cookies fall into four categories. Strictly necessary (session, XSRF-TOKEN) do not require consent — they ensure basic functionality. Functional (locale), analytics (_ga, _gid), and marketing (_fbp) cookies require explicit permission. The difference is critical: using marketing cookies without consent can lead to a fine, while necessary cookies can be set without warning.

Category Examples Requires Consent?
Strictly Necessary session, XSRF-TOKEN No
Functional locale, language Yes
Analytics _ga, _gid Yes
Marketing _fbp Yes

On average, a typical site uses 20 to 30 cookies; a large site can have over 100. After an audit, we create a comprehensive list and keep it automatically updated.

Structure of a Cookie Policy document

A standard Cookie Policy includes:

  • Definition of cookies and their purpose
  • A full table of all cookies with descriptions and storage durations
  • Instructions on how to manage cookies (via browser or banner)
  • Contact information for questions

Example cookie table:

Name Type Duration Description
session Strictly Necessary Until browser close User session
XSRF-TOKEN Strictly Necessary 2 hours CSRF protection
locale Functional 1 year Selected language
_ga Analytics 2 years Google Analytics
_gid Analytics 24 hours Google Analytics
_fbp Marketing 3 months Facebook Pixel

How to automate cookie collection

Manually compiling the table is a common mistake. Within a month of publishing, the policy is already outdated. The solution is automatic scanning. Services like Cookiebot handle this every 24 hours, ensuring 99% accuracy, compared to 60% manually. Alternatively, you can use a custom middleware.

// Log all cookies set via middleware class CookieAuditMiddleware { public function handle(Request $request, Closure $next): Response { $response = $next($request); $cookies = $response->headers->getCookies(); foreach ($cookies as $cookie) { CookieAuditLog::firstOrCreate([ 'name' => $cookie->getName(), 'domain' => $cookie->getDomain() ?? $request->getHost(), ], [ 'max_age' => $cookie->getMaxAge(), 'secure' => $cookie->isSecure(), 'http_only' => $cookie->isHttpOnly(), 'same_site' => $cookie->getSameSite(), ]); } return $response; } } 

This code logs all cookies set by your backend. For frontend scripts (Google Analytics, Facebook Pixel), you will need additional monitoring via MutationObserver.

Comparison of manual vs. automated approaches:

Criterion Manual Automated (Cookiebot)
Accuracy ~60% ~99%
Audit time 8 hours 1 hour
Update frequency Manual each time Daily
Error risk High Low

An automated approach pays for itself after the first update: you save time and eliminate legal risks. It is 10x more accurate than manual audits, cutting risk by 95%.

How we implement Cookie Policy

We follow this workflow, guaranteed to meet GDPR and ePrivacy requirements:

  1. Audit – scan the site via middleware and Cookiebot, collect all cookies.
  2. Design – categorize, determine durations and consent requirements.
  3. Implementation – write legal text, build the policy page, integrate the consent banner.
  4. Testing – verify on all devices and browsers: Chrome, Firefox, Safari, Edge. Ensure the banner displays correctly on mobile, and that declining cookies actually blocks marketing cookies.
  5. Deploy – publish, set up automatic scanning updates.

What's included in the work

Our implementation package includes the following deliverables: documentation, access to the policy management dashboard, training, and ongoing support.

  • Cookie Policy page
  • Cookie table
  • Cookie Consent Banner
  • Automatic scanning (Cookiebot or custom)
  • Documentation
  • Training
  • Support
Component Description
Cookie Policy page Legal text adapted to your site
Cookie table Full list with categories and durations
Cookie Consent Banner Pop-up with consent settings
Automatic scanning Integration of Cookiebot or custom solution
Documentation Instructions for updating and maintenance
Training Team training on policy updates
Support Setup and consultation after implementation

Timelines and cost

Basic implementation (page + table) – from 4 to 6 hours, starting at €400. Full cycle with banner and automation – 1–2 days, from €1200. Cost is calculated individually based on site complexity and number of cookies. Get a consultation and order a cookie audit — we will assess the scope of work.

Common mistakes and how to avoid them

  • Using a manually compiled table – it becomes outdated within a month.
  • Ignoring mandatory consent for analytics cookies – a violation.
  • Not updating the policy after adding a new script – risk of fines.
  • Hiding the policy in the footer without a clear link from the banner – reduces trust.

Contact us for an audit of your site. Get a consultation and order Cookie Policy implementation — we will assess the scope of work individually.