📄️ Country-Specific Requirements
Messaging regulation in Africa is set at the national level. Each regulator defines its own rules for sender ID registration, content restrictions, opt-in requirements, and quiet hours. This page summarizes the requirements that apply when sending through AfriRoute, country by country.
📄️ Phone Number Formatting
AfriRoute requires all destination numbers in E.164 format: a leading +, the country code, and the national subscriber number with no spaces, dashes, or parentheses. Correct formatting is the single biggest factor in delivery success and avoids wasted credits on undeliverable numbers.
📄️ Sender ID Registration
A sender ID is the name or number that appears as the "from" on a recipient's phone. Across most African markets, alphanumeric sender IDs (for example MyBrand) must be registered with the national regulator and the carriers before they can be used. Unregistered traffic is increasingly filtered, masked, or blocked outright.
📄️ Data Protection & Privacy
When you send messages through AfriRoute you are processing personal data — phone numbers, names, and sometimes financial or health details inside message bodies. African data protection laws, alongside the EU GDPR for any EU residents you contact, impose specific obligations on how that data is collected, stored, and used. This page explains how AfriRoute helps you meet them.
📄️ GDPR Compliance
If any of your recipients are located in the European Union — for example diaspora customers, EU-based staff, or travelers — your messaging falls under the EU General Data Protection Regulation (GDPR), regardless of where your business is based. AfriRoute is built to support GDPR compliance for these flows alongside African data protection laws.
📄️ PCI DSS Compliance
How AfriRoute handles cardholder data, reduces your PCI DSS SAQ scope through tokenization, and what merchants remain responsible for.