Built for the EU Right to Disconnect era

Your overtime, documented.
Your data, on your machine.

OvertimeLog is a desktop app that detects after-hours Slack activity, groups it into billable sessions, and generates invoices with cryptographic evidence. It runs entirely on your computer — no cloud, no telemetry, no account.

↓ Download How it keeps data local

🔒 100% local. No data ever leaves your computer.

Download OvertimeLog

Binaries in beta — Windows installer ships first, macOS & Linux follow. Check back here or email support@overtimelog.com to be notified.

🪟 Windows Beta soon

Windows 10 / 11 · 64-bit · ~32 MB · Installer via Inno Setup

Coming soon SHA256 checksum will be published with release.

🍎 macOS Beta soon

macOS 12+ · Apple Silicon & Intel · notarized .dmg

Coming soon Requires macOS notarization — shipping alongside Windows.

🐧 Linux Verified build

Single-file binary, 32 MB · Tested on Ubuntu 22.04

Coming soon AppImage packaging in progress.

Want to see what you'll get before the binary lands?

Walk the full Detect → Bill → Export flow and download a real sample PDF + Excel built with the production export code.

See it in action →

Privacy by design

Your data never leaves this machine.

OvertimeLog is a single-user desktop app, not a SaaS. There is no backend. There is no account. Your Slack messages, your billing adjustments, and your invoices are stored in an SQLite file on your own disk — and stay there.

💻

Your computer

OvertimeLog + SQLite

⇄

💬

Slack API

Your own user token

☁️

Our servers

(don't exist)

The only network traffic OvertimeLog generates is between your computer and Slack — using your own user token. Anthropic or similar AI services are called only if you explicitly enable AI summaries with your own API key.

🏠

Local-only storage

SQLite database in your user data folder. Nothing is uploaded, mirrored, or synchronised anywhere.

📡

No telemetry

No analytics, no crash reporting, no "improve the product" pings. The app does not call home on launch or ever.

🙈

No account required

No email, no signup, no license server round-trip. Pro license keys are validated locally against a public signing key.

What OvertimeLog does

Reads your Slack DMs through your user token
Stores events in a local SQLite file
Generates PDF / Excel invoices on your machine
Lets you export everything as JSON (GDPR Art. 20)

What OvertimeLog doesn't do

Upload your messages to any server
Post a bot that your coworkers can see
Track anyone other than you
Phone home, collect telemetry, or require an account

Want to verify? Point Wireshark or Little Snitch at the app — it only talks to slack.com. Source inspection of the networking layer is planned for a public audit repo.

EU labour law

The Right to Disconnect is real law — in most of Europe.

After-hours messages are not a personality quirk of your manager. They are, in an increasing number of EU member states, potentially unlawful employer conduct. OvertimeLog documents them so you have evidence when you need it.

Country	Scope	Key requirement
🇫🇷 France 2017 · El Khomri Law	Companies with 50+ employees	Must negotiate written disconnection policies
🇧🇪 Belgium 2022	Federal + companies with 20+	Written disconnection agreement required
🇮🇹 Italy 2017 · Smart Working Law	"Smart working" agreements	Disconnection clauses mandatory
🇪🇸 Spain 2018 · Organic Law 3/2018	All employees in digital context	Right to digital disconnection enshrined
🇵🇹 Portugal 2021	Companies with 10+ employees	Cannot contact workers outside hours
🇮🇪 Ireland 2021 · Code of Practice	Guidance (non-binding)	WRC can consider breaches in claims

“

Member states must require employers to set up an objective, reliable and accessible system enabling the duration of time worked each day by each worker to be measured.

— CCOO v Deutsche Bank, ECJ Case C-55/18 (May 2019)

How OvertimeLog helps

Automatic time records. CCOO requires an objective, reliable log. OvertimeLog provides one that's cryptographically tied to the underlying Slack messages.
Burden of proof. In most EU jurisdictions, if the employer can't produce records, the burden shifts to them to disprove your claim. You arrive with evidence.
Pattern documentation. Systematic violations — every Sunday evening, every weekday after 21:00 — are easier to argue with months of structured data than screenshots.
Labour inspectorate filings. French DIRECCTE, Belgian SPF Emploi, Spanish Inspección de Trabajo — all accept timestamped documentary evidence.
Employee-initiated, not employer monitoring. The app uses your Slack user token. No bot, no visibility to coworkers, no employer infrastructure — the same data you could already read by scrolling Slack yourself.

OvertimeLog is documentary software, not legal advice. Consult a lawyer before acting on the records it produces.

What it does

From a 22:47 ping to a finished invoice.

🕒

Stealth DM monitoring

Uses your own Slack user token. Invisible to coworkers — no bot, no notifications, no visible presence.

🧾

Automatic session grouping

Related after-hours messages collapse into billable sessions using a configurable time-gap.

🌍

Timezone-aware

Cross-midnight schedules, custom work days, per-message timestamps tied to your actual timezone.

🔐

SHA256 evidence hashes

Every captured message gets a deterministic hash so any later tampering is detectable.

📄

PDF & Excel invoices

Three-sheet Excel invoice, branded PDF, or a redacted privacy-mode version that hides message text.

🤖

Optional AI summaries

Bring your own API key or use a local model. Summaries never touch our servers — because we don't have any.

📅

Timesheet view

Calendar grid of your overtime blocks. See weekly and monthly patterns at a glance.

📦

Full data export

One click dumps the whole database as JSON — GDPR Art. 20 portability, built in.

Pricing

Pay once. Keep the data.

Free to try for 30 days with full Pro features. After that, a one-time license unlocks Pro for good. Optional updates subscription if you want the new stuff.

Free

€0

Always free. Local-first forever.

Last 14 days of data
OvertimeLog-branded PDF export
Unlimited sessions & adjustments
Optional AI summaries (your own API key)

Download

Common questions.

Is my data sent to any server?

No. OvertimeLog stores everything in a local SQLite database on your own machine. The only outbound traffic it generates is to Slack's API, using your own user token. There is no OvertimeLog backend to send data to — none exists.

Will my employer or coworkers notice?

No bot, no app integration visible to them. OvertimeLog uses your own Slack user token (xoxp-), which is functionally equivalent to you scrolling your own Slack history. No activity is visible to anyone but you.

Is this legal where I live?

Reading your own Slack messages is legal everywhere Slack is. Using that record to support an overtime claim is separately protected in most of the EU under the CCOO ruling and national labour law. OvertimeLog is documentation software, not legal advice — talk to a labour lawyer before acting on what it produces.

How does GDPR fit in?

The lawful basis is legitimate interest (GDPR Art. 6(1)(f)) in documenting your own working time. Since data stays on your machine, there is no cloud data flow to regulate. The app ships with a privacy mode that strips message text from exports and a one-click JSON export of all stored data (Art. 20 portability).

What happens if I uninstall?

Your data stays in your user data folder (%APPDATA%\OvertimeLog on Windows, ~/Library/Application Support/OvertimeLog on macOS, ~/.local/share/OvertimeLog on Linux). Delete the folder to wipe everything.

Can I audit the source?

A source-available audit repository — containing the Slack client, the interaction grouping logic, and the export pipeline — is planned. The goal is to make the privacy claims on this page independently verifiable.

How do refunds work?

30-day money-back guarantee on the one-time Pro licence — email support@overtimelog.com and you'll get a refund, no questions asked.

Your overtime, documented.Your data, on your machine.