Security & Compliance Protocols

Data Governance & Privacy

How we enforce security best practices across local agent captures, network sockets, and database indices.

Compliance Essential

Client-Side Privacy Blurring

Unlike other trackers that apply filters server-side, our desktop client executes Gaussian blurring locally in hardware-accelerated memory using macOS CoreImage kernel filters. This ensures that raw, unblurred screen content is never written into the upload stream, nor is it read from the employee's machine.

Storage Architecture

Direct-to-S3 Presigned Uploads

Desktop agents upload blurred screenshot files directly to MinIO or DigitalOcean Spaces storage buckets using secure presigned PUT URLs generated on demand. This bypasses the application server entirely, keeping transmission bandwidth low and restricting S3 access keys to backend systems.

Data Isolation

Isolated Database Engines

We utilize two distinct database layers: PostgreSQL handles highly secure SaaS metadata (users, auth states, override policies) with strict tenant-level row-level filtering, while ClickHouse isolates time-series activity telemetry. Telemetry queries respond in milliseconds with no crossover potential.

Access Policy

JWT Token Access & Expiry

All endpoints, including agent pings and activity ingestion, are gated using JWT tokens signed with HS256 keys. Tokens carry explicit company credentials and automatically expire after a set time frame (72 hours default), rendering intercepted requests unusable.

GDPR & HIPAA Compliance Alignment

By avoiding the storage of plain-text screen logs or unblurred screenshots, our platform is designed from the ground up to comply with GDPR data-minimization policies and HIPAA healthcare administrative security rules.

TLS EncryptionAES-256 in Transit
Client SovereigntyLocal-Key Signing
Data RetentionCustom Expiry Cron
Tenant IsolationPG Row-Level Rules