Explicit session action
The supported field workflow gives the employee a visible start and stop action instead of presenting location capture as an invisible permanent state.
Employee location privacy
Scootee records an employee’s location only during a work session the employee starts and ends, not as all-day phone monitoring. Before rollout, explain the purpose, what is recorded and who can see it, then verify start, stop and recovery behaviour on the mobile build your staff will use.
The supported field workflow gives the employee a visible start and stop action instead of presenting location capture as an invisible permanent state.
Check a normal session, an ended session, and an interrupted session on the deployed mobile build. Confirm what happens after restart or recovery; design intent alone is not an off-shift tracking guarantee.
Location records should be limited by tenant, portal authority, and workforce scope, with negative tests for users who must not see the employee.
Operating-system permissions, background restrictions, battery settings, connectivity, and release configuration materially affect tracking and sync behavior.
While a work session is active, the field app records location fixes with their time and reported accuracy, and builds the route, stops and final distance in kilometres with the calculation method shown. The employee also adds the work records they choose to submit, such as customer visit outcomes, tasks, expense claims and receipt photos.
Outside an active session the tracking workflow does not record location. That boundary is what makes the employee tracking app easier to explain to field staff than all-day monitoring.
On Android, the app shows a location disclosure before it asks for permission. It explains that location is collected to record shifts, routes, distance and customer visits, including when the app is in the background, only while a tracking session is active, and that the data is shared with the employer. The operating system then asks for location permission, and on Android an ongoing notification stays visible while a session is recording.
The employee can see their own sessions and trips in the field app. In the portal, location records are limited by organization and by the reviewer’s permissions, so an area manager sees only the branches or departments they are allowed to manage. Some review aids, such as the GPS drift estimate on a session, are shown to reviewers only. See security and access controls for how scopes are set.
Phones lose signal, run out of battery or get restricted by battery savers, so some routes will be incomplete. From the history screen of the Scootee Android app, an employee can raise a journey correction for a missed journey or for the kilometres on a recorded session, with a reason and supporting evidence. A reviewer approves it, rejects it or asks for more information, and the originally recorded distance is kept alongside the decision. This matters most when the distance feeds conveyance reimbursement.
Under the Digital Personal Data Protection Act, 2023, the employer that decides why location is collected generally carries the Data Fiduciary duties. These include telling employees in clear language what personal data is processed and why, processing it only for a lawful purpose — the Act lists certain employment purposes among its legitimate uses — keeping it secure, erasing it once the purpose is served unless the law requires retention, and handling grievances. Employees, as Data Principals, have rights such as access to a summary of their data, correction and erasure.
Scootee does not make an employer compliant and this page is not legal advice. Agree the purpose, notice, retention and grievance process with your legal adviser before switching tracking on.
Scootee’s privacy policy states that work records may be retained while the organization’s account is active and as needed for payroll, expense, audit, security, contractual or legal requirements. This page does not promise a fixed deletion period. Ask for the current retention schedule and agree the period your policy needs during evaluation.
Employer rollout checklist
Explain the purpose, capture behavior, access, and how employees can raise a disputed record. This checklist is operational guidance, not legal advice or a compliance certification.
Plan the mobile pilotQuestions / answers
Supported location capture is designed around an explicit field work session. The production mobile build, device permissions, recovery behavior, and release configuration must be tested before rollout.
The field tracking workflow records location only inside a work session that the employee starts and ends. Explain the start and stop, the purpose and who can see the data to employees before rollout, and verify the behaviour on the phones they use.
Access is intended to follow authenticated tenant, role, and workforce scope. Buyers should test employee self-access, manager scope, branch or department boundaries, and cross-tenant negative cases.
Write down the business purpose, limit recording to working sessions, and give staff a plain notice of what is collected, when, why and who can review it. Agree retention and access with HR, then take legal advice on your duties under the Digital Personal Data Protection Act, 2023 and your employment terms.
No. Each employer must define the work purpose, lawful basis, employee notice, consent where applicable, retention, access, device policy, and regional requirements with appropriate legal and privacy advice.
Test the boundary yourself
Run a work session on your own phone during the trial, end it, and check what the manager can and cannot see.