Disclaimer
1. Not legal, HR, or financial advice
Nothing the Software or this website produces — including invoices, PDF exports, evidence hashes, AI summaries, or the EU compliance section of the landing page — constitutes legal advice. Employment law and workplace-monitoring law vary significantly by country, state, and employer. Before taking any formal step based on data generated by the Software (including sending an invoice, raising a grievance, or filing a claim), please consult a qualified employment lawyer or your local labour-rights organisation.
2. No guarantee of legal outcomes
The Software captures data that may be useful as evidence in a wage claim, working-time dispute, or right-to-disconnect escalation. Whether a given court, tribunal, inspectorate, works council, or HR department will accept that evidence — and what weight they will give it — depends on the facts of your case, the law of your jurisdiction, the rules of the forum, and factors entirely outside our control. We make no guarantee about any such outcome.
3. What SHA-256 hashes do and don't prove
OvertimeLog computes an SHA-256 hash for every captured message from the Slack user ID, the Slack message timestamp, and the full message text. These hashes help you demonstrate that an export has not been altered since it was generated.
| Hashes do prove | Hashes do not prove |
|---|---|
| The exported PDF/Excel matches the local database record bit-for-bit. | That the message still exists in Slack. |
| That the local record has not been tampered with after capture. | That the message was not edited or deleted in Slack before the Software recorded it. |
| That the three inputs (user ID, timestamp, text) collide only on genuinely identical content. | Who actually wrote the message, or whether the claimed sender's account was compromised. |
| That two exports claiming the same source data must share the same hash. | That a particular authority, court, or tribunal will accept the hash as evidence. |
Where the underlying message is still present on Slack, you can corroborate the record by visiting the permalink the Software exports alongside it.
4. EU compliance content
The landing page summarises EU law on working time and the right to disconnect (Working Time Directive, CCOO v Deutsche Bank, national legislation in France, Belgium, Italy, Spain, Portugal, Ireland). That summary is plain-English background, accurate to the best of our knowledge at the "Last updated" date, and not a legal opinion. Employment law is updated frequently; please cross-reference an authoritative source (official gazette, EUR-Lex, your national labour inspectorate) before relying on any specific statement.
5. AI-generated summaries
If you enable the optional AI summaries feature, the generated text is produced by a large language model (yours or a third-party provider's). Large language models sometimes hallucinate or misattribute. AI summaries in OvertimeLog exports are provided for convenience only; they are not evidence. The authoritative records are the raw messages, timestamps, and permalinks.
6. Your responsibility
You are responsible for:
- Ensuring you have the right to access the Slack data you're collecting (in practice: your own conversations);
- Complying with applicable employment, privacy, and workplace- monitoring law in your jurisdiction;
- Reviewing any export you present to a third party, and enabling Privacy Mode if you need to redact message content;
- Keeping your device secure — an encrypted drive and a device password are the baseline.
7. No warranty
The Software is provided "as is" without warranty of any kind, as set out in the Terms of Use. Bugs happen. If you find one, please report it (contact).
Tl;dr: the Software gives you timestamps, text, hashes, and a permalink. What to do with that is between you, your employer, your lawyer, and — where relevant — the labour inspectorate. We can't and don't pretend to advise on any of that.