Proof of work, without the busywork

Every freelancer has had the awkward conversation. A client looks at an invoice, sees "6 hours — design work," and asks: six hours on what, exactly? Usually you can answer. Sometimes you're guessing. Either way, you're defending the number after the fact instead of letting the work speak for itself.

The fix isn't more discipline. It's better defaults.

Capture the context, not the content

While a timer is running, TimeRecord records the root domain of your active tab — figma.com, linear.app, docs.google.com. That's it. Not the full URL, not the page title's contents, not what you typed. Just enough to reconstruct where the work happened, attached to the session automatically.

So when that invoice question comes up, the entry already answers it: six hours, across Figma and your client's staging site, on the "Homepage redesign" task. The proof was captured while you worked, not invented afterward.

Privacy is the whole point

A tool that watches your browser only earns trust if it's disciplined about what it sees:

• Domains are captured only while a timer is running — never when it's stopped.
• Only the root domain is stored — never full URLs, query strings, or page contents.
• Blacklist any sites you never want recorded; they're skipped before anything is written.
• If you never sign in, the data never leaves your browser.

Proof of work shouldn't require surveillance. It should require capturing the smallest useful signal, at the right moment, and nothing else.

That's the line TimeRecord draws — and it's why the timesheets it produces are both easy to make and easy to defend.