What monitoring software sees and a personal tracker should not

23 August 2026 · 7 min read

Employee monitoring software is built to show someone else what you did: screenshots, keystrokes, window titles, URLs, idle gaps, often uploaded to a dashboard as it happens. A personal time tracker answers a question you are asking yourself, and it only needs the app name and the clock to do that. The permissions an app requests on first launch tell you which kind it is before you read a word of the marketing.

What monitoring software typically collects

Monitoring products vary, but the category is defined by how much it can see. Depending on the product and how it is configured by whoever deployed it, the list can include:

• Periodic screenshots, sometimes of every display.
• Window titles, which on a Mac means document names, email subjects, and page titles.
• URLs visited, by domain or full address.
• Keystroke counts or keystroke contents.
• Mouse activity, used to compute an “active” percentage.
• Idle time, with a threshold set by the administrator.
• Webcam captures, in some products.
• Location, from the network or the machine.
• The list of apps running, not just the one in front.

All of that goes to a server. The person who installed it reads it on a dashboard, often live, sometimes with an alert when a threshold is crossed.

Whether that is appropriate is a question for your employment contract, not for this post. The subject here is what the same mechanics look like when an app that claims to be for you quietly does the same things.

Why a personal tracker needs almost none of it

Ask what question you want answered. For most people tracking their own time, it is one of these: where did the day go, how much of it was meetings, how long was I actually in the editor, did I stop at six. Every one of those can be answered with two facts: which app was in front, and for how long.

Nothing on the monitoring list above is required for that. Screenshots do not improve an app total. Window titles add the name of the document, which is a detail you already remember. URLs tell you which site, which might be interesting once but is not the question. Keystrokes and mouse counts measure motion, not work, and a person reading a long document looks idle to both. Webcams and location have no bearing on the day total at all.

A tracker that collects more than it needs is either planning to do something with the extra (sell a “productivity score,” feed a team view, train a model) or was built from a monitoring codebase and never trimmed. Either way, it is collecting on behalf of someone other than you, even if the only someone is a future feature. The reasoning for why trackers want titles specifically is in why most time trackers want your window titles.

The permission prompts that give it away

macOS makes a lot of this visible, because collecting the detailed data requires permissions the system asks you to grant by name.

• Accessibility. Needed to read window titles, UI contents, and in some cases keystrokes from other apps. A tracker that wants this is planning to read more than the app name.
• Screen Recording. Needed for screenshots, and on recent macOS versions, needed even to read the titles of other apps’ windows. A tracker that wants this can see your screen.
• Full Disk Access. Needed to read files in protected locations, including mail and message databases. There is no time-tracking reason to need it.
• Input Monitoring. Needed to observe keystrokes and mouse events system-wide. This is the keystroke-logging permission.

Knowing which app is in front does not require any of those. The system will tell any app which application is currently active; that information is not protected because it is not sensitive on its own. A personal tracker that asks for zero permissions is not being clever. It is asking only for what the question needs. The full breakdown is in what Mac apps can see about you, permission by permission.

Where the data goes

The second distinguishing mark is the destination. Monitoring software uploads, because the reader is not the person being monitored. A personal tracker has no reason to upload; the reader is sitting at the Mac where the data was collected.

So ask: does this app have an account? Does it sync? Does it have a web dashboard? Does it send “anonymous usage statistics”? Each of those is a channel from your Mac to a server, and each one means the data about your day exists somewhere you cannot inspect or delete with certainty. A tracker that keeps one file on your disk, which you can open, export, and remove, has a fundamentally different relationship with you than one that keeps a copy elsewhere.

A five-minute check before installing any tracker

1. Read the permissions it asks for on first launch. Accessibility, Screen Recording, Input Monitoring, or Full Disk Access each deserve a reason. If the reason is vague, stop.
2. Look for an account or sign-in screen. If there is one, find out what happens to your entries on the server and who at the company can see them.
3. Find the data on disk. Open Finder, choose Go, then Go to Folder, and try ~/Library/Application Support/ followed by the app name. If you cannot find a local copy, the only copy is remote.
4. Read the privacy policy for the words “screenshot,” “title,” “URL,” “keystroke,” and “activity level.” If any appear, the app is capable of collecting them, whatever the default setting.
5. Check for an export and a delete. A personal tracker should let you take the data out in a plain format and wipe it completely.

If the app passes all five, it is a personal tracker. If it fails the first one, treat it as monitoring software that happens to be running on your own behalf, and decide whether that is what you want.

Punchcard, by comparison

Punchcard is an example of how far you can go in the other direction. It asks for zero macOS permissions: no Accessibility, no Screen Recording, no Full Disk Access. It records app names only, never window titles, document names, URLs, keystrokes, or screen contents. At the closing time you set, it prints a paper receipt for the day, itemized by app with a day total and a stamp. It contains no networking code at all; the release build fails if a networking symbol appears, so there is no account, no sync, no analytics, and no crash pings. Your data is one SQLite file at ~/Library/Application Support/Punchcard/punchcard.sqlite, and “Burn the roll” deletes everything.

The limits follow from the same design. It cannot show a manager your day, cannot split time by project or client, has no idle-detection settings, and has no team features. If an employer needs visibility into your hours, Punchcard will not provide it, and a receipt on your own screen is not a timesheet. For contractors who want a record without monitoring, there is a fuller discussion in contract work from a Mac: keeping a record without monitoring software.

Questions

Can my employer see what a personal tracker records?

Only if they have access to your Mac or the app uploads somewhere they can reach. A tracker that keeps data in a local file and has no account gives them nothing to log into. If the Mac is managed by your company, assume they can read files on it, and ask before installing anything.

Is a tracker that takes screenshots “for my own review” a problem?

It is a choice. Screenshots require Screen Recording permission, which lets the app see everything on your display, including passwords and private messages that appear on screen. If you want them, accept that; if you only want hours, you do not need them.

What about trackers that measure “activity level” from typing and mouse?

That needs Input Monitoring or equivalent, and it measures motion rather than work. Thinking, reading, and talking on a call all register as idle. A personal tracker does not need it to answer where the day went.