PDPA and custom software: what Thailand's data protection law means for your project
Thailand's Personal Data Protection Act changes how business software must be designed: legal bases, data subject rights, retention, security - translated into requirements.
Thailand’s Personal Data Protection Act (PDPA) - in full force since 2022 - applies to any system that processes personal data of people in Thailand: customer portals, CRMs, HR systems, e-commerce, mobile apps. For a software project it translates into concrete design requirements: collect only what a stated purpose needs, record the legal basis, control and log access, implement data subject rights (access, correction, deletion) as working functions, enforce retention schedules, and secure data throughout. Retrofitting these costs multiples of designing them in - so the PDPA belongs in your specification, not your postmortem. Here is the law translated into requirements a development team can build.
A scope note: this is an engineering guide, not legal advice - the design patterns below implement obligations whose exact application to your business belongs with your counsel and the PDPC’s official guidance.
Why should a software buyer care, specifically?
Three reasons beyond the fines. First, enforcement exists: the PDPA carries administrative penalties plus civil and criminal exposure, and the Personal Data Protection Committee (PDPC) issues guidance and handles complaints. Second, your counterparties check: enterprise customers, banks and multinationals increasingly audit their suppliers’ data handling - PDPA readiness is becoming a sales requirement in Thailand the way GDPR readiness did in Europe. Third, and least appreciated: compliance retrofits are miserable projects. Adding purpose tracking, access logging and deletion capability to a running system costs a multiple of specifying them on day one.
What does the PDPA require, in engineering terms?
The legal text speaks in duties; systems speak in features. The mapping:
| PDPA principle | What the system must actually do |
|---|---|
| Purpose limitation | Each data field tied to a stated purpose; no “collect now, think later” |
| Legal basis | Record why processing is allowed (consent, contract, legal duty…) per purpose |
| Consent (where used) | Granular, logged, and withdrawable - with withdrawal actually stopping the processing |
| Data minimization | Forms and schemas carry only what the purpose needs |
| Data subject rights | Access, correction, deletion and export as functions, not archaeology |
| Retention | Schedules per data class, enforced by the system - auto-delete, not good intentions |
| Security | Encryption in transit and at rest, access control by role, and audit logs of who saw what |
| Breach readiness | Enough logging to know what happened, to whose data, quickly |
Two of these decide most of the architecture. Data subject rights mean the system must be able to find, correct, export and truly delete one person’s data across tables, backups strategy included - trivial if designed in, brutal if not. Retention means data classes and schedules exist in the design (the same discipline a document system enforces) - because “we keep everything forever” is now a liability, not a backup policy.
How does this change a software project’s lifecycle?
- Specification. Add a data section to your spec: what personal data, for which purposes, on which legal basis, kept how long, visible to whom. Five rows in a table now, or five workshops later.
- Design. Access by role, logging on personal-data reads and changes, deletion paths designed with the schema. Where real data isn’t needed - analytics, testing - use anonymized or synthetic data instead.
- Development and testing. Production personal data does not belong in development environments; test data is generated. (Ask your vendor how they handle this - the answer is diagnostic.)
- Operations. Retention jobs run, logs are kept, and the rights requests have an owner and a deadline path.
- Contracts. Your development or hosting partner is a processor: documented instructions, confidentiality, security duties and support for your obligations go into the agreement - alongside where the data physically lives.
What about GDPR, and multi-market systems?
The PDPA is modeled in part on the GDPR, and the overlap is a gift for system design: purposes, legal bases, subject rights, breach duties - one architecture serves both. The differences live in the details (definitions, timelines, local guidance), so the working pattern for companies serving both markets is: design to the stricter reading, specify both explicitly, and have counsel review the delta. For European companies building with a Thai team, this is familiar ground - the same habits your GDPR projects taught apply here with a Thai accent.
In short
- The PDPA has been in force since 2022, with a real regulator (PDPC) - and it applies to internal systems, not just customer-facing ones.
- Compliance is a feature list: purposes, legal bases, consent handling, subject-rights functions, retention enforcement, security and logging.
- Put it in the specification - retrofits cost multiples, and enterprise customers now audit for it.
- Your vendor is a processor: processing terms, data location and test-data discipline belong in the contract.
- PDPA and GDPR share a spine: design once, properly, and both markets are served.
AD System Asia builds PDPA-conscious systems as standard practice - data sections in specifications, synthetic test data, subject-rights functions designed in - for clients in Thailand and Europe. Describe your project and its data.
Frequently asked questions
What is Thailand's PDPA?
The Personal Data Protection Act is Thailand's data protection law, in full force since 2022 and supervised by the Personal Data Protection Committee (PDPC). Modeled in part on the EU's GDPR, it governs how organizations collect, use, disclose and store personal data - with administrative, civil and criminal consequences for violations.
Does the PDPA apply to my company's internal software?
If the software processes personal data of people in Thailand - customers, employees, suppliers' contacts - the PDPA applies, whether the system is customer-facing or internal. HR systems, CRMs and customer portals are all in scope; the system's audience doesn't exempt its data.
What does the PDPA mean for how software is designed?
Concretely: collect only data you need for a stated purpose, record the legal basis for processing, control and log access, support data subject rights (access, correction, deletion) as system functions, enforce retention schedules, and secure data in transit and at rest - requirements that must be in the specification, not retrofitted.
What is the difference between PDPA and GDPR for a software project?
They share the core architecture - purposes, legal bases, data subject rights, breach duties - so software designed properly for one covers most of the other. Details differ (definitions, notification timelines, local guidance), so multi-market systems should be specified against both and reviewed by counsel.
Is my software vendor responsible for PDPA compliance?
Responsibility is shared and should be contractual: you as the data controller decide purposes and remain accountable; a vendor building or operating the system acts as a processor and must follow documented instructions, protect the data, and support your obligations. Put processing terms in the development and hosting contracts.