Log hours against tasks and see daily, weekly, and all-time totals — saved in your browser, no login.
A time tracker for people who just want an honest log of hours against tasks — freelancers billing a client, someone estimating how long a side project is actually taking, or anyone who's ever finished a week wondering where the time went. No account, no app to install, no per-seat pricing: every entry is saved directly in your browser via localStorage and stays there across visits until you clear your browser data or remove entries yourself.
Add an entry with a date, a task name, an optional category (useful for grouping related tasks — "Client A," "Deep Work," "Admin"), and the number of hours, in quarter-hour increments. The three summary numbers update immediately: today's total, this calendar week's total (Monday through Sunday), and your all-time total across every entry you've logged. The category breakdown shows what fraction of your logged time has gone to each category, so patterns become visible without needing a spreadsheet.
Because everything lives in this browser's local storage rather than a server, your log is private by default and works offline — but it also means it won't follow you to a different browser or device, and clearing your browser's site data will clear it too. For anything you need to keep long-term or access from multiple devices, treat this as a fast day-to-day log and export or copy totals elsewhere periodically.
No — everything is stored locally in this browser using localStorage. Nothing is sent to a server, which also means the log won’t appear on a different browser or device, and clearing your browser data will erase it.
As a Monday-through-Sunday calendar week based on each entry’s date, not a rolling 7-day window from today.
Not directly — remove the entry and add it again with the corrected details. This keeps the tool’s logic simple and avoids a whole separate edit-in-place flow for what’s meant to be a quick daily log.
No hard limit, but browser localStorage has a practical ceiling (typically several MB) that a very long-running log could eventually approach. For most day-to-day tracking this won’t come up.