Privacy
An activity and time system, not surveillance
Activity Platform is an employee activity and time management system, not a keylogging or surveillance system. Every design decision in the product follows from that distinction. This page describes exactly what the desktop agent and browser extension collect, what they never collect, and how long data is kept.
What is collected
| Signal | Purpose |
|---|---|
| Active application name | Application usage reporting |
| Window title (text only) | Context for what was worked on |
| Browser domain (not the full URL) | Website usage reporting |
| Keyboard/mouse activity as a yes/no signal | Active vs. idle detection |
| System lock/unlock, sleep/wake | Session boundaries |
| Device metadata (OS, agent version) | Fleet health and support |
What is never collected
- Keystroke content: the agent detects that typing happened, never what was typed
- Passwords, form field contents, or clipboard contents
- Private message contents (email bodies, chat contents)
- Full page URLs or query strings; only the domain
- Page source, screenshots, screen recordings, audio, or webcam capture
These are architectural guarantees, not configuration toggles. There is no code path in the desktop agent, the browser extension, or the backend that reads or transmits any of the above.
Data minimization in practice
- Raw activity events are aggregated into sessions and deleted after the organization's configured retention window (30 days by default). Reports and aggregated sessions are kept longer, but at a much lower level of detail than raw events.
- The desktop agent batches and throttles activity signals locally, sending at most one heartbeat every 30 seconds, rather than streaming every keystroke or mouse movement.
- The browser extension reports a page's domain, not its full URL, and never its content.
Screenshots
Screenshot capture is not part of the product. Every build is checked automatically, and the check fails if any screenshot or screen-recording code is present. If capture were ever added for an organization with a compliance requirement, it would be opt-in per organization and off by default, disclosed to employees before being enabled with an in-app indicator while active, restricted to organization administrators with every view recorded in the audit log, encrypted at rest, and governed by a retention policy at least as strict as raw activity events.
Screen Recording permission on macOS
On macOS the agent asks for Screen Recording access, and macOS words that prompt as “record your screen”. It is worth being exact about why. Since macOS 10.15, the operating system will not tell an application the title of a window belonging to another program unless it holds this permission. Without it the agent still sees which application is in front, but every window title arrives blank. There is no narrower permission to request.
The agent reads the title of the frontmost window and captures nothing. The prompt is never triggered silently: it appears only when an employee chooses to allow window titles in the agent. Declining costs window titles alone — applications, domains, active and idle time, and productivity reporting are all unaffected, because titles feed no calculation. The permission can be revoked at any time in System Settings under Privacy & Security, without uninstalling the agent. Windows and Linux require no equivalent permission.
Your employer's responsibilities
The software provides the technical controls; it does not replace an organization's own obligations. An organization deploying Activity Platform should communicate its tracking policy to employees before enabling tracking, configure idle thresholds, retention windows, and productivity rules consistently with local employment and privacy law (works-council consultation, GDPR, CCPA, or equivalent), and restrict who can view individual activity. Role-based access enforces that last point technically, but administrators still decide who is granted the administrator or manager role.
Received an invite? Download the agent.