Where your organization has enabled it, the mobile app can record a location trail during your working session — the path of a field day, used for route review, visit verification and journey planning. The design principle throughout is that tracking is bounded and visible: it runs only while you are checked in, it announces itself on the device while it runs, and it never operates without the operating system's location permission, which stays in your hands. This page explains exactly when it records, what it records, and where the boundaries are.
This page deliberately has no web screenshot. The evidence that matters is native and stateful — the pre-check-in disclosure, operating-system permission prompt, active-session notification and check-out transition — and a responsive web page cannot prove any of them. Add a visual only from an authenticated demo2 mobile build in a test check-in session that can be ended immediately after capture.
Verify the organization has enabled tracking, review the disclosure before check-in, confirm the operating-system permission and look for the persistent tracking indicator while the session is active. Check-out must end capture; revoking permission must degrade or stop it without silently widening collection.
When it records — and when it cannot
The trail is tied to the attendance check-in session. Recording starts when you check in, and stops when you check out — there is no other trigger. Off shift, before check-in, after check-out, or in an organization that has not enabled the feature, no trail is captured. Where your organization allows pausing a check-in session, pausing also stops location capture until you resume; the session timer and the trail freeze together.
The check-in screen tells you before you start: when tracking is enabled, it states that your location will be recorded at roughly the configured interval while you are checked in — including with the app in the background — and that recording stops at check-out. You check in with that disclosure in front of you, not after the fact.
What is captured
While a session is active, the app records position fixes on the cadence your organization configured — typically about once a minute, and only when you have actually moved a minimum distance, so standing at a counter does not generate a stream of identical points. Each fix carries coordinates, their accuracy, a timestamp, and where the device provides them, speed and heading. That is the whole payload: the trail is position over time, not screen activity, not audio, not anything else on the phone.
Fixes are batched on the device and sent to the server in groups. Offline, batches queue like any other change and go up when connectivity returns, so a day in poor coverage still produces a complete trail — with nothing extra captured because of the gap.
Visible while it runs
Continuous tracking is deliberately impossible to miss on the device. The operating system shows its own location-in-use indicator, and the app posts a persistent notification for the duration — xMatix is tracking your visit path / Location is recorded while you are checked in. When the notification is gone, tracking is not running. This is the practical answer to "is it recording right now": look at the phone, not the documentation.
Permissions stay with you
Background tracking requires the OS-level "always allow" location permission, which only you can grant and can revoke later in device settings. When your organization has enabled a session trail, the app treats that background permission as a check-in prerequisite: the check-in screen explains why it is needed, shows the device-settings path, and keeps Check in disabled until permission is granted. This prevents a session from starting under a disclosure that the phone cannot actually honor. Your organization may separately require a single location at the moment of check-in as an attendance gate; that one-time stamp is governed by its own rule and is distinct from the continuous trail.
Trail versus stamp
It is worth separating continuous tracking from the single location stamps the platform uses elsewhere, because they are governed differently. A check-in punch may carry the location where it happened; a form's geography field fills with Use my location when you tap it; a visit activity may stamp the record it creates. Each of those is one point, captured at one deliberate moment, attached to one record. The trail described on this page is the only continuous capture in the app, and it exists only inside a check-in session in organizations that have turned it on.
Common questions
Can the app track me after I check out, or off shift?
No. Capture starts at check-in and stops at check-out; outside a session there is no recording mechanism running. The persistent notification gives you an independent check — if it is not showing, the app is not tracking. Uninstalling nothing and configuring nothing on the device changes this boundary; it is how the feature is built.
What if I deny the location permission?
If continuous tracking is enabled for the selected mobile app, check-in stays disabled until background location access is granted. If tracking is not enabled, the separate attendance configuration may still require a one-time location fix for the punch. The check-in screen states which requirement is blocking the action; permission changes are made through the operating system and take effect when the app rechecks them.
Who can see my trail?
Your organization, under its own security configuration — trails are organizational records like other work data, visible to the people your organization's roles and permissions allow, typically managers reviewing routes and journey plans. The app itself gives no other party access. If you want the specific answer for your organization, your administrator can tell you which roles see location data.
Does location tracking drain the battery?
It costs something — continuous GPS always does — but the design keeps it modest: fixes on an interval rather than continuously, a minimum-distance filter, balanced accuracy rather than maximum, and batched uploads. A normal working day is well within a phone's budget. If battery is a problem in the field, a power bank solves more than any setting will.