Privacy
TIMO360 Privacy Architecture & Data Protection Policy
TIMO360 is employee monitoring software: 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 collects, what it never collects, and how long data is kept.
What is collected
| Signal | Purpose |
|---|---|
| Active application name | Application usage reporting |
| Window title (text only), including the name of the active browser tab | Context for what was worked on |
| Keyboard/mouse activity as a yes/no signal | Active vs. idle detection |
| Punch in/out, break and meeting times | Attendance and working-time reports |
| 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
- 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 (7 days by default). Aggregated sessions (365 days by default) and reports (730 days by default) 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.
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.
Window titles on macOS
Since macOS 10.15, the operating system releases another program's window title only to applications holding Screen Recording access — see Apple's Screen Recording permission guidelines. macOS words the prompt for it as “record your screen”, so it is worth being precise about what the agent actually does with it: it reads the title of the frontmost window and captures nothing else. The prompt is never triggered silently. It appears only when an employee chooses to allow window titles from within the agent, next to an explanation of what the permission is and is not used for.
Declining costs window titles alone. They feed no calculation on any platform, only a detail line in the timeline, so application usage, active and idle time, and reports are unaffected either way. The permission can be revoked at any time in System Settings, without uninstalling the agent. Windows and Linux release window titles without any permission, and the agent reads them there.
Your employer's responsibilities
The software provides the technical controls; it does not replace an organization's own obligations. An organization deploying TIMO360 should communicate its tracking policy to employees before enabling tracking, configure idle thresholds, retention windows and access 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.
Ready to get started?
Download the agent and connect using your secure enrollment token.