personal-data-protection
Personal-data-protection compliance reference for engineers building applications subject to Singapore PDPA, Indonesia UU PDP, Thailand PDPA, Malaysia PDPA, Philippines DPA (RA 10173), or Vietnam PDPL (91/2025/QH15)
Install / Use
npx skills add hashgraph-online/awesome-codex-plugins --skill personal-data-protectionInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Content & MediaSupported Platforms
Our assessment of personal-data-protection
personal-data-protection scores 87/100 on our quality scale, 656th of 1,155 Content & Media skills we index.
Its SKILL.md is 14 KB long, split into 7 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
With 1,075 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so personal-data-protection is actively maintained.
- Our last check on 2026-11-01 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
personal-data-protection compared with similar skills
All 4 of these similar skills score higher than personal-data-protection; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| personal-data-protection (this skill)by hashgraph-online | 87 | 1.1k | 53d ago | SKILL.md |
| siyuanby siyuan-note | 100 | 47.3k | today | MCP Server |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install personal-data-protection?
- Run
npx skills add hashgraph-online/awesome-codex-plugins --skill personal-data-protection. The install tabs above show the steps for each supported agent. - Which AI agents does personal-data-protection work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is personal-data-protection safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is personal-data-protection still maintained?
- The repository was last updated about 2 months ago, so personal-data-protection is actively maintained.
Skill content
View source on GitHubname: personal-data-protection description: Personal-data-protection compliance reference for engineers building applications subject to Singapore PDPA, Indonesia UU PDP, Thailand PDPA, Malaysia PDPA, Philippines DPA (RA 10173), or Vietnam PDPL (91/2025/QH15). Use when reviewing or modifying code that touches personal data — signup/auth/consent, data export, account deletion, retention/purging, admin access to personal-data stores, third-party processors, breach response, or privacy/T&C documents.
Personal Data Protection Compliance — Layered Reference
⚠ Reference material, not legal advice
This skill is engineering reference material, not legal advice. The maintainers and contributors are not licensed to practise law in Singapore, Thailand, Indonesia, Malaysia, the Philippines, Vietnam, or any other jurisdiction. No attorney–client relationship is created by use of this skill.
Do not rely on this skill as your sole source of truth for personal-data-protection compliance. Always (a) verify any statute citation, threshold, or obligation against the official source, and (b) engage a qualified Data Protection Officer or privacy lawyer before making compliance decisions that materially affect your obligations or your users' rights.
Source-text posture: this skill does not reproduce or republish any of the underlying statutes. It provides engineer-facing interpretation and short attributed quotations of operative phrases under fair-dealing principles, with links to the official sources. Anyone planning to package or redistribute the content beyond similar engineering-reference use should read DISCLAIMER.md § Copyright in source materials — Malaysia's PNMB-published Act 709 / Act A1727 carry the strictest publisher's notice of the populated jurisdictions and may require prior permission.
By using this skill you accept the full disclaimer in DISCLAIMER.md, including the "use at your own risk" terms and the maintainers' zero liability for any decision taken in reliance on this content.
This skill helps engineers ship features that comply with personal-data-protection statutes in Singapore, Thailand, Indonesia, Malaysia, the Philippines and Vietnam. It is organised by where in the stack the obligation lives rather than by statute section number — engineers shouldn't need to learn statute references to do their job.
Step 1 — Identify the active jurisdiction(s)
On first use in a project, check for .pdp-compliance.json at the project root. If present, use personalDataProtection.jurisdictions and load only the matching jurisdictions/<code>/README.md files. If absent, ask the user which jurisdiction(s) apply. The answer depends on where the application's users are located, not where the company is registered.
"Which personal-data-protection regimes does this application need to comply with? Pick all that apply: Singapore (PDPA 2012), Indonesia (UU PDP 27/2022), Thailand (PDPA B.E. 2562), Malaysia (PDPA 2010 with 2024 Amendments), Philippines (DPA / RA 10173), Vietnam (PDPL 91/2025/QH15). If users span multiple jurisdictions — and note Vietnam applies to Vietnamese citizens wherever they are —, pick all relevant — the strictest rule will usually win."
Once selected, suggest creating .pdp-compliance.json in the project root so future sessions and local guardrails do not need to re-ask:
{
"personalDataProtection": {
"jurisdictions": ["sg-pdpa"],
"mode": "strictest-wins",
"reviewPolicy": "warn"
}
}
Then load only the relevant jurisdictions/<code>/README.md files. Cross-jurisdiction comparison lives in jurisdictions/_index.md.
Codes: sg-pdpa, th-pdpa, id-pdp, my-pdpa, ph-dpa, vn-pdpl — all populated. Per-jurisdiction status and the full comparison grid live in jurisdictions/_index.md.
Once the user has chosen, persist that choice in .pdp-compliance.json when the project allows file changes. If the project cannot accept that file, persist the choice somewhere project-specific (a comment in the project's AGENTS.md, CLAUDE.md, or equivalent project-instruction file) so subsequent sessions don't need to re-ask.
Step 2 — Pick the right entry point
You're starting work on something. Open the matching checklist:
| Task | Checklist |
|---|---|
| Adding or modifying a feature that touches personal data | checklists/new-feature.md |
| Adding a column / field that holds personal data | checklists/new-data-field.md |
| Adding a third-party SDK or vendor that will process personal data | checklists/new-vendor.md |
| Responding to a security incident | checklists/breach-response.md |
You want depth on a specific layer. Open the matching layer file:
| Layer | What it covers | |---|---| | 01 Non-technical | DPO, staff acceptable-use, vendor contracts, complaint handling | | 02 Architecture | Data residency, isolation, encryption, secret handling, defence-in-depth | | 03 Data model | Consent records, audit records, retention markers, deletion conventions, PII inventory | | 04 Controls and processes | Access control, retention sweeps, log hygiene, breach detection signals | | 05 Feature / UX | Signup consent, settings, account deletion, data export, primer dialogs, EXIF strip | | 06 Disclosure | Privacy policy, T&C, OS permission strings, contextual notices | | 07 Operational | Incident response, retention sweeps, backups, vendor reviews, monitoring |
Layer files are universal across all populated jurisdictions — implementation patterns are shared. Jurisdiction-specific obligations live in jurisdictions/<code>/obligations/.
Jurisdiction files
Once the active jurisdiction is known, open its files directly from this table rather than following links from one file to the next. Each README.md states scope, statute version and verification date; statute-map.md maps sections to layers; the obligation files hold the per-statute rules.
| Code | Start here | Statute map | Obligations |
|---|---|---|---|
| sg-pdpa | README | statute-map | 01 accountability · 02 consent · 03 purpose · 04 access correction · 05 care · 06 breach notification · 07 offences |
| th-pdpa | README | statute-map | 01 accountability · 02 consent · 03 purpose · 04 access correction · 05 care · 06 breach notification · 07 offences |
| id-pdp | README | statute-map | 01 accountability · 02 consent · 03 purpose · 04 access correction · 05 care · 06 breach notification · 07 offences |
| my-pdpa | README | statute-map | 01 accountability · 02 consent · 03 purpose · 04 access correction · 05 care · 06 breach notification · 07 offences |
| ph-dpa | README | statute-map | 01 accountability · 02 consent · 03 purpose · 04 access correction · 05 care · 06 breach notification · 07 offences |
| vn-pdpl | README | statute-map | 01 accountability · 02 consent · 03 purpose · 04 access correction · 05 care · 06 breach notification · 07 offences · 08 sector specific |
Templates to copy into a project: INCIDENT_RESPONSE.md.template (breach runbook) and pdp-nudge.sh.template (changed-file reminder hook).
Critical thresholds (commit to memory)
These vary by jurisdiction — the active one(s) determine which apply.
| | Singapore PDPA | Thailand PDPA | Indonesia UU PDP | Malaysia PDPA | Philippines DPA | Vietnam PDPL | |---|---|---|---|---|---|---| | Breach notification window to authority | 3 calendar days after assessing as notifiable (s26D(1)) | 72 hours from awareness (s37(4)) | 72 hours from awareness — to both subject AND regulator (Pasal 46(1)) | 72 hours from discovery to Commissioner (s12B(1) + JPDP Guideline 25 Feb 2025); 7 days post-Commissioner to affected subject | 72 hours from knowledge / reasonable belief — to both NPC AND affected subject (§ 38 IRR + NPC Circular 16-03 § 12) | 72 hours from detection of the act (Điều 23(1)) — no assessment step | | Significant-scale / risk threshold | ≥ 500 affected individuals | "Risk to rights and freedoms"; "high risk" triggers individual notification | Always notify subject; "certain circumstances" trigger public notification (Pasal 46(3)) | "Significant harm" triggers subject notification (s12B(2)) — no fixed scale threshold | Information-type-driven: SPI or identity-fraud-enabling info, acquired by unauthorised person, real risk of serious harm (NPC Circular 16-03 § 11); ≥ 100 persons triggers § 35 penalty aggravation | None — harm-based trigger covering national defence/security
Truncated for display — read the full file on GitHub.
Related Skills
siyuan
47.3kAn open-source, privacy-first, self-hosted knowledge workspace where humans and AI agents work together 开源、隐私优先、自托管的知识工作空间,让人与智能体在此协作
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
