Our approach to privacy
Logless reconstructs a draft of your working week from the tools you already use — it does not claim to know exactly what you worked on, and it is not built to monitor you. It reconstructs, you review, you decide.
What Logless reads
Only lightweight metadata from the work-tools you explicitly connect. Today that means GitHub:
Commits
Message, timestamp, and the repository they belong to.
Pull requests
Title, timestamps, and repository.
Reviews
That a review happened, on which pull request, and when.
Issues
Title, timestamps, and repository.
We deliberately do not fetch or store source code, file contents, or diffs — even though GitHub's API would let us. It isn't needed to draft a timesheet, so we don't collect it.
What Logless never does
This list exists because timesheet tools have a history of drifting into surveillance. Logless is built specifically to avoid that.
- Take screenshots of your screen
- Log your keystrokes
- Track your mouse or cursor movement
- Access your webcam or microphone
- Monitor your browser history
- Monitor your desktop or IDE
- Score, rank or compare developers' productivity
Who sees what
You see your own detected activity and draft timesheet, and you control every entry before approving it. Managers and admins see approved timesheets, team status, and aggregate hours — not your underlying activity feed. Company data is fully isolated: no user can access another company's clients, projects, or timesheets.
Estimates, not claims
Detected hours are a starting estimate built from configurable, deterministic heuristics — never a claim of exactly how long something took. Every entry is editable, and nothing is final until you explicitly approve it. Revenue recovery figures are estimates based on your own billing rates, not guarantees.
This page describes Logless's product design and data-handling approach. It is not a legal privacy policy or terms of service.