Singapore’s ERP 2 system will replace the old electronic road pricing system on 1 January 2027, and the Home Team expects to use data from ERP 2 to prevent, detect and solve crimes from that date. The Ministry of Home Affairs confirmed this in a 3 November 2026 parliamentary answer. It cited existing legal powers, including Section 20 of the Criminal Procedure Code, under which Police can require production of information relevant to investigations, inquiries, trials or proceedings.
Separately, the Land Transport Authority (LTA) has stated that vehicle-specific ERP 2 data is used for payment, charging and enforcement, while traffic planning and management use aggregated and anonymised data. LTA can retrieve vehicle-related location information where needed for lawful enforcement such as detecting deregistered or restricted-use vehicles and illegal cross-border taxi services. Government has also described data security, access controls and retention according to investigative needs, without publishing a universal fixed number of days for every kind of record.
This guide helps motorists, parents, delivery drivers, businesses and students distinguish a vehicle’s GNSS location, anonymised traffic analysis, specific law-enforcement access and a privately connected mobile application. It explains the public-safety rationale alongside genuine privacy questions without suggesting that ordinary motorists can personally extract OBU records or that every road journey incurs distance-based charging in January 2027.
Updated 4 November 2026 following the 3 November parliamentary statement. This independent eduKateSG explanation of ERP 2 data and law enforcement is not a legal ruling, privacy guarantee or official investigative instruction. The statutory framework and agency notices determine actual powers and obligations.
The officially confirmed 2027 position
- MHA’s 3 November 2026 reply says the Home Team expects to use ERP 2 data from January 2027 for crime prevention, detection, deterrence and investigation.
- MHA cites existing statutory powers, including Section 20 of the Criminal Procedure Code, enabling Police to order production of information necessary or desirable for relevant proceedings.
- All Singapore-registered motor vehicles used on public roads generally require an ERP 2 on-board unit from 1 January 2027, subject to specified exemptions.
- ERP 2 uses satellite-based positioning for charging at defined locations rather than requiring conventional visible gantries.
- LTA says vehicle-specific data may be collected for charging, payment and authorised enforcement, but planning and general traffic management use aggregated/anonymised information.
- Examples of vehicle enforcement include detecting deregistered vehicles, illegal cross-border taxi services, off-peak cars used outside permitted hours and certain restricted vehicles on public roads.
- Government says ERP 2 data access and use will be subject to legal and public-sector data-governance safeguards, with protection against unauthorised access and disclosure.
- Officials said Police retain relevant data for as long as needed for its lawful purpose, including investigations and court proceedings, rather than announcing one universal retention period.
- Third-party smartphone applications are restricted to one-way access to appropriate OBU information and require motorist consent for relevant sharing.
- Distance-based ERP charging is not part of the initial 1 January 2027 rollout; future consideration is distinct from a present charge.
What the official statements do not establish
- Using ERP 2 information for investigations does not mean every motorist is suspected of a crime or that every personal journey is reviewed by a Police officer.
- Anonymised traffic planning data and specific vehicle records retrieved for enforcement are different data-use categories.
- The Criminal Procedure Code powers cited do not mean every request requires the same warrant or court order in every situation; the relevant legal power and safeguards must be checked.
- Data-retention language based on investigative need is not a published promise to delete all OBU data after an exact number of hours or days.
- An OBU is not a consumer-facing CCTV recorder from which motorists may automatically download every historical movement or image.
- Current road pricing is not distance-based merely because the underlying technology uses satellite positioning.
- Car owners must not tamper with or remove required OBU components to avoid legitimate collection or tracking.
- A private app’s consent process is not equivalent to an unrestricted permission for third-party access to all Government OBU records.
Contents and key questions
- 1. What Parliament clarified on 3 November 2026
- 2. What ERP 2 changes in the transport system
- 3. Vehicle-specific data versus anonymised statistics
- 4. What the Criminal Procedure Code reference means
- 5. Why road-traffic data can help investigations
- 6. LTA already has related enforcement responsibilities
- 7. Illegal cross-border taxi services
- 8. Off-peak cars, laid-up and restricted vehicles
- 9. Are motorists continuously monitored by officials?
- 10. Data security and OBU encryption
- 11. Retention of information from investigations
- 12. Consent when connecting third-party applications
- 13. Can the driver download every historic location?
- 14. Public safety and personal privacy both matter
- 15. No distance-based charging on 1 January
- 16. A practical 2027 motorist data and safety checklist
This article distinguishes how the road-pricing system functions from how data can be used for individual enforcement and the safeguards governing that use. The hypothetical examples do not assert that any specific person was investigated.
1. What Parliament clarified on 3 November 2026
The Ministry of Home Affairs responded to a question about whether Police and other Home Team agencies may access vehicle-specific ERP 2 data and what legal protections apply. It explained that existing statutory powers allow authorised agencies to obtain relevant information from available sources, including sensors, and that the Home Team expects to use ERP 2 data from January 2027 to help prevent, detect and solve crimes. This is not a brand-new universal exemption from legal controls. The Government said ERP 2 information would receive the same legal and data-governance safeguards applicable to other data lawfully obtained for similar purposes.
An illustrative Singapore situation
Hypothetical example: A driver reads a social-media headline saying the Government has created a completely unregulated new power to view every journey without any controls.
What to verify or do
The parliamentary answer refers to existing legal powers and safeguards. Read the actual reply and distinguish an available investigative tool from unlimited uncontrolled use.
2. What ERP 2 changes in the transport system
ERP 2 replaces the old system of physical gantries with satellite-based positioning and vehicle on-board units. The new technology identifies when a vehicle passes a designated charging location and calculates the relevant fee. Road signs and OBU notifications replace some of the old gantry’s visual functions. It also provides a source of data relevant to traffic and vehicle management. The launch does not automatically introduce distance-based charging or abolish current congestion-management principles. A vehicle must still comply with the ordinary road rules, and the OBU must be properly installed and functioning where required.
An illustrative Singapore situation
Hypothetical example: A commuter sees new GNSS technology and assumes the Government will charge for every kilometre driven from New Year’s Day.
What to verify or do
The initial system charges at defined ERP locations. A possible later distance-based framework would require its own announcement and implementation.
3. Vehicle-specific data versus anonymised statistics
LTA says individual vehicle information is used for authorised purposes such as payment, charges and enforcement. By contrast, broader planning and traffic management use anonymised and aggregated data, which support analysis of movements or congestion patterns without treating every record as a personal dossier. These descriptions address different tasks: an agency deciding which road needs better junction management does not necessarily need to know the owner of every vehicle, while enforcing an offence may require identifying a particular registered vehicle. Responsible analysis should keep the categories clear.
An illustrative Singapore situation
Hypothetical example: A resident hears that LTA collects anonymised traffic data and therefore assumes no identifiable data can ever be retrieved for any lawful enforcement purpose.
What to verify or do
That is not LTA’s stated distinction. Anonymisation applies to the specified planning uses; vehicle-specific enforcement is treated separately under safeguards.
4. What the Criminal Procedure Code reference means
MHA cited Section 20 of the Criminal Procedure Code as an example of Police authority to order production of documents or other things necessary or desirable for an investigation, inquiry, trial or other proceeding. The law provides a framework for obtaining information in appropriate cases. The parliamentary reply did not promise that every single data access always uses one identical court-warrant procedure, nor did it publish a complete operational manual for investigators. A sound public explanation should describe the legal power actually cited and avoid inventing a stronger or weaker protection than the official answer establishes.
An illustrative Singapore situation
Hypothetical example: A commentator states that ERP 2 data is accessible only after a High Court warrant in all circumstances, even though that universal claim is not in the cited reply.
What to verify or do
Read the actual statutory procedure and ministerial answer rather than substitute an imagined one-size-fits-all rule.
5. Why road-traffic data can help investigations
Vehicle-related information may be useful when authorities need to establish whether a vehicle was present near a location, understand a sequence of movements or investigate an offence involving road use. Such data may complement witness evidence, camera footage and other records rather than substitute for a complete criminal investigation. A location observation does not prove who personally drove a vehicle or why the trip occurred. Context and the reliability of each source matter. The same tool can therefore support public safety while requiring careful controls against inappropriate inference or use.
An illustrative Singapore situation
Hypothetical example: A delivery vehicle is recorded at a location associated with an incident, and someone assumes this proves every registered worker using that vehicle committed an offence.
What to verify or do
Vehicle data alone cannot establish all necessary facts. Proper investigations require lawful procedures, corroboration and fairness.
6. LTA already has related enforcement responsibilities
LTA’s September 2026 ERP 2 announcement explains that the earlier ERP 1 gantry records were already used to detect vehicles that should not be on public roads, such as deregistered vehicles. ERP 2 can continue and enhance that type of enforcement. The distinction matters because road-pricing records have never been solely a monthly billing convenience. Under the new system, authorised information can help identify vehicles that violate registration, usage or operating restrictions. These are traffic and vehicle obligations, not automatically criminal findings about the individual owner in every case.
An illustrative Singapore situation
Hypothetical example: A car that has been deregistered is seen travelling despite registration restrictions, and the owner argues the ERP system should be permitted to record only toll payments.
What to verify or do
LTA has described an enforcement role under both ERP versions. Actual action still depends on the relevant vehicle law and evidence.
7. Illegal cross-border taxi services
LTA has identified illegal cross-border taxi services as one of the serious vehicle-related offences against which data can assist enforcement. Cross-border travel is common between Singapore and Johor, and most residents use ordinary licensed transport. The focus is on operators who provide a regulated service without the correct authorisation, not on criminalising every passenger crossing the border. Identifying a vehicle’s movement may help enforcement, but the legal status of a particular operation depends on licences, the service provided and actual evidence rather than location alone.
An illustrative Singapore situation
Hypothetical example: A family travels to Johor in a private car and hears that any ERP record near a checkpoint is automatically evidence of illegal taxi operation.
What to verify or do
That is inaccurate. Cross-border travel is not itself the offence. Use authorised services and the current LTA rules for commercial transport.
8. Off-peak cars, laid-up and restricted vehicles
Vehicle schemes can limit how or when a car may be used. LTA has discussed continuing enforcement of off-peak cars driven outside their permitted hours and vehicles on laid-up or Keeping status that should not be driven on ordinary public roads. ERP 2 data can help identify specific vehicles involved in suspected breaches, subject to law and safeguards. This function is separate from checking whether the appropriate ERP fee was paid. Vehicle owners need to know the real status and restrictions linked to their registration, especially after transferring ownership or changing a scheme.
An illustrative Singapore situation
Hypothetical example: A driver owns a car under a restricted use arrangement and assumes fitting an OBU automatically gives permission to drive anywhere at any time.
What to verify or do
The OBU is not a waiver of registration restrictions. Check the actual permitted use and vehicle documents before travelling.
9. Are motorists continuously monitored by officials?
Satellite technology can support location-related records, but a capability to retrieve specific information is not equivalent to proof that a person at a desk watches every motorist continuously. Government policy distinguishes authorised enforcement from aggregated traffic planning and refers to safeguards against unauthorised access. At the same time, the ability to obtain vehicle-specific data creates legitimate privacy concerns that deserve transparent explanation. A careful article should neither dismiss such concerns nor state as fact that every journey is routinely examined for unrelated personal reasons without evidence. Oversight and appropriate uses remain the central questions.
An illustrative Singapore situation
Hypothetical example: A resident sees an OBU and assumes a live human investigator sees a continuous map of that driver’s every movement, because the device has GNSS capability.
What to verify or do
That is not established by the public notice. Focus questions on authorised data collection, security, uses and accountability rather than assume a particular monitoring practice.
10. Data security and OBU encryption
LTA and Government representatives have described stringent technical measures and encryption associated with the on-board unit and information it transmits. The device and related Government systems are subject to security requirements, and motorists cannot directly access protected stored OBU data as though the box were an ordinary removable memory drive. Security measures reduce risks but cannot justify saying any digital system is absolutely impossible to attack. The relevant practical requirement is to install and maintain the OBU through authorised channels, avoid unauthorised modifications and seek legitimate assistance when the device fails.
An illustrative Singapore situation
Hypothetical example: A motorist is offered a cheap third-party device modification that claims to disable tracking without affecting the OBU’s legal status.
What to verify or do
Do not tamper with required equipment. Unauthorised work may be an offence and may compromise the security and reliability of the unit.
11. Retention of information from investigations
In Parliament, officials said Police retain data for as long as it is needed for the lawful purpose for which it was obtained. For criminal investigations and court proceedings, that can mean until the investigation or relevant proceedings are completed. This is a need-based retention explanation, not a universal public schedule promising deletion exactly seven, thirty or ninety days after a journey. Some records will also be governed by distinct public-sector operational or statutory requirements. People discussing privacy should avoid inventing a specific maximum when the cited ministerial response did not provide one.
An illustrative Singapore situation
Hypothetical example: A website says every OBU movement record is permanently retained for all drivers, while another claims all records automatically disappear after 24 hours.
What to verify or do
Neither universal claim follows from the cited reply. Use the published purpose-and-need retention explanation and request authoritative details where applicable.
12. Consent when connecting third-party applications
LTA allows third-party mobile application developers to integrate certain ERP 2 information with protections including one-way access to permitted data. The authority says such applications should not be able to read unrelated stored information or alter the device, and motorists must consent to relevant sharing. This applies to optional connected app use rather than giving the public general access to Police files or the entire Government data system. App users should distinguish convenience features such as journey alerts from the actual permissions granted to a specific software service.
An illustrative Singapore situation
Hypothetical example: A driver downloads an unofficial ‘ERP2 tracker’ claiming that granting phone permission gives a private developer the ability to download every protected vehicle record.
What to verify or do
That does not match LTA’s stated controls. Check the genuine developer, permissions and consent before using any connected app.
13. Can the driver download every historic location?
LTA’s public explanation says OBU data is secured and not directly accessible by motorists. Some drivers may want records to challenge a charge, confirm a route or resolve a dispute. Their appropriate route is to use the Government’s prescribed transaction, feedback or dispute process, rather than try to remove a protected storage component. Not all vehicle-specific records are necessarily a video, a photograph or a detailed log intended to be handed to the registered owner on request. Any statutory right to information or evidence should be assessed under the relevant law and actual official procedure.
An illustrative Singapore situation
Hypothetical example: A driver accused of a road offence tries to dismantle an OBU to retrieve all satellite location information as though it were a dashcam.
What to verify or do
Seek the correct official review or legal process rather than attempting unauthorised access to protected device components.
14. Public safety and personal privacy both matter
Road and crime enforcement can benefit from accurate vehicle-related information, particularly when a serious offence involves a car that would otherwise be hard to trace. But location data can also be sensitive: a record of frequent visits may reveal aspects of a person’s private life without explaining the reason for the trip. Public confidence therefore depends on legally defined purposes, restricted access, security, accountability and clarity about how long information is needed. Recognising both perspectives is more useful than portraying privacy as a reason to stop every investigation or enforcement as proof that privacy no longer matters.
An illustrative Singapore situation
Hypothetical example: Two neighbours disagree: one says no investigative use is ever justified, while the other says any employee should be able to see any car’s movements.
What to verify or do
The public framework describes authorised use with safeguards. A responsible discussion asks how those controls operate rather than choosing either absolute.
15. No distance-based charging on 1 January
One of the biggest misunderstandings about ERP 2 is that GNSS capability automatically means all journeys are charged by distance. LTA’s September 2026 statement and the Government’s explanation say the immediate ERP 2 system maintains congestion pricing at specified charging locations. Authorities have acknowledged that more advanced forms of pricing could be considered in a later phase, but a future possibility is not an operative charge. The privacy and enforcement discussion should therefore not be conflated with an invented per-kilometre toll that has never been announced for the initial rollout.
An illustrative Singapore situation
Hypothetical example: A driver estimates their January ERP bill by multiplying every kilometre driven by a supposed mandatory rate taken from a viral post.
What to verify or do
Use the published charge locations, times and vehicle categories. Do not treat a future technology option as the present pricing framework.
16. A practical 2027 motorist data and safety checklist
Before January, confirm whether the vehicle requires an OBU and whether it was installed through an authorised workshop. Keep software and connected-app permissions under appropriate review, and avoid equipment tampering. During the year, use official payment, transaction and dispute channels. Understand the distinction between anonymised traffic statistics and specific data retrieved for authorised enforcement or lawful criminal investigation. If a public notice claims a new surveillance power, retention period or road charge, check the MHA, MOT and LTA sources and the exact announcement date before sharing it.
An illustrative Singapore situation
Hypothetical example: A family receives an urgent message claiming that every driver must pay an additional annual privacy-registration fee to make ERP 2 data safe.
What to verify or do
The published framework creates no such universal fee. Verify through OneMotoring or the responsible authority and do not submit credentials to a lookalike site.
Understanding four different ERP 2 data uses
| Purpose | Data treatment described publicly | What it does not mean |
|---|---|---|
| ERP payment and charge calculation | Vehicle-specific data for the relevant charge | Distance-based pricing from January |
| Traffic planning and management | Aggregated/anonymised analysis | Every commuter personally profiled for every planning report |
| Lawful traffic/vehicle enforcement | Vehicle-specific records where authorised | A vehicle record automatically proves the driver guilty |
| Home Team criminal investigations | Access under existing legal powers and safeguards | Unlimited informal access or one fixed universal retention period |
A practical motorist checklist
- Confirm the vehicle’s OBU requirement and current installation status.
- Use authorised workshops and avoid prohibited hardware tampering.
- Understand actual ERP charge locations rather than invent kilometre charges.
- Distinguish aggregate traffic data from individual enforcement information.
- Read the Government’s statement about relevant Criminal Procedure Code powers accurately.
- Do not invent a blanket warrant rule or fixed retention period absent from published guidance.
- Check app permissions before sharing permitted OBU data with private software.
- Use authentic LTA transaction, complaint and feedback channels.
- Never provide sensitive passwords to an unofficial OBU data retrieval agent.
- Read current MHA, MOT and LTA updates before forwarding a surveillance claim.
Frequently asked questions
When will Home Team agencies begin using ERP 2 data for investigations?
MHA said they expect to use it from January 2027.
What legal power was cited in Parliament?
Section 20 of the Criminal Procedure Code was given as an example of Police information-production powers.
Does every request require the same court warrant?
MHA cited existing statutory powers and safeguards, not one universal warrant procedure for every situation.
Does LTA use personal vehicle data for ordinary traffic planning?
LTA says planning and general traffic management use anonymised and aggregated information.
Can authorities obtain vehicle-specific location data?
Yes, for authorised enforcement and investigations under the relevant legal framework.
What vehicle offences were identified?
Examples include illegal cross-border taxis, deregistered vehicles, and off-peak or otherwise restricted vehicles used unlawfully.
Are motorists individually watched by a human at all times?
The official statements do not establish that routine practice; they describe authorised data uses and security safeguards.
How long will Police retain relevant data?
Officials said as long as necessary for the relevant lawful purpose, including investigations and court proceedings.
Can a driver directly extract all data stored inside an OBU?
No. LTA describes protected data that motorists cannot directly access that way.
Can a third-party app access all OBU information?
LTA describes restricted one-way access to permitted information and consent requirements.
Does ERP 2 introduce distance-based charging immediately?
No. The 1 January 2027 rollout retains location-based charging points; distance pricing is a possible later phase.
Where can I verify privacy and enforcement claims?
MHA’s 3 November 2026 parliamentary answer, LTA’s ERP 2 privacy FAQ and the official MOT ERP page.
Official primary sources
These official sources support the documented legal basis, stated uses and privacy safeguards. They should be consulted for the precise operative rule, not treated as a substitute for individual legal advice.
- MHA, 3 November 2026: legal basis and Home Team ERP 2 data safeguards
- LTA OneMotoring: ERP 2 OBU, data privacy and consent controls
- LTA, 28 September 2026: ERP 2 road signs, charges and enforcement
- MOT: ERP 2 system overview and 1 January 2027 launch
- gov.sg: Land Transport and Related Matters Act, ERP 2 safeguards
- LTA: ERP charge information and actual price schedules
Related eduKateSG articles
- Singapore 2027 | ERP 2 Launch, OBU Rules and Charging Locations
- Singapore 2027 | Traffic Demerit Points and Road Safety
- Singapore 2027 | Data Centre Security and Cloud Resilience
Conclusion: useful road data needs accountable safeguards
ERP 2 changes how road pricing works and creates more capable vehicle-related data systems. Government has described specific authorised uses for charges, enforcement and criminal investigations, while distinguishing ordinary aggregated planning data. These capabilities can improve public safety, but they also make transparency, legal limits and secure handling of information important.
Motorists should understand the actual requirements without assuming that a new technology erases privacy or creates a kilometre-based charge. A careful civic discussion asks which purpose applies, which law authorises access and how misuse is prevented. Those are more useful questions than a misleading headline about unlimited tracking.