Fair use policy

Where MessageReach draws the line on outbound traffic, and what a recipient can do about a message that should never have reached their phone.

14 August 2026
Updated
Cyprus
Jurisdiction
A shield module on a dark plinth with a glowing check mark on its face

Scope

This policy applies to every message sent through the platform, on every plan and every channel, including sandbox traffic that reaches a real network. It forms part of the terms of service. Where this policy and a market's own rules differ, the stricter of the two applies.

MessageReach supplies infrastructure to licensed gaming operators and their technology suppliers. We do not operate a gaming site, take wagers, hold player funds, or market anything directly to end users. Every message leaves under a customer's own licence and sender identity.

Marketing traffic requires a demonstrable opt-in from the recipient, recorded with its source and its timestamp. Purchased, scraped, rented or appended lists are not acceptable and are the fastest way to lose a key.

  • Opt-out instructions must appear in every marketing message, in the language of the destination market.
  • STOP and its local equivalents are matched at the gateway and written to the consent record within one second, whether or not your systems are reachable.
  • A recipient who has self-excluded from a brand must not receive marketing from it, and keeping that list current is the operator's responsibility.
  • Transactional messages, such as a security code or a withdrawal confirmation, do not require marketing consent but must not carry a promotional payload.

Content rules

The gateway will not carry messages that:

  • Are unlawful in the destination market, or promote an activity that is.
  • Misrepresent an offer, its terms, its odds, or the identity of the sender.
  • Target a person under the legal age for the activity being promoted.
  • Use pressure tactics aimed at someone showing signs of harm, or encourage chasing losses.
  • Omit responsible-play information where the destination market requires it.
  • Carry a shortened link on a shared domain, which networks routinely block and which makes phishing harder to distinguish.
  • Are sent inside a market's quiet hours, which are enforced from the destination number.

Sender identity

A sender identity must correspond to the licensed brand the recipient knows, and must be registered on the destination network wherever registration exists. Sending from an unregistered identity, or from one belonging to another party, breaches this policy regardless of whether a network happens to accept it.

Technical conduct

  • Do not attempt to exceed the throughput ceiling on your key by rotating keys or splitting traffic across accounts.
  • Do not probe routes, enumerate numbers, or use the consent endpoint as a lookup service.
  • Do not retry a send that failed with an identity or content reason code. Fix the cause instead.
  • Do not embed a key in a client application, a mobile binary, or a public repository.

Enforcement

Most of this is enforced automatically at the routing layer, which is the point: a send that would breach licensing, consent or quiet hours is refused rather than delivered and regretted. Where a pattern needs human review we contact the account's named administrators, and we may suspend a key while it is investigated.

Serious or repeated breaches end the agreement. Where a network or a regulator requires it, we will disclose what traffic was sent and under whose key.

Reporting abuse

Anyone can report a message sent through our network, whether or not they are a customer. Write to api@messagereach.net with the sender identity shown on the message, the date and approximate time, and the text if you still have it. Those three things let us identify the exact message and the customer that sent it.

Reports are investigated on receipt. Where a breach is confirmed we act on the customer's key, and we tell the reporter the matter was addressed without disclosing commercial detail about the customer.

Removal from a list

Replying STOP to the message is the fastest route and takes effect at the gateway within a second, for every future message from that sender identity. If replying is not possible, write to api@messagereach.net with the number and the sender identity and we will record the opt-out on your behalf.

We can stop the messages. We cannot close an account you may hold with the operator, or answer questions about it. The brand on the message is the right party for that, and if you tell us which one it is we will point you at their contact details.