Time Tracking & Attendance
Toggl Track
EU-Made Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Toggl OÜ · toggl.com
Compare with clockodo → Compare with Clockify → Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Toggl Track, from Estonian vendor Toggl OÜ, is scored as a project time tracker, not a German compliance tool. Project and billing is the strongest result, clustering at 6: billable rates from Starter, Premium labor costs and profitability reports, fixed-fee projects, and time-actuals-versus-estimates dashboards. Weakest are payroll export and working time law, both 1 to 2: the month leaves as CSV, PDF or the API with no named payroll system or surcharge handling, and no break rules, rest periods or inspection-ready record appear on the pages. Time capture clusters at 4 — built for people at a desk, with no public information on shared terminals or offline clock-in — and absence and planning runs 3 to 4: holiday capacity, not duty rostering. The genuine split is sovereignty, 3 to 6: higher scores credit processing stated to sit in Estonia under Toggl OÜ plus ISO/IEC 27001:2022 certification; lower ones cite the Delaware contracting option and a sub-processors page not captured. Pricing transparency scores 5 to 6: Starter at $9 and Premium at $16 per user per month are public; add-on prices are not.
Speaks for it
- Billable rates from Starter plus Premium labor-cost, profitability and fixed-fee reporting carry recorded time through to client billing
- Timers run on web, mobile, desktop and browser extensions, with idle-time detection and timesheet approvals in Premium
- Starter at $9 and Premium at $16 per user per month are public, with a $0 free plan, a 30-day trial and an annual '4 months free' option
- ISO/IEC 27001:2022 certification with regular audits is on record, with processing operations stated to sit in Estonia under Toggl OÜ
- The timeline and auto-tracker are opt-in, with their records visible only to the user concerned
Held against it
- Only CSV, PDF and API export are evidenced for a closed month, with no named payroll system, defined payroll format or surcharge handling shown
- No public information appears on break rules, daily maxima, rest periods or a working-time record built for inspection
- No public information appears on offline capture, shared terminals or GPS clock-in for deskless crews
- Leave handling shows no public information on entitlement calculation, carry-over or sickness recording, and the Time Off Pro add-on carries no public price
- Enterprise is contact sales and the free plan is 'for a limited number of users' with no number stated, so a full annual invoice cannot be computed from public pages
Best for
- You run an agency or professional-services team that bills client time and needs billable rates, fixed-fee projects and profitability reporting
- Your team captures time at a desk across web, mobile, desktop or browser timers
- You want public per-user pricing and a $0 free plan with a 30-day trial before committing seats
Avoid if
- You must hand a closed month to a payroll system in a defined format with surcharge handling — the documented exits are CSV, PDF and the API
- You carry the German working-time recording duty and need break and rest-period checks with an inspection-ready record
- Your crews clock in at shared terminals, offline or by GPS at job sites rather than from personal devices
- You need duty rosters with substitution and coverage checks rather than project boards, timelines and calendars
The scores
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 — One browser timer and nothing else; anyone away from a desk records nothing.
3 — Web plus a mobile app, but no offline capture, no shared terminal, and corrections are an admin task rather than a workflow.
5 — Web, mobile and at least one shared capture point (kiosk, terminal or badge), with offline capture that syncs, and a correction workflow with approval.
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
Timers run on web, Android and iOS, Windows and macOS desktops and browser extensions, and Premium adds timesheet approvals and idle detection. For the workshop wall and the field crews we found no public information on offline capture, a shared kiosk or terminal, or GPS check-in, so capture ends at whoever carries their own phone. 2 2
The Payroll Officer
Web, mobile, desktop and browser extensions give desk staff several ways to start a timer, and timesheet approvals in Premium mean corrections at least pass a reviewer. We found no public information on offline capture, shared terminals or kiosks for site crews, geofenced check-in, or an audit trail of who changed what on an entry. This is a timer built for people at a desk, not a capture model for a mixed workforce. 2 2
The Works Council Advocate
Desktop, browser, web and mobile timers with idle-time detection cover the office, and I note the timeline and auto-tracker are opt-in with their records visible only to the employee concerned — that is how it should be. But we found no public information on a shared terminal or kiosk for shift and deskless crews, on offline capture, or on GPS or geofenced check-in and what it stores, and correction rides on Premium timesheet approvals with no stated audit trail of who changed what. 3 2 2
The Agency Owner
Capture is built for desk teams like mine: web, Windows and macOS desktop apps, iOS and Android, Firefox and Chrome extensions, real-time and manual timers, idle detection, and timesheet approvals on Premium. We found no public information on offline capture, shared kiosks or terminals for site crews, GPS check-in, or bulk corrections with an audit trail of who changed what. 2 2
The Field Supervisor
Timers run on web, mobile, desktop and browser plugins, with timesheet approvals and idle detection — fine for desk staff, but I found no public information on offline capture, a shared kiosk or terminal for a crew, or GPS and geofenced clock-in. Anyone working in a basement fills this in from memory on Friday. 2 2
The Skeptic
Web, mobile, desktop and browser-extension timers with idle-time detection are documented, and timesheet approvals at Premium give corrections a workflow rather than an admin chore. But we found no public information on offline capture, a shared kiosk or badge terminal, or GPS/geofenced clock-in — so the site crew and the shift worker have no evidenced way in. This is capture built for people who already have a browser tab open. 2 2
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 — Hours are summed and nothing else; no break handling, no limits, no retention statement.
3 — Break deduction exists but is a flat rule; no daily maximum or rest-period checks, and no stated retention period.
5 — Configurable break rules, warnings on the 8/10-hour daily maximum and the 11-hour rest period, and per-employee reports covering the recording duty.
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, 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
Timesheet approvals and required fields are evidenced, but we found no public information on break rules, the eight- or ten-hour daily maximum, the eleven-hour rest period or a two-year retention of time records built for an inspection. The retention figures published — 90 days for logs, seven years for billing records — sit in a privacy policy, not a working-time record. 3 2
The Payroll Officer
Nothing in the captured pages addresses the German recording duty: no break rules, no daily maximum or rest-period checks, and no statement that time entries are kept for the statutory period. The privacy policy shows a formal retention policy and ISO/IEC 27001 certification, but those govern personal data generally, not a working-time record that survives inspection. I would not hand this month to an auditor as evidence of compliant working time. 3 2
The Works Council Advocate
Nothing captured addresses the German recording duty: no break rules, no warnings on the eight-hour maximum or eleven-hour rest period, no tamper-evident change history, no on-call, standby or travel-time handling. The retention figures I found — seven years for contract and billing records, ninety days for logs — sit in the privacy policy and are not a working-time record kept for inspection. 3 2
The Agency Owner
The timers produce timestamped entries and approvals exist, which is a floor, but these pages sell project time, not German compliance: we found no public information on break rules, the eight and ten hour daily maximums, the eleven-hour rest period, or a two-year working-time record built for an inspection. 2
The Field Supervisor
I found no public information on break handling, rest periods, the daily maximum, or retention aimed at working-time records; the retention statements that do exist cover personal data like ninety-day logs and seven-year billing records. Idle detection is a nudge, not break enforcement, and nothing here reads as built for an inspection. 3 2
The Skeptic
We found no public information on break handling, the eight- and ten-hour daily maxima, the 11-hour rest period, or retention of the working-time record itself — nothing on the pages maps a feature to the BAG 2022 decision or § 3 ArbSchG. The only retention statements we found cover personal data, logs and accounting records, not an inspection file for a German authority. The vendor positions the product around capacity and profitability, and the captured pages make no conformity claim I could test. 3 1
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 — No absence handling; vacation lives in a separate calendar or spreadsheet.
3 — Vacation requests with approval, but entitlement is manual, carry-over is not handled and there is no rostering.
5 — Automatic entitlement and carry-over, sickness recording, an absence calendar, and basic shift planning with availability.
8 — Public-holiday calendars per location, pro-rata entitlement, 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
PTO, public holidays and flexible hours are listed, and a Time Off add-on connects leave management with capacity planning, which is more than a spreadsheet. We found no public information on automatic entitlement, carry-over, sickness recording, swaps or any shift roster with rest checks — and with workshop and field staff, no roster means the time data tells me half the story. 2 2
The Payroll Officer
Capacity basics list PTO, public holidays and flexible hours, and a Time Off Pro add-on promises to connect leave management with capacity planning. We found no public information on automatic entitlement, carry-over, sickness recording, or any shift roster with substitution and coverage checks — the planning on show is project planning, not a duty roster. Vacation appears as a capacity assumption rather than an administered entitlement. 2 2
The Works Council Advocate
PTO, public holidays and flexible hours appear as capacity basics, and a Time Off Pro add-on connects leave management with capacity planning, but we found no public information on automatic entitlement, carry-over, sickness recording or a request-approval workflow. The planning views on display are boards, task lists, timelines and calendars for projects — not shift rosters with qualification or rest-period checks. 2 2
The Agency Owner
PTO and public holidays feed individual-level capacity, flexible hours are modelled, and a Time Off Pro add-on connects leave management to capacity planning. We found no public information on automatic entitlement with carry-over, sickness recording, substitution and swap workflows, or a shift roster — this is holiday planning for project teams, not duty rostering. 2 2
The Field Supervisor
PTO, public holidays and flexible hours appear in the plans and a Time Off Pro add-on handles leave, but I found no public information on entitlement calculation, carry-over, sickness recording or any shift roster. What's planned here is tasks and Gantt-style views, not a duty roster a foreman publishes for a site. 2 2
The Skeptic
The absence offer is 'PTO, public holidays, and flexible hours' at Starter plus a Time Off Pro add-on for leave management, while the planning features — boards, task lists, a Timeline working as a Gantt chart, a Calendar — plan projects rather than people's shifts. We found no public information on automatic entitlement, carry-over, sickness recording, substitution or swap workflows, or shift templates with rest-period checks. What gets approved is the timesheet, not the leave, and the add-on is named without price or mechanics. 2 2
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; no project, task or cost-centre dimension at all.
3 — A free-text note or a single project field, with no rates, no billable flag and no per-project reporting.
5 — Projects and tasks with a billable flag and per-project reports, plus a rate per person or per project.
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
Unlimited projects and tags, tasks with billable rates, labour costs, profitability reports, fixed-fee projects and time-actuals-versus-estimates dashboards are all evidenced — an agency or professional-services team could genuinely bill on this. We found no public information on a client-and-cost-centre hierarchy, rate cards by role, budget warnings or an invoice-ready handoff into named accounting systems. 2 2
The Payroll Officer
Unlimited projects and tags, billable rates from the Starter tier, and labor costs, fixed-fee projects and profitability reports in Premium mean recorded time genuinely carries a billable dimension through to reporting. We found no public information on a client-project-task or cost-centre structure, rate rules that survive a mid-project rate change, budget warnings, or a maintained handoff into any invoicing or accounting system. Strong for project time, unfinished for revenue. 2 2
The Works Council Advocate
This is the product's home ground: unlimited projects and tasks, billable rates from the Starter tier upward, fixed-fee projects, labour costs and profitability reports, and dashboards of time against estimates. We found no public information on cost-centre levels, rate cards per role, budget warnings or an invoice-ready export into a named invoicing or accounting system. 2 2
The Agency Owner
Unlimited projects, tasks and tags, billable rates from Starter, team revenue reports, labour costs and profitability on Premium, fixed-fee projects, and dashboards of time actuals against estimates by task and member — the allocation I bill on is present. We found no public information on a client and cost-centre level above projects, rate cards by role that survive a mid-project change, budget warnings before an overrun, or a maintained handoff into a named invoicing system; the export evidence is generic CSV and PDF. 2 2
The Field Supervisor
This is home ground: billable rates from Starter upward, labor costs and profitability reports, fixed-fee projects, estimates against actuals, and timesheet approvals behind the numbers. I found no public information on cost-centre structure, budget warnings or a handoff into a named invoicing system — the exports shown are generic CSV and PDF. 2 1 2
The Skeptic
This is the home ground: billable rates from Starter, team revenue reports, fixed-fee projects, Premium labor-cost and profitability reports and dashboards of time actuals versus estimates — real allocation for an agency. We found no public information on a client–project–task–cost-centre hierarchy, role-based rate cards, budget warnings, or an invoice-ready export into a named accounting system; the exports on offer are CSV and PDF. Timesheet approvals exist, but they are sold for data accuracy, not as a billing release gate. 2 2
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 — No payroll path stated; the month leaves as a spreadsheet someone retypes.
3 — Generic CSV said to be usable for payroll, with no named system, no defined format and no handling of surcharges.
5 — A named payroll integration or a documented export format for at least one major system, 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
The month can leave as CSV or PDF, but we found no public information on any named payroll system — DATEV or otherwise — a defined payroll format, surcharge handling or a lock before transmission. For my payroll clerk that is a file someone retypes. 2
The Payroll Officer
The month leaves as a CSV export, a PDF or through the API — no named payroll system, no defined format, no night, Sunday or holiday surcharges, no time account, no lock before transmission and no path for corrections after the close. A CSV is an admission the handoff was never designed; someone retypes the month and owns the surcharge maths themselves. For a payroll run this sits at the bottom of the scale. 2
The Works Council Advocate
The month leaves as a CSV or PDF export. We found no public information on any named payroll system, a defined payroll format, surcharge handling for night, Sunday or holiday work, or a lock step before transmission — for payroll, this is a spreadsheet someone retypes. 2
The Agency Owner
The only export evidenced is generic CSV and PDF. We found no public information on a named payroll system, a defined payroll format, night, Sunday or holiday surcharges, or a lock step before transmission. 2
The Field Supervisor
I found no public information on a payroll handoff — no named system, no defined format, no surcharge handling, no lock step. All that's shown is generic CSV and PDF export, so the month leaves as a file somebody retypes. 2
The Skeptic
The documented exits for a closed month are CSV export, PDF export and an API; we found no public information on a named payroll system such as DATEV, a defined payroll format, night, Sunday or holiday surcharges, time-account transfer, or a lock step before transmission. That is a file someone retypes into payroll — exactly the chore the buyer is trying to stop paying for. 2
European sovereignty
panel opinion
panel disagrees
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.
0 — Non-EU vendor and contracting entity, hosting region unstated or non-EU, subprocessors not named.
3 — EU hosting offered as an option, but the contracting entity is non-EU or the subprocessor list is absent.
5 — EU hosting as standard and an EU contracting entity, but the subprocessor chain includes non-EU providers without an explained safeguard.
8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, full subprocessor list published, 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
Processing is stated to sit in Estonia under the Estonian company, even where the contract runs through the Delaware entity, with Standard Contractual Clauses and adequacy mechanisms named for transfers. The captured pages name no external subprocessors, no data-centre provider and no on-premises option, and the Delaware contracting option is a wrinkle I would want closed in writing before 200 staff's data lands anywhere. 3
The Payroll Officer
The default contracting party is Toggl OÜ in Tallinn with processing operations in Estonia, and transfers outside the EU are at least given named mechanisms such as adequacy decisions and Standard Contractual Clauses. But the full sub-processor list sits on a page whose contents we have not captured, a Delaware sister entity can also be the contracting party, and we found no public information on the data-centre provider or its certification. Sovereignty is plausible but asserted, not evidenced end to end. 3 2
The Works Council Advocate
The default controller and processor is Toggl OÜ with processing in Estonia, and even customers contracting through the Delaware sister entity have their processing delegated to Toggl OÜ in Estonia, with international transfers documented through adequacy decisions or Standard Contractual Clauses with impact assessments. But the referenced sub-processors page was not among the captures, so the chain beyond the internal Toggl group cannot be verified here, and no data-centre provider is named. 3
The Agency Owner
The privacy policy puts processing in Estonia with Toggl OÜ as the default processor, and ISO/IEC 27001:2022 certification plus documented transfer mechanisms including standard contractual clauses are stated. The group also contains a Delaware entity customers may contract with, and the sub-processor list lives on its own page — we found no public information on who is on it. 3 2
The Field Supervisor
The privacy policy states processing operations in Estonia with Toggl OÜ as the default processor, and transfer mechanisms (adequacy decisions, contractual clauses with impact assessments) are spelled out. Against that stand a Delaware contracting option, a sub-processors page whose contents are not among the captured pages, and no named data-centre provider with its certification. 3 2
The Skeptic
Processing operations are stated to sit in Estonia, the default controller/processor is the Estonian Toggl OÜ, and ISO/IEC 27001:2022 certification with regular audits is on record. But the same privacy policy names Toggl, Inc. of Delaware as an entity customers may contract with, and beyond internal Toggl Group companies we found no public information on the sub-processor chain, the data-centre provider or ownership. International transfers are papered over with adequacy decisions and standard contractual clauses — lawful scaffolding, not a DACH-clean chain. 3 2
Pricing transparency
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 per-user headline exists, but hardware, modules or a minimum seat count are unpriced or unmentioned.
5 — Per-user prices public for the main tiers with the billing period stated, but at least one commonly needed piece (terminal hardware, planning module, payroll export) sits in an unpriced bundle.
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
Starter at $9 per user per month and Premium at $16 per user per month are public with monthly billing, an annual "4 months free" term, a $0 free tier and a full feature-comparison page. Enterprise is contact-sales, the Time Off and onboarding add-ons carry no number, and we found no public information on VAT treatment or minimum terms — so I cannot compute my annual invoice for 200 heads from the public pages alone. 2 2
The Payroll Officer
Starter at $9 per user per month and Premium at $16 per user per month are public with the monthly period stated, annual billing is spelled out as 4 months free, and a compare-all-plan-features page exists. The Time Off Pro add-on, the expert onboarding package and the Enterprise tier carry no price, and VAT treatment is not stated, so a buyer can price the seats but not the whole annual invoice. 2 2
The Works Council Advocate
Starter at $9 per user per month and Premium at $16 per user per month are published with monthly billing stated, alongside an annual option advertised as 4 months free, a free tier and a full feature-comparison page. The Enterprise plan is contact-sales only and the Time Off Pro and expert-onboarding add-ons carry no public price, so the real annual invoice for a given headcount cannot be computed from public pages alone. 2 2
The Agency Owner
Starter at $9 per user per month, Premium at $16 per user per month, Free at $0, and "4 months free Annual (Save 33.3%)" give the per-user maths for the main tiers with the billing period stated. Enterprise is "Contact Us", and the pieces I would add — Time Off Pro and the expert onboarding package — carry no public number; we found no public information on VAT treatment or minimum terms. 2 2
The Field Supervisor
Starter and Premium are priced publicly per user per month ($9 and $16) with the annual deal stated as four months free, plus a $0 tier and a feature-comparison page. But the free tier is quoted as free "for a limited number of users" without the number, Enterprise is contact-sales, and the add-ons — Time Off Pro, expert onboarding — carry no price I could find, with VAT treatment and minimum term unstated. 2 2
The Skeptic
Starter at $9 per user per month and Premium at $16 per user per month are public, with monthly billing and an annual option of '4 months free', plus a feature-comparison page. But the Free plan is 'for a limited number of users' with no number stated, Enterprise is 'contact sales', and we found no public price for the Time Off Pro add-on or the expert-onboarding package — a buyer with leave-management needs cannot compute the annual invoice. We also found no public information on VAT treatment or a minimum term. 2 2
European sovereignty — proven facts
0 of 4 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 |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 30 Aug 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, Data residency. 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.
- 95 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 17 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 13 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 12 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 subprocessors fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (10)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Product page toggl.com Checked 5 Oct 2026 +2 earlier captures: 11 Sep 2026, 30 Aug 2026 Details →
- 2 Pricing toggl.com Checked 5 Oct 2026 +2 earlier captures: 16 Sep 2026, 30 Aug 2026 Details →
- 3 Privacy policy toggl.com Checked 5 Oct 2026 Details →
- 4 Legal notice — found from the homepage toggl.com Checked 5 Oct 2026 Details →
- 5 Capture in the real workplace — found from sitemap toggl.com Checked 5 Oct 2026 Details →
- 6 Capture in the real workplace — found from sitemap toggl.com Checked 5 Oct 2026 Details →
- 7 Absence & shift planning — found from sitemap docs.toggl.com Checked 5 Oct 2026 Details →
- 8 Project, cost-centre & billing — found from sitemap support.toggl.com Checked 5 Oct 2026 Details →
- 9 Project, cost-centre & billing — found from sitemap toggl.com Checked 5 Oct 2026 Details →
- 10 Payroll handoff — found from sitemap toggl.com Checked 5 Oct 2026 Details →