Skip to content

Security

SMSFabric is built against the OWASP Top 10 for web applications, the OWASP API Security Top 10 and the OWASP Mobile Top 10. This page summarizes the controls that matter to you as a customer.

  • Every connection to the API, the portal and the phone app uses TLS. HTTP Strict Transport Security is on, so browsers never fall back to plain HTTP.
  • The Android app refuses cleartext connections and pins the API’s certificate.
  • Webhook URLs must be https.
  • Message bodies, contact phone numbers, webhook signing secrets, 2FA secrets and provider credentials are encrypted with AES-256-GCM, with a separate data key per organization.
  • Contact numbers are searchable without decrypting them, through a keyed hash index.
  • Uploaded CSV files are stored encrypted until the import finishes, then deleted.
  • Passwords are hashed with Argon2id. API keys and refresh tokens are stored only as peppered SHA-256 hashes, so a database copy can’t be used to call the API.
  • Verify codes are never stored, logged or returned: only a keyed hash is kept, compared in constant time.
  • Every query on your data is filtered by the organization of the key or user making the request, taken from the credential, never from the request body.
  • An id that belongs to another organization returns 404 not_found, the same as one that doesn’t exist, so ids can’t be probed.
  • Request bodies are checked against an explicit schema; unknown fields are rejected, so a request can’t set fields such as orgId or role.
  • Responses are explicit objects: hashes, encrypted fields and internal flags never leave the server.
  • Every endpoint is denied by default and declares the permission it needs. API keys carry scopes, a subset of their creator’s permissions.
  • Keys can expire and can be limited to IP ranges. A rotated key’s old secret stops after 24 hours; a revoked key stops at once.
  • Creating keys, managing the team and widening Verify countries require a signed-in user, so a leaked key can’t escalate itself.
  • Users can turn on two-factor authentication (TOTP) with single-use recovery codes. Repeated failed sign-ins slow down and then lock the account for 15 minutes.
  • Passwords must be at least 12 characters and are checked against known breaches without sending the password anywhere.

Sign-ins, 2FA changes, API key creation, rotation and revocation, role changes, phone pairing, webhook changes, contact exports and erasures, campaign actions and Verify blocks are recorded with the actor, IP and request id. Read it in the portal under Audit log or with GET /v1/audit. Actions by SMSFabric staff are recorded in a separate, append-only admin log, and staff actions on your organization also appear in yours.

  • Every delivery is signed with HMAC-SHA256 and a timestamp. Verify it as shown in Webhooks.
  • Webhook and forwarding URLs go through an SSRF guard: the host name is resolved and private, loopback, link-local and other internal addresses are refused, both when you save the URL and when each delivery connects. Redirects are not followed.
  • Rate limits per key, user, IP and organization, size limits on every request, and capped page sizes.
  • Verify blocks SMS-pumping fraud with country permissions, per-number, per-country and per-organization limits, and automatic blocking of suspicious number ranges.
  • STOP replies opt recipients out automatically.
  • The phone app stores its credential in the Android Keystore, keeps its local message store encrypted, disables backups, and exposes no components to other apps without a permission.
  • A phone only receives messages assigned to it, and can only report status for those.
  • Unpairing a phone in the portal revokes its token at once.
  • The iOS companion app never sends SMS silently, and never reads SMS or runs USSD.

Phone numbers, message bodies and tokens are redacted from SMSFabric’s application logs. Error responses never include stack traces or internal details; quote the requestId when you contact support.

  • Give each key only the scopes it needs, set an expiry, and add an IP allowlist for servers with fixed addresses.
  • Keep keys and webhook secrets in a secret manager, never in code, logs or the browser.
  • Verify webhook signatures on the raw body and reject old timestamps.
  • Turn on 2FA for every member, and remove members who leave.
  • Review the audit log after any change you didn’t expect.
  • If a key leaks, revoke it in Developers → API keys right away, then create a new one.