Skip to main content
This page lists what leaves a tracked computer. It is written field by field from the client source rather than from a marketing summary, so it can be handed to a security team, a works council or a data protection officer as it stands.

​
Activity: one row per window session

The client groups the windows of one application into a session. A session becomes one row. Everything below is one field on that row.
Window titles are recorded. A window title is often harmless (Inbox, Sales report), but it can also contain a document name, an email subject or a customer name, depending on the application. If your assessment turns on what could be inferred from titles, this is the field to look at. It is the only field that can carry free text out of the tracked application.
Full URLs, rather than just the site, are recorded only when this is switched on, and it is off by default. Nothing enables it silently: we change it for your organisation at your request. If you have not asked for it, it is off.

​
Identifiable and anonymised rows

If your organisation uses a corporate list, every session is checked against it before it is uploaded.
  • On the list and marked corporate: the row carries the username.
  • Not on the list, or on it and marked non-corporate: the row carries an anonymised identifier instead, so the time is counted at group level but cannot be traced to a person.
The check is described in full on Corporate and non-corporate targets. The practical consequence for an assessment: personal browsing is measurable in aggregate but is not attributed to a named individual, and this is enforced on the machine before anything is sent, not by filtering afterwards. If your organisation does not use a corporate list, every row is identifiable.

​
Machine record

Recorded once per installation, not per session.

​
Sign-in record

One row per sign-in, used for the Versions page and the access log.

​
What is never collected

None of the following is captured, uploaded or stored, and none of it can be switched on by a setting:
  • Screenshots or screen recording of any kind
  • Keystroke contents. Typing is measured as a duration. What was typed is never read.
  • Clipboard contents
  • Camera or microphone. The client does not request access to either.
  • File contents, file paths, or the contents of documents
  • Email, chat or call contents. The client can tell that a meeting is happening. Nothing inside it is read.
  • Location or GPS
  • Passwords or form contents
  • Personal accounts. The client signs in as the ReclaimTime account for the Windows user. It has no access to the person’s email, files or other services.
  • Anything at all while tracking is off on the account, and anything outside working hours as configured for the organisation or the person

​
Where it goes

Activity rows go to your organisation’s ReclaimTime backend over HTTPS. Larger customers are given a dedicated backend application, separate from the one serving other customers. Nothing is sent to a third party for analytics, advertising or model training. When the machine is offline, rows are held in a local database on the machine and uploaded when the connection returns. Nothing is discarded and nothing is queued anywhere else.

​
Retention

Retention is not yet implemented. Activity rows are kept indefinitely today. A retention policy, daily rollups and a deletion job are scheduled for December 2026, and the retention period is a decision for each customer rather than a default we impose. If you are assessing ReclaimTime now and need a retention commitment in writing, ask us for it rather than assuming a period.
Checked against ReclaimTime client 8.0.0.9 and dashboard V3 on 5 September 2026.