> ## 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.
# Regional Posture Hub — Per-Country Rules Index
> One landing point for every per-country compliance page: a matrix of region → sender and registration requirement → official-law link, the check-the-row-first workflow for send failures, and the template new per-country pages follow.
# Regional Posture Hub — Per-Country Rules Index
Country rules sprawl. Sender registration lives with one regulator,
marketing consent with another, quiet hours with a third — and Orbit's
per-country pages each document one jurisdiction in depth. This page is
the index over all of them: one matrix to find your target country's
page, one workflow to route a send failure to the right surface, and
one template so new country pages stay uniform.
Everything here documents **tenant-owned controls**. Orbit maintains
the country-rules reference and the send-time gates; the legal posture
for each destination is yours. This page is documentation, not legal
advice.
Country coverage is tenant-level — a country listed here is not
necessarily enabled on your account. The live, per-channel answer for
any destination is always
`GET /api/v1/compliance/country-rules`, not this page; this page
points you at the right deep-dive once you know the row.
***
## The country matrix
Start with the live row, then read the page. The first stop for any
destination is the
[Country Compliance Requirements](/compliance/country-requirements)
reference — per country and per channel, it carries the accepted sender
types, the `registration` level (`none` / `recommended` / `required`),
content restrictions, and the opt-out keyword requirement.
```bash theme={null}
curl "https://api.orbit.devotel.io/api/v1/compliance/country-rules?channel=sms®ion=EU" \
-H "Authorization: Bearer $ORBIT_API_KEY"
```
Where a jurisdiction needs more than a matrix row — an opt-in regime, a
no-send window, a statutory register — Orbit ships a dedicated page.
Those pages aggregate here:
| Country | Governing rules | Registration / sender requirement | Dedicated page | Official law |
| --------------------------------------------- | ------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| **United Kingdom** (`GB`) | PECR + UK GDPR (ICO), Ofcom sender rules, TPS/CTPS do-not-call registers | Marketing SMS/email/calls are opt-in; automated calling always requires consent; scrub TPS/CTPS before voice campaigns | [UK PECR and ePrivacy](/compliance/uk-pecr-eprivacy) | [Privacy and Electronic Communications Regulations 2003](https://www.legislation.gov.uk/uksi/2003/2426/contents) |
| **France** (`FR`) | GDPR + the marketing-SMS no-send windows and French STOP requirement | Marketing opt-in mandatory; no marketing sends 20:00–08:00 or Sundays/holidays; STOP au 36111 | [France Marketing SMS Rules](/compliance/fr-marketing-sms-rules) | [GDPR (EU) 2016/679](https://eur-lex.europa.eu/eli/reg/2016/679/oj) |
| **Canada** (`CA`) | CASL (CRTC) for commercial electronic messages | Express or documented implied consent before you send; sender identification and a working unsubscribe in every message | [CASL (Canada)](/compliance/casl-canada-anti-spam) | [S.C. 2010, c. 23](https://laws.justice.gc.ca/eng/annualstatutes/2010_23/) |
| **Australia** (`AU`) | Spam Act 2003 + Do Not Call Register Act 2006 (ACMA) | Consent before commercial electronic messages; identifiable sender; functional unsubscribe; scrub the Do Not Call Register for voice | [Australia Spam Act](/compliance/au-spam-act) | [Spam Act 2003](https://www.legislation.gov.au/C2004A01214/latest/text) |
| **Brazil** (`BR`) | LGPD (ANPD) + Anatel A2P SMS rules | Channel-native sender registration dominates (short codes, WABA); LGPD consent and data-subject rights on top | [Brazil LGPD + Anatel](/compliance/lgpd-brazil) | [Lei nº 13.709/2018](https://www.planalto.gov.br/ccivil_03/leis/l13709.htm) |
| **Mexico** (`MX`) | NOM-184-SCFI disclosure standard (SCT) | Explicit, time-stamped opt-in backed by prescribed disclosure language for promotional SMS | [Mexico NOM-184 Consent](/compliance/mx-nom-184-consent) | [NOM-184-SCFI-2018](https://www.dof.gob.mx/normasOficiales.php?idnota=654749) |
| **India** (`IN`) | TRAI DLT regime | Principal Entity, Headers (sender IDs), and content templates registered on a DLT portal before any A2P SMS delivers | [DLT-India Onboarding](/compliance/dlt-india) | [TRAI TCCCPR 2018](https://www.trai.gov.in/) |
| **European Union / GDPR-class jurisdictions** | GDPR (opt-in regimes across member states) | Lawful basis before processing; the strictest European marketing regimes are opt-in regardless of channel | [GDPR Posture Guide](/compliance/gdpr-posture-guide) | [GDPR (EU) 2016/679](https://eur-lex.europa.eu/eli/reg/2016/679/oj) |
| **United States** (`US`) | TCPA (voice/SMS), CAN-SPAM (email), 10DLC A2P registration | 10DLC brand + campaign vetting for A2P SMS; CAN-SPAM's opt-out-with-content-requirements model for email | [CAN-SPAM](/compliance/can-spam) · [10DLC guide](/guides/10dlc-registration) | [15 U.S.C. § 7701 et seq.](https://www.law.cornell.edu/uscode/text/15/chapter-103) |
Registration levels change at the regulator — always read the live
`registration` field for your target row rather than relying on this
table's snapshot. Where the row says `recommended` or `required`, file
the sender through
[Sender-ID Registration](/compliance/sender-id-registration); where a
country runs its own regime (India DLT, US 10DLC), use the dedicated
flow its page describes.
***
## Check the row first, then the law
When a send to a new destination fails or filters, walk this sequence —
it resolves the large majority of country-launch failures before they
reach support:
`GET /compliance/country-rules?channel=` for the
destination. If `registration` is `required` and you have no
approved Sender ID for that country, the send-time gate holds the
traffic — this is the intended behavior, not a fault.
Confirm your "from" identity is in the row's `sender_types`. An
alphanumeric Sender ID into a long-code-only market (or the
reverse) fails at the carrier even when consent is perfect.
Read `content_restrictions` and `stop_requirement` on the row. A
missing localized STOP keyword (French STOP au 36111 is the
canonical example) or a restricted industry
([list](/compliance/restricted-industries)) blocks or filters the
send independently of registration.
If the row is satisfied and sends still fail, the destination's
dedicated page (matrix above) maps the remaining obligations —
opt-in regimes, no-send windows, statutory scrub registers — to the
Orbit surface that carries each one.
If the gate still looks wrong after both steps, contact support
with the country code, the channel, the `registration` value you
read, and what the send-time gate returned. Support routes
country-rule disputes much faster with those four facts than with a
message ID alone.
The full per-gate error surface is
[Troubleshooting Compliance Error Codes](/compliance/troubleshooting-compliance-error-codes);
the matrix above tells you which page a country-specific code belongs
to.
***
## Template for a new per-country page
New per-country pages follow one shape so the matrix stays browsable.
Copy this outline and fill each section — a page that skips a section
leaves a support gap the hub cannot route around:
1. **Frontmatter** — `title: " Rules"` + a one-line
`description` naming the country, the regime, and the channels it
covers.
2. **Opening paragraphs** — the regulating body and statute, which
channels it governs, and whether the regime is opt-in or opt-out.
State plainly that the posture is tenant-owned: Orbit provides the
surfaces, the tenant owns the legal position.
3. **A ``** — documentation, not legal advice; name the
enforcement exposure (penalties, enforcement body) without advising
on it.
4. **Obligations → Orbit surface table** — one row per statutory duty
mapped to the consent ledger, DNC scrub, suppression, quiet-hours,
or recording-announcement surface that carries the evidence. This
table is the page's spine; it is what the hub's step 4 links into.
5. **Send-time posture** — the org-level knobs the country's regime
argues for (consent-default policy, unknown-marketing policy) with a
copy-pasteable configuration call.
6. **Worked configuration** — a numbered end-to-end sequence a tenant
can follow before first send, ending at a defensible posture.
7. **Related references** — cross-links to the country-requirements
reference, the sender-registration flow, and the sibling regime
pages.
Keep one jurisdiction per page, cite the official law once in the
opening, and add the page to this hub's matrix in the same change —
an unlisted country page is a country page nobody finds.
***
## Related references
* [Country Compliance Requirements](/compliance/country-requirements) —
the live per-country, per-channel rules reference this hub indexes.
* [Sender-ID Registration](/compliance/sender-id-registration) — file
and track a sender registration where a row requires it.
* [Send Gates](/compliance/send-gates) — the send-time enforcement
points these rules feed.
* [Restricted & Prohibited Industries](/compliance/restricted-industries) —
content restrictions that apply on top of every country's posture.
* [Troubleshooting Compliance Error Codes](/compliance/troubleshooting-compliance-error-codes) —
the gate-error surface for step 5 of the routing workflow.