Acceptable use policy
The traffic we refuse, the content we restrict, and how this policy is enforced.
Last updated:LEGAL_
Draft: not legal text yet. The headings below show what this page will cover. Nothing on this page is a binding term or a notice.
Scope
To be written: the services and customers this policy applies to.
Traffic we refuse
We refuse: artificially inflated traffic (AIT) and SMS pumping; spam and other unsolicited messages; phishing and smishing content or links; unregistered or spoofed sender IDs; SIM-farm origination; A2P traffic disguised as P2P; content illegal in the origin or destination country.
To be written: the full clause for each type of traffic listed above.
Restricted content
To be written: the categories accepted only per destination and only when declared in the traffic declaration before sending (marketing, iGaming, crypto, political and any other we list), how they are declared and approved, and that undeclared restricted content is a breach: RESTRICTED_
Sender IDs and content
To be written: the sender-ID and content rules, including registration where a destination requires it.
Use of lookups
To be written: that HLR and MNP lookups are for routing and list hygiene only, and never for tracking individuals.
Suspension and termination
To be written: when traffic is suspended and when an account is terminated.
Cooperation with network operators and authorities
To be written: how we cooperate with network operators and authorities when a breach is found.
Reporting abuse
To be written: how to report abuse (ABUSE_
Changes to this policy
To be written: how changes are announced and dated.
Talk to the team.
Ask for rates on the destinations and traffic you send, request a test route, or pick a time to meet.