An acceptable use policy is the document in which a gateway states what may not be sent through it (illegal content, phishing, impersonation, unsolicited bulk) and what happens when it is.
Where a provider does not vet who you are, the policy on what you send is the real compliance instrument. A good one is short, concrete and enforced. It names the prohibited traffic: typically illegal content, phishing and other fraud, the impersonation of brands and public bodies, lists collected without consent and the unsolicited bulk sends they feed, and promotions disguised as transactional messages. It states that consent and legal compliance remain the sender's responsibility, and it describes the consequences, from blocked messages and closed routes to account termination; some policies also withhold refunds for prohibited traffic.
Gateways need one because carriers hold a provider responsible for everything it hands over, and abuse from one account can get a route closed for every account on it. The policy protects the other senders on the same routes as much as the recipients. It also has to follow the carriers' own codes, which can be stricter than the law: US carrier guidelines, for instance, restrict whole categories of content.
A policy is not a legal opinion. A message the gateway accepts is not thereby lawful, and a lawful message can still be refused because no route will carry it. When comparing providers, look for named categories rather than a line about "illegal use", a clear account of what is checked before sending, and what happens when a rule is broken; pages copied from a template with no mention of SMS protect nobody, as the guide to vetting a provider notes.
A hypothetical example: a courier's alert reads "Your parcel arrives today between 10:00 and 12:00". A sales team appends "20% off your next delivery" and sends it with the transactional flag so that it skips quiet hours. The intent may be harmless; the result is marketing disguised as an alert, which a policy of this kind treats as abuse.
At SMSMeteor: no identity check is made at sign-up, so the acceptable use policy is what governs an account. It refuses phishing, the impersonation of banks, carriers and public services, and harvested lists. Content filters check messages before they are sent, people review traffic patterns, and confirmed abuse leads to route closure and account closure. Promotional content flagged as transactional is treated as abuse. The no-KYC page sets out what is asked, held and refused.
