What Data Retention and Access Controls Matter for Singapore Location Records?
What Data Retention and Access Controls Matter for Singapore Location Records?
Introduction
Live location tracking helps Singapore businesses coordinate delivery drivers, field employees, security personnel, maintenance technicians and other mobile teams. By collecting GPS coordinates, visit check-ins, route histories and location-based attendance records, organisations can improve scheduling, monitor field operations and respond to unexpected delays.
However, location records can reveal more than an employee's current position. They may show daily travel patterns, customer visits, work schedules, break periods and movements between different locations. If these records are kept indefinitely or made available to too many people, they can create privacy, security and compliance risks.
Singapore businesses should therefore establish clear rules for how long location records are retained, who can access them, what information each user can view and how records are securely deleted.
The Personal Data Protection Act (PDPA) requires organisations to protect personal data through reasonable security arrangements and stop retaining it when the purpose for collection is no longer being served and retention is no longer necessary for legal or business purposes. The PDPA does not prescribe one universal retention period for all location records.
This article explains the key data retention and access controls Singapore businesses should consider when using employee location tracking software.

1. Identify the Types of Location Records Being Collected
Before deciding how long to retain information, businesses should understand exactly what their tracking system collects.
Location records can include several types of information:
- Live GPS coordinates: The current or most recently reported location of an employee or vehicle.
- Location history: Records showing where a tracked device travelled during a particular period.
- Route history: A sequence of location points used to reconstruct a journey.
- Geofence events: Records showing when a device entered or exited a defined location boundary.
- Attendance check-ins: GPS-supported clock-in and clock-out events.
- Customer visit records: Location, arrival time, departure time and visit details.
- Delivery records: Vehicle arrival, delivery status and proof-of-delivery information.
- Location-related alerts: Notifications about route deviations, missed check-ins or unexpected stops.
- Device information: Device identifiers, application status and location-update timestamps.
Not every business needs to retain every category for the same period. For example, a delivery company may need proof-of-delivery records for customer service and dispute handling, while detailed GPS route histories may have a shorter operational value.
Organisations should create an inventory of the location information collected and identify the purpose of each category.
2. Establish a Clear Retention Policy
A location data retention policy should explain how long each category of information is stored and why that period is necessary.
Under Section 25 of Singapore's PDPA, an organisation must cease retaining personal data, or remove the means by which it can be associated with particular individuals, when the original purpose is no longer being served and retention is no longer necessary for legal or business purposes.
This means businesses should not keep employee location histories indefinitely simply because their software makes long-term storage possible.
A practical retention policy should specify:
- The type of location information collected.
- The business purpose for collecting it.
- The approved retention period.
- Whether the information is required for a legal or contractual purpose.
- Who approves exceptions to the retention period.
- How records are deleted or anonymised.
- How deletion is verified across connected systems and backups.
The retention period should be based on the actual purpose and applicable legal or industry requirements, rather than an arbitrary setting chosen by the software vendor.
3. Distinguish Location Records From Statutory Employment Records
One important consideration for Singapore employers is that not all location records are automatically statutory employment records.
The Ministry of Manpower (MOM) requires employers to maintain specified employment records under the Employment Act. These include information such as working hours, salary details, public holidays and leave taken.
MOM states the following general retention requirements for employment records covered by the Employment Act:
| Employee category | Employment record retention requirement |
|---|---|
| Current employees | Latest two years |
| Former employees | Last two years, retained for one year after leaving employment |
However, these requirements should not automatically be applied to every GPS coordinate, route history or location alert. Employers should identify which records form part of the required employment documentation and which are separate operational records.
For example, an attendance record may be needed to support working-hour documentation, while a detailed route history showing every location update during a shift may not need to be retained for the same period.
Businesses should retain the necessary employment information without assuming that every underlying tracking event must be stored indefinitely.
4. Create Different Retention Periods for Different Data Categories
A single retention setting for all location information can lead to unnecessary storage or premature deletion.
Businesses should consider separate retention rules for different record types.
| Record category | Retention approach |
|---|---|
| Live location updates | Keep only as long as needed for current operational visibility |
| Detailed GPS route history | Define a limited period based on dispatch, investigation or other justified needs |
| Geofence entry and exit events | Retain according to attendance, site verification or operational requirements |
| Attendance records | Follow applicable employment recordkeeping requirements |
| Delivery completion records | Retain according to customer, contractual, accounting and dispute requirements |
| Incident-related location records | Preserve where necessary for an active investigation or legal matter |
| System access logs | Retain for a defined security monitoring and investigation period |
| Aggregated operational reports | Consider anonymisation or removal of employee identifiers when individual-level information is no longer needed |
The periods should be determined by the organisation's actual requirements. The table is a policy framework, not a statement that Singapore law prescribes a particular number of days for each category.
5. Define When Location Tracking Starts and Stops
Retention controls begin with appropriate collection practices.
If a company tracks employees throughout the day, it may collect more information than necessary for its stated operational purpose. Businesses should decide when tracking is required and configure the application accordingly.
For example:
- Delivery drivers may be tracked during authorised delivery shifts.
- Maintenance technicians may share location while travelling to assigned service jobs.
- Sales employees may use event-based customer visit check-ins instead of continuous tracking.
- Security personnel may be tracked during assigned patrol duties.
- Employees using company vehicles may be subject to a separate vehicle tracking policy.
The system should make tracking status clear and provide appropriate controls for shift start, shift end and authorised breaks.
Where continuous tracking is not necessary, businesses should consider periodic location updates or event-based check-ins.
6. Apply Role-Based Access Controls
Not every employee or manager needs access to complete location histories.
Role-based access control (RBAC) allows organisations to assign permissions according to job responsibilities. This reduces unnecessary exposure of personal location information.
For example:
| User role | Appropriate access |
|---|---|
| Dispatcher | Current locations of assigned drivers and relevant delivery status |
| Field supervisor | Location and visit information for the supervisor's assigned team |
| Operations manager | Operational summaries, exceptions and authorised historical records |
| HR team | Attendance-related information needed for employment administration |
| Payroll team | Approved working-time and attendance records rather than full GPS histories |
| IT administrator | Technical access required to maintain the system, subject to controlled administrative procedures |
| Senior management | Aggregated operational reports and approved performance information |
| External customer | Relevant delivery status or proof of delivery, not unrestricted employee location history |
The exact permissions should reflect the organisation's structure and legitimate business requirements.
A useful system should allow administrators to control access by role, team, location, employee group and data category.
7. Restrict Access to Historical Location Data
Access to a live location map and access to historical route records are not necessarily the same permission.
Historical records can reveal detailed movement patterns over time. They may show where employees regularly work, which customers they visit and how they travel between locations.
Businesses should therefore consider restricting historical data more tightly than basic operational status information.
Useful controls include:
- Separate permissions for live tracking and historical tracking.
- Approval before downloading detailed route histories.
- Restrictions on searches covering large employee groups.
- Access limited to relevant dates and operational areas.
- Additional approval for sensitive investigations.
- Automatic expiry of temporary access permissions.
- Periodic review of users with historical-data privileges.
For example, a dispatcher may need to know where a driver is during an active delivery shift but may not need access to six months of the driver's movement history.
8. Use Strong Authentication and Secure Login Controls
Location information should not be accessible through weak or shared user accounts.
Businesses should require individual accounts and appropriate authentication controls for managers, administrators and other authorised users.
Important security features include:
- Unique user accounts: Each user should have an identifiable account.
- Multi-factor authentication: Require an additional verification method, particularly for privileged accounts.
- Strong password policies: Apply appropriate password and account protection controls.
- Single sign-on: Where suitable, integrate the tracking system with the organisation's identity provider.
- Session management: Automatically expire inactive sessions.
- Account deactivation: Remove access promptly when employees change roles or leave the organisation.
- Privileged access controls: Limit administrative permissions to authorised personnel.
Businesses should also prevent managers from sharing login credentials. Individual accounts make it easier to investigate access activity and identify responsibility for inappropriate use.
9. Maintain Detailed Access and Audit Logs
An access log records who viewed, changed, downloaded or deleted location information.
Audit logs are particularly important when location data is used for attendance verification, customer disputes, incident investigations or employee-related decisions.
A useful audit trail should record:
- User account and role.
- Date and time of access.
- Employee or device record accessed.
- Type of information viewed.
- Search or export activity.
- Changes made to records.
- Deletion actions.
- Administrative permission changes.
- Failed login attempts and unusual access activity.
For example, if a manager downloads a detailed route history for a driver, the system should record who performed the download, when it happened and which records were exported.
Audit logs should themselves be protected against unauthorised modification or deletion. Their retention period should also be defined according to the organisation's security and investigation requirements.
10. Control Downloads, Exports and Screenshots
A location tracking platform may have strong login security but still expose information through unrestricted downloads.
Managers may export GPS histories to spreadsheets, download reports to personal computers or share screenshots through messaging applications.
Businesses should consider the following controls:
- Restrict bulk downloads to authorised roles.
- Require approval for large or sensitive exports.
- Apply encryption to exported files.
- Prevent storage on unauthorised personal devices.
- Use secure sharing methods.
- Set expiry dates for shared report links.
- Record export activity in audit logs.
- Remove unnecessary employee identifiers from reports.
- Prohibit unauthorised sharing through personal email or messaging accounts.
Where possible, managers should use dashboard summaries instead of downloading detailed location histories.
11. Protect Location Records Stored in the Cloud
Many tracking platforms store location information on cloud infrastructure. Businesses should understand how the vendor stores, processes, protects and deletes this information.
Important questions include:
- Where is the data hosted?
- Which cloud providers or subcontractors are involved?
- Is location information encrypted during transmission?
- Is stored information encrypted?
- How are encryption keys managed?
- Who can access production databases?
- Are administrator actions logged?
- How are backups protected?
- How does the vendor handle security incidents?
- Can the organisation obtain evidence of deletion?
The PDPA does not impose a blanket requirement that all personal data must be stored in Singapore. However, when personal data is transferred overseas, the organisation must comply with the PDPA's transfer limitation requirements, including ensuring a standard of protection comparable to that under the Act.
Businesses should therefore review the vendor's hosting arrangements, contractual commitments and overseas data transfer safeguards before implementation.
12. Manage Vendor and Third-Party Access
Location tracking vendors may need access to customer data to provide hosting, technical support, troubleshooting and maintenance.
Organisations should not assume that vendor access is automatically unrestricted or harmless.
A suitable vendor agreement should address:
- Permitted purposes for processing location information.
- Security responsibilities.
- Access restrictions for vendor personnel.
- Confidentiality obligations.
- Use of subcontractors.
- Overseas processing and transfers.
- Data breach notification procedures.
- Retention and deletion requirements.
- Return or export of records when the contract ends.
- Audit or assurance arrangements.
Where a vendor processes personal data on behalf of an organisation, it may act as a data intermediary under the PDPA. The organisation should understand the respective legal responsibilities and ensure that the written contract and operating arrangements address the applicable obligations.
Vendor support access should be limited to the information needed for a particular support task and removed when that task is complete.
13. Establish a Secure Deletion and Anonymisation Process
Deleting location records should be part of the normal data management process, not an occasional manual exercise.
Businesses should confirm that their tracking software can remove records when the approved retention period expires. They should also understand whether deletion applies to all connected systems.
A suitable deletion process should cover:
- Location records stored in the main tracking platform.
- Downloaded reports and exported files.
- Records synchronised with HR, payroll or delivery systems.
- Copies held by third-party service providers.
- Backup and archive arrangements.
- Temporary files and cached records on devices.
Where individual identification is no longer necessary, businesses may consider anonymising information so that it cannot reasonably be associated with a particular employee. Simply removing an employee's name may not be sufficient if the remaining location details can still identify the person.
Organisations should also document deletion exceptions. For example, if location records are relevant to an ongoing legal claim, safety investigation or customer dispute, the relevant records may need to be preserved for as long as the applicable purpose requires. Such exceptions should be approved, limited in scope and reviewed periodically.
14. Separate Operational Records From Investigation Records
Location histories may sometimes be needed to investigate an accident, missing delivery, security incident, customer complaint or suspected unauthorised access.
However, retaining every employee's full movement history indefinitely because an investigation might occur is not a proportionate approach.
Businesses should establish a controlled preservation process:
- Record the reason for preserving the information.
- Identify the employees, devices and dates relevant to the matter.
- Restrict access to authorised investigation personnel.
- Preserve original records and relevant timestamps.
- Document any copies or exports made.
- Prevent routine deletion of the specifically preserved records.
- Review the preservation requirement when the investigation ends.
- Delete or anonymise the information when it is no longer required.
This approach helps organisations retain evidence when genuinely necessary without extending the retention period for unrelated location records.
15. Make Employee Access and Correction Processes Clear
Employees may want to understand what location information their employer holds and how it is used.
Businesses should have a clear process for handling appropriate employee requests relating to their personal data, including access and correction requests under the PDPA where applicable.
A practical process should explain:
- How employees can submit a request.
- Which department handles the request.
- How the organisation verifies the employee's identity.
- What categories of location information may be available.
- How inaccurate records can be reported.
- How corrections are reviewed and documented.
- How applicable statutory exceptions are handled.
For example, a driver may report that a GPS check-in shows the wrong location because the device recorded an inaccurate position near a high-rise building. The organisation should have a review process rather than automatically treating the original location as conclusive.
Where a record is corrected, the system should preserve an appropriate audit trail showing the original entry, the correction, the person who made it and the reason for the change.
16. Define How Location Data Can Be Used for Employee Decisions
Access controls should also govern how location information is used, not just who can view it.
Businesses should explain whether location data may be used for:
- Dispatch and job allocation.
- Attendance verification.
- Customer visit confirmation.
- Route planning.
- Safety and incident investigations.
- Reviewing delivery exceptions.
- Employment administration or performance management.
A location record should not automatically be treated as proof of misconduct, poor performance or failure to work.
For example, a stationary GPS position may indicate traffic congestion, a loading bay queue, a customer access delay or a scheduled break. It does not, by itself, establish that the employee was inactive or acting improperly.
Managers should consider relevant context and follow established internal procedures before making employment-related decisions based on location records.
17. Protect Location Data on Mobile Devices
Location records may be stored temporarily on drivers' and field employees' phones before being synchronised with the central platform.
This creates additional risks, particularly when employees use personal devices or work in areas with poor network coverage.
Businesses should evaluate whether the mobile application supports:
- Encrypted local storage.
- Secure authentication.
- Automatic logout or session expiry.
- Device-level access protection.
- Remote logout or access revocation.
- Secure offline record storage.
- Automatic synchronisation when connectivity returns.
- Removal of cached data when no longer needed.
If employees use personal devices, businesses should clearly explain which information the work application can access and how company data is separated from personal information.
A remote-wipe feature should be designed carefully so that it removes company data without unnecessarily affecting an employee's personal files.
18. Prepare for Data Breaches Involving Location Records
Unauthorised access to location information can expose employee routines, customer locations, work schedules and sensitive operational details.
Potential incidents include:
- A manager sharing a tracking dashboard with an unauthorised person.
- A stolen phone containing cached location records.
- A vendor account being compromised.
- An employee downloading route histories without approval.
- An exposed report link allowing public access.
- A misconfigured system displaying one team's location records to another team.
Singapore's PDPA includes data breach notification requirements. Where an organisation determines that a breach is notifiable, it must notify the Personal Data Protection Commission (PDPC) as soon as practicable and no later than three calendar days after making that determination. Affected individuals must also be notified where required.
Organisations should maintain a response procedure covering:
- Detection and reporting of the incident.
- Immediate containment of unauthorised access.
- Assessment of the type and volume of location data affected.
- Identification of affected individuals.
- Evaluation of whether the breach is notifiable.
- Required regulatory and individual notifications.
- Recovery and corrective action.
- Documentation and review to prevent recurrence.
The organisation should also ensure that its location tracking vendor has a clear process for promptly reporting suspected breaches and cooperating with investigations.
19. Review Access Permissions Regularly
Access permissions can become outdated when employees change roles, teams or responsibilities.
For example, a former dispatcher may still have access to historical driver routes even after moving to a different department.
Businesses should schedule periodic access reviews and check:
- Which users can view live locations.
- Which users can access historical records.
- Who can export or delete location data.
- Whether former employees' accounts have been disabled.
- Whether external vendor accounts remain active.
- Whether temporary permissions have expired.
- Whether administrator privileges are still necessary.
- Whether access logs show unusual activity.
Access should be removed or adjusted promptly when it is no longer needed.
A quarterly review may be a useful starting point for some organisations, but the appropriate frequency depends on the sensitivity of the data, number of users and operational risk. Privileged access and high-risk accounts may require more frequent checks.
Conclusion
Data retention and access controls are essential when Singapore businesses use live tracking software to monitor delivery teams, field employees, security personnel and other mobile workers.
Organisations should identify the location records they collect, establish purpose-based retention periods, distinguish operational GPS histories from statutory employment records and restrict access according to job responsibilities. Strong authentication, audit logs, secure exports, vendor controls and reliable deletion processes further reduce the risk of inappropriate access or unnecessary retention.
The PDPA does not prescribe a universal retention period for location data. Businesses must assess how long each category of information is genuinely needed and stop retaining personal data when the relevant purposes and legal or business needs have ended.
By combining clear retention rules with role-based permissions and regular access reviews, Singapore organisations can use location tracking responsibly while protecting employee privacy and maintaining useful operational records.
Review who can access past locations, export records and set retention periods. Ask InnBuilt for documentation suited to Singapore workforce data handling.