Skip to main content
Every session, before it leaves the machine, is checked against your organisation’s corporate list. The check has one output: does this row carry the person’s name, or not. This happens on the machine, before upload. A non-corporate row has never had a name attached to it at any point, so no dashboard setting, export or database query can produce one.

​
The matching rules

The order matters, and it is not symmetric between websites and applications. For a browser window with a site:
  1. Each target’s website is checked to see whether the site contains it. The first match wins and its corporate flag decides the outcome.
  2. If no target matches, the row is non-corporate.
For everything else:
  1. Each target’s application name is checked to see whether the application name starts with it. The first match wins.
  2. If no target matches, the row is non-corporate.
So the default for anything unrecognised is non-corporate: unknown means anonymised, never named. That is the safe direction, but it has a consequence worth understanding.
A work tool that nobody added to the list is recorded as non-corporate. Its time still counts, but without a name, and it will read as unattributed time rather than as work. If a team’s named time looks implausibly low, the first thing to check is whether the tool they actually use is on the list.
Website matching is a substring test, so salesforce.com also matches eu.salesforce.com and login.salesforce.com. Application matching is a prefix test, so Microsoft would match every Microsoft application at once. Be as specific as you mean to be.

​
If your organisation has no corporate list

The check is only performed when the organisation has corporate targets switched on. With it off, every row is identifiable, including personal browsing. This is the right setting for a shop or shared machine where there is no personal use to protect, and the wrong one almost everywhere else. If you are not certain which applies to your organisation, ask us.

​
Why this design

It lets an organisation answer “how much of the day went to work systems” and “how much went elsewhere” without building a record of any individual’s personal browsing. The second number is real and reportable at team level. The identity behind it was never collected. It is also the part of ReclaimTime a works council or a data protection officer will look at first, so it is worth being able to explain in one sentence: work targets by name, everything else anonymised, decided on the machine.

​
What it means for the dashboard

The Activity Type filter on Statistics selects between the two sets. Corporate rows can be filtered to one person. Non-corporate rows cannot, because there is no person on them. Adding the two gives you the full picture of where time went. Reading only the corporate half and treating it as the whole day is the most common misreading of the dashboard.

​
Maintaining the list

The list is edited on the Targets page. Two things to keep in mind:
  • Changes are not retroactive. Rows already written keep the treatment they had. Marking a site non-corporate today does not anonymise yesterday’s rows.
  • The list ages. Entries added at rollout stay until somebody removes them, and anything on it marked corporate is tracked by name. A general-purpose site that was work-relevant three years ago is still producing named records today.
An annual review of the list is worth the hour it takes, and it is a privacy decision as much as a reporting one.
Checked against ReclaimTime client 8.0.0.9 and dashboard V3 on 5 September 2026.