Staff tap a card, scan a code, or stand in front of a shared device — and they're clocked in, verified by place, person and time. No shared login, no paper register, no arguing about hours on payday.
15-day trial · no card · works on the phones your team already carries
Rotates every day. Scanned from outside the geofence gets routed to review, not silently rejected.
Nobody has to think about it on the floor. What changes underneath is how confidently Clockify can answer where, who and when.
A shared device, a tapped NFC card, or a scanned wall QR — whichever fits the site and the budget.
Location, an on-device face check and server time combine into one assurance score for the punch.
Written once, append-only. A correction adds a new row and marks the old one superseded — nothing is edited away.
A personal code on the staff app rotates every 30 seconds. The shared device scans it, takes the selfie with its own camera, reads its own GPS. Works either direction — the kiosk can scan staff, or staff can scan the kiosk.
Tap to clock, with location and a photo. NTAG424 DNA cards sign every tap with AES-CMAC for High assurance; budget NTAG213/215 cards are capped at Medium and always require a location and face check.
No hardware to buy — the whole reason it exists. It is intentionally not single-use, so its ceiling is Medium: the geofence and face check are what stop a photo of the poster from being scanned at home.
One screen, one button, and an honest view of their own hours.
Know who is in, who is late, and clear exceptions before the shift ends.
Configure the rules once, then run payroll from records you can defend.
A dead battery, a basement with no signal, a phone without NFC, a face the camera can't read in backlight. None of it should cost someone their hours.
The site’s policy decides the fallback — usually the wall QR, or a supervisor approving in person.
Clockify states the distance plainly and offers to submit for review rather than silently refusing.
Backlight and masks are image problems, not suspicion. Retake, or a manager captures it for them.
The punch is stored on the device with its real captured time, and uploads itself once reconnected.
The day is marked incomplete and routed for correction — Clockify never invents hours to fill the gap.
Capped at Medium assurance automatically, with a location and face check always required on that tag.
Hours, overtime and late arrivals roll up per site from records that were never editable in the first place.
| Employee | Site | Regular | OT |
|---|---|---|---|
| Aisha Rahman | Marina | 104h 10m | 3h 20m |
| Rahul Verma | Andheri | 96h 30m | 1h 10m |
| Sara Al Amri | Marina | 106h 00m | 5h 45m |
Every tenant’s data is isolated by a database policy, not application code that could forget to filter — with a dedicated database available for auditors who want physical separation.
A database trigger rejects DELETE on punches; audit events reject UPDATE and DELETE. A correction writes a new row — the original stays visible.
The camera opens only for a clock-in or clock-out. Selfies upload under a server-issued key — the client never chooses where its own evidence is stored.
Selfies default to a 90-day purge; consent for face, location and storage is captured per purpose, versioned, and withdrawable.
Only if you want High assurance from day one — an old phone at the door, or NFC cards. The wall QR option needs nothing but a printed sheet, at a lower assurance ceiling.
A supervisor can capture the punch from their own device, including the verification photo. It’s always recorded as an override and always reviewed.
The credential proves the place, the face check proves the person. A passed-around phone or a photographed poster fails the check the site requires, and repeated attempts surface as a flag rather than a silent rejection.
It doesn’t bounce. Assurance below the site’s minimum routes the punch to a review queue instead of rejecting it outright — a manager decides, with the evidence attached.
Clear the review queue, then export validated hours as a CSV, or read them through the API into the payroll system you already use.
Most companies use the shared, RLS-isolated cluster. A dedicated database is available at twice the plan price for teams whose auditors want physical separation — you can move to it later.
300 + tax a month covers up to 5 people, including a year of stored attendance data. Each additional person is 30 + tax a month. It is a monthly subscription billed in advance, no annual plan — the 15-day trial is followed by a full month’s charge, then monthly after that; staff added mid-month are billed in full for that month. Keeping data on file beyond the first year is 500 + tax a year. Prices outside India are 50% higher in the local currency.
Register, add a site, order or write your first tag, invite the team. Most shops are running before the next shift starts.

Attendance a shared device, an NFC card, or a printed QR code can capture — with the evidence attached, not just a timestamp.
Occasional notes on new features and product changes. Never daily mail.
Punch clocks and shift reviews — wherever you are.
Benagon Technologies Private Limited — trading as Clockify
CIN: U72200KL2022PTC077476 | GSTIN: 32AALCB0089Q1Z9
© 2026 Benagon Technologies Pvt. Ltd. All rights reserved.
Compliant with IT Act 2000, DPDPA 2023 & Consumer Protection Act 2019