Contact
overtimelog.com domain, email forwarding, and
the public GitHub repository are live. The page structure is final;
only the values in this monospace style need filling
in at launch.
OvertimeLog is a one-person project. There isn't a ticket system or a live-chat widget — just an email address, a bug tracker, and reasonable response times. Pick the route that fits your message:
1. General support
Help with installation, connecting Slack, billing questions, anything the FAQ doesn't answer:
⏱️ Response time
Usually within 2 business days, often faster. Weekends and European holidays may be slower — this is a side project, not a 24/7 operation.
2. Bug reports & feature requests
Open an issue on the public bug tracker. Bugs filed there are visible to everyone, which means duplicates are cheap to spot and fixes ship faster.
🐛 GitHub issues
Preferred channel for reproducible bugs.
https://github.com/overtimelog/overtimelog-audit/issues
💡 Feature requests
Use the "Feature request" label on the same tracker. Include what you're trying to accomplish, not just what feature you want — it helps us design the right solution.
A good bug report includes: OS + version, OvertimeLog version (Settings → About), what you did, what happened, what you expected. If the app crashed, attach the log file from your app-data folder.
3. Billing, licences, refunds
💳 Billing questions
Lost licence key, payment problems, VAT invoice requests.
↩️ Refund requests
Within 30 days of purchase, no questions asked. See the Refund Policy. Email above or reply to your purchase receipt.
4. Privacy & data requests
🛡️ Privacy / GDPR
Questions about the Privacy Policy or data we hold about you in connection with a purchase.
📦 Your app data
Your own Slack data never reaches us — Art. 20 portability happens inside the app. Settings → 🛡️ Privacy & GDPR → Download all data (JSON).
5. Security disclosure
Found a vulnerability? Please report it privately before disclosing publicly. We aim to acknowledge within 72 hours and issue a fix on a reasonable timeline relative to severity. Credit is offered in release notes if you want it.
🔐 Security email
Use for anything affecting authentication, Slack token handling, the licence system, or local-data integrity.
🔑 PGP (optional)
If you want end-to-end encryption, ask for a PGP key by email first. For most reports, plain email is fine.
6. Press & legal
📰 Press / interviews
Articles about EU working-time enforcement, right-to- disconnect laws, or the product itself.
⚖️ Legal notices
Formal legal correspondence (GDPR notices, IP concerns, subpoenas).
7. Postal address
For formal legal correspondence only. Please email first if possible — paper mail takes weeks to reach us.
OvertimeLog — Kamil [surname]
[Street address]
[City, postal code]
Poland
Everything you send to the addresses above lands in a single inbox triaged by the person who built OvertimeLog. Please keep messages concise, include what you've already tried, and be patient — a thoughtful reply beats a fast one.