Denmark · Executive Order no. 1148 of 9 December 2011 on information and consent for storing or accessing information in end users' terminal equipment (cookiebekendtgørelsen)

Cookie consent in Denmark: what the cookie order requires

In Denmark, nobody may store or read information on a user's device, or let a third party do so, unless the user consents after receiving adequate information, under section 3 of the cookie executive order (cookiebekendtgørelsen, no. 1148 of 2011). The Agency for Digital Government (Digitaliseringsstyrelsen) supervises the order and ordered Meta and Google to fix their consent banners in 2023, while Datatilsynet handles the GDPR side. Their joint guidance of May 2025 requires consent for visitor statistics and a reject option as visible as accept.
Published 21 October 2026 · By the Cookiequiet team · Markdown

Quick facts

Applies toAny natural or legal person that stores or reads information on an end user's device in Denmark, or lets a third party do so through its website or app
Consent modelOpt-in after adequate information; the joint guidance applies the GDPR consent standard
Cookie ruleSection 3 of executive order no. 1148 of 9 December 2011 (cookiebekendtgørelsen), in force since 14 December 2011
AuthorityDigitaliseringsstyrelsen (Agency for Digital Government) for the cookie order; Datatilsynet for the GDPR
Maximum fineThe order sets a criminal fine (bøde) with no fixed ceiling (section 5); GDPR fines up to 20 million euros or 4% of turnover, imposed by the courts
Key guidanceJoint guidance of Digitaliseringsstyrelsen and Datatilsynet, Brug af cookies og lignende teknologier (May 2025)

Which Danish rule regulates cookies?

Denmark transposes Article 5(3) of the ePrivacy Directive in an executive order rather than a statute: Bekendtgørelse nr. 1148 af 9. december 2011 om krav til information og samtykke ved lagring af eller adgang til oplysninger i slutbrugeres terminaludstyr, known as the cookie order (cookiebekendtgørelsen). It was issued under the Act on Electronic Communications Networks and Services and has applied since 14 December 2011.

Section 3(1) is the core rule. Natural or legal persons may not store information, or gain access to information already stored, in an end user's terminal equipment, or let a third party do so, unless the end user consents after receiving adequate information. Section 3(2) defines adequate information. At a minimum it must:

  1. be written in clear, precise and easily understandable language;
  2. state the purpose of the storage or access;
  3. identify every natural or legal person behind the storage or access;
  4. give the user immediate access to refuse or withdraw consent, with clear instructions on how to use it;
  5. be given to the user directly, collected in one place and clearly.

Where storage happens through a website or app, the information must also stay permanently available through a direct and clearly marked link on that service.

The order defines consent as a voluntary, specific and informed indication of wishes. The joint guidance applies the stricter GDPR standard, which also requires an unambiguous, active choice.

Which cookies are exempt?

Section 4 has the two exemptions of the Directive: storage or access whose sole purpose is to transmit a communication over a network, and storage or access required for the provider to deliver an information society service the user explicitly asked for. Section 4(2) adds that storage is required when it is a technical precondition for delivering the service in line with its purpose.

The May 2025 guidance gives examples of technically necessary technologies: login and user validation, shopping carts, settings the user actively chose such as language or font size, authentication on restricted services and load balancing. It also covers third-party fonts, but only when the third party uses the data solely to deliver the fonts and not to track users across sites.

Yes. The guidance states plainly that you must obtain consent if you use cookies and similar technologies to generate visitor statistics or show personalized ads. There is no analytics exemption in Danish law. The order applies whatever information is collected, so even statistics that are not personal data need consent if they rely on storing or reading something on the device.

The joint guidance of Digitaliseringsstyrelsen and Datatilsynet describes the banner in detail:

  • Refusing as easy as accepting. Users must be able to decline, and it must be as easy to refrain from consenting as to consent. A banner with only an accept button is invalid.
  • No nudging. The guidance shows a green OK button next to a pale Reject as an example of unlawful nudging: refusing must appear as clearly as accepting. Showing the banner again on every visit is also pressure.
  • Granular purposes. Users must be able to consent per purpose, and vague labels such as "third-party technologies" are not specific enough.
  • First-layer information. The first layer must at least name the organization and its partners, the purposes, the types of data, whether data goes to third parties and the right to withdraw consent. Cookie names, providers and expiry dates can sit on a second layer.
  • Easy withdrawal. For example a clear link at the top or bottom of every page, or a fixed icon that reopens the choices.
  • Renewal. It will often be appropriate to renew consent once a year, and to ask again a user who refused once a year.
  • Documentation. You must be able to document your consent procedure, for example with screenshots of each version of the banner.

Cookie walls are not banned outright. They can be acceptable when users get a reasonable alternative, such as access for a reasonable price, and Datatilsynet has set four criteria for that alternative. A wall with no alternative does not produce voluntary consent.

Two authorities share the work. Digitaliseringsstyrelsen, the Agency for Digital Government, supervises the cookie order. Datatilsynet, the Danish data protection authority, supervises the GDPR and the Danish Data Protection Act when cookies process personal data.

The most visible case so far came on 6 November 2023, when Digitaliseringsstyrelsen announced orders against Meta Platforms for da-dk.facebook.com and against Google for google.dk. The agency found that their cookie solutions breached the order and gave both companies four weeks to let users consent per main purpose, give users immediate, persistent and clearly marked access to withdraw consent, and provide persistent information about all cookies used in clear language.

How high are the fines in Denmark?

Section 5 of the cookie order punishes breaches of section 3 with a fine (bøde), and companies can be held criminally liable. It is a criminal fine imposed by the courts, not an administrative penalty, and the order sets no maximum. Denmark also has no administrative GDPR fines: Datatilsynet reports a case to the police and the courts set the fine, within the GDPR ceiling of 20 million euros or 4% of worldwide annual turnover. We found no court fine under the cookie order as of October 2026.

Does the banner have to be in Danish?

The guidance says you should, as far as possible, write the consent solution in the same language as the rest of your service, so a Danish-language site should have its banner and privacy policy in Danish. It also asks for plain language without unnecessary technical or legal terms.

How Cookiequiet fits

Setting up Cookiequiet takes one script tag and about five minutes: the scan fills the cookie table, Reject all sits next to Accept all on the first layer by default, and the banner is shown in Danish to visitors whose browser asks for it, among 24 languages. Each choice goes into a consent log, and geo-targeting is included on every plan, including Free. The cookie scanner lists what your site sets, which the guidance recommends checking each time you add a feature, and the Reject all guide covers the button design.

Questions

Digitaliseringsstyrelsen, the Agency for Digital Government, supervises the cookie executive order. Datatilsynet supervises the GDPR when cookies process personal data. The two published joint guidance on cookies and similar technologies in May 2025.
Yes. The joint guidance says consent is required when cookies or similar technologies are used to generate visitor statistics. Only technically necessary storage, such as login, shopping cart and load balancing, is exempt.
Only with a reasonable alternative. A wall that blocks the site until the user accepts, with no other option, does not give voluntary consent. A paid alternative can work if the price is reasonable and the paid version collects no more data than it needs.
The rules set no fixed period. The joint guidance says it will often be appropriate to renew consent once a year, and to ask a user who refused again once a year, and always when the purposes change.

Put a quiet banner on your website today

Free for one website with every core feature, no card and no trial clock. Upgrade a website to Starter for $3 a month to match your brand with AI and drop the branding, or to Pro for $9 to design it with the AI agent.