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

# Poland UKE + RODO Sender Rules

> The Poland A2P SMS posture expanded from the country-requirements matrix: UKE telecom oversight and RODO data protection, the live PL country-rules row, sender-ID acceptance across Orange, Play, Plus, and T-Mobile PL, Art. 172 marketing opt-in with consent records, and the Polish STOP vocabulary you add yourself.

# Poland UKE + RODO Sender Rules

Poland (`PL`) is one of the larger A2P SMS markets in the EU, and its
posture joins a telecom consent regime enforced by UKE to the GDPR as
applied in Polish law (RODO). Marketing traffic into Poland requires
prior opt-in, a consent record you can produce, and an opt-out path that
speaks Polish. This page expands the PL row of the
[country-requirements matrix](/compliance/country-requirements) so you
can close those items deliberately instead of re-reading one JSON blob
per launch.

Poland is a **tenant-owned burden**. Orbit never mandates your posture —
it keeps the [country-rules reference](/compliance/country-requirements)
that feeds the send-time gates, and it gives you the consent ledger,
quiet-hours, opt-out, and DNC surfaces below. The legal posture is yours.

<Note>
  This page is documentation, not legal advice. The Polish rules bind
  the sender, not the platform: Art. 172 consent and RODO accountability
  are enforced against you, not against Orbit. Have counsel review your
  consent capture and opt-out handling; Orbit supplies the surfaces.
</Note>

***

## The regulators: UKE for telecom, UODO for RODO

Two authorities split the Polish surface:

| Authority | Remit | What it means for you |
| - | - | - |
| UKE (Urząd Komunikacji Elektronicznej) | The telecom regulator: enforces the Art. 172 consent regime for marketing over electronic communications, and sender identification rules | Marketing SMS without prior consent is an Art. 172 violation pursued against the sender. Sender-ID spoofing and mislabelled traffic sit with UKE. |
| UODO (Urząd Ochrony Danych Osobowych) | The data-protection regulator: RODO, the GDPR as applied through Poland's implementing regulation | The consent conditions, the record-keeping, and the data-subject rights behind every PL contact row are yours as controller. |

The marketing consent rule lives in Art. 172 — first of the
Telecommunications Law (Prawo telekomunikacyjne), carried over into the
electronic-communications statute that replaced it. The substance is
unchanged: prior consent is required before you place marketing over
electronic communications, and that consent must satisfy the RODO
conditions. Opt-in is therefore the PL default posture, not a
preference.

***

## The live PL country-rules row

Read the PL row live rather than trusting any static copy, because the
row is tenant-upsertable and your admin may have tightened it:

```bash theme={null}
curl "https://orbit.devotel.io/api/v1/compliance/country-rules?channel=sms" \
  -H "Authorization: Bearer <token>"
```

Find the PL entry and read the same four fields the FR and DE rows
carry:

| Field | How to read it for PL |
| - | - |
| `sender_types` | Which sender forms the market accepts — alphanumeric and long code both work in PL; see the next section for operator posture. |
| `registration` | Whether the sender ID needs a registration entry before sends gate on it. Treat `recommended` as effectively required for production volumes. |
| `content_restrictions` | The market's content posture, including the opt-in requirement that reflects Art. 172. |
| `stop_requirement` | The opt-out obligation. PL carries no statutory keyword of its own in the seed — see the STOP vocabulary section for what to add. |

The [country-rules directory](/compliance/country-rules-directory) and
the console's [country-rules view](/guides/compliance-country-rules-console)
render the same row if you prefer a screen to a curl.

***

## Sender-ID acceptance across Orange, Play, Plus, and T-Mobile PL

Poland's four mobile networks — Orange Polska, Play (P4), Plus
(Polkomtel), and T-Mobile Polska — all accept alphanumeric sender IDs on
A2P traffic, alongside long codes for conversational use. Acceptance is
not the same as indifference:

| Operator | Alphanumeric sender ID | Practical note |
| - | - | - |
| Orange Polska | Accepted | Unregistered names are more likely to be filtered or relabelled; register the name you send from. |
| Play (P4) | Accepted | Same posture — registration keeps the sender stable and deliverable. |
| Plus (Polkomtel) | Accepted | Spoofing filters act on unregistered alphanumerics; a registered entry avoids relabelling. |
| T-Mobile Polska | Accepted | Consistent with the other three: register for stable delivery. |

The shared rule: alphanumeric sending works out of the box, but a
registered sender ID is the difference between delivered-as-branded and
relabeled-to-a-long-code. Submit the names you plan to send from through
[Sender-ID Registration](/compliance/sender-id-registration) before the
first production campaign, and check the PL `registration` level in the
live row above for whether the [send-time gate](/compliance/send-gates)
holds sends on it.

***

## Marketing opt-in under Art. 172, consent records under RODO Art. 7

Art. 172 makes PL an opt-in market: the consent record must exist before
the first marketing send, and RODO Art. 7 sets the conditions that record
must satisfy:

| RODO Art. 7 condition | What your consent record must show |
| - | - |
| Demonstrable | Who consented, when, on which channel, and to which wording — the consent ledger captures this; see [Consent Management](/compliance/consent-management). |
| Freely given and specific | Consent captured for "marketing by SMS" is not consent for voice calls or partner lists. Scope the record to `sms`. |
| Informed | The capture surface stated who sends and what. Keep the capture wording tied to the record. |
| Easy to withdraw | Withdrawal must be as easy as giving consent — this is exactly what the Polish STOP vocabulary section below wires up. |

Orbit binds each sent message to the consent record it was sent under,
so a PL marketing send carries its own proof of consent into your
evidence export — see
[Consent Receipt Integrity](/compliance/consent-receipt-integrity) and
the [GDPR posture guide](/compliance/gdpr-posture-guide) for the
EU-side record-keeping posture. Record the consent entry with `sms`
scope before dispatch; a PL send without one is an Art. 172 exposure
you keep at scale.

***

## The Polish STOP vocabulary is yours to add

Here is the gap to close deliberately: the shipped
[opt-out keyword alias table](/compliance/opt-out-keyword-alias-table)
has **no Polish row**. The table seeds English, Turkish, German,
Spanish, French, Portuguese, Italian, Arabic, and Dutch — so a Polish
contact is covered only when they type the bare English `STOP`. The
natural Polish opt-outs — `WYPISZ` ("unsubscribe me") and `ZREZYGNUJ`
("I resign") — are not seeded, and a PL contact typing `WYPISZ` today
does not reach your suppression list until you add it.

Add the Polish synonyms the same way the alias-table page documents for
any custom vocabulary, over
`POST /api/v1/settings/opt-out-rules`:

```bash theme={null}
curl -X POST "https://orbit.devotel.io/api/v1/settings/opt-out-rules" \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{
    "keyword": "WYPISZ",
    "channel": "sms",
    "action": "opt-out",
    "auto_reply_text": "Zrozumiano. Nie będziesz już otrzymywać od nas wiadomości SMS."
  }'
```

Repeat the call for `ZREZYGNUJ` (and, if your lists re-subscribe over
SMS, the opt-in counterparts with `"action": "opt-in"`). Two properties
of the matcher do the heavy lifting for you: matching is
case-insensitive and normalises diacritics, so one stored spelling also
catches its variants (`ZREZYGNUJĘ`, `Wypisz!`); and a matched opt-out
suppresses the number across channels, not just SMS, exactly as the
alias-table page describes. The same rows are editable in the dashboard
under **Messages → SMS → Opt-out Rules** — see
[Opt-Out & Opt-In Rules](/guides/opt-out-rules).

Custom additions widen the trigger surface; they never weaken the
mandatory `STOP` path, and they never unblock a number a suppression
entry already holds.

***

## Polish do-not-call: the tenant owns the scrub

Poland's do-not-call register ("Lista Nie Dzwonimy", reinforced by the
2023 amendments) is a voice-marketing surface: numbers on it must not
receive unsolicited marketing calls. For SMS your gate is Art. 172
consent either way — a number absent from any DNC list still needs a
consent record before you send. Where the register bites is any PL voice
campaign, and the operational answer is the same as elsewhere: Orbit
does not scrub for you, because coverage posture is a tenant decision.
Load the register into your scrub list and let the send-time suppress
do the work — see [DNC Scrub](/compliance/dnc-scrub) for the import and
sync surfaces.

***

## Quiet hours convention

Poland sets no statutory SMS no-send window of the FR kind. The market
convention is simply civil hours: keep marketing sends inside
roughly 08:00–20:00 recipient time (Europe/Warsaw), and treat Sundays as
low-value send days. That convention is reference data, not a platform
gate — Orbit's tenant quiet hours default **off / fail-open**, and you
opt into enforcement deliberately:

| | Tenant quiet hours | PL convention |
| - | - | - |
| Whose rule | Yours — an opt-in tenant control | The market's — a convention, not a statute |
| Default | **Off / fail-open** | Reference data, surfaced in the PL row, not enforced as a platform gate |
| Configured via | [Quiet-Hours Configuration](/guides/quiet-hours-configuration) | Nothing to configure — honor it at the campaign level |

If you run PL marketing traffic, set tenant quiet hours to
08:00–20:00 Europe/Warsaw so the control enforces what the convention
asks for.

***

## PL launch checklist

Narrowed from the generic launch checklist in
[Country Compliance Requirements](/compliance/country-requirements) to
the PL row:

<Steps>
  <Step title="Look up the PL row">
    Call `GET /api/v1/compliance/country-rules?channel=sms` and read the
    PL entry's `sender_types`, `registration`,
    `content_restrictions`, and `stop_requirement`.
  </Step>

  <Step title="Register the sender ID">
    Alphanumeric works at all four MNOs; register the name through
    [Sender-ID Registration](/compliance/sender-id-registration) so it
    stays branded and deliverable.
  </Step>

  <Step title="Capture opt-in before the first send">
    Record a consent entry with `sms` scope that satisfies the RODO
    Art. 7 conditions; PL is opt-in, not opt-out.
  </Step>

  <Step title="Add the Polish STOP vocabulary">
    `POST /api/v1/settings/opt-out-rules` with `WYPISZ` and `ZREZYGNUJ`
    so Polish opt-outs actually reach your suppression list.
  </Step>

  <Step title="Scrub voice campaigns against the DNC register">
    Load Lista Nie Dzwonimy into your scrub list for any PL voice
    traffic — see [DNC Scrub](/compliance/dnc-scrub).
  </Step>

  <Step title="Set quiet hours to the PL convention">
    08:00–20:00 Europe/Warsaw via
    [Quiet-Hours Configuration](/guides/quiet-hours-configuration) — a
    deliberate opt-in, not an Orbit default.
  </Step>

  <Step title="Launch">
    With consent recorded, the sender registered, Polish opt-outs
    wired, and quiet hours set, start sending.
  </Step>
</Steps>

***

## Related references

* [Country Compliance Requirements](/compliance/country-requirements) —
  the full matrix this page expands one row of.
* [Opt-Out Keyword Alias Table](/compliance/opt-out-keyword-alias-table) —
  the shipped vocabulary that lacks a Polish row, and the custom-rule
  flow this page applies to PL.
* [Consent Management](/compliance/consent-management) — where the
  Art. 172 opt-in record lives.
* [Consent Receipt Integrity](/compliance/consent-receipt-integrity) —
  the message-to-consent binding that makes each PL send provable.
* [GDPR Posture Guide](/compliance/gdpr-posture-guide) — the EU-side
  consent and record-keeping posture behind RODO.
* [Sender-ID Registration](/compliance/sender-id-registration) — the
  submit-and-track flow for the four PL MNOs.
* [DNC Scrub](/compliance/dnc-scrub) — the tenant-owned scrub surface
  for Lista Nie Dzwonimy.
* [Quiet-Hours Configuration](/guides/quiet-hours-configuration) — the
  tenant-owned opt-in control you use to honor the PL convention.


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