Acceptable Use Policy.
Overview
What may and may not be sent over BroadNet's network. This policy forms part of the Master Services Agreement and applies to every account, on every channel, in every market we route to.
Scope
This policy applies to all traffic submitted to BroadNet over any interface — REST, SMPP, the dashboard, or a partner integration — across SMS, voice, WhatsApp, RCS and email. It binds the account holder and anyone they permit to send. Where a customer resells our capacity, the customer is responsible for their own end users' compliance with this policy.
Consent and opt-in
Send only to recipients who have given verifiable consent to receive the category of message you are sending, or where a specific regulatory exemption applies (for example transactional one-time passcodes to a customer completing an authentication they initiated). Consent must be demonstrable on request: purchase records, sign-up logs, or a documented opt-in flow. Consent obtained for one brand or purpose does not transfer to another. Purchased, scraped, rented or otherwise third-party lists are not acceptable evidence of consent.
Opt-out and STOP handling
Every marketing or promotional message must carry a working opt-out. STOP, UNSUBSCRIBE and the local-language equivalents are honoured automatically on BroadNet-managed sender IDs and short codes, and suppression is applied at the platform level within the timeframe the destination market requires. Customers running their own opt-out handling must suppress within the same window and must not re-add a suppressed number without fresh consent.
Sender identity
Sender IDs must be registered where the destination market requires registration, and must accurately identify the brand actually sending. Impersonating another business, a bank, a government body, an operator or BroadNet is prohibited. Alphanumeric sender IDs, short codes and 10DLC registrations obtained through BroadNet may only be used for the traffic and brand they were registered for.
Prohibited content
The following may not be sent over the network in any market: phishing, smishing or any message designed to obtain credentials, payment details or one-time passcodes under false pretences; malware, or links distributing it; fraud, advance-fee schemes and deceptive financial offers; content that sexually exploits or endangers minors; incitement to violence or unlawful discrimination; and any content unlawful in either the origin or the destination market.
Restricted categories
Some categories are permitted only where the destination market allows them and only with prior written approval on the account: gambling and betting; adult content; cryptocurrency, digital assets and high-risk financial promotions; pharmaceuticals, tobacco, vaping, alcohol and cannabis; debt collection; and political or electoral messaging. Approval is granted per market, because a category lawful in one country is frequently prohibited in the next. Sending a restricted category without approval is a breach of this policy.
Network and routing integrity
Traffic must be submitted for genuine delivery to real subscribers. The following are prohibited: artificially inflated traffic and SMS pumping, including any arrangement that generates messages to numbers a fraudulent party controls or profits from; sender-ID spoofing and SIM-box or grey-route origination; deliberate evasion of an operator's firewall, filtering or registration requirements; and any attempt to disguise the true nature, volume or origin of traffic. BroadNet routes operator-direct and screens submissions at multiple checkpoints; traffic engineered to defeat that screening is a material breach.
Sanctions and restricted destinations
BroadNet does not serve, provision, or route traffic to countries or territories subject to comprehensive international sanctions or embargoes. Every destination is screened, and customers may not attempt to reach a restricted destination through routing, number manipulation, or any intermediary. This restriction is absolute and is not subject to commercial exception.
Volume, throughput and testing
Respect the throughput agreed for your account. Load testing against production requires prior notice so that operator relationships are not put at risk by traffic patterns indistinguishable from an attack. Use your test credentials for functional testing. Sudden unannounced volume changes of an order of magnitude may be throttled while we verify them — this protects your delivery rates as much as the network.
Data protection
Send only the personal data necessary for the message, and do not place special-category data — health, biometric, financial account credentials, or similar — in message bodies. Message content is processed under the Data Processing Agreement and retained per the retention terms stated there.
Reporting abuse
Report suspected abuse of the network, phishing traffic purporting to originate from a BroadNet route, or a compromised account to abuse@broadnet.me. Security vulnerabilities go to security@broadnet.me — see our disclosure policy for the machine-readable contact.
Enforcement
Where traffic breaches this policy BroadNet may filter or suspend the affected traffic, suspend the sender ID or the account, and in serious or repeated cases terminate the agreement. Action is proportionate and, wherever the circumstances allow, preceded by notice — but traffic that puts subscribers, an operator relationship or the network at immediate risk may be stopped first and discussed after. Operators may independently block traffic that breaches their own rules, and we are obliged to act on their instruction.
Changes
This policy changes as regulation does — market rules for A2P messaging move continually. Material changes are notified to account contacts in advance. The version on this page is the operative one.
Definitions
Capitalised terms used in this document carry the meanings assigned to them in the Master Services Agreement and the BroadNet Data Processing Agreement. Where conflict arises, the MSA prevails for commercial terms and the DPA prevails for data-protection terms.
- BroadNet
- BroadNet Technologies Sarl, headquartered in Dubai, United Arab Emirates, and its wholly-owned subsidiaries.
- Customer
- The legal entity that has executed an order form or Master Services Agreement with BroadNet.
- Services
- The messaging APIs, dashboards, and supporting infrastructure provided by BroadNet under an order.
- Personal Data
- Has the meaning given in Article 4(1) GDPR; equivalent definitions apply under UAE PDPL and Saudi PDPL.
Questions?
Questions about this document or our legal terms? Our legal team responds within two business days.
legal@broadnet.me