Logless understands the work — not the code.

How your data moves

Logless understands the work — not the code.

What Logless reads

Only lightweight metadata from the work-tools you explicitly connect. Today that means GitHub:

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.

Repository names are not a normal part of Logless

GitHub tells us which repository an event came from, since that's how we work out which of your internal projects it belongs to — but that identifier is used briefly during ingestion and then not stored or shown again. Your own timesheet, your manager's view, and every AI-assisted feature all work with your internal project names instead, never with GitHub repository, organisation, or branch names. The one exception is the repository-to-project mapping screen in Settings, which necessarily shows repository names because that's the one place you're choosing which repositories to track.

What reaches AI features

When AI-assisted summaries are enabled, only an anonymised signal is ever sent to the AI provider: activity counts (commits, pull requests, reviews) and a time window, referenced by an opaque internal project label — never a commit message, a PR title, a repository name, or any other identifying detail. If no AI provider is configured, Logless works identically using deterministic rules only — AI is an optional enhancement, not a requirement.

Encryption and honesty about it

Traffic to Logless is encrypted in transit (TLS/HTTPS). Your GitHub access token is encrypted at rest and never sent to the browser. We want to be precise about what that does and doesn't mean: this is not end-to-end encryption — Logless's servers can decrypt data to operate on it, which is what lets us build your timesheet. We won't describe this product as end-to-end encrypted, and we won't claim Zero Data Retention from our AI provider unless that provider and plan genuinely guarantee it. Neither is true of the current setup, and we'd rather say so than imply otherwise.

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 and not repository names. Company data is fully isolated: no user can access another company's clients, projects, or timesheets.

Retention

Detected activity metadata is kept for a limited window and then automatically deleted. Your approved timesheets — the hours and descriptions you reviewed and signed off — are your own records and are kept independently of the underlying activity data that originally produced them.

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.