For EU buyers tired of negotiating a 14-page Data Processing Agreement just to log billable hours. We never receive the data, so we never need a DPA. All time entries live in JSON files on your own machine. Windows + macOS.
What GDPR requires of us, and what it doesn't:
The time-entry data, customer names, and timesheet content never leave your own machines. Therefore, we are not a processor of that data, no DPA is needed for it, and Schrems II transfer concerns are not engaged. However: as the buyer of the licence, you exchange standard commercial contact data with us (your email, name, company on the order) which is governed by our normal privacy policy. This page is a plain-English explanation aimed at IT and procurement, not formal legal advice - your DPO should review the technical facts and reach their own conclusion.
The time-entry JSON files are written to disk on your laptop. We have no server that receives them. No backup of your data exists outside your control.
Your end users do not register with us. There is no "Workforce Time Tracker user" in any database we own. There is nothing to delete on subject access / right-to-erasure requests on the user side.
The app does not phone home with usage analytics, crash reports, or click-tracking. The only optional outbound call is a version check (disable-able in Settings).
If you use multi-device sync we put JSON files in a folder you control. You decide whether that folder is Dropbox, OneDrive, iCloud, SyncThing, or a NAS share you operate. Your existing agreement with that provider applies.
Your data is in a text format you can read, audit, copy and delete with standard OS tools. There is no proprietary database to dump, decrypt or migrate from. Right-to-erasure is "delete the file."
The licence is RSA-PSS-signed and verified locally. Even the licence-validation step never contacts us. If we vanish tomorrow, your installation continues to work indefinitely.
| GDPR consideration | Workforce Time Tracker | Typical SaaS time tracker |
|---|---|---|
| Data Processing Agreement (Article 28) required | No | Yes |
| Vendor sub-processor list to review | No | Yes (typically AWS / GCP / Azure + 5-15 sub-processors) |
| Records of Processing Activity (Article 30) update | Internal only | Plus a vendor entry |
| Standard Contractual Clauses (SCCs) | Not engaged | Required (likely) |
| Transfer Impact Assessment for non-EU vendor | Not engaged | Required (likely) |
| 72-hour breach notification dependency on vendor | No | Yes |
| Subject access / right to erasure on user data | Local file delete | Vendor process, vendor SLA |
| Vendor risk assessment / procurement review | Software install | Full SaaS vendor onboarding |
This table compares the GDPR overhead of two procurement paths, not the products' features. It is general guidance, not legal advice. Your DPO is the decision-maker.
Because we never process your personal data. The app stores all time entries, customer names, and timesheet data in JSON files on your own machine. Nothing is uploaded to us. Under GDPR Article 28 a Data Processing Agreement is required between a controller and a processor; we are neither, so there is no relationship to paper. Note: as the licence purchaser you do exchange minimal contact data with us (email + name on the order), which is governed by our standard privacy policy.
No. We never receive the time-entry data. You (the customer) are the controller of your own employees' working-hours data, and you process it on your own machines. We provide software; we do not provide processing infrastructure for the data.
Schrems II concerns transfers of personal data from the EU/EEA to third countries. Because the time-entry data never leaves your own machines (no transfer happens), Schrems II is not engaged for the time-tracking data itself. Standard Contractual Clauses, Transfer Impact Assessments and supplementary measures are not required for this product.
On your own machines. Time entries are stored in JSON files in the folder you choose - typically next to the .exe (Windows) or under ~/Library/Application Support/WorkforceTimeTracker/ (macOS). Multi-device sync uses a folder you already replicate (Dropbox, OneDrive, iCloud, SyncThing, NAS) - the choice of cloud provider for that sync is yours, governed by your existing agreement with them.
Most DPOs we have spoken to consider this a standard desktop software install (the same category as installing Excel or Notepad++) rather than a new SaaS deployment. The internal record-of-processing entry remains the same as before - your IT department continues to be the controller. Naturally, your DPO has the final call on this; we are happy to provide the technical detail they need (no servers, no telemetry, RSA-PSS-signed local licence, JSON files on disk).
Nothing - your installations and data are unaffected. The licence is RSA-PSS-signed and validated locally, with no server contact required. The signed licence file you have on disk continues to validate forever. Your existing copy of the app keeps working indefinitely. Your data remains in human-readable JSON you can read, export, or import into another tool.
The current UI is English only. Currency, date format and timezone are configurable per user, so the app handles EUR, GBP and other currencies; weekly start day (Monday is default in Europe) is configurable; date format follows your OS regional settings. UI translation to other EU languages is on the roadmap.
You get a 14-day grace period after the expiry date during which the app keeps working normally. After that, the app shows renewal reminders but does not lock, encrypt, or hide your data. Time entries, customer list, exports, settings and backups stay in plain JSON files you can read with any text editor, archive, or migrate to any other tool. This is written into the EULA at section 8.5 - it is a contractual commitment, not a marketing line.
Same product on Windows and macOS. One licence covers both.
Download the trial