Choosing a time tracker for a Mac in 2026: a plain checklist

23 August 2026 · 7 min read

There is no single best time tracker for a Mac, because “tracking time” covers three different jobs: billing clients, reporting to a team, and understanding your own day. Pick the job first, then run the checklist below. Most apps fail on permissions, data location, or the amount of daily effort they ask for, not on the length of their feature list.

First, which job is this tracker for

Write down, in one sentence, what you will do with the numbers. The sentence determines almost everything that follows.

“I will put them on an invoice.” You need projects or clients, a way to mark time billable, rates, and a report per client. Manual timers are usually unavoidable here, because only you know which client a given hour belongs to. Accept the daily effort as part of the job.

“I will report them to a team or a manager.” You need shared visibility, which means an account, a server, and probably a subscription. Decide with your team what gets shared, and read the privacy policy carefully, because the tracker may collect more than the team needs.

“I want to know where my day went.” You need an automatic record of which app was in front, a daily moment to read it, and a place it is kept. You do not need projects, timers, rates, or an account, and every one of those will make the habit harder to keep.

The checklist

Run every candidate through these ten items. A “no” on any of the first four is usually disqualifying; the rest are trade-offs to make with your eyes open.

1. Does it ask for permissions it can justify? On first launch, note every macOS permission prompt. Accessibility, Screen Recording, Input Monitoring, and Full Disk Access each need a specific reason. Knowing which app is in front needs none of them.
2. Where is the data, exactly? A documented file path on your Mac is the best answer. “In your account” is an answer, but it means the record lives on a server. No answer at all is a warning.
3. Can you export everything, in a plain format? CSV, covering the full history, available at any time. Test it in the trial before paying.
4. Can you delete everything? A single action that wipes the local record, and, if there is a server, a documented deletion process with a timeline.
5. How much does it ask of you during the day? Count the decisions: start, stop, pick a project, answer an idle prompt. Every one is a switch. For the “where did my day go” job, the right number is zero.
6. Does it need an account? If the job is personal, it should not. If it insists, find out what the account unlocks.
7. What does it record beyond the app name? Window titles, URLs, screenshots, keystroke counts. Each is more detail and more exposure. Match the detail to the question.
8. How is the day reported? Live dashboard, daily summary, weekly email, a receipt. A finished summary you read once suits the personal job; a live view suits the team job.
9. What is the price shape? Subscription, one-time, one-time with paid upgrades. Match it to whether the app does anything for you on a server.
10. Does it still work with no internet? Disconnect and use it for a day. An app that fails offline is a cloud service, whatever the installer says.

The detailed version of the privacy items is in privacy-first time tracking on a Mac: what to look for.

Permissions: the three that should make you pause

Item one deserves its own section, because permission prompts are the clearest signal you will get before reading a single policy.

Accessibility lets an app read the contents of other apps’ windows and, in combination with other access, observe input. Trackers ask for it to read window titles. If you want titles, it is the price; if you want app names, it is unnecessary.

Screen Recording lets an app capture your display. Trackers ask for it to take screenshots, and on recent macOS versions, sometimes just to read other apps’ window titles. Either way, once granted, the app can see everything on screen.

Input Monitoring lets an app observe keystrokes and mouse events system-wide. Trackers ask for it to compute idle time or “activity levels.” It is the keystroke-logging permission, and a tracker that wants it is measuring motion rather than work.

The list of trackers that need Accessibility, and one that does not, is in time trackers that ask for Accessibility permission and one that doesn’t.

Price shapes that are honest

There are three common shapes, and each is fair in its place.

A subscription is fair when the app runs something for you on a server: sync, team views, hosted reports, integrations. You are paying for infrastructure, and the price stops when the infrastructure stops.

A one-time price with every update included is fair when the app runs entirely on your Mac. There is no server to fund, and the developer is betting that new customers will pay for continued work.

A one-time price with paid major upgrades is also fair, as long as it is stated up front. You pay again every few years for a significant new version and keep the old one regardless.

Where Punchcard fits on this list, and where it does not

Punchcard is built for the third job and nothing else, so it is worth being precise about which checklist items it passes and which it does not attempt.

It asks for zero macOS permissions (item one). Its data is one SQLite file at ~/Library/Application Support/Punchcard/punchcard.sqlite (item two), exportable to CSV (item three), and “Burn the roll” deletes everything (item four). It asks nothing of you during the day: no timers, no projects, no tags, no idle prompts (item five). There is no account (item six). It records app names only, never window titles, documents, URLs, keystrokes, or screen contents (item seven). The day is reported as a paper receipt printed at the closing time you set, itemized by app with a day total and a stamp, plus a week roll on Sunday and a month roll (item eight). It is $9 once for two Macs with every update included, after seven free receipts, with a 30-day refund (item nine). And it contains no networking code at all; the release build fails if a networking symbol appears, so it works identically with no internet (item ten).

It does not pass the other two jobs. Punchcard has no per-project or per-client tracking, no billable rates, no invoicing, no manual timers, no idle-detection settings, no team features, no iPhone app, and no integrations. If your sentence was “I will put them on an invoice” or “I will report them to a team,” it is the wrong tool, and the checklist above will point you at the right category. For the “where did my day go” job, a week of receipts is a fair trial, and how to set up Punchcard in ninety seconds covers the whole setup.

Questions

Can one tracker do all three jobs?

Some try, by combining automatic capture with projects and a team view. The cost is that the app needs broad permissions to guess projects from window titles, needs an account for the team view, and still needs you to confirm or correct its guesses. If you genuinely need all three, that trade may be worth it. If you need one, a tracker built for that one will be simpler and more honest.

How long should a trial be before deciding?

One full week, including a weekend. A single day tells you whether the app runs; a week tells you whether you kept using it and whether the weekly view shows anything. Check the export and the delete during the trial, not after.

Does “2026” change anything about this list?

The permissions have tightened (recent macOS versions gate window titles behind Screen Recording in more cases), and more trackers have moved to subscriptions. The jobs have not changed, and neither has the core question: what does this app need to know to answer what I am asking?