> ## 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.

# Norway Marketing Act Sender Rules (Markedsføringsloven, Nkom)

> The Norway posture expanded from the country-requirements matrix: the Marketing Control Act and e-commerce act's opt-in rule for electronic direct marketing, Nkom telecom oversight, the national reservation register scrub posture for voice, and the tenant-owned consent, suppression, and quiet-hours surfaces that carry a Norwegian campaign.

# Norway Marketing Act Sender Rules (Markedsføringsloven, Nkom)

Norway (`NO`) is an enabled Orbit destination for voice and SMS, dialing
prefix `47`. Norwegian marketing traffic sits under the
Markedsføringsloven (the Marketing Control Act, act no. 2 of 9 January
2009\) together with the e-handelsloven (the e-commerce act), which carry
the country's opt-in rule for electronic direct marketing to individuals.
Telecom-side oversight sits with Nkom (the Norwegian Communications
Authority); marketing-practice enforcement with the Forbrukertilsynet (the
Norwegian Consumer Authority). Norway applies the GDPR and the ePrivacy
consent rule through the EEA Agreement, with the national
reservasjonsregisteret (reservation register) as the do-not-contact list
for covered telephone marketing. This page expands the NO row of the
[country-requirements matrix](https://docs.orbit.devotel.io/compliance/country-requirements.md) so you can
assemble the posture before your first Norwegian send.

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

> [!NOTE]
>
> This page is documentation, not legal advice. The Marketing Control
> Act's direct-marketing provisions are enforced against the sender, and
> the reservation register's coverage has its own statutory scope. Have
> counsel review your consent and scrub practice for Norwegian
> recipients; Orbit supplies the surfaces.

***

## Accepted sender types and registration level

Norway operates no statutory alphanumeric sender-ID registry. Norwegian
operators accept alphanumeric senders, and the live NO country-rules row
reads `registration: recommended`: registration is a deliverability
posture the market argues for, not a statutory filing. Confirm how
Norwegian carriers handle your sender before a branded campaign, and file
it through [Sender-ID Registration](https://docs.orbit.devotel.io/compliance/sender-id-registration.md)
where stable branding matters.

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

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

***

## Opt-in and opt-out posture

Electronic direct marketing to Norwegian individuals requires prior
consent; the e-commerce act carries the ePrivacy side of that rule for
electronic communications. Record consent before dispatch, and honor
revocations on every channel. For voice campaigns, the reservasjonsregisteret
is the national scrub layer: registered numbers on the reservation
register must not receive covered marketing calls, so scrub it before a
Norwegian voice campaign alongside your own suppression ledger.

| Norwegian 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) |
| Norwegian-language stop vocabulary on Norwegian sends | Add `STOP` plus the Norwegian `STOPP` alias via the [opt-out rules editor](https://docs.orbit.devotel.io/compliance/opt-out-keyword-alias-table.md) |
| Reservation-register scrubbing before voice campaigns | [DNC Scrub](https://docs.orbit.devotel.io/compliance/dnc-scrub.md) against the reservasjonsregisteret, on top of the suppression ledger |
| Evidence retention for consent and revocation | [Archival Export](https://docs.orbit.devotel.io/compliance/archival-export.md) |

***

## Quiet hours

Norway 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 Norwegian campaigns,
opt in a recipient-local window over Europe/Oslo 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

Norway 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
Norwegian 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 Norwegian send

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

Capture prior consent for each Norwegian 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 Norwegian stop vocabulary**

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

**3. Scrub the reservation register for voice**

Before any Norwegian voice campaign, run the
[DNC Scrub](https://docs.orbit.devotel.io/compliance/dnc-scrub.md) against the reservasjonsregisteret
and keep the suppression ledger current for every channel.

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

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

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

Re-read `GET /api/v1/compliance/country-rules?country=NO` 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 NO row this page expands.
* [Denmark Marketing Act Sender Rules](https://docs.orbit.devotel.io/compliance/denmark-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) — the neighboring
  Nordic regime with its own NIX scrub posture.
* [Consent Management](https://docs.orbit.devotel.io/compliance/consent-management.md) — where the
  Norwegian opt-in record lives.


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