Security & trust
Monitoring software has to be held to a higher bar. These are the controls built into the product — not policies written next to it.
Controls at a glance
Secrets encrypted with AES-256-GCM
The controls
Each control below is enforced by the platform itself, on every request.
By default, the server rejects an agent's content data until the employee has acknowledged the current monitoring notice — and asks again whenever the notice changes. The agent is visible (tray icon + notice), never a hidden process. Screenshots, live screen, recordings, clipboard, app and web activity all ship switched off.
Every organisation has its own enrolment key, its own users, devices and settings. Cross-tenant access is refused at the query layer, not by convention, and a suspended company is cut off at every entry point — console, agents, portal links and API keys — at once.
Role-based access with data scopes (company, branch, department, team, reporting line, self). A branch administrator sees their own branch, not the company; every check reads effective permissions on the server. Sensitive changes can require a second administrator's approval.
Authenticator-app (TOTP) two-step sign-in with recovery codes, required for platform operators and available to every company. Password rules a company may only tighten, lockout after repeated failures, idle sign-out, concurrent-device limits, sign-in audit and an operator IP allowlist.
Sign-ins, permission changes, exports, downloads, payments, settings and support access are written to an audit log the company can read and export. Platform operators act through fail-closed, audited gates and see aggregates — never a company's captured content without a time-capped grant from that company.
Data exports are off until the service provider switches them on for a company, and can be blocked for any one person; agent downloads can be switched off company-wide. Exports are encrypted and watermarked. Capture retention is a rolling window the company sets; nothing is kept longer than its policy says.
Operator credentials (mail, payment gateway, inbox) are stored encrypted (AES-256-GCM) and are write-only over the API. Payments are verified against the gateway or the bank reference before any plan is activated — a browser saying "paid" is never enough.
Self-hostable on your own infrastructure (Node + MariaDB). If you stop paying, capture pauses but the console stays readable and your data remains available to you.
We will walk your security team through the deployment model, the consent flow and the audit trail on a real instance, and answer a questionnaire in writing.
