Security
Last updated 26 September 2026
Draft pending review by qualified legal counsel. This page describes how CallyraSMS operates today; it is not legal advice and may change before launch.
- Every balance change is a row in an append-only ledger written inside a database transaction with row locks, so a wallet cannot be spent twice or go negative.
- Database row-level security limits each signed-in user to their own records; money-moving functions can only be called by our servers.
- Payment webhooks are signature-verified and re-checked with the payment provider before a wallet is credited; amount, currency and customer must match the payment you started.
- Admin access requires an individual admin account, and every admin action is recorded in an append-only audit log.
- Developer API keys are stored only as keyed hashes; webhooks we send are signed and time-stamped.
- Automated systems can pause features (Safe Mode) but cannot change balances, code or permissions.
Reporting a vulnerability
Email security@callyrasms.com. Please give us reasonable time to fix an issue before disclosing it.