> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orbit.devotel.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Denmark Marketing Act Sender Rules (Markedsføringsloven, Datatilsynet)

> The Denmark posture expanded from the country-requirements matrix: the Marketing Practices Act's opt-in rule for electronic direct marketing, operator-level alphanumeric acceptance with no statutory sender register, and the tenant-owned consent, suppression, and quiet-hours surfaces that carry a Danish campaign.

# Denmark Marketing Act Sender Rules (Markedsføringsloven, Datatilsynet)

Denmark (`DK`) is an enabled Orbit destination for voice and SMS, dialing
prefix `45`. Danish marketing traffic sits under the Markedsføringsloven
(the Marketing Practices Act, consolidated act no. 426 of 3 May 2017, as
amended), which carries the country's opt-in rule for electronic direct
marketing to individuals. The personal-data side of every send rides the
GDPR and the Databeskyttelsesloven under Datatilsynet (the Danish Data
Protection Agency); marketing-practice enforcement sits with the
Forbrugerombudsmanden (the Danish Consumer Ombudsman). This page expands
the DK row of the
[country-requirements matrix](https://docs.orbit.devotel.io/compliance/country-requirements.md) so you can
assemble the posture before your first Danish send.

Denmark is a **tenant-owned burden**. Orbit keeps the country-rules
reference and the send-time surfaces; the legal posture for your Danish
recipients is yours.

> [!NOTE]
>
> This page is documentation, not legal advice. The Marketing Practices
> Act's direct-marketing provisions are enforced against the sender, and
> the Forbrugerombudsmanden publishes enforcement guidance that moves over
> time. Have counsel review your consent practice for Danish recipients;
> Orbit supplies the surfaces.

***

## Accepted sender types and registration level

Denmark has never operated a statutory alphanumeric sender-ID registry.
The Danish market accepts alphanumeric senders at the operator level, and
the operative layer is carrier deliverability rather than law: an
unregistered alphanumeric sender can be relabeled in transit, so register
the sender identity where stable branding matters and treat that as
posture, not statute. Expect the live DK country-rules row to read
`registration: none`:

```bash theme={null}
curl "https://api.orbit.devotel.io/api/v1/compliance/country-rules?country=DK" \
  -H "Authorization: Bearer $ORBIT_API_KEY"
```

```json theme={null}
{
  "country": "DK",
  "sender_types": ["alphanumeric", "long_code"],
  "registration": "none",
  "content_restrictions": ["opt-in direct marketing under the Marketing Practices Act"],
  "stop_requirement": "STOP honored; a working opt-out in every marketing message"
}
```

Registration levels change at the regulator and the operators; always read
the live `registration` field rather than this snapshot. Where a row ever
reads `recommended` or `required`, file the sender through
[Sender-ID Registration](https://docs.orbit.devotel.io/compliance/sender-id-registration.md).

***

## Opt-in and opt-out posture

Electronic direct marketing to Danish individuals requires prior consent;
record it before dispatch and honor revocations on every channel. The
consent record, the suppression ledger, and the stop vocabulary are the
three surfaces the Danish posture lives on:

| Danish obligation | Orbit surface |
| - | - |
| Prior consent for electronic direct marketing to individuals | [Consent Management](https://docs.orbit.devotel.io/compliance/consent-management.md); [GDPR Posture Guide](https://docs.orbit.devotel.io/compliance/gdpr-posture-guide.md) for the lawful basis |
| Identifiable sender and a working opt-out in every marketing message | Suppression ledger; [Opt-Out Keyword Alias Table](https://docs.orbit.devotel.io/compliance/opt-out-keyword-alias-table.md) |
| Danish-language stop vocabulary on Danish sends | Add `STOP` plus the Danish `AFMELD` alias via the [opt-out rules editor](https://docs.orbit.devotel.io/compliance/opt-out-keyword-alias-table.md) so a recipient who replies AFMELD is suppressed |
| Revocation honored across SMS and voice | Suppression ledger; [DNC Scrub](https://docs.orbit.devotel.io/compliance/dnc-scrub.md) for voice campaigns |
| Evidence retention for consent and revocation | [Archival Export](https://docs.orbit.devotel.io/compliance/archival-export.md) |

***

## Quiet hours

Denmark sets no statutory marketing quiet-hours window for SMS; the
recipient's consent and your own sending policy carry the clock. Orbit's
tenant quiet-hours channel toggles default OFF, per
[Quiet Hours FAQ](https://docs.orbit.devotel.io/compliance/quiet-hours-faq.md); for Danish campaigns, opt
in a recipient-local window over Europe/Copenhagen and apply an evening
cutoff consistent with your consent basis. The toggle is tenant-owned and
fails open until you set it, matching the platform posture that every
compliance control except the US federal voice window is yours to
configure.

***

## Number purchase

Denmark is not a member of the platform's regulated
`phone_number_purchase` set (DE, GB, FR, BR, MX, IN, JP, FI, NL, SE), so a
Danish number order does not wait on an approved compliance profile. The
marketing posture above still applies to the traffic you originate from
the number: the purchase gate and the sending posture are separate
obligations, and the lighter purchase path does not soften the opt-in
rule.

***

## Worked configuration before your first Danish send

**1. Record consent with an sms scope**

Capture prior consent for each Danish recipient in
[Consent Management](https://docs.orbit.devotel.io/compliance/consent-management.md) before the first
send; store the source and timestamp so the record is producible.

**2. Add the Danish stop vocabulary**

Confirm `STOP` is active and add `AFMELD` as a Danish alias in the
[opt-out rules editor](https://docs.orbit.devotel.io/compliance/opt-out-keyword-alias-table.md) so
Danish-language replies suppress immediately.

**3. Set the quiet-hours window**

Opt in the tenant quiet-hours toggle for the SMS and voice channels
and set a Europe/Copenhagen evening window per
[Quiet Hours FAQ](https://docs.orbit.devotel.io/compliance/quiet-hours-faq.md).

**4. Read the live row and send**

Re-read `GET /api/v1/compliance/country-rules?country=DK` for the
current `registration` and `sender_types` values, then send. A
revocation received on any channel lands in the suppression ledger
and blocks the next send to that recipient.

***

## Related references

* [Regional Posture Hub](https://docs.orbit.devotel.io/compliance/country-rules-directory.md) — the index
  this page is listed in.
* [Country Compliance Requirements](https://docs.orbit.devotel.io/compliance/country-requirements.md) —
  the live DK row this page expands.
* [Norway Marketing Act Sender Rules](https://docs.orbit.devotel.io/compliance/norway-marketing-act-sender-rules.md)
  and [Portugal ePrivacy + CNPD Sender Rules](https://docs.orbit.devotel.io/compliance/portugal-eprivacy-cnpd-sender-rules.md) —
  the sibling pages this coverage wave adds.
* [Sweden (PTS) Rules](https://docs.orbit.devotel.io/compliance/sweden-pts-rules.md) and
  [Finland Traficom / Ficora Rules](https://docs.orbit.devotel.io/compliance/finland-ficora-rules.md) —
  the neighboring Nordic regimes.
* [Consent Management](https://docs.orbit.devotel.io/compliance/consent-management.md) — where the
  Danish opt-in record lives.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.