Security and compliance, built into every message.
Your messages, your customers’ phone numbers and your brand are worth protecting. SMPP Forge enforces the rules on every path — API, SMPP, portal and bulk — and keeps the evidence.
- Two-factor sign-inBuilt in
- Audit trailRecording
- IP allowlistsPer account
- Sender-name registryBuilt in
- Phone numbers in logsMasked
- Where your data livesYour servers
Data sovereignty
Your data never leaves your hands
With a hosted API, every message passes through someone else’s cloud. With SMPP Forge, it never leaves yours.
Self-hosted by design
SMPP Forge runs in your cloud account or data center. We never see your traffic, your customers or their phone numbers.
Private by default
Phone numbers are masked in logs and message text is never written to them — so routine troubleshooting does not expose personal data.
Data residency, your way
Choose the country, the region and the infrastructure. Meet local residency rules without asking a vendor for an exception.
Security controls
Enterprise security, switched on from day one
The controls your security team will ask about in the first meeting — already built in.
Two-factor sign-in
Authenticator-app verification for every console user, with backup codes.
Role-based access
Administrators and customers see and change only what their role allows.
IP allowlists & rate limits
Restrict access by network, per account, and slow down abusive clients automatically.
Complete audit trail
Every administrative change is recorded — who made it, what changed and when.
Encrypted connections
Encrypted SMPP sessions, with optional certificate-based authentication on both sides.
Signed notifications
Every webhook is signed, so your systems can verify it really came from your gateway.
Callback protection
Callback addresses are checked, so they cannot be abused to reach your internal network.
Instant suspension
Suspend a customer or a whole customer group in one click; access stops immediately.
Fair-use throughput
Per-account message-rate limits stop one customer’s burst from affecting everyone else.
Compliance engine
Stop spoofing and unconsented messages before they leave
A sender name is the easiest way to impersonate a brand, and regulators are closing the gap. SMPP Forge checks every message against your rules before a carrier ever sees it.
- A sender-name registry that locks each name to its verified owner and approved countries
- Look-alike protection — case, separators and digit swaps are caught, so “ACM3 BANK” cannot pass for “ACME Bank”
- Consent and opt-in records by region for commercial traffic
- Quiet hours that hold marketing outside permitted times
- Content rules and number blocklists, by region
- Numeric-only destinations such as the United States enforced automatically
- The same rules on every path — API, SMPP, portal and bulk
Approved names go out exactly as registered. Near-copies resolve to the original and are refused for anyone but its verified owner.
Sender rules by market
Every market has its own rules — we track them
Regulators worldwide are moving to registered sender names. Here is where some of the largest markets stand today.
| Market | Authority | Regime | What it means for senders |
|---|---|---|---|
| United States | CTIA · The Campaign Registry | Numeric senders only | Business texting uses registered 10DLC numbers, verified toll-free numbers or short codes |
| Canada | CWTA · CRTC · CASL | Numeric senders only | Short codes are vetted by CWTA; commercial messages require consent |
| United Kingdom | MEF SenderID Protection Registry | Brand-protection registry | Registered brands — and thousands of look-alike variants — are blocked for everyone else |
| Spain | CNMC alias registry | Registration required | Every alphanumeric sender name sent to Spanish numbers must be pre-registered |
| India | TRAI DLT | Registration required | The business, its 6-character header and each message template must be registered |
| Singapore | SGNIC SSIR (IMDA) | Registration required | Unregistered sender names are shown as “Likely-SCAM” since January 2023 |
| Australia | ACMA Sender ID Register | Registration required | All alphanumeric sender names, new and existing, must be registered from July 2026 |
| Türkiye | BTK · İYS · KVKK | Registration required | Names must match a trade name or brand; commercial SMS needs İYS consent |
Summary of public regulator and industry guidance as of September 2026. Rules change — confirm current requirements with your carriers before approving senders.
Regulations
Designed to help you meet the rules that matter
SMPP Forge gives you the controls. How you configure and operate them completes the picture.
GDPR
Data minimization, regional hosting, access control and audit trails.
TCPA & CTIA guidelines
Consent records, quiet hours and numeric-sender enforcement.
CASL
Consent tracking for commercial electronic messages.
KVKK & İYS
Consent checks and registered, brand-matched sender names.
TRAI DLT
Registered sender headers enforced per destination.
SSIR
Only registered sender names reach Singapore numbers.
This page describes product capabilities and is not legal advice.
Found a security issue?
Please report it privately to info@smppforge.com. We will acknowledge it promptly and keep you updated until it is resolved.
Bring your security team to the demo
We will walk your security and compliance reviewers through every control — and answer their questionnaire.