The short version
- Counts, not content. No keylogging, ever.
- Nothing is recorded when the timer is stopped.
- Every person can open their own record in the same detail their manager sees.
Every tool in this category has a sentence it would rather you did not read closely. Ours is the one about activity: TeamTrek records an activity level for each interval while a timer is running. That sentence is doing a great deal of quiet work, and the honest version of it takes a paragraph rather than a line.
So here is the paragraph. An activity level is a count of input events in a span of time — how many times a key was pressed, how far a mouse moved — expressed as a share of what that interval could hold. It is a measure of whether a machine was being used. It is not a measure of what was typed, what was decided, or whether any of it was any good.
What is actually recorded
Four things, while a person’s own timer is running, and nothing at all once they stop it:
- Hours, against the project and task the person picked.
- Activity, as counts per interval, never the characters behind them.
- Apps and URLs that held focus, where an organisation has that setting on.
- Screenshots, only where an admin has turned them on and the team has been told.
Try this
Open your own record for yesterday and read it as a stranger would. Whatever makes you uncomfortable there is what your team will ask about on the first day.
What is not recorded, at all
The content of anything typed. Not in a field, not in a document, not in a private message. There is no keystroke log, because there is no honest use for one that could not be served by something narrower.
A number that measures input cannot measure output. Anyone selling you the second thing while recording the first is selling you a feeling.
Nor is anything recorded outside a running timer. That sounds like a small promise until you consider the alternative: a tool that keeps watching after hours is a tool that has decided, on your behalf, that the working day has no edges.
Why the distinction matters
Because the two readings lead to different management. A record that says this project took 980 hours against an 800-hour estimate invites a question about the estimate. A record that implies this person was 62% productive invites a conversation nobody can win, built on a number that was never measuring productivity in the first place.
See activity beside hours, apps and projects
One record, and every person can open the part of it that describes them.
Telling the team
Whatever you switch on, tell people before you switch it on, and show them their own view first. Not as a courtesy — as a design constraint. A record that a person cannot open is not a record, it is surveillance with a reporting feature, and teams work out which one they are living with inside a fortnight.
Rules on monitoring differ by location, and this piece is not legal advice.
Was this useful?