SECURITY AND DATA

Your data is on your server.Here is what that means.

Not a shared database with a tenant column. One company, one installation, one database, one address. What follows is what is built, not a badge wall.

Your own address: yourcompany.flarehub.co.ke, or your own domain

Two-factor required of administrators and managers, enforced by the server

An append-only audit log, including our own support actions

Nightly backups, fourteen kept; retention on the schedule you set

One company, one installation

Your CRM runs on its own server with its own database. It is not a row in ours. A fault, a breach or a bad deploy elsewhere cannot reach it, and neither can another customer.

Your own address: yourcompany.flarehub.co.ke, or your own domainYour own database; nobody else’s data in the same tablesTraffic encrypted in transit; passwords hashed and visible to nobody

Two-factor on every account

Available to everyone and required of administrators and managers. Privileged screens stay locked until an authenticator is enrolled, and that is enforced by the server, not just hidden by the interface.

Authenticator app, with backup codes shown onceRequired for admins and managers; optional for agents unless you say otherwiseSessions end after twelve hours and after an idle period you set

Roles decide what each person sees

Three roles. Agents see what they own, managers see their team, administrators see everything. Every screen and every API route checks it, and refusals are logged like everything else.

Admin, manager, agentAgent visibility set to owned, team or allA refused request is written to the audit log with who and what

An audit log nobody can edit

Every consequential action is appended with before and after values, the person, the time and the address. Append-only at the database level. Not an administrator, not us, not anyone can change or delete a line.

Record changes, settings, roles, recording plays and downloadsOur own support actions appear in your log, naming us and the reasonKept for the life of the installation

Backups you can count

Taken nightly, the last fourteen kept, and the status of the last one is shown on the system health page. If a plan includes it, you can download a snapshot yourself.

Nightly, fourteen retainedLast backup time and result visible in SettingsRestore checksum verified

Retention on a schedule you set

Deleted records are hidden first and destroyed when your purge period passes, so a mistake can be undone. Recordings are deleted at the number of days you choose. A nightly job does it whether anyone remembers or not.

Soft delete with a purge period you setRecording retention in days, up to your plan’s ceilingRaw PBX events and message payloads pruned separately

What we can and cannot do inside your installation

When you ask for help we can do three things and no more. Each is written into your own audit log the moment it happens, naming us and the reason given.

List who is able to sign in

Clear one person’s second factor so they can set up a new authenticator

End one person’s sessions

Read your contacts, calls, messages or deals

Create accounts or change what anybody is allowed to do

Delete anything, remotely or otherwise

The audit log, showing who did what and when

Ask us the hard questions.

Bring your own checklist to the call. If something here is not true of your installation, we will say so.

Book a demo