Website development • Denmark market

Cookie Consent Fixes for Websites Operating in Denmark

A cookie banner on a Danish website can look tidy and still break the rules. This happens when analytics or ad tags start before the visitor clicks anything, or when the way to say no sits one click deeper than the Accept button. Danish supervisors look at what the browser actually stores, not at how the banner is designed.

We work on the technical layer of WordPress-based, Magento and custom Laravel sites used by English-speaking and international companies in Denmark. That covers the banner set-up, script blocking, consent records and the cookie list. Our team works remotely from India. This is implementation work, not legal advice.

Request a cookie consent review for your Danish site

Tell us your website address, the platform behind it and which consent tool you currently use. If Digitaliseringsstyrelsen or Datatilsynet has contacted you, mention that so we can prioritise.













The Danish Cookie Order and GDPR consent in practice

Two sets of rules apply at once to a Danish website, and each has its own authority.

The Cookie Order is Executive Order No. 1148 of 9 December 2011, known in Danish as cookiebekendtgørelsen. It covers storing information on, or reading it from, a visitor's device. The rules are technology-neutral, so tracking pixels, local storage, fingerprinting and third-party content are in scope as well as classic cookies. When personal data is collected through these technologies, the GDPR also applies, including its standard for valid consent.

Who supervises what

The Agency for Digital Government (Digitaliseringsstyrelsen) supervises compliance with the Cookie Order. It took over this role from the Danish Business Authority. Datatilsynet, the Danish data protection authority, supervises the data protection side. In May 2025 the two authorities published a joint Danish-language guide on cookies and similar technologies, together with a separate note of practical advice.

Why English-language guidance can mislead

The official English guide to the Cookie Order dates from 2013. It predates both the GDPR and the joint 2025 guidance. If your team relies on it alone, your banner may follow outdated expectations. When we audit your site, we check it against the current Danish material, and we point out anything your legal adviser should confirm.

Six consent checks for websites serving visitors in Denmark

These come from the Danish authorities' published guidance and the GDPR consent standard. Your adviser decides how they apply to your business.

Nothing optional loads first

Only technically necessary cookies may be set before the visitor decides. Analytics, advertising pixels, heatmaps and social embeds stay switched off until consent is given.

A choice per purpose

Visitors can accept statistics but refuse marketing, for example. Optional categories start unticked, and continuing to browse is never treated as a yes.

Decline on the first layer

Datatilsynet's guidance expects visitors to be able to say yes or no actively in the banner itself. Accepting in one click but refusing only behind a details or settings button does not meet that.

Withdrawal that stays within reach

A visitor who changes their mind should be able to reopen the choices from any page and withdraw consent as easily as they gave it.

A record of each choice

You need to be able to show what a visitor agreed to, when, and which banner text they saw. The consent tool stores this, not a spreadsheet.

Accurate cookie information

For each cookie or similar technology, the cookie list states who sets it, what it is for and when it expires. It should match what the site really stores today.

Browser tests we run on your Danish website

We run each scenario in a clean browser profile and record the storage and network requests. You receive the results for every scenario, before and after our changes.

ScenarioWhat we look forAcceptable result
First visit, banner ignoredCookies, local storage and third-party requests while the banner is still openOnly technically necessary items; no analytics or ad calls
Visitor declinesWhether any optional tag fires after refusal, including on later pagesOptional tags stay off for the whole visit and on return
Statistics accepted, marketing refusedWhether categories are respected separatelyAnalytics runs; pixels and remarketing tags do not
Consent withdrawn laterWhether the settings link reopens the banner and stops tagsTags stop and the stored choice updates
Returning visitorWhether the stored choice is read correctly and loggedNo repeated prompts, and no tags set before the stored choice is read

From tag audit to verified script blocking on a Danish site

Inventory

We list every cookie, storage entry, pixel and embedded service the site uses. We also note where each one comes from: theme code, a plugin or module, a tag manager or a hard-coded snippet.

Classification

Each item is labelled as necessary, preferences, statistics or marketing. Any item we cannot classify with confidence goes to you and your adviser for a decision, so nothing stays unclassified.

Banner configuration

We set up your existing consent tool, or a replacement if it cannot block scripts. Accept and decline both appear on the first layer, the categories are granular, and Danish or English text is supplied by you.

Script blocking

Optional scripts are rewired so they only run once their category is accepted. Where an embed cannot be gated, we replace it with a click-to-load placeholder.

Logging and retest

We confirm that consent records are stored with time and banner version, then repeat the browser tests and send you the comparison.

Platform notes: WordPress, Magento and Laravel sites in Denmark

WordPress-based sites and stores

Consent problems on WordPress often come from overlap. A cookie plugin may display the banner while an SEO plugin, a page builder or a marketing add-on injects its own tracking independently. We trace each script to its source and make sure it runs only through the consent layer.

Magento

On Magento stores, analytics and advertising extensions often have their own switches, and these are easy to miss. Full-page caching can also show a stale banner state. We check extension settings, layout files and cache behaviour together.

Custom Laravel applications

Bespoke sites rarely have one central place for third-party code. We add a small consent service that reads the stored choice on each request and only outputs the scripts for categories the visitor has accepted.

What this Denmark cookie project covers and what it leaves out

Covered

  • Browser-level audit of cookies, storage and third-party calls
  • Banner set-up with decline on the first layer and per-purpose choices
  • Script and embed blocking until the relevant consent is given
  • Consent records, a persistent settings link and a cookie list that matches the site
  • Before-and-after test results you can keep on file

Left out

  • Legal advice, or any statement that your site is lawful
  • Writing your privacy policy or the legal wording of the banner
  • Handling correspondence with Digitaliseringsstyrelsen or Datatilsynet
  • Server and hosting security reviews, which are a separate service
  • Predicting how the authorities will rule in a specific case

Working remotely with our India team on Danish cookie fixes

Everyone working on your site is based in Thrissur or in Indiranagar, Bengaluru. We have no one in Denmark. India is 3.5 to 4.5 hours ahead of Danish time, depending on the season. Calls therefore suit your morning, and a fix agreed at lunchtime in Copenhagen can often be tested on staging the same day.

We need an admin or developer login, access to your tag manager if you use one, and preferably a staging copy of the site. All accounts stay in your name.

Illustrative example

Illustrative example, not a real client: an English-language software firm with Danish customers uses a WordPress site. Its banner offers Accept plus a Details link, and declining is only possible inside Details. Our audit finds a marketing pixel added by a form plugin, firing on first load. After the fix, accept and decline sit side by side on the first layer. The pixel waits for marketing consent, and the cookie list names the pixel's provider and expiry.

Who makes the consent changes on your Danish website

The work is done by Appeonix Creative Lab, an Indian micro enterprise registered under Udyam since 2014. Its head office is in Thrissur, Kerala, and it has an office in Indiranagar, Bengaluru. It also holds an Ontario business name registration. We have no office, staff or company in Denmark, and we are not lawyers. Your legal adviser should decide how the Cookie Order and GDPR apply to you, and we implement the technical side of their decisions. You can remove our access at any time.

Questions about cookie consent fixes in Denmark

Who checks cookie compliance in Denmark, Datatilsynet or the Agency for Digital Government?

Both, for different rules. The Agency for Digital Government (Digitaliseringsstyrelsen) supervises the Cookie Order, which covers storing and reading information on visitors' devices. Datatilsynet supervises the GDPR side, which applies when personal data is collected. Their joint guidance from May 2025 covers both.

Can we rely on the English-language guide to the Danish Cookie Order?

Use it with care. The official English guide dates from 2013, before the GDPR, and the current guidance is the 2025 joint guide, which is in Danish. We work against the current material and point out anything your adviser should confirm.

Is a Danish-language banner needed if our website is in English?

Visitors must be able to understand what they are agreeing to. Usually that means the banner uses the same language as the page they are reading. If you publish Danish pages, we set up a Danish banner as well, using text from you or a translator. Whether English alone is enough for your audience is a question for your adviser.

Can simple visitor statistics run before consent?

The Cookie Order exempts only what is technically necessary for the service the visitor asked for, and most analytics tools do not fall into that category. We usually set analytics to wait for the statistics category. If your adviser concludes that a particular set-up is exempt, we configure the site to match their decision.

How would we prove that a visitor actually consented?

Through the consent log. We make sure your tool records each choice with a timestamp, the categories accepted and the banner version shown. We then test that a withdrawal updates the record. You keep access to these logs in your own account.

See what your Danish website loads before visitors decide

Send us your website address and platform. We will reply with the tracking we can see starting before consent and the changes we would make.

Send an enquiry WhatsApp +91 99619 90007