Inno Time — attendance for people who sit at a computer

A terminal at the gate answers nothing for a desk worker. What this records, what it deliberately does not, and why the PC’s claim is kept in its own column.

Attendance for people who sit at a computer

A fingerprint terminal at a factory gate answers the attendance question for the factory. It answers nothing for the person who works at a desk, and it answers nothing for a branch with no terminal.

What Inno Time records

It runs on the employee’s own PC. It records a check-in, a check-out, and how many minutes of the day were active — where active comes from the operating system’s last-input counter, not from watching what anybody types.

The privacy line, and where it is drawn

• There is no keystroke logging and no screenshot code path.
• Application names are opt-in, and it is the SERVER that decides — a branch with app tracking switched off has those names trimmed on arrival, not merely hidden on a screen.
• Minutes that cannot be measured are counted as unknown rather than quietly counted as idle.
• The employee’s own profile screen shows them exactly what is being recorded.

It is the machine’s claim, and it is labelled as one

What the PC reports is kept apart from what the server observed, and the reports show them in separate columns. A tool that blends the two lets a client-reported figure pass as an audited one.

Running unattended, and saying so when it cannot

It can start with Windows and run with nobody opening a window. Every reason it might refuse — not configured, branch switched off, a crash — is written to a log beside the config, because a background tool whose failures are invisible is a tool everybody believes is working.