The Online Criminal Harms codes require more anti-scam safeguards from designated platforms, but they do not make every listing, app or account safe. Users should understand which provider carries which duty and keep a separate response plan for suspicious transactions.
The reader task is to understand which safeguards are directed at platforms, when they take effect and what users should do when an account or transaction still looks suspicious. The article therefore keeps the governing fact, the calculation or comparison, and the final decision in separate steps.
Three platform groups, different controls
App stores
The Police codes cover designated app-distribution services, with safeguards intended to reduce access to harmful apps and improve accountability.
Official source 1 was opened on 29 August 2026 and checked for this exact app stores claim.
January 2027 is an implementation milestone
Online services
Designated online communication and service providers face risk-reduction measures under the OCHA framework.
Automation strengthens enforcement
E-commerce
The codes include transaction-safety measures for designated e-commerce services, where seller identity and scam patterns matter.
The user still controls money and credentials
Timing
The 18 August 2026 issuance sets implementation periods extending to January 2027 for specified measures. Users should read platform notices for exact changes.
Three platform groups, different controls
Enforcement
The related Bill proposes faster computer-program directions and penalties of up to S$10 million for each instance of non-compliance with codes or implementation directives.
Official source 2 was opened on 29 August 2026 and checked for this exact enforcement claim.
Reproduce the result
The first original tool is a platform-by-platform timetable for app stores, designated online services and e-commerce services. Create it from the dated source material, show every input and keep the unresolved cells visible. A correct-looking answer with an undocumented input is not ready for a decision.
The second tool is a user action map separating platform reporting, ScamShield checks, bank action and police reporting. Use it after the first tool, because the comparison only adds value when the underlying person, entity, place, account or time period has already been matched correctly.
Ask another person to repeat the result from the saved evidence without seeing your conclusion. If they cannot reproduce the same branch, inspect the source date, definition, arithmetic and exception before relying on it. This catches errors that a polished summary can conceal.
A decision table you can use
| Suspicious app | Stop installation and use official store/report route | Do not sideload a replacement |
| Marketplace payment request | Keep payment in platform and verify seller | Call bank immediately after transfer |
| Account takeover sign | Change credentials from a clean device | Report to provider and contacts |
| Possible scam | Use ScamShield and police guidance | Preserve messages and transaction proof |
The table is a working aid. Date the evidence, preserve the original notice or statement, and flag any cell that depends on an assumption rather than a controlling source.
Do not collapse these checks
Do not combine app stores, online services, e-commerce into one yes-or-no box. Each answers a different question and can change on a different date. A pass on one row does not cure a failure on another.
Do not convert an authority’s illustration, capacity figure, proposed rule, programme status, straight-line distance or published operating hour into a personal guarantee. Keep the source’s own limitation beside the number whenever it affects money, timing, access, safety or eligibility.
Before choosing, write down the strongest reason the opposite decision could be right. Then identify the evidence that would switch your answer. This small counter-case prevents the first attractive number, convenient route or reassuring label from controlling the whole judgment. If no evidence could change the conclusion, the exercise has become advocacy rather than a decision.
Finally, set a review trigger. Reopen the controlling page when a deadline passes, a formal notice arrives, the person or entity changes, the route is altered or the decision is delayed. The current answer remains useful only while its material inputs remain current.
Worked example
A seller moves a buyer from a marketplace chat to an unfamiliar payment page. Platform safeguards may help detect the account, but the buyer still stops, checks the merchant inside the platform and refuses the external transfer.
This example is an illustration, not a report of a real person, interview, visit, taste test, price check or transaction. It shows how to apply the decision method while keeping the underlying evidence visible. Replace every sample input with the reader’s own current evidence before using the outcome.
What to verify before acting
- Open the current authority, operator or organiser page instead of relying on a saved social post.
- Match the rule or listing to the correct person, entity, property, platform, route or account.
- Record the effective date, closing date or data date separately from the webpage update date.
- Check any amount, threshold, deadline and exception against the exact source passage that controls it.
- Keep a stop condition for missing evidence, changed access, conflicting dates or an unaffordable downside.
Limits and next reading
Codes apply to designated services and contain provider-specific duties. They do not create a guarantee, compensate every victim or replace urgent contact with the bank and Police after a transfer.
For useful context on the next decision, LBRD explains how to understand the separate Online Safety Commission. A second practical progression is to avoid becoming a scam mule. Both links were checked against the intended live pages before publication.
Featured image: Singapore Police Force and digital enforcement. Image: Singapore Police Force. Image source and rights record.
