What does the system record when I check in?
A check-in records the moment, the date and the person. The attendance row then holds check-in, check-out, working hours derived from the pair, a status, and the late minutes against the assigned shift. No location, no photograph and no device fingerprint is captured at any point.
Naming what is captured matters more than reassuring people about it, because a list can be checked and a reassurance cannot.
Everything in that row exists to answer one of two questions. When did the day start and end, and how does that compare with what was scheduled.
Nothing in it answers where somebody was, because nothing collects that. The browser card takes no position and the settings behind it hold no location option to enable.
The fingerprint terminal is the exception people expect, and it is narrower than it sounds. A device on the office network matches a scan to an enrolled device user. The link between that device user and a system account is held in its own mapping screen.
That mapping is worth knowing about, because it is where this path usually goes wrong. A person enrolled on the device but not linked to an account produces scans that land nowhere. The screen counts those unmapped users for exactly that reason.
None of this changes the shape of the row. Whichever path wrote it, the row holds a time, a date, a status and the hours between the pair.
Read your own row rather than trusting a summary of it. Every figure built for a team starts as rows like yours, and the row is the thing that is actually true.
Corrections add their own layer. An approved manual punch is applied by a named person, and the activity log keeps the field-level before and after values, so an amended row shows what it previously held.
Read your own record rather than asking what it contains. Seeing your own attendance sits in the baseline every account holds, alongside marking it.
Related questions
Is there a photograph or selfie capture?
No. Nothing in the check-in path captures an image. The browser card records a time, and the office terminal matches a scan against an enrolled device user.
Who can see my row?
You can, and so can people whose role carries the attendance permissions. Visibility follows the role model rather than being open to everyone.
How current is the terminal data?
The attendance header shows how many minutes ago the device last synced, so the freshness of the figure is visible rather than assumed.