Your customers trust you. We take that personally.
Phone rooms hold names, numbers and deal details that can't be allowed to leak. Here's how CallRoom Pro protects them, in plain English.
Every room is fenced off in the database
Each company's rows are tagged to its room, and Postgres row-level security refuses to return them to anyone else. Even a bug in our application code can't show one room's data to another. Links between records are checked by the database too.
Deal lockdown, always on
When a lead becomes a sale, the database hides that record, its notes, its callbacks and its website form fills from agents and managers, in search, lists, exports and everywhere else. Only room admins and customer support can open it, and every view is logged.
Contact details masked by default
Agents see full phone numbers and emails only on leads they're working. Managers see masked details unless a room admin turns that off. Masked values can't be written back by mistake.
Sign-in done properly
Passwords are hashed with Argon2id. Sign-in is rate-limited per account and per network. Accounts are created by invitation only, and one-time links expire.
Sessions you control
Room admins choose an idle timeout and a maximum session length, can see every sign-in and failed attempt, and can sign everyone else out with one button. Session cookies only work on the exact address they were issued for.
An audit log that can't be edited
Important actions are written to an append-only log: role changes, exports, erasures, billing changes, every view of a closed deal, and every visit by a CallRoom Pro platform administrator, which is time-limited and recorded in our own audit log.
Export and erasure built in
Room admins can export everything they own at any time and erase an individual customer's personal data on request, keeping their do-not-call status. Export files are private to the room and expire after 24 hours.
Full card numbers are never stored
CallRoom Pro is not a payment system and never charges cards. When a closer enters a customer's card on a deal, the card goes into Authorize.net's own secure window and is saved in your own Authorize.net account. We keep only the card brand, last 4 digits, expiry and Authorize.net's reference (plus name on card and billing address). The full number and security code are never saved by us. Only room admins and customer support can see those details; they run the payment in your own Authorize.net account. Saved cards are deleted from Authorize.net once a client is marked Paid, or after the number of days you set (14 by default, 1 to 30). Card numbers typed into notes or other free-text fields are masked automatically when saved (only the last 4 digits are kept), but always use the secure card window.
Encrypted, rotating backups
The database is backed up every night, encrypted at rest with a key stored separately from the backups, and kept for 14 days.
Least privilege underneath
The application connects with a database account that can't change the schema, can't bypass row-level security and can't rewrite the audit log. Secrets live outside source control with locked-down permissions.
Who's responsible for what
You own your customers' data and decide how it's used; Stephens Quantum LLC looks after it for you as your processor. The details are in our Data Processing Addendum and privacy policy.
Found a security issue? Please tell us privately at security@callroompro.com and we'll respond quickly.