Organization boundaries
Operational and workforce records carry tenant context, and access rules are designed around the authenticated organization.
Security
Scootee protects field workforce data with authenticated sign-in, organization-level isolation enforced by database row-level security, portal permissions limited by branch and department, private storage for receipts and documents, and an audit history of access changes. Each customer should test both allowed and denied access during the pilot.
Operational and workforce records carry tenant context, and access rules are designed around the authenticated organization.
Portal authority remains separate from employee job identity and can be limited by organization, branch, department, permission template, and override.
Web and native mobile workflows use authenticated sessions and tenant-aware APIs rather than public operational endpoints.
Location, workforce, request, receipt, and document access depend on product-specific data and storage policies. Verify the permitted and denied access paths in the customer deployment.
Every operational and workforce record in Scootee carries the organization it belongs to. Database row-level security policies check the signed-in user’s organization before a row is returned or changed, so the boundary is enforced in the data layer and not only in the screens. During evaluation, test a request for another organization’s record and confirm it is denied.
Portal access is granted as a permission, not inferred from a job title. An office user can be given access to all branches or only to listed branches and departments, and payroll data can be further limited by payroll group. Individual permissions come from a permission catalogue and can be adjusted per user with overrides.
In practice an area manager sees their own team’s sessions, visits and claims, a director can see across branches, and an employee sees their own records in the field app. The employee tracking app page shows how this looks during a working day.
Receipts, journey-correction evidence, chat files and form evidence are kept in private storage buckets with file-type and size limits, and the portal opens them through time-limited signed links rather than public URLs. Access to each file follows the same organization and record permissions as the claim or request it belongs to. Confirm the storage behaviour for the document types your team uploads.
The field apps check the employee’s access status after sign-in. Deactivated or login-disabled employees are blocked, and an employee whose organization membership has been removed is told so explicitly instead of seeing a blank app. Their historical records stay with the organization for payroll, expense and audit review under its retention policy.
The Digital Personal Data Protection Act, 2023 places duties on the organization that decides why and how personal data is processed — for employee tracking, usually the employer. Those duties include giving notice, processing only for a lawful purpose (the Act lists certain employment purposes among its legitimate uses), protecting data with reasonable security safeguards, reporting personal data breaches, erasing data once the purpose is served, and answering grievances. Rules made under the Act phase in some obligations over time.
Scootee’s privacy policy describes Scootee as a processor of the workforce records customers submit. Scootee provides access controls and records that can support these duties; it does not make an organization compliant, and this page is not legal advice. The employee location privacy checklist covers the notice and rollout steps.
This page does not assert SOC 2 or ISO 27001 certification, a fixed data-retention period, a specific hosting region, or a legal compliance guarantee. Ask for the current security documentation, subprocessors and retention schedule during procurement, and record the answers in your evaluation. Our privacy policy describes how Scootee itself handles account and field-app data.
Location and employee data
Scootee is designed around explicit field work sessions. Agree employee notice, device policy, authorized reviewers, retention and deletion, and the actual mobile build’s start, stop, and recovery behavior. This is operational guidance; obtain legal or privacy advice for your jurisdiction.
Security review checklist
Questions / answers
Records are encrypted in transit between the mobile apps, the portal and Scootee’s cloud services, as described in the Scootee privacy policy. Ask for the current documentation on encryption at rest, hosting region and subprocessors during procurement.
Not when their access is limited. Portal users can be scoped to listed branches and departments, and payroll data can be limited by payroll group. Test both the allowed and the denied view for each reviewer role during the pilot.
No. The Scootee privacy policy states that Scootee does not sell personal data or share it with advertisers. The employer administers the work account and decides which roles can see field records.
This page does not claim SOC 2 or ISO 27001 certification. Ask which independent attestations, security documents and contractual commitments are available for your deployment before you sign.
Procurement questions
Ask about hosting and data regions, subprocessors, retention and deletion, recovery procedures, and any independent attestations available for your deployment. Then test the controls with your own roles in a Scootee demo or a scoped pilot of the field force management software.