smspostam

Legal

Anti-Spam Policy

If your recipients didn't consent, don't send. We suspend workspaces that ignore this — because our sender-ID reputation, and yours, depends on it.

Version 1.0Last updated 18 April 2026

Consent is the bright line

This policy applies to your use of smspostam, a service operated by PostAm Swift Networks Ltd. Every marketing message sent through smspostam must go to a recipient who has given clear, documented consent to receive that specific type of message from your business. Transactional messages (OTPs, order confirmations, service updates) don't require marketing consent, but they still require the underlying relationship — you're responding to something the recipient did, not reaching out cold.

What counts as valid consent

Consent is valid if you can answer yes to all four:

  1. The recipient gave their number to you directly. A form they filled, a checkbox they ticked, a keyword they texted, a paper form they signed, or documented verbal consent at point of service.
  2. The consent was specific. They agreed to receive SMS from your business — not "marketing emails from our partners" or a vague "we may contact you."
  3. You can show the source and timestamp. If asked, you can produce the form, the signup URL, the checkbox label, or the recording. Our platform lets you record a proof URL per contact.
  4. The consent hasn't been withdrawn. The recipient hasn't replied STOP and hasn't asked to be removed.

STOP handling

When a recipient replies STOP to one of your messages, our platform automatically:

The suppression is immediate and permanent from the platform's side. Re-opting-in must come from the recipient, not from you — you can't re-add a STOPped number through an upload.

Every marketing message you send must include a way for the recipient to opt out — typically a short "Reply STOP to opt out" line. We don't automatically add this line to your messages; it's your responsibility to include it when required.

DND compliance

Nigerian mobile users can register their number on the Do Not Disturb (DND) list maintained by their carrier. DND-registered numbers automatically block promotional SMS at the carrier edge. smspostam respects this by routing:

Attempting to misclassify a marketing message as transactional to reach DND numbers is a violation of this policy. Our preflight catches obvious cases; we suspend workspaces that attempt it repeatedly.

Read our DND Guide for a full explanation of how the register works and which messages are permitted.

Sender ID rules

Sender IDs are carrier-approved and must honestly represent the business sending the message. You cannot use a sender ID that:

We review every sender ID request before it goes to the carrier, and the carrier reviews again. Approval is not a guarantee — we can revoke an approved sender ID if we discover it's being used to deceive.

What we do when this policy is broken

When we detect a violation, the escalation is:

  1. Warning email to the workspace owner with specifics.
  2. Feature restriction — marketing-class sends disabled pending review.
  3. Workspace suspension — all sending paused; access to billing and export retained for audit.
  4. Termination — for severe or repeat offences. We may also revoke your sender ID with the carrier.

We also report serious abuse — phishing, impersonation of regulated entities, fraud — to the relevant authorities, and we may suspend without warning when public safety is involved.

Reporting abuse

If you've received a message you believe violates this policy, email us at support@postamglobal.com with the sender name, message body, and (if possible) the date and time you received it. We investigate every report and respond within one business day.