DraftThis page is a draft. Values set in grey monospace are placeholders and are not confirmed yet.
Compliance and trust
Our rules, written down.
Acceptable use, anti-fraud, KYC and data protection: summarised here, set out in full in our trust pack.
Acceptable use
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.
We suspend traffic that breaks these rules, and we cooperate with network operators and the authorities.
Some content categories are restricted, not refused: marketing, iGaming, crypto and political messaging are accepted only on destinations where local rules and the route allow them, and only when listed in your traffic declaration before you send. The rate deck states what each destination accepts: RESTRICTED_
CONTENT_ POLICY. CONFIRM_ BEFORE_ PUBLISH
Anti-fraud and AIT
We monitor each account for AIT signals: traffic velocity, unusual destination and number-range patterns, and conversion rates where you share them. When we see AIT we pause the affected traffic, show you what we saw and agree next steps. Disputes are raised within DISPUTE_
Our controls follow the principles set out in the industry’s SMS anti-fraud commitment: fraud-prevention targets, detection processes, blocking fraudulent number ranges, avoiding payment flows to fraudsters, and sharing information on suspicious traffic. CONFIRM_
KYC, KYB and KYT
Before a rate deck or a test route: a short company check (your company and domain). Before live traffic: company documents, beneficial ownership, licences where they apply, the authorised signatory and a traffic declaration. We re-verify accounts KYC_
Re-papering your suppliers?
UK rules on business messaging bring know-your-customer (KYC) and know-your-traffic (KYT) duties from 15 July 2027, and they flow down into wholesale contracts. In the UAE, A2P senders must move to the TDRA’s ‘Direct Model’ by 31 December 2026. We hand over our trust pack before you ask. CONFIRM_
A summary of third-party regulation, not legal advice.
Data protection
- Roles
- For website enquiries we are the controller. For SMS traffic and lookups we act as your processor, on your instructions, under a DPA available on request. CONFIRM_
BEFORE_ PUBLISH - Retention
- Message content is retained for RETENTION_
PERIOD; CDRs for CDR_ RETENTION. - Transfers
- TRANSFER_
MECHANISM - Website processors
- Vercel (hosting and cookieless analytics), Resend (email), Telegram (internal lead alerts without contact details).
- Lookups
- HLR and MNP results are routing data only: reachability, porting and number type. CONFIRM_
BEFORE_ PUBLISH
Sanctions, security and abuse
- Sanctions
- We screen counterparties against SANCTIONS_
LISTS at onboarding and periodically thereafter, and we don’t serve sanctioned entities or jurisdictions. CONFIRM_ BEFORE_ PUBLISH - Security posture
- Encrypted customer connections, IP allow-listing, role-based access, and PENTEST_
CADENCE penetration testing. CONFIRM_ BEFORE_ PUBLISH - Abuse and law enforcement
- Report abuse to ABUSE_
EMAIL. We acknowledge within ABUSE_ RESPONSE_ TIME. Law-enforcement requests: LE_ REQUEST_ POLICY. - Security researchers
- Report a vulnerability to SECURITY_
EMAIL.
Policies
The traffic we refuse, the content we restrict, and how this policy is enforced.
How personal data collected through this website and its forms is handled.
The terms that govern the use of this website.
The cookies and similar technologies this website uses, and what would change if marketing tags were added.
Talk to the team.
Ask for rates on the destinations and traffic you send, request a test route, or pick a time to meet.