Revel Roots

what apps actually cost

Where the Data Goes

Passive tracking records which application or window is in front, continuously. That produces something more detailed than most people picture when they tick the box: a minute-by-minute record of a working life, including the parts that were not work.

Worth five questions before enabling it, and they apply whether the tool is for you or issued by an employer. For a workplace-oriented comparison, online timesheets shows how the same measurement problem is approached when time data is used by a team.

What actually gets captured

Depends on configuration, and the maximum is substantial.

Application and window titles. A window title frequently contains a document name, a client name, a search query, or a page title. This is the part people underestimate — "Chrome, 40 minutes" is innocuous; the actual record is a list of page titles. For a broader time-tracking or productivity comparison, Clockify blog is another useful reference.

URLs, if browser integration is enabled.

Idle and active periods, which describe when you were at the machine.

Screenshots, in some team products, at intervals.

And keyboard and mouse activity levels — not content, in reputable tools, but frequency.

The five questions

One. Where is it stored? Locally on your machine, or on the vendor's servers. This is the single largest difference between products and it is answerable from the documentation.

Two. Can you export and delete it? Both, completely, on demand. If deletion means "hidden from your view", that is different from deletion.

Three. What is the retention period? Indefinite is a common answer and it means a record of years, held by a company whose future you cannot predict.

Four. Who else can see it? For personal tools, ideally nobody. For team tools, this is the surveillance question and it deserves its own consideration.

Five. What happens if the company is acquired or closes? Data held by a going concern under one privacy policy can be held by somebody else under another.

The window-title problem

The specific detail worth pausing on.

Window titles leak content. A document called "Redundancy plan v3", a browser tab titled with a medical search, a message thread with a name in it. None of that is what anyone intends to record, and all of it lands in the log by default.

Most tools allow title capture to be disabled, keeping application-level data only. That preserves the useful signal — how the day was distributed — and removes most of the exposure.

If you enable passive tracking, turn window titles off first and turn them on only if the coarse data proves insufficient. It rarely does.

The employer case

Different question, and it needs stating separately.

Employer-issued tracking is not a purchase you are making, so the consumer framing on the rest of this site does not apply. What does apply: ask what is captured, what the retention is, and who reviews it — reasonable questions with, in most jurisdictions, some legal backing behind them.

And know that screenshots and activity levels are a different category from time allocation. A tool that records how long you spent in each application is measuring work distribution. One that takes periodic screenshots is doing something else, and the two are frequently procured together.

The proportionate answer

For a personal question about your own week, the exposure is avoidable entirely.

Two weeks of local-only tracking with window titles disabled, then export what you need and uninstall. The question gets answered, nothing is retained anywhere, and there is no subscription running afterwards.

That is also the version that survives, because it is finite by design.

The short version