Call center data security and protection
Recordings and caller numbers are sensitive, so access to them should be limited and every use traceable. Halo's call center data security covers accounts, recordings, backups, where data lives and updates, and helps you keep call data in Ethiopia.
Two-step login
Accounts
Admins and phone users sign in with two-step login: a password, then a second step. These are the accounts that can change settings or handle calls, so they get the extra check. Accounts lock after repeated wrong passwords.
Calls out are limited too. Daily outbound call caps limit how many calls each person can make, and international calls are blocked by default. Halo also keeps a full audit log.
Every play is logged
Recordings
Recordings can be played and downloaded only by the roles allowed to, and every play is logged. You decide which roles can listen, for example supervisors and quality reviewers. Other roles, such as agents, can be left without access. When a question comes up about who heard a call, the log answers it. See call recording for how recordings are kept and searched.
Second server in Ethiopia
Backups
Halo makes encrypted nightly backups to a second server in Ethiopia. The backups are append-only, and a weekly automatic restore test checks that the database can be brought back from them.
Call data in Ethiopia
Where data lives
Halo runs on a server for your company alone, yours or one from Skynet. Calls, recordings and history are kept on it, with encrypted nightly backups on a second server in Ethiopia. If you choose a server from Skynet, it is still a server for your company alone, not shared with other customers. Telegram alerts show masked numbers only. This helps you keep call data in Ethiopia. Read more about running Halo on your own server.
Delivered by Skynet
Updates
Skynet delivers updates, so new versions reach your server without your team having to track them. The yearly licence includes all updates and Skynet support Mon-Sat 08:00-18:00 by phone, Telegram and email, with remote fixes. You do not need your own team to follow Halo releases.
Facts
- Sign-in
- Two-step login for admins and phone users
- Wrong passwords
- Accounts lock after repeated attempts
- Outbound calls
- Daily caps; international calls blocked by default
- Audit
- A full audit log
- Recordings
- Played and downloaded only by allowed roles; every play logged
- Backups
- Encrypted, nightly, append-only, second server in Ethiopia, weekly restore test
- Where data lives
- A server for your company alone; alerts show masked numbers
- Updates
- All updates included in the yearly licence, delivered by Skynet
Questions about call center data security
Who can play a recording?
Only the roles you allow. Those roles can play and download recordings, and every play is logged. Other roles cannot open them. If you need to know who listened to a call, the log shows it.
Are the backups tested?
Yes. Every week an automatic test restores the database from the backups. The backups are encrypted, made every night, append-only and kept on a second server in Ethiopia.
Do Telegram alerts show customer phone numbers?
No. Telegram alerts show masked numbers only. The full numbers, the recordings and the call history stay on the Halo server for your company.
Can agents call international numbers?
Not unless you allow it. International calls are blocked by default, and daily outbound call caps limit how many calls each person can make. Halo keeps a full audit log alongside these limits.
Is call history ever deleted?
Call history is kept in Halo’s own database on your server, and v1 does not delete call records automatically. Recordings are kept for the number of days you set, and Halo raises a critical alert if the disk reaches 95% and the oldest recordings have to be deleted.
Related features
Where this matters most: Banks and microfinance. See how Halo is priced on the pricing page.