Skip to content

Security and compliance

A plain description of how the platform protects your data and what each compliance feature does — including its limits.

Each business's data is kept separate

Every customer runs in its own organization. Row-level security is enabled on every table in our database, and API routes check which organization a user belongs to before returning data.

Payments

Checkout and recurring billing run through Stripe. Card numbers are entered on Stripe's systems; SpartanComm does not store full card numbers.

Encryption

Calls from the mobile app and the browser phone use encrypted media (DTLS-SRTP). Desk phones support TLS-encrypted signaling (the Grandstream WP826 we ship uses it by default). Calls that leave our network to the public phone network travel over the carrier network like any other phone call.

Account protection

Dashboard accounts support multi-factor authentication. Each desk phone and app registers with its own extension credentials.

911 calls (Kari's Law and RAY BAUM'S Act)

Users dial 911 directly, with no prefix. You register a dispatchable address for each location and it travels with the 911 call; the platform also logs the call and notifies your team. If an extension has no registered address, it cannot place 911 calls — register addresses before going live and update them when phones move.

Call recording notice

Calls can be recorded. Every recorded inbound call first plays a short recording notice — in Spanish, or in English for English-language accounts and for callers who choose English. Recording-consent rules vary by state and some require consent from every party, so confirm your setup meets the rules where you operate.

Business texting rules (A2P 10DLC)

US carriers filter business texts from 10-digit numbers that aren't registered with The Campaign Registry. If you plan to send reminders, notifications or marketing by SMS, talk to us about registration before you start sending.

Report a security issue

Email the details to support@espartan.net.

See also our Privacy Policy and Terms of Service. Privacy Policy · Terms of Service