Four modes, one policy engine

Track each person the way their role, contract and country require.

Manual for people who start their own clock. Automatic for continuous-capture environments. Hybrid for most knowledge work. Silent only where law and device ownership allow. One workspace, one set of approved hours.

Get started See what it measures

Manual Mode

Press Start; nothing is recorded until you do.

Best for: Freelancers, agencies, consultancies and trusted seniors.
Who starts it: The member starts and stops the clock.
Capture window: Exactly while the timer runs.

Zero capture events of any kind while the timer is stopped.
Explicit project and task chosen per entry.
Idle time is offered back to you: keep, discard or reassign.
Primary risk is under-reporting — you forgot to start — never over-collection.

Automatic Mode

The agent runs whenever the device does — bounded by policy.

Best for: Offices, BPOs, call centres and regulated operations.
Who starts it: The device starts it, at boot or login.
Capture window: A policy-defined window: continuous, or a working-hours fence.

Reaches its tracking state within ten seconds of login, inside the window.
Outside the window it records a suppressed marker — the gap is explained, not mysterious.
First-run disclosure precedes any capture; the acknowledgement is recorded.
Attribution resolves automatically, with a single end-of-day catch-up prompt.

Hybrid Mode

Automatic capture, with an optional manual timer for attribution.

Best for: The recommended default for most knowledge-work teams.
Who starts it: The device captures; the member may start a timer to label it.
Capture window: The automatic capture window; the timer only tags the stream.

One capture stream — the timer labels it, so double-counting is impossible.
When the timer runs, time attributes to that project and task.
When it doesn't, capture continues and attributes by rule.
Best for agencies with salaried staff, product teams and hybrid offices.

Silent Mode

A windowless variant for company-owned devices, where lawful.

Best for: High-security estates with explicit, company-owned-device policy.
Who starts it: The device, with no visible indicator on the machine.
Capture window: As configured — but every gate below must pass first.

Requires Business+, a permitting region, and a company-owned device.
Requires a signed Owner acknowledgement, stored with timestamp and IP.
Blocked in the EU, NSW/ACT, and under every GDPR-/HIPAA-/GLBA-safe profile.
Even then, the member's own web dashboard still shows their data by default.

The capture fence

Working hours are a fence around capture — never a schedule, never attendance.

A working-hours window exists for exactly one reason: to bound when the automatic agent may capture. That's what makes continuous mode lawful. It is a capture boundary, and nothing more.

Inside the fence

The agent captures apps, sites, input counts and — if enabled — screenshots.
Outside it, the agent stays alive and records a single suppressed marker — the gap is explained, not mysterious.
Genuinely working late? Open an explicit out-of-window session. It's tracked time — not overtime entitlement.

“You're outside your capture window — nothing is being recorded.”

What the fence is not

Tracked time is still tracked time — a report can show a person tracked 6h 20m on a Tuesday. What it will never do is call that “present”, judge it late, or measure it against an expected day.

No punch in / punch out
No present / absent / late status
No punctuality or absenteeism
No attendance calendar
No location or office-vs-remote inference

Hybrid is the recommended default — automatic capture, with an optional timer to attribute it.

Create a workspace How we keep it lawful