Time Tracking & Attendance
My Hours
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by My Hours d.o.o. · myhours.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
My Hours at a glance
- Vendor
- My Hours d.o.o.
- Headquarters
- Not stated on the vendor’s pages as of 3 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 3 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 3 Nov 2026
- Panel verdict
- The AI panel rates My Hours 2.5/5, the mean of 6 judges. My Hours, from Spica International in Ljubljana, Slovenia, is strongest at project and billing, scoring 8 with no spread: a clients-projects-tasks-tags hierarchy, rates per user, task, project or single time log, budgets in hours, billable amount or costs with alerts, and numbered invoices from logged hours. how scores are made
- As of
- Vendor pages captured 3 Nov 2026; evaluated by the panel 4 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
My Hours, from Spica International in Ljubljana, Slovenia, is strongest at project and billing, scoring 8 with no spread: a clients-projects-tasks-tags hierarchy, rates per user, task, project or single time log, budgets in hours, billable amount or costs with alerts, and numbered invoices from logged hours. Time capture sits at 7 with no spread — mobile and web clocking, timeclock terminals, Bluetooth beacons, a customizable kiosk, offline entries that auto-sync — and we found no public information on GPS or geofenced check-in or bulk corrections. The weak side is statutory: working-time law sits at 4 because the pages frame rounding under FLSA and the 40-hour week, and we found no public information naming the German recording duty, ArbZG break and rest rules, or statutory retention. Payroll export sits at 4, and we found no public information naming a payroll system; the route to "any payroll provider" runs through Zapier and API keys. Sovereignty scores spread between 2 and 3, weighing a stated EU base and ISO certifications against an unstated Azure region and a subprocessor list available on request.
Speaks for it
- Project and billing tops the scores at 8 with no spread: budgets in hours, billable amount or costs with automatic alerts, rates per user, task or project, and numbered invoices created straight from logged hours.
- Time capture holds at 7, covering mobile and web clocking, timeclock terminals, Bluetooth beacons, a customizable kiosk, and offline entries that auto-sync once connectivity returns.
- A full audit log of all actions and changes, filterable by period, user and team, exports in XLS ready to present to auditors.
- The pages state there is no keystroke logging, no screenshots and no mouse-movement detection.
- Timesheets can be locked daily, weekly or monthly, after which only system administrators can edit.
Held against it
- Working-time law sits at 4: compliance is framed under FLSA rounding and the 40-hour week, and we found no public information naming the German recording duty, ArbZG break and rest rules, or statutory retention.
- Payroll export sits at 4: we found no public information naming a payroll system, and the route to "any payroll provider" runs through Zapier and API keys.
- Absence and planning runs 4 to 5: absences are tracked by creating a project titled 'Absences' with leave types as its tasks, and we found no public information on shift templates, swap workflows or carry-over.
- Sovereignty runs 2 to 3: the Azure region is not stated, the subprocessor list is available only on request, and we found no public information on a data processing agreement.
- Pricing transparency sits at 2: the public prices are free for teams of up to 5 users and a 14-day free trial, with no public per-user price for the paid tiers.
Best for
- You run client projects and need logged hours to flow into per-person rates, budget alerts and numbered invoices without retyping.
- Your crews clock in away from desks and need terminals, Bluetooth beacons, a shared kiosk and offline entries that auto-sync on reconnect.
- You need a filterable audit log that exports in XLS, plus daily, weekly or monthly timesheet locking, to present to auditors.
- Your works council rejects surveillance tooling — the pages state there is no keystroke logging, screenshots or mouse-movement detection.
Avoid if
- You must satisfy the German recording duty with German-law break, rest and retention rules in view — the captured pages frame rounding under FLSA and the 40-hour week, and we found no public information naming ArbZG rules or statutory retention.
- Your payroll office needs a named system or German format such as DATEV — the handoff described on the pages is Zapier and API keys toward "any payroll provider".
- You need rostering with shift templates, employee availability and substitution or swap workflows — planning here is a calendar overview of absences and shifts.
- Your procurement must pin down the hosting region and subprocessor chain before signature — the pages state Azure hosting without naming a region and offer the subprocessor list only on request.
The scores
| Criterion | Panel median |
|---|---|
| Capture in the real workplace | 3.5 of 5 |
| Working-time law & audit record | 2 of 5 |
| Absence & shift planning | 2 of 5 |
| Project, cost-centre & billing | 4 of 5 |
| Payroll handoff | 2 of 5 |
| European sovereignty | 1.5 of 5 |
Capture in the real workplace
Show reasoningHide reasoning
How this is scored
How time actually gets recorded across the workforces a buyer has — desk staff, field and site crews, shift and deskless workers — and what happens when the network is not there.
0 — Not a time-recording tool; working time cannot be captured in the product.
3 — Clocking in and out or a timer in the browser or an app, with manual entries; offline use, shared terminals and corrections are basic or not described.
5 — Web and mobile apps for clocking in and out, a shared kiosk, terminal or badge option or offline capture that syncs, and corrections requested by the employee and approved by a manager.
8 — Several capture paths including hardware terminals or badge readers, reliable offline handling, GPS or geofenced check-in where the vendor states its limits, and bulk correction with an audit trail of who changed what.
10 — Capture fits the workforce rather than the reverse: desk, deskless, field and shift models all first-class, offline as a designed state rather than a failure mode, and every correction attributable, reasoned and reversible.
The Operations Lead
Clocking is documented across mobile apps, browser, timeclock terminals and Bluetooth beacons, with a customizable kiosk and offline entry that auto-syncs on reconnect — that speaks to my field and workshop crews. An audit log of all actions and changes, filterable by period, user or team, gives the who-changed-what record. We found no public information on GPS or geofenced check-in with stated limits, or on employee-requested corrections in bulk. 1 3 4 10
The Payroll Officer
Clock-in runs through mobile apps, the browser, a customizable kiosk, timeclock terminals and Bluetooth beacons, and entries made offline auto-sync once connectivity returns. Timesheets are submitted to managers for approval and the platform keeps a full audit log of all changes, filterable by period, user and team, exportable to XLS. We found no public information on GPS or geofenced check-in with stated limits or on bulk corrections, which keeps this short of the top marks. 3 4 6 10
The Works Council Advocate
Capture reaches field crews, not just the desk: web and browser clocking, iOS and Android apps, a shared kiosk, timeclock terminals and Bluetooth beacons are all named, and entries made offline auto-sync once connectivity returns. Corrections run through timesheet approval with a full audit log of every action, filterable by period, user and team, and the pages state plainly there is no keystroke logging, no screenshots and no mouse-movement detection — a tool that measures rather than watches. We found no public information on GPS or geofenced check-in and its limits, nor on what a Bluetooth beacon actually stores, which is the first question co-determination would ask. 1 3 4 6 10
The Agency Owner
Mobile apps, web clocking, timeclock terminals and Bluetooth beacons are all named capture methods, and offline entries auto-sync when connectivity returns — that covers my desk staff and site crews alike. Every change sits in a filterable audit log behind a submit-approve workflow with daily, weekly or monthly locking. I found no public information on GPS or geofenced check-in or on bulk correction. 3 4 6 10
The Field Supervisor
Mobile and web clocking, timeclock terminals, Bluetooth beacons and a kiosk adaptable to the devices are capture paths that survive a real site, and entries made offline auto-sync once the signal returns. Timesheets are submitted to managers for approval or rejection, and a full audit log of all actions and changes filters by user and exports to XLS. We found no public information on GPS or geofenced check-in or on bulk corrections, which holds it below the top of the range. 3 4 6 10
The Skeptic
Four capture paths are documented — mobile and web clocking, timeclock terminals and Bluetooth beacons — plus a customizable kiosk, and offline entries auto-sync once connectivity returns. Timesheets are submitted by employees and approved or rejected by managers, with a full audit log of all actions and changes filterable by period, user and team, exportable in XLS. We found no public information on GPS or geofenced check-in, or on bulk correction of past entries. 3 4 6 10
Working-time law & audit record
Show reasoningHide reasoning
How this is scored
Whether the record satisfies the German recording duty (BAG 2022, § 3 ArbSchG) and the ArbZG rules around it — breaks, maximum hours, rest periods, retention — and whether it survives being inspected.
0 — A project or task timer that keeps no attendance record of working time (start, end, breaks).
3 — Start, end and break times recorded per day with a working-time report per employee; ArbZG checks and retention are basic or not described.
5 — Start, end and breaks recorded for the recording duty (BAG 2022 or ArbZG named), automatic break rules, warnings on the daily maximum or the rest period, and overtime balances.
8 — The ArbZG rules are modelled rather than approximated: break and rest enforcement with documented exceptions, overtime and time-account rules, the two-year retention handled by the system, a change log on entries, and an export built for an inspection.
10 — The vendor treats the record as evidence: tamper-evident entries with full change history, retention and deletion executed per statute, documented handling of on-call, standby and travel time, and published guidance mapping features to the ArbZG sections they serve.
The Operations Lead
Attendance from clock-in events with lunch breaks, overtime and flexitime balances, daily/weekly/monthly locking of timesheets, and an audit log exportable in XLS "ready to present to auditors" are all documented. The compliance framing on the captured pages is American — rounding tied to FLSA and the standard 40-hour week — and we found no public information naming the German recording duty, ArbZG rest or daily-maximum enforcement, or statutory retention beyond up to 90 days after account closure. The raw record is there; the German legal scaffolding around it is not evidenced. 2 4 6 8 10
The Payroll Officer
Clock-in events, calculated overtime, lunch breaks and paid/unpaid hour types are recorded, with hourly flexitime balances and daily or weekly alerts on target hours, but compliance is framed in American terms — FLSA rounding to the 7-minute rule and the standard 40-hour week — rather than the German recording duty. Locking can be daily, weekly or monthly with only system administrators able to edit afterwards, and the audit log exports to XLS ready to present to auditors. We found no public information naming the BAG 2022 decision or the ArbZG, automatic break rules, rest-period enforcement or statutory retention of the working-time record; the only retention statement covers customer data up to 90 days after account closure. 2 4 6 8 10
The Works Council Advocate
Clock-in events, tracked lunch breaks, weekly target hours with overtime alerts, timesheet locking and an XLS audit log "ready to present to auditors" give a defensible daily record. But the pages frame rounding under the American FLSA 7-minute rule and a 40-hour week, and we found no public information naming the German recording duty, on automatic break rules, on rest-period enforcement, or on retention beyond deletion within 90 days after account closure. For our inspection duties under the ArbZG, the statutory layer is undocumented on the captured pages. 2 4 5 6 8 10
The Agency Owner
There is a genuine attendance record — clock-in events, lunch-break tracking, weekly target-hour alerts, flexitime balances and an XLS audit-log export for auditors — but the framing is the 40-hour week and FLSA rounding, which is American law, not the German recording duty. I found no public information on BAG or ArbSchG, automatic break rules, rest-period enforcement or statutory retention. 4 5 6 8 10
The Field Supervisor
Clock-in events, lunch breaks and overtime against target hours are recorded, timesheets can be locked daily, weekly or monthly, and the audit log exports for auditors. The compliance talk on these pages is American — FLSA rounding, the 7-minute rule, the 40-hour week — and we found no public information naming the German recording duty, ArbZG break and rest enforcement, or a statutory retention period; the only retention figure given is up to 90 days after account closure. 2 4 5 6 8 10
The Skeptic
Clock-in events, lunch breaks, overtime against weekly targets and flexitime balances are recorded, with daily/weekly/monthly locking and an exportable audit log behind them — but the one working-time rule the vendor names is American: FLSA rounding to the quarter hour. The security and privacy pages cite GDPR, CCPA, DCAA and SOC II; we found no public information naming the German recording duty, ArbZG break or rest rules, the daily maximum, or statutory retention. For a German inspection, the audit log is the only artifact aimed at auditors. 2 4 6 8 10
Absence & shift planning
Show reasoningHide reasoning
How this is scored
Vacation, sickness and the shift or duty roster — the half of attendance that decides whether the time data means anything.
0 — Neither absence handling nor shift planning is part of the product.
3 — Vacation requests with approval and an absence calendar, or a basic shift plan; entitlement rules and rostering are basic or not described.
5 — Absence management with entitlement balances, sickness recording and an absence calendar, plus shift or duty planning with templates or employee availability.
8 — Public-holiday calendars per location, pro-rata entitlement and carry-over, substitution and swap workflows, shift templates with qualification and rest-period checks, and coverage warnings before publication.
10 — Planning and recording are one system: rosters that respect statutory rest and the works agreement, absence that reflows the plan automatically, and forecast-versus-actual reporting a team lead can act on.
The Operations Lead
Absences are handled by creating a project titled 'Absences' with sick leave, annual leave, maternity leave and national holidays as tasks — a workable construct, but a project tracker's answer to absence, not an entitlement engine. Vacation quota monitoring, employee absence requests with an approval hierarchy, and a calendar overview of absences and shifts are documented. We found no public information on holiday calendars per location, carry-over, substitution and swap workflows, or shift templates with availability. 4 6 7
The Payroll Officer
Employees request absences through a department and approval hierarchy, vacation quotas are monitored, and sick leave, annual leave, maternity leave and national holidays are recorded as task types in a dedicated absence project, alongside a calendar overview of absences and shifts and automatic morning, afternoon and night shift detection with bonuses in the sibling product All Hours. Absences export to payroll. We found no public information on pro-rata entitlement, carry-over, substitution and swap workflows, coverage warnings, or rostering with templates and availability checks. 4 6 7
The Works Council Advocate
Vacation requests with an approval hierarchy, vacation quotas, sick-leave and maternity-leave types and a combined calendar of absences and shifts are documented. Yet the vendor's own help page describes tracking absences by creating a project titled 'Absences' and adding the leave types as tasks — a workaround rather than an entitlement engine — and the fuller absence planning is presented as belonging to the sister product All Hours. We found no public information on holiday calendars per location, carry-over rules, substitution or swap workflows, or rest checks in the roster. 4 6 7
The Agency Owner
Absence requests run through department and approval hierarchies with vacation quotas monitored, and sick, annual, maternity and holiday types are recorded — via a workaround project titled Absences with the leave types as its tasks. Shift planning is a calendar overview of absences and shifts with automatic morning, afternoon and night detection; I found no public information on shift templates, employee availability or entitlement carry-over. 4 7
The Field Supervisor
Employees can request absences, approval hierarchies run as deep as needed, sick leave, annual leave, maternity leave and national holidays are recordable, vacation quotas are monitored and absences export to payroll — though the method is a project titled 'Absences' with leave types as its tasks. Planning is described as a calendar overview of absences and shifts. We found no public information on shift templates, employee availability, swap workflows, or public-holiday and carry-over entitlement rules. 4 6 7
The Skeptic
Absence requests, an approval hierarchy, vacation quotas and a calendar overview of absences and shifts are documented — but the vendor's own help pages describe absence tracking as a convention the customer builds: create a project titled 'Absences' and add sick leave, annual leave and maternity leave as tasks to it. We found no public information on shift templates, employee availability, substitution or swap workflows, holiday calendars per location, or carry-over of entitlement. 4 6 7
Project, cost-centre & billing
Show reasoningHide reasoning
How this is scored
Whether recorded time can carry the allocation an agency, workshop or professional-services firm needs — project, task, cost centre, billable status — through to an invoice or a client report.
0 — Attendance only; the product records time without any project, task or cost-centre dimension.
3 — Time booked to projects or clients with a report per project; rates and billable status are basic or not described.
5 — Projects and tasks with a billable flag, hourly rates, reports per project and client, and an export or integration toward invoicing.
8 — Multi-level structure (client, project, task, cost centre), rate cards by person, role and project, budget tracking with warnings, and an invoice-ready export.
10 — Time becomes revenue without re-entry: approval before billing, rate rules that survive a rate change mid-project, client-facing reports, and a maintained handoff into named accounting or invoicing systems.
The Operations Lead
This is the product's centre of gravity: clients, projects and tasks with tags, rates at person, task and project level with labor costs kept separate from billable amounts, budgets in hours, billable amount or costs with percentage alerts, cost-centre and CapEx/OpEx allocation reports, and numbered invoices created straight from logged hours. Approval before billing exists via timesheet submission to managers. We found no public information on a maintained handoff into named accounting systems or on how rates behave when changed mid-project. 1 4 8 9 10
The Payroll Officer
Recorded time carries a four-level hierarchy of clients, projects, tasks and tags, with cost centres and job codes enabled through custom fields, separate labor and billing rates set per user, task, project or single time log, and monetary or time budgets in total hours, billable amount or costs with percentage-spend email alerts. Numbered invoices are created straight from hours logged, report updates can be scheduled to clients, and a period-specific export of every categorized time entry is built for upload into accounting systems. We found no public information on rate rules surviving a mid-project rate change, and the accounting handoff names no specific systems. 4 8 9 10
The Works Council Advocate
This is the product's spine and it is thorough: clients, projects, tasks and tags in a four-level hierarchy, custom fields for cost-centre or job codes, hourly rates per person, task and project with labour cost kept separate from billing rates, budgets in hours, billable amount or cost with percentage alerts, expenses with receipts, and numbered invoices created straight from logged hours. What holds it back is the handoff: accounting is described generically as 'popular accounting systems', Zapier and API, and we found no public information on rate rules surviving a mid-project rate change. 1 4 8 9 10
The Agency Owner
This is the core of my business: a client-project-task hierarchy with rates by person, project and task, billable flags at every level, and budgets in hours, billable amount or costs with automatic alerts at a set percentage of spend — per project or per task — emailed to the responsible managers, while entry continues after the budget is spent so my teams never stop recording. Invoices are created straight from logged hours, client reports can be scheduled, and time pushes into accounting or ERP. I found no public information on rate rules surviving a mid-project change or on named accounting systems. 1 4 8 9 10
The Field Supervisor
A four-level hierarchy of clients, projects, tasks and tags, rates set per user, task, project or single entry with labour and billable rates kept apart, budgets in hours, billable amount or cost with percentage alerts, and numbered invoices created straight from logged hours — the crew's hours become a client invoice without retyping. Cost allocation reports split CapEx and OpEx by project, team, cost centre and task. We found no public information on handling a rate change mid-project or a maintained handoff into named accounting systems. 4 8 9 10
The Skeptic
Clients, projects, tasks and tags form a four-level hierarchy with cost centers via custom fields; rates can be set per user, project, task and individual time log with labor cost separated from the billable rate; budgets run in hours, billable amount or costs with automatic alerts; and numbered invoices are created straight from logged hours. Timesheets are approved before reports go out. We found no public information on how rates behave when changed mid-project, and the accounting handoff runs through Zapier and an API into unnamed 'popular accounting systems'. 4 8 9 10
Payroll handoff
Show reasoningHide reasoning
How this is scored
How the recorded month reaches payroll — DATEV, Lohn und Gehalt, an in-house system or the tax adviser — and how much of it is automated rather than retyped.
0 — Payroll is outside the product: it records client or project time only and prepares nothing for payroll.
3 — An export (CSV, Excel or PDF) of hours and absences for the payroll office; named formats and surcharges are basic or not described.
5 — A named payroll integration or a documented export format for at least one major system (e.g. DATEV LODAS/Lohn und Gehalt), covering hours, absences and overtime.
8 — Vendor-maintained integration with a named provider, covering night, Sunday and holiday surcharges, time accounts and mid-month changes, with a lock step before transmission.
10 — Payroll is designed for, not exported to: several named systems maintained, an auditable approval and lock, retro handling for corrections after the close, and the tax adviser given their own scoped access.
The Operations Lead
Paid and unpaid hours, overtime, lunch breaks and work-from-home are calculated, absences can be exported to payroll, and reports go out in PDF, XLS and raw CSV/TSV "ready for payroll processing", with a period-specific time-entry report for upload into accounting systems. Connections to payroll run through Zapier and API keys to "any payroll provider" — we found no public information naming a specific system such as DATEV. For my German payroll office this is a build-it-yourself handoff, not a maintained connector. 4 6 10
The Payroll Officer
Payroll export is a declared use case, and paid and unpaid hours, work from home, overtime, lunch breaks and absences export as PDF, XLS or CSV/TSV, with an API and Zapier to connect to any payroll provider the buyer chooses; time logs can be locked daily, weekly or monthly before handoff. The captured pages name no payroll system — nothing like DATEV or Lohn und Gehalt appears — and the only surcharge handling we found is the sibling product All Hours calculating bonuses for morning, afternoon and night shifts. We found no public information on Sunday and holiday surcharges in the export, mid-month changes, or retro corrections after the close. 1 4 6 10
The Works Council Advocate
Hours, absences and overtime export as PDF or XLS "ready for payroll processing", the payroll report covers paid and unpaid hours, overtime and lunch breaks, an API claims to reach "any payroll provider", and time logs can be locked per period before anything leaves. But we found no public information naming a payroll system — DATEV or any other — on surcharge export for night, Sunday and holiday work, or on mid-month changes and retro corrections; the app calculates night-shift bonuses in its shift detection, yet we found no public information on a payroll handoff that carries them. 4 6 10
The Agency Owner
Reports export to PDF and XLS described as ready for payroll processing, overtime goes out in PDF, XLS or CSV, tracked absences export to payroll, and an API is pitched for any payroll provider alongside Zapier with API keys. The captured pages name no payroll system such as DATEV, and timesheet locking at least gives a close step before transmission. I found no public information on night, Sunday or holiday surcharge handling in the export itself. 1 4 6 10
The Field Supervisor
Exports cover paid and unpaid hours, work from home, overtime, lunch breaks and absences in PDF, XLS and CSV/TSV, periods can be locked against editing, and an API or Zapier route is offered toward any payroll provider. We found no public information naming a payroll system or a German-ready format such as DATEV, nor a lock step tied to transmission. 4 6 10
The Skeptic
Paid and unpaid hours, absences, overtime and morning/afternoon/night shift bonuses are calculated, reports export as PDF, XLS or CSV 'ready for payroll processing', and a per-period export of every categorized time entry is built for upload into accounting systems. We found no public information naming a payroll system — the route to 'any payroll provider' runs through Zapier and API keys. Time logs and timesheets can be locked by day, week or month, but we found no public information tying that lock to a transmission step or covering corrections after the close. 4 6 10
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where the data lives, who the contracting entity is, who the subprocessors are, and whether that is documented rather than assumed. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it. Dimensions not proven either way are unknown, not non-European.
0 — Vendor, contracting entity and hosting shown to be outside the EU, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist and one European element is proven (an EU contracting entity or representative, or EU hosting as an option); the rest of the chain is not stated.
5 — An EU contracting entity and EU hosting stated, with a data processing agreement; the subprocessor list is not published in full or includes non-EU providers without a stated safeguard.
8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, the full subprocessor list published with locations, and any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor in the EU, data-centre certification published, and an on-premises or private-cloud option for buyers who need it.
The Operations Lead
The vendor states it is based in the EU with HQ in Ljubljana, Slovenia, claims full GDPR compliance, and holds ISO 27001, 27017 and 27018 certifications. Hosting is Microsoft Azure with the region not stated, the sub-processor list is available only on request, and we found no public information on a data processing agreement. One European element — the EU entity — is proven; the rest of the chain is not stated. 1 2 5
The Payroll Officer
The pages state a European footing — headquarters in Ljubljana, Slovenia and "we are based in the EU" — and hosting is on Microsoft Azure with 99.95% uptime, but no Azure region or EU hosting guarantee is stated. The full subprocessor list is available only on request, and we found no public information on a data processing agreement. A European vendor presence is proven while the rest of the chain — hosting region, subprocessors, agreement — remains unstated. 1 2 5
The Works Council Advocate
The company stands in the EU — headquarters in Ljubljana, Slovenia, and "based in the EU" for over 30 years — with claimed GDPR compliance, TLS 1.3, ISO 27001/27017/27018 certification and backups several times per hour. But hosting is on Microsoft Azure and we found no public information naming the region, the subprocessor list is available only on request by email, vendor staff can reach customer data over VPN for troubleshooting (restricted, logged, monitored), and we found no public information on a data processing agreement or the actual data residency. For co-determination purposes, the chain behind the word 'Azure' is undocumented. 1 2 5
The Agency Owner
Headquarters in Ljubljana, Slovenia and a stated EU base count for something, with GDPR compliance claimed and Azure hosting at a stated 99.95 percent uptime. The Azure region is not stated and the subprocessor list is only available on request; I found no public information on a data processing agreement. 1 2 5
The Field Supervisor
The vendor states it is based in the EU with headquarters in Ljubljana, Slovenia, claims GDPR compliance, and hosts in Microsoft Azure with no region stated; the sub-processor list is available only on request. We found no public information on a data processing agreement, on where the data resides, or on the contracting entity's jurisdiction. 1 2
The Skeptic
The vendor states it is based in the EU with HQ in Ljubljana, Slovenia, claims GDPR compliance, and hosts on Microsoft Azure — but the Azure region is not stated, so EU hosting is proven neither way. The subprocessor list is available only by emailing support, and we found no public information on a data processing agreement or on where the contracting entity is established beyond the stated HQ. 1 2 5
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual invoice for their headcount — including terminals, modules and minimums — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price per user or one priced tier; how cost scales with modules, hardware or minimum seats is unclear.
5 — Per-user prices public for the main tiers with the billing period stated and the main inclusions given; some pieces (terminal hardware, planning module, payroll export) may be unpriced.
8 — Every tier and module priced publicly with per-user maths, billing period, minimum term and VAT treatment stated; only genuinely custom work lacks a number.
10 — Complete price computability: a calculator or table producing the annual invoice for a given headcount and module selection, including hardware, setup and renewal terms.
The Operations Lead
Public and exact: free for teams of up to 5 users, a 14-day free trial with no credit card needed, and API access in every subscription. We found no public information on per-user prices for the paid tiers, and the pages invite teams of 20+ users to book a demo. I cannot compute an annual invoice for 200 heads from these pages. 1 3 5
The Payroll Officer
Public pricing stops at structure rather than amounts: free for teams of up to five users, a 14-day free trial with no credit card, API access in every subscription, and an invitation for teams of 20 or more users to book a demo. We found no public information on per-user prices for the paid tiers, billing periods, or the cost of terminals and planning modules, so a buyer cannot compute an annual invoice from the captured pages. 1 3 4 5
The Works Council Advocate
Public pricing amounts to: "My Hours is free for teams of up to 5 users", a 14-day free trial, no credit card needed, API access in every subscription, and teams of 20+ users invited to book a demo. We found no public information on per-user prices, tier names, billing periods, minimum terms, VAT treatment or terminal hardware. A buyer cannot compute a paid annual invoice for a given headcount from these pages. 1 3 4 5 8
The Agency Owner
Public pricing amounts to free for teams of up to five users, a 14-day trial with no credit card needed, and an invitation for teams of 20-plus users to book a demo. I found no public per-user price for the paid tiers, and no billing period, module or terminal costs, so I cannot compute an annual invoice for my forty heads from these pages. 1 3 5
The Field Supervisor
The public numbers are free for teams of up to five users and a 14-day trial, with API access in every subscription; teams of 20 or more are invited to book a demo. We found no public information on per-user prices for paid tiers, billing period, minimum term, VAT treatment, or what terminals and modules cost — a buyer with thirty workers cannot compute an annual invoice from these pages. 1 3 5
The Skeptic
The only public prices are that teams of up to 5 users are free and the trial runs 14 days with no credit card; we found no public per-user prices, billing period, minimum term or VAT treatment for the paid tiers. Teams of 20 or more users are steered to a demo with product experts, and the timeclock terminals and Bluetooth beacons shown on the capture pages carry no price at all. 1 3 5
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined ⚠ unverified | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about My Hours
Is My Hours European?
Not determined: the vendor’s pages as captured do not say where My Hours is based.
Where does My Hours store data?
Not stated on the vendor’s pages as of 3 Nov 2026.
Does My Hours have a free plan?
Yes. My Hours has a free plan, per the vendor’s page captured 3 Nov 2026.
What are the best alternatives to My Hours?
As of 4 Nov 2026, the panel rates TimeTac (3.5/5), clockodo (3/5) and GFOS (3/5) highest among the other 27 Time Tracking & Attendance products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is TimeTac (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: My Hours alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 3 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity, Hosting location. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (10)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page myhours.com Checked 3 Nov 2026 Details →
- 2 Privacy policy — found from the homepage myhours.com Checked 3 Nov 2026 Details →
- 3 Capture in the real workplace — found from sitemap myhours.com Checked 3 Nov 2026 Details →
- 4 Capture in the real workplace — found from sitemap myhours.com Checked 3 Nov 2026 Details →
- 5 Working-time law & audit record — found from sitemap myhours.com Checked 3 Nov 2026 Details →
- 6 Absence & shift planning — found from sitemap myhours.com Checked 3 Nov 2026 Details →
- 7 Absence & shift planning — found from sitemap help.myhours.com Checked 3 Nov 2026 Details →
- 8 Project, cost-centre & billing — found from sitemap myhours.com Checked 3 Nov 2026 Details →
- 9 Project, cost-centre & billing — found from sitemap help.myhours.com Checked 3 Nov 2026 Details →
- 10 Payroll handoff — found from sitemap myhours.com Checked 3 Nov 2026 Details →