Cookie consent, self-hosted.

One script tag. GDPR/CCPA-aware banners, category-blocked scripts, and a real consent audit trail — a drop-in replacement for Cookiebot's own public JS API, so migrating an existing site doesn't mean rewriting your tagged scripts.

Get a site set up Admin login

Already runs across the Digi Soft UG product portfolio — see digi-soft.tech for the full write-up.

🍪

Compatible snippet

window.Cookiebot.consent.*, CookiebotOnAccept, and <script type="text/plain" data-cookieconsent> blocking — the same public API real Cookiebot exposes.

🌍

Region-aware

Opt-in banners for GDPR/UK/CH visitors, opt-out for US traffic, no banner where neither applies — defaults to the more protective posture whenever region can't be determined.

📋

Real audit trail

Every consent decision is logged with a timestamp and region — proof of consent, not just a banner that disappears after one click.

How it works

1

Add one script tag

We create a site, you get back a site_key and one <script src="…/c/{key}/consent.js"> tag. No account, cookie, or SDK for your visitors to load.

2

The right banner, automatically

A visitor's country decides the posture: opt-in for GDPR/UK/CH, opt-out for the US, no banner elsewhere — unknown always falls back to the safer, opt-in posture.

3

Every decision, on record

Each accept/decline is timestamped and region-tagged in your own dashboard — real proof of consent if you're ever asked for it, not just a cookie in the visitor's browser.

For companies & site owners

  • ✓ One dashboard for every domain you run — add a new site in seconds, each gets its own script tag and settings.
  • ✓ Migrating off Cookiebot needs no script rewrite — the same window.Cookiebot globals and events your existing tags already listen for.
  • ✓ A real, queryable consent log per site — not just a banner that fires and forgets.
  • ✓ Declare your cookies once (name, category, provider, purpose, expiry) and expose them at a public JSON endpoint for your own "which cookies do we use" page.
  • ✓ Self-hosted by Digi Soft UG on EU infrastructure — no US-based consent vendor in your data-processing chain.

Currently used internally across the Digi Soft UG product portfolio; onboarding a new external site today is a manual setup — email us and we'll get you set up directly.

For your visitors

  • ✓ A choice, not a wall — necessary cookies always work; everything else is opt-in where the law requires it.
  • ✓ Nothing tracking-related loads until they've actually chosen to allow that category.
  • ✓ No raw IP address is ever stored — consent records use a one-way hash, unique enough to avoid duplicate prompts without being reversible back to a real visitor.
  • ✓ Preferences can be reopened and changed any time via the same widget, not just on first visit.

Frequently asked

Is this a real replacement for Cookiebot?

For the consent-banner and script-blocking side, yes — the public JS API is deliberately shaped to match Cookiebot's own, so existing tagged scripts and event listeners keep working unchanged. It doesn't (yet) include Cookiebot's automated cookie-scanning crawler; cookie declarations are entered once, manually, per site instead.

Where is the data hosted?

On Digi Soft UG's own EU infrastructure (Germany), the same setup that runs the rest of the Digi Soft UG product portfolio. Nothing is sent to a third-party consent vendor.

Does it slow my site down?

The embed is one small, self-contained script — no external SDK bundle, no tracking pixels of its own.

How do I get a site added?

Onboarding is currently manual — email info@digi-soft.tech with your domain and which cookie categories you use, and we'll set it up and send you the script tag.

Want this on your site?

A Digi Soft UG product — built and operated by the same team behind the rest of the portfolio.

info@digi-soft.tech