On 9 November 2026, Thailand's Personal Data Protection Committee (PDPC) held a public hearing on its draft Personal Data Protection Master Plan for 2028–2032. The plan would replace the 2024–2027 plan. According to Tilleke & Gibbins' summary of the draft, the PDPC is expected to bring refined drafts back in March 2027, and the plan would take effect in 2028. The plan is a statement of regulatory intent, not a new rule. Even so, it is the clearest signal yet of how Thailand wants its data law to work in a digital economy that depends on cloud services, biometrics and AI.
The case for a more active regulator
The strongest argument for a heavier hand is that the Personal Data Protection Act, B.E. 2562 (2019), took years to bite. The Act was published in the Government Gazette on 27 May 2019, and its core obligations were postponed repeatedly before they took full effect. Its reach is broad. Section 5 applies the Act to foreign controllers and processors that offer goods or services to people in Thailand or monitor their behaviour there.
Enforcement is also still young. On 1 August 2025 the PDPC announced eight administrative fines across five cases. The largest was THB 7 million, imposed on a computer and accessories company. Tilleke lists the recurring failures as weak security measures, unreported breaches, and no data protection officer. Those are basic hygiene failures, and a regulator that wants compliance has a fair claim to push harder.
What the draft actually proposes
Tilleke's reading of the draft describes four strategies:
- People and capacity: a tiered competency framework and certification for data protection officers, plus training for functions such as HR and procurement.
- Clear, practical rules: guidance on AI, biometrics, cloud and automated decision-making, plus standards and certification schemes, including a privacy seal. It also addresses gaps in supervising small businesses.
- Risk-based enforcement: supervision, investigation and complaint handling, with more information-sharing among regulators and closer international enforcement cooperation.
- Responsible data use and technological innovation: a higher Thai profile in the OECD, APEC and EU forums, guidance on cross-border transfer tools, and support for policy research and regulatory sandboxes. Tilleke reads the cross-border emphasis as a possible signal that Thailand is positioning to join the Global CBPR System. That is an inference from the draft, not a stated commitment.
The design is mostly sound. The 2019 Act sets the statutory floor, and the plan is aimed at the gap between that floor and what a 20-person Thai software firm can actually do on Monday morning. Certification and sandboxes lower the cost of compliance. A risk-based enforcement posture concentrates scarce regulatory attention on harmful processing instead of paperwork violations.
Why the cross-border strategy matters most
Section 28 of the Act restricts transfers abroad unless the destination offers an adequate standard of protection. The exceptions are consent, contract performance and legal compliance, and the Act also allows safeguards such as certified intra-group policies, with the details left to PDPC rules. Its adequacy test is only as useful as the PDPC's rules make it. For firms using global cloud providers, uncertainty about which transfer route is safe is a real tax on investment.
A mutually recognised certification system would let a Thai company show compliance once instead of negotiating contract clauses with every foreign partner. It would also help Thai firms that want to serve customers abroad, not only foreign firms entering Thailand. That is the pro-innovation logic behind the plan's fourth strategy, and it is consistent with the OECD accession track. The OECD Council invited Thailand to begin accession discussions on 17 June 2024, after Thailand's February 2024 letter of intent. The Foreign Ministry notes that the process may take many years. Data protection alignment is one of many workstreams, and the draft mentions cooperation through the OECD but does not tie the plan to accession.
Where the draft is vulnerable
First, the schedule is back-loaded. A revised draft in March 2027 and an effective date in 2028 mean that practical guidance on AI, biometrics and cloud could arrive only as the plan starts. Businesses deploying these systems now are making design decisions without it. The PDPC should publish guidance in stages, so it does not wait for the plan's start date.
Second, "risk-based" is a promise, not a method. Without published criteria for how the PDPC ranks risk, businesses cannot predict which processing will draw scrutiny. Small firms will assume the worst and over-comply, which is how well-meant privacy regimes end up favouring large incumbents with compliance departments. A published risk-scoring approach would let supervision be both proportionate and predictable.
Third, certification can drift from a voluntary route into a market requirement. A privacy seal is useful if it is optional and recognised abroad. If procurement rules or informal pressure make it mandatory, it becomes a licensing regime in all but name. The PDPC should state in the final plan that certification is a safe harbour and not a precondition for lawful processing.
What good implementation looks like
The regulator can keep the plan's ambition without adding burden. It should set dated milestones for each guidance document and publish the enforcement-risk methodology. It should treat sandboxes and certification as voluntary, and move early on cross-border mechanisms, because those deliver the clearest economic gain.
The hearing process itself is a good sign. A public draft, a consultation and a revision stage give industry and civil society a chance to correct the plan before it takes effect. The draft's balance between capacity building and enforcement is right. What remains to be shown is that its practical-rules strategy will produce usable guidance on a timetable that matches how fast Thai companies are adopting AI and cloud services.