top of page

101 Series: PDPA in Thailand

4 days ago
10 min read

A customer gives a phone number for delivery. A hotel scans a passport. A clinic stores medical history. A small shop saves LINE chat records so it can confirm an order later. These everyday actions all involve personal data, and in Thailand they fall under the Personal Data Protection Act, better known as the PDPA.


The PDPA sets rules for how organisations collect, use, store, share, and delete personal data. It affects large companies, small businesses, schools, hospitals, charities, online sellers, landlords, employers, and many others. If an organisation handles information that can identify a person, the law is likely relevant.


This guide explains the basics in plain English. It is not legal advice, but it will help make the main ideas clearer and give a practical starting point for compliance.


Eye-level view of a person writing privacy choices on a paper form at a wooden kitchen table
Personal data rules often begin with simple everyday records.

What the PDPA is and why Thailand introduced it


The Personal Data Protection Act B.E. 2562 (2019) is Thailand’s main data protection law. Its full enforcement began on 1 June 2565 (2022), after a delay period.


The law gives people more control over their personal information. It also gives organisations clear duties when they handle that information.


At its core, the PDPA asks three simple questions:


  • What personal data are you collecting?

  • Why do you need it?

  • Are you treating it fairly and securely?


The law is overseen by the Personal Data Protection Committee, often called the PDPC. The PDPC has powers to issue guidance, receive complaints, and enforce the law.


The PDPA in Thailand has similarities with data protection laws in other places, such as the European Union’s GDPR, but it is a Thai law with its own terms, exemptions, and enforcement approach. A business should not assume that copying a privacy policy from another country will be enough.


What counts as personal data


Personal data is any information that can identify a living person, either directly or indirectly.


Direct identifiers are easy to spot. These include:


  • Full name

  • National ID number

  • Passport number

  • Phone number

  • Email address

  • Home address

  • Photo of a person


Indirect identifiers can also count if they can point back to someone. These may include:


  • Customer ID

  • IP address

  • Location data

  • Online account username

  • Work history

  • Purchase records

  • CCTV footage


The law also recognises sensitive personal data. This type of information needs extra care because misuse could cause serious harm or unfair treatment.


Sensitive personal data can include:


  • Health information

  • Biometric data, such as fingerprints or facial recognition data

  • Race or ethnic origin

  • Religion

  • Political opinions

  • Criminal records

  • Sexual behaviour

  • Disability information

  • Trade union membership


An example makes the difference clear. A coffee shop loyalty card with a customer’s name and phone number involves personal data. A hospital record showing diagnosis, medication, and test results involves sensitive personal data.


Who must follow the PDPA


The PDPA applies to many organisations in Thailand. It can also apply to organisations outside Thailand if they offer goods or services to people in Thailand or monitor their behaviour.


The law uses two key roles.


Role

What it means

Simple example

Data controller

Decides why and how personal data is used

An online shop that collects customer names and delivery addresses

Data processor

Handles personal data on behalf of the controller

A delivery system provider that stores order details for the online shop


A single organisation can be a controller in one situation and a processor in another. The role depends on what the organisation is doing with the data.


A small business is not automatically exempt just because it is small. If it collects customer details, employee records, supplier contacts, website enquiries, or CCTV footage, it should understand its duties.


Common situations covered by the PDPA


In Thailand, the PDPA often appears in normal daily operations:


  • A restaurant collects names and phone numbers for reservations.

  • A condo juristic person keeps resident records and CCTV.

  • A school stores student files and parent contact details.

  • A clinic keeps patient records.

  • An employer keeps staff payroll and ID documents.

  • An e-commerce seller stores customer addresses and chat histories.

  • A hotel collects passport details from guests.


The key point is not whether the activity feels “digital” or “technical”. Paper forms, photocopies, handwritten logs, and printed files can also involve personal data.


The main PDPA principles explained


The PDPA is built around a few practical principles. These ideas help organisations handle personal data in a fair and lawful way.


Have a lawful reason to use the data


An organisation needs a lawful basis before it collects, uses, or discloses personal data. Consent is one lawful basis, but it is not the only one.


Common lawful bases include:


  • Consent from the person

  • Contract performance

  • Legal obligation

  • Legitimate interest

  • Vital interest, such as preventing serious harm

  • Public task or official authority


For example, an online shop may need a customer’s address to deliver a paid order. That can relate to contract performance. An employer may need payroll data to meet tax and labour law obligations. That can relate to legal obligation.


Consent is often needed for activities such as marketing messages, optional data collection, or use of sensitive personal data. When consent is used, it should be clear, separate from unrelated terms, and easy to withdraw.


Tell people what is happening


People should know how their data is being used. This is usually done through a privacy notice.


A good privacy notice should explain:


  • What data is collected

  • Why it is collected

  • The lawful basis for using it

  • Who it may be shared with

  • How long it will be kept

  • What rights the person has

  • How to contact the organisation about privacy matters


The notice should be easy to understand. Long legal wording may protect nobody if people cannot read it.


Collect only what is needed


The PDPA encourages data minimisation. In plain terms, do not collect more than required.


If a salon needs a phone number to confirm bookings, it may not need a national ID number. If a giveaway campaign needs an email address, it may not need date of birth unless there is a real reason.


The more data an organisation keeps, the more it must protect. Collecting less can reduce risk.


Keep data accurate and secure


Personal data should be reasonably accurate and kept safe from loss, misuse, unauthorised access, alteration, or disclosure.


Security does not always mean expensive systems. It can include basic steps such as:


  • Limiting access to staff who need the data

  • Using strong passwords

  • Locking cabinets that hold paper files

  • Avoiding shared accounts

  • Training staff on privacy rules

  • Checking access rights when staff leave

  • Using secure methods to send sensitive files


Security should match the risk. A health clinic needs stricter controls than a casual mailing list for a weekend workshop.


Close-up view of a locked metal file box beside a Thai national ID photocopy with details covered
Paper records need privacy care just like digital files.

Rights people have under the PDPA


The PDPA gives individuals, called data subjects, several rights over their personal data. These rights are a major part of the law.


Right to be informed


People have the right to know what data is collected and how it will be used. This is why privacy notices matter.


Right of access


A person can ask whether an organisation has their personal data and request access to it. In many cases, they can also ask for a copy.


Right to correction


If data is wrong, outdated, or incomplete, the person can ask for it to be corrected.


For example, a customer may ask a delivery company to update an old phone number. An employee may ask HR to correct a misspelled name.


Right to deletion or destruction


In some cases, a person can ask an organisation to delete, destroy, or anonymise their data. This may apply when the data is no longer needed or when consent has been withdrawn.


This right is not absolute. An organisation may still need to keep some records to comply with law, defend legal claims, or complete a contract.


Right to restrict use


A person may ask an organisation to stop using their data in specific situations, such as when they dispute accuracy or object to certain processing.


Right to object


People may object to certain uses of their data, especially where the organisation relies on legitimate interest or uses data for direct marketing.


For direct marketing, organisations should make opt-out choices clear and easy.


Right to data portability


In some cases, a person can ask to receive their data in a format that can be used or transferred elsewhere.


Right to withdraw consent


If consent was the basis for using data, the person can withdraw that consent. The process should be no harder than giving consent.


For example, if someone subscribed to promotional messages through a simple online form, unsubscribing should also be simple.


What organisations should do to comply


PDPA compliance can look complex at first, but the starting point is practical. The aim is to understand what data exists, why it is used, who can access it, and how long it is kept.


Map the personal data you handle


Start by listing the places where personal data appears.


Common places include:


  • Customer forms

  • Sales records

  • Chat messages

  • CCTV systems

  • Email inboxes

  • Accounting files

  • Employee records

  • Website forms

  • Delivery records

  • Cloud storage

  • Paper folders


For each category, ask:


  • What data is collected?

  • Where did it come from?

  • Why is it needed?

  • Who can access it?

  • Who is it shared with?

  • How long is it kept?


This simple inventory often reveals unnecessary data, old files, or risky habits.


Review consent and privacy notices


If an organisation relies on consent, the consent request should be specific and clear. Avoid broad wording that tries to cover everything.


A weak consent statement might say:


“By using our service, you agree that we may use your data for any purpose.”

A clearer version would explain the actual purpose, such as sending promotional offers by SMS, sharing information with a delivery provider, or storing allergy information for food safety.


Privacy notices should be placed where people can see them before or at the time data is collected. For websites, that may be near forms or in a privacy policy page. For physical locations, it may be a notice near a sign-up counter or CCTV area.


Put agreements in place with processors


If another company handles personal data for you, such as a payroll provider, cloud system, booking platform, or delivery vendor, check the contract.


A data processing agreement should make clear:


  • What data the processor handles

  • What the processor may do with it

  • Security duties

  • Confidentiality duties

  • Subcontracting limits

  • What happens when the service ends

  • How breaches are reported


Do not rely only on trust. Written terms help both sides understand their duties.


Prepare for data breaches


A data breach can include loss, theft, unauthorised access, accidental sharing, or damage to personal data.


Examples include:


  • Sending a file to the wrong recipient

  • Losing a laptop with customer records

  • Exposing a database online

  • Posting a document that shows ID numbers

  • Letting former staff keep access to systems


Organisations should have a simple breach response plan. The plan should say who checks the incident, who decides next steps, how affected people are contacted, and when the PDPC may need to be notified.


Under the PDPA, some personal data breaches must be reported within a set time. The exact duty depends on the risk and facts, so serious incidents should be reviewed quickly.


Practical examples for everyday compliance


The easiest way to understand the PDPA is through real-life situations.


Online seller


An online seller collects names, phone numbers, chat messages, payment slips, and delivery addresses.


Good PDPA habits include:


  • Use customer data only to process orders unless marketing consent is given.

  • Avoid keeping payment slips longer than needed.

  • Cover unnecessary details before saving documents.

  • Limit access to order files.

  • Tell customers if their data is shared with delivery providers.


Hotel or guesthouse


A hotel may collect passport details, nationality, booking records, payment details, and CCTV footage.


Good PDPA habits include:


  • Explain why guest information is collected.

  • Store ID copies securely.

  • Limit staff access to guest records.

  • Place clear CCTV notices.

  • Set a retention period for old records.


Employer


An employer handles staff ID documents, bank details, tax records, medical certificates, attendance records, and performance files.


Good PDPA habits include:


  • Keep employee files in a secure place.

  • Share payroll data only with authorised people or providers.

  • Collect medical data only when there is a valid reason.

  • Remove system access when staff leave.

  • Give staff a privacy notice about employment data.


Clinic or wellness service


A clinic, spa, or wellness provider may collect health information, treatment history, allergies, and appointment notes.


Good PDPA habits include:


  • Treat health data as sensitive personal data.

  • Ask for clear consent where required.

  • Avoid discussing customer details where others can hear.

  • Use secure appointment systems.

  • Keep records only as long as needed by law or service needs.


Penalties and risks under the PDPA


The PDPA includes several types of consequences. These can include administrative penalties, civil liability, and criminal penalties for certain serious acts.


The greater risk is often wider than the fine. A privacy problem can damage trust, disrupt operations, and create conflict with customers, staff, or partners.


For most organisations, a sensible approach is better than panic. Start with the highest-risk areas:


  1. Sensitive personal data

  2. Large customer or employee databases

  3. Data shared with third parties

  4. Marketing lists

  5. CCTV and access logs

  6. Old files with no clear purpose

  7. Systems used by former staff


Then work through the rest step by step.


A practical compliance checklist can help:


  • Create a personal data inventory.

  • Identify the lawful basis for each use.

  • Write or update privacy notices.

  • Review consent forms.

  • Check vendor and processor contracts.

  • Set data retention periods.

  • Restrict access to personal data.

  • Train staff on basic privacy rules.

  • Prepare a breach response plan.

  • Review the process regularly.


The PDPA is not only a legal project. It is a habit of handling people’s information with care.


A clear way to think about data protection


The simplest PDPA test is this: if someone asked why you have their data, how you use it, who sees it, and when you will delete it, could you answer clearly?


If the answer is no, start there.


Good data protection does not require perfection on day one. It requires awareness, honest review, and steady improvement. For a beginner, the best first step is to list the personal data you handle and remove what you do not need.


PDPA compliance becomes much easier when data has a clear purpose, clear ownership, and clear limits. Treat personal information as something borrowed, not something owned forever. That mindset is the foundation of safer, fairer data use in Thailand.


bottom of page