About — OvertimeLog

1. Why this exists

Plenty of people work overtime in Slack. A message at 22:47, a follow-up at 07:12, a "quick thing" on a Saturday. These aren't abstract — they're contacts that pull attention, push decisions, and materially extend the working day. When it comes time to demonstrate that the work happened, there's usually no record on the employer's side and nothing on the employee's side either.

The European Court of Justice made the employer side of that problem explicit in CCOO v Deutsche Bank (C-55/18, 2019): without an "objective, reliable and accessible" time-tracking system, employers can't show compliance with the Working Time Directive, and workers can't enforce their rights. Most workplaces still don't have one. OvertimeLog is the employee-side mirror — a personal working-time record with enough evidence attached that it can actually be used.

2. Principles

Principle	What it means in practice
Local-first	There is no server. Your Slack history lives in a SQLite file on your laptop. Privacy claims are verifiable — not a promise, just the architecture.
Evidence-driven	Every captured message carries an SHA-256 hash and a Slack permalink. Exports are reproducible and tamper-evident.
Honestly scoped	The app documents; it doesn't advise. The Disclaimer Employer notice template is where the limits are spelled out.
Quiet by default	User token, not a bot. No install event in your workspace, no sidebar icon, no activity indicator. Your coworkers don't know you're using it — which is the entire point.
Small surface	Python + Flask + SQLite + the Slack SDK. Fewer moving parts, fewer places for your data to leak, lower long-term maintenance burden on a one-person project.

3. Who built it

OvertimeLog is built by Kamil, a developer based in Poland. It started as a private tool during a particularly intense delivery window, turned out to be useful, and eventually turned into a product. There is no company structure, no investors, and no plan to add any. The product is paid for by the one-time Pro purchases and the optional annual update plan — that's the whole business model, and it's deliberately small.

4. Roadmap (April 2026)

The near-term trajectory is stability and distribution, not more features:

Windows and macOS desktop bundles with signed installers so people don't have to run python web.py.
Listing on the Slack Marketplace (via a hybrid static-redirect flow that keeps everything local-only).
A public source-available "audit repo" for the parts of the codebase that make the network claims on the landing page independently verifiable.
Translated UI for the countries whose right-to-disconnect legislation is named on the homepage — starting with French, Spanish, Italian, and Polish.

Full plan: TODO.md in the repo.

5. What OvertimeLog is not

Not a productivity tracker. It doesn't measure "focus time" or score your output. It measures hours you were contacted.
Not a surveillance tool. It runs with your credentials on your device; pointing it at someone else is a terms-of-use violation.
Not a legal service. A well-populated export is useful; a lawyer's opinion on how to use it is a different thing entirely.
Not an HR platform. It has no concept of a team, an org chart, or approval flows. One user, one laptop, one ledger.

6. Supporting development

The best way to support OvertimeLog is to buy a Pro licence if it saves you time or helps you recover wages. Second best: report the bug you found. Third best: tell a coworker who needed this two years ago.