Trakwyse
Privacy policy

Data handling, in plain terms

Trakwyse is available cloud-hosted or on your own infrastructure — which changes who's responsible for the data it collects. Here's how each model works.

Two deployment models, two data-handling paths

On a dedicated deployment, the organization running Trakwyse owns the infrastructure and is the data controller for everything collected — timesheets, attendance, screenshots, and activity logs live on that organization's own servers. On a cloud-hosted plan, Milta hosts the deployment on the organization's behalf, acting as a data processor under the same access restrictions described below. Either way, each organization is responsible for its own policies toward its employees.

What Trakwyse can collect

Depending on what an organization enables, the desktop agent may record:

  • Time entries against clients, tasks, and subtasks
  • Session events — login, lock, unlock, idle, and logoff
  • Application usage (process name and window title, not file contents)
  • Periodic screenshots, with an optional blur applied before storage

Access is restricted by design

Screenshot access is off by default and must be explicitly granted per team or per employee, separate from general team-lead status. Team-scoped reports are only visible to admins and leads of that specific team — never leaked across team boundaries. Every employee can always see their own tracked data.

Storage & retention

Data is retained for as long as the deploying organization chooses to keep it. Trakwyse does not sell or share tracked activity data with any third party.

Questions about a specific deployment

If you're an employee with questions about how your organization's Trakwyse deployment is configured, the right first step is your own IT or HR team — they control the settings for your instance. For questions about Trakwyse the product itself, contact us directly.