
thailand-pdpa
Guides compliance with Thailand's Personal Data Protection Act B.E. 2562 (2019). Covers consent framework, DPO requirements, PDPC enforcement, lawful bases for processing, cross-border transfer mechanisms, and data subject rights under the PDPA. Keywords: Thailand PDPA, PDPC, consent, DPO, cross-border transfers, data subject rights.
- Installs
- 44
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/mukul975/privacy-data-protection-skills --skill thailand-pdpa- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads thailand-pdpa automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Thailand PDPA Compliance
Overview
Thailand's Personal Data Protection Act B.E. 2562 (PDPA), published in the Royal Gazette on 27 May 2019, became fully effective on 1 June 2022 after two postponements from the original 2020 effective date. The PDPA applies to the collection, use, and disclosure of personal data by data controllers and data processors in Thailand, and extraterritorially where activities target data subjects in Thailand (Section 5).
The Personal Data Protection Committee (PDPC, คณะกรรมการคุ้มครองข้อมูลส่วนบุคคล) is the supervisory authority established under Section 8. The Office of the Personal Data Protection Committee (OPDPC) serves as the operational secretariat.
Lawful Bases for Processing (Section 24)
| Basis | Section | Detail |
|---|---|---|
| Consent | Section 19 | Explicit consent; freely given, specific, informed; written or electronic; may be withdrawn at any time |
| Contract performance | Section 24(3) | Necessary for performance of a contract to which the data subject is a party |
| Vital interests | Section 24(4) | Necessary to prevent or suppress danger to life, body, or health |
| Public task | Section 24(4) | Necessary for public interest tasks or exercise of official authority |
| Legitimate interest | Section 24(5) | Legitimate interests of the controller or third party, balanced against data subject's fundamental rights |
| Legal obligation | Section 24(6) | Compliance with a law to which the controller is subject |
| Archiving/research | Section 24(1) | Necessary for archiving, research, or statistics in the public interest with appropriate safeguards |
Sensitive Data (Section 26)
Sensitive data categories: racial or ethnic origin, political opinions, religious or philosophical beliefs, criminal records, trade union membership, genetic data, biometric data, health data, disability data, sexual orientation, and any other data prescribed by the PDPC.
Processing requires explicit consent unless:
- Necessary to prevent or suppress danger to life, body, or health (Section 26(1))
- Relating to lawful activities of non-profit organisations regarding members (Section 26(2))
- Personal data manifestly made public by the data subject (Section 26(3))
- Necessary for legal claims (Section 26(4))
- Necessary for compliance with employment law (Section 26(5))
Consent Framework
Consent Requirements (Section 19)
| Requirement | Detail |
|---|---|
| Explicit | Must be an express statement or conduct clearly indicating agreement |
| Freely given | Must not be a condition of service where unnecessary; no bundling with T&Cs (Section 19(4)) |
| Specific | Consent per purpose; blanket consent is invalid |
| Informed | Full disclosure of purpose, data items, recipients, retention period |
| Written or electronic | Written request for consent must be clear, not misleading, easily accessible |
| Withdrawal | Data subject may withdraw at any time; withdrawal must be as easy as giving consent (Section 19(5)) |
| Children | Under 10 years: consent from parent/legal guardian; 10 years and above: may consent if age-appropriate understanding demonstrated |
Implementation at Zenith Global Enterprises
| Processing Activity | Consent Type | Mechanism |
|---|---|---|
| Customer freight services | Contract performance (Section 24(3)) — consent not required | N/A |
| Marketing communications | Explicit consent (Section 19) | Opt-in checkbox in Thai and English |
| Employee health data processing | Explicit consent for sensitive data (Section 26) | Written consent form at onboarding |
| Cross-border transfer to EU HQ | Explicit consent with transfer disclosure (Section 28) | Dedicated transfer consent form |
DPO Requirements (Section 41-42)
When DPO Appointment is Required
The PDPC Notification on DPO Appointment Criteria (2022) requires a DPO when:
- The data controller or processor is a public authority (except courts acting in judicial capacity)
- Core activities require regular and systematic monitoring of data subjects on a large scale
- Core activities consist of processing sensitive data or criminal records on a large scale
DPO Responsibilities (Section 42)
| Responsibility | Detail |
|---|---|
| Advise on compliance | Advise the controller/processor on PDPA compliance obligations |
| Monitor compliance | Monitor compliance with the PDPA and internal policies |
| Audit coordination | Cooperate with the OPDPC; act as the contact point for the OPDPC |
| Confidentiality | Maintain confidentiality of personal data accessed in the course of duties |
| Independence | Must be able to perform duties independently; no dismissal for performing duties |
Zenith Global Enterprises DPO
| Element | Detail |
|---|---|
| DPO (Thailand) | Siriporn Chaiyaporn, Compliance Manager — Bangkok office |
| Contact | dpo-thailand@zenithglobal.co.th |
| Reporting line | Reports to Chief Privacy Officer; independent reporting access to Board of Directors |
Cross-Border Transfer (Section 28)
Transfer Conditions
Personal data may be transferred to a foreign country or international organisation only if:
| Condition | Section | Detail |
|---|---|---|
| Adequate protection | Section 28(1) | Destination has adequate personal data protection standards as determined by the PDPC |
| Compliance with group rules | Section 28(3) | Transfer within a group of undertakings conducting business together, with appropriate data protection policies inspected and certified by the OPDPC (BCR equivalent) |
| Contract necessity | Section 28(4)(a) | Necessary for contract performance with the data subject |
| Consent | Section 28(4)(b) | Data subject's consent after being informed of inadequate standards |
| Vital interests | Section 28(4)(c) | Necessary to prevent or suppress danger to life, body, or health |
| Legal obligation | Section 28(4)(d) | Necessary for important reasons of public interest |
| Legal claims | Section 28(4)(e) | Necessary for establishing, exercising, or defending legal claims |
| Appropriate safeguards | Section 28(2) | Appropriate protection measures prescribed by the PDPC are in place |
PDPC Adequacy Determinations
As of March 2026, the PDPC has not published a formal list of adequate countries. Transfers primarily rely on consent, contract necessity, or appropriate safeguards.
Data Subject Rights (Sections 30-36)
| Right | Section | Response Deadline | Implementation |
|---|---|---|---|
| Right of access | Section 30 | Within 30 days | Privacy portal in Thai and English |
| Right to data portability | Section 31 | Within 30 days | Structured format (JSON/CSV) |
| Right to object | Section 32 | Without unreasonable delay | Objection mechanism in customer portal |
| Right to erasure | Section 33 | Without unreasonable delay | Automated deletion with legal hold check |
| Right to restriction | Section 34 | Without unreasonable delay | Processing flagging system |
| Right to rectification | Section 35 | Without unreasonable delay | Self-service correction in portal |
| Right to withdraw consent | Section 19(5) | Without unreasonable delay | One-click withdrawal mechanism |
Breach Notification (Section 37(4))
| Element | Requirement |
|---|---|
| OPDPC notification | Within 72 hours of becoming aware of the breach |
| Data subject notification | Without delay if the breach is likely to affect rights and freedoms |
| Content | Nature of breach, DPO contact, likely consequences, remedial measures |
| Cross-border | Notify the OPDPC even if the breach occurred outside Thailand if Thai data subjects are affected |
Enforcement (Sections 90-91)
Administrative Fines
- Up to THB 5 million (approximately USD 140,000) per violation
Criminal Penalties
- Imprisonment up to 1 year and/or fine up to THB 1 million for certain violations (Section 90)
- Apply to natural persons responsible for the violation
Punitive Damages
- Court may award punitive damages up to double the actual damages (Section 78)
Notable PDPC Actions
- The PDPC has issued multiple compliance guidance documents since 2022
- Enforcement focus initially on education and compliance guidance, transitioning to formal enforcement from 2024
- Sectoral guidance published for: financial services, telecommunications, healthcare, e-commerce
Compliance Programme
| Component | Detail |
|---|---|
| DPO | Siriporn Chaiyaporn, Bangkok office |
| Privacy notice | Published at zenithglobal.co.th/privacy in Thai and English |
| Consent management | Platform with Thai language support; separate consent per purpose |
| ROPA | Processing activities register maintained per Section 39 |
| Breach notification | 72-hour workflow to OPDPC; data subject notification procedure |
| Cross-border safeguards | Consent-based transfers with disclosure; intra-group policy for headquarters transfers |
| Employee training | Annual PDPA training for all Thailand employees |
| Data subject rights | 30-day response workflow via privacy portal |
FAQ
What does the thailand-pdpa skill do?
Guides compliance with Thailand's Personal Data Protection Act B.E. 2562 (2019). Covers consent framework, DPO requirements, PDPC enforcement, lawful bases for processing, cross-border transfer mechanisms, and data subject rights under the PDPA. Keywords: Thailand PDPA, PDPC, consent, DPO, cross-border transfers, data subject rights.
How do I install thailand-pdpa?
Run npx skills add https://github.com/mukul975/privacy-data-protection-skills --skill thailand-pdpa in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/thailand-pdpa/ (personal) or .claude/skills/thailand-pdpa/ (project).
Which AI agents can use thailand-pdpa?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is thailand-pdpa safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains thailand-pdpa?
It is published by mukul975 in mukul975/privacy-data-protection-skills. It has 44 recorded installs.
More from mukul975/privacy-data-protection-skills
brazil-lgpd
mukul975/privacy-data-protection-skills
Guides compliance with Brazil's Lei Geral de Proteção de Dados (LGPD, Lei 13.709/2018). Covers the 10 lawful bases under Art. 7, DPO appointment, ANPD enforcement, data subject rights under Arts. 17-22, and international transfer mechanisms. Keywords: LGPD, Brazil data protection, ANPD, lawful bases, data subject rights, international transfers.
analytics-cookie-consent
mukul975/privacy-data-protection-skills
Managing consent for analytics cookies and implementing privacy-preserving measurement. Covers GA4 privacy configuration, consent mode fallback behavior, aggregate reporting alternatives, and cookieless measurement approaches.
audit-report-writing
mukul975/privacy-data-protection-skills
Guides privacy audit report writing including executive summary drafting, findings classification (critical, high, medium, low), evidence referencing, root cause analysis documentation, recommendation formulation, management response tracking, and report distribution protocols. Covers report structure from scope definition through appendices and sign-off. Keywords: audit report, findings documentation, executive summary, recommendations, report structure, privacy audit deliverables.
gdpr-compliance-audit
mukul975/privacy-data-protection-skills
Guides a comprehensive organisational data protection audit against key GDPR requirements including Articles 5, 24, 25, 28, 30, 32, 35, and 37. Includes 50+ control points covering principles, accountability, security, and governance. Activate when performing compliance audits, preparing for supervisory authority inspections, or assessing organisational GDPR maturity. Keywords: data protection audit, compliance audit, GDPR audit, control points, accountability.
conducting-gdpr-dpia
mukul975/privacy-data-protection-skills
Guides the end-to-end GDPR Data Protection Impact Assessment process under Article 35, including mandatory trigger identification per Art. 35(3), DPIA content requirements per Art. 35(7), and EDPB WP248rev.01 methodology. Activate for systematic profiling, large-scale special category processing, or large-scale public monitoring. Keywords: DPIA, Article 35, impact assessment, WP248, data protection, risk assessment.
backup-retention-erasure
mukul975/privacy-data-protection-skills
Manages backup and archive data under retention schedules and erasure obligations. Covers the technical infeasibility exception for backup deletion, backup cycle alignment with retention periods, restore-and-delete procedures, and interim protective measures during backup retention. Activate for backup deletion, archive erasure, backup retention, restore and delete, technical infeasibility queries.
Popular security skills
azure-compliance
microsoft/azure-skills
Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.
minimal-run-and-audit
lllllllama/rigorpilot-skills
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized reprooutputs/ files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.
seo-audit
coreyhaines31/marketingskills
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
firebase-security-rules-auditor
firebase/agent-skills
Audits Firebase (Firestore, Cloud Storage) security rules for vulnerabilities, privilege escalation, role bypasses, create vs update inconsistencies, resource exhaustion, type safety, size limits, and hasOnly ownership checks. Use when auditing/reviewing rules, running red-team rule assessments, or scoring against auditor checklists. Don't use for Firebase CLI (login, deploy), Auth, Crashlytics, Remote Config, or database queries.
audit
pbakaus/impeccable
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
competitors
coreyhaines31/marketingskills
When the user wants to create competitor comparison or alternative pages for SEO and buyer-facing use. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'competitor teardown,' 'audit our competitor pages,' 'are our comparison pages out of date,' or 'competitive asset audit.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For auditing existing claims (not researching competitors from scratch, which is competitor-profiling; not technical SEO on these pages, which is seo-audit), use the asset audit here. For internal battle cards and sales-specific competitor docs, see sales-enablement.