Everything people ask before they install it.

It is a desktop application that runs quietly behind your work and writes down what was actually in front of you: which program, which document, which email, which tab, minute by minute. At the end of the day you look at a timeline of your real day, and it records everything automatically with nothing to sort into projects. You never start a timer and you never stop one.

The problem it solves is simple. At 5 PM you cannot remember what you were doing at 10:40 AM, so you either guess your timesheet or you quietly lose the hour. This remembers for you.

Consultants, contractors, agencies, lawyers, accountants, anyone who bills for their time and switches between clients all day. It is bought and installed by the person using it, for their own work.

No, and it is built so it cannot be. There is no admin console, no team dashboard, no fleet deployment, and no way to view anyone else's timeline. The recording never leaves the machine it was made on, so there is nowhere for a manager to look even if they wanted to.

A timer needs you to remember to start it, stop it, and switch it every time you change task, which is exactly what you fail to do on a busy day. Project Timebook works the other way around: it records everything by default, so at the end of the day you either glance at the whole day at once or just press Generate and let it write the summary for you.

No. It is a real native desktop application, one binary, no browser and no Electron. That is a large part of why it can promise your data stays local.

No. It never captures an image of your screen, at any interval, for any reason.

No. It is not a keylogger. It does not read what you type, anywhere.

Once a second it asks the operating system two things: which program is in the foreground, and what is the title of that window. Plus whether you have gone idle. That is the entire capture surface.

Into one AES-256 encrypted SQLite file in your own user data directory, on your own disk. The key lives in your operating system's credential store, which on Windows means DPAPI tied to your Windows account. We hold no copy of any of it.

Your email address and whether your account has early access. That is the complete list.

We do not hold your activity, your window titles, your documents, your projects, your tasks, your hours, or your clients. Read the terms and the privacy page, both of which say it in full.

Yes, and this is the part most trackers get wrong. Set an app to Never and nothing is written when it is in front: not the title, not even the app name. The rule is applied at the moment of capture, so no row ever reaches the database.

That matters because hiding is not privacy. If the data was stored and merely hidden from the view, it could still leak. Here there is nothing stored to leak. There is also App only, which keeps the app name and never the titles, for things like Slack.

Three things, and only these. Signing in sends your email to the licence service. Buying sends a payment through Stripe. And Client Brief, if you press it and if you have added your own OpenAI API key, sends a summary of your recorded work for the period you chose — the apps and documents and their time — after showing you that exact summary first. That one goes from your machine straight to OpenAI under your own key, not through us.

If you never press Client Brief, nothing you record ever leaves your machine at all.

No, and it will never ask. If you want meetings on the timeline it reads the calendar copy your own desktop has already synced to this disk, or a plain .ics file you point at it. It asks you which on first run, and "no calendar at all" is one click.

A single entry, a whole day, or everything you have ever recorded. A delete genuinely removes the rows and reclaims the space rather than just hiding them. There is no cloud copy that survives it.

Once you pass your idle threshold it closes the current block and writes away time instead of billing an imaginary hour of whatever was left open. Locking the machine or letting it sleep does the same. The threshold is yours to set.

Add them by hand. Manual entries sit on the timeline next to the captured ones and go into reports the same way.

No. Select a batch and file twenty at once. Better still, teach it that Excel belongs to Q3 Planning and it files that work automatically from then on, including backfilling what it already recorded today.

Split it, and file the halves separately.

Yes. Pick any range, group by app or day, round to 5, 6, 10, 15 or 30 minutes or keep exact time, and export a CSV. The per-entry CSV is the integration surface: if your billing system can read a spreadsheet, it can read your hours.

Search from the top bar. It searches across everything you have ever recorded, not just today.

An optional feature that drafts a detailed client update from the work it recorded for the period you choose. It is off unless you press it, and it stays blank unless you add your own OpenAI API key, so it runs on your key and your account rather than ours.

It shows you the exact summary it would send — the apps and documents you worked on, with their time — before anything is sent, and only when you press Generate. It never sends executable paths or calendar events.

Dark, light, or follow the system, and if none of those suit you, set your own background, text and accent colours.

Project Timebook is Mac-first early access for Intel Macs running macOS 13 or newer. It has been tested on Intel Macs only. Windows and Linux are coming soon.

Yes. It is one native codebase compiled for each platform, not separate products that merely resemble each other. The product page shows the same day captured on the existing desktop builds so you can compare them directly.

Yes. The Mac-first release supports Intel Macs on macOS 13 or newer and has been tested on Intel Macs only. Download the installer for a normal install into Applications. An official Mac App Store release will follow.

It can. Turn on starting with your session and it records quietly in the background from login, without needing the window open.

Nothing during early access. WyConnect sign-in is required, but there is no trial and no payment.

Yes. Early access is fully unlocked after required WyConnect sign-in. There is no trial and no payment.

WyConnect is the required single Lee Wyatt Corp login. It identifies the person using Project Timebook and carries no captured activity, timeline data, projects, or hours.

WyConnect sign-in needs a connection. Captured activity is stored locally on your own computer and is never sent to Lee Wyatt Corp.

Project Timebook has its own separate terms of service. They govern this product alone and they do not inherit the terms published at leewyattcorp.com, including where the WyConnect sign-in is concerned.