C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Implements compliance with South Africa's Protection of Personal Information Act (POPIA), Act No.
Install South Africa Popia
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill south-africa-popia -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills south-africa-popia --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/privacy/south-africa-popia .claude/skills/south-africa-popia && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "south-africa-popia" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/south-africa-popia into .claude/skills/south-africa-popia/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "south-africa-popia", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/south-africa-popiaType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill south-africa-popia -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills south-africa-popia --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/privacy/south-africa-popia .agents/skills/south-africa-popia && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "south-africa-popia" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/south-africa-popia into .agents/skills/south-africa-popia/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "south-africa-popia", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill south-africa-popia -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills south-africa-popia --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/privacy/south-africa-popia .cursor/skills/south-africa-popia && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "south-africa-popia" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/south-africa-popia into .cursor/skills/south-africa-popia/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "south-africa-popia", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mukul975/Privacy-Data-Protection-Skills.git --path skills/privacy/south-africa-popia--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill south-africa-popia -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills south-africa-popia --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/privacy/south-africa-popia .gemini/skills/south-africa-popia && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "south-africa-popia" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/south-africa-popia into .gemini/skills/south-africa-popia/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "south-africa-popia", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mukul975/Privacy-Data-Protection-Skills south-africa-popiaInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill south-africa-popia -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/privacy/south-africa-popia .github/skills/south-africa-popia && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "south-africa-popia" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/south-africa-popia into .github/skills/south-africa-popia/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "south-africa-popia", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill south-africa-popia -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills south-africa-popia --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/privacy/south-africa-popia .opencode/skills/south-africa-popia && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "south-africa-popia" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/south-africa-popia into .opencode/skills/south-africa-popia/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "south-africa-popia", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
south-africa-popia- GitHub stars
- 301
- Token cost
- ~1.9k tokens
- SKILL.md length
- 923 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Implements compliance with South Africa's Protection of Personal Information Act (POPIA), Act No.
- Works in 6 steps: The recipient is subject to a law,… → The data subject consents after being… → Transfer is necessary for performance of… → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Key Definitions, Eight Conditions for Lawful… and Cross-Border Transfers…, plus 3 more sections
- Runs Python scripts from its folder
What it does
South Africa Popia is an agent skill from mukul975/Privacy-Data-Protection-Skills. Implements compliance with South Africa's Protection of Personal Information Act (POPIA), Act No. 4 of 2013. Covers conditions for lawful processing, data subject rights, cross-border transfer restrictions, Information Regulator enforcement, and responsible party obligations. Keywords: POPIA, South Africa, Information Regulator, responsible party, operator, prior authorisation.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts, reference files and assets (for example `assets/template.md`, `references/standards.md` and `references/workflows.md`).
It sits in Legal & Compliance, covering Privacy and GDPR. The repository describes itself as: 282+ structured privacy & data protection skills for AI agents. GDPR, CCPA, EU AI Act, HIPAA, LGPD, PIPL, DPDP Act. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Privacy and GDPR
Example prompts
- “Use the south-africa-popia skill to implement compliance with South Africa's Protection of Personal Information Act (POPIA), Act No”
- “/south-africa-popia”
Requirements
- Python 3
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- The recipient is subject to a law, binding corporate rules, or binding agreement providing an adequate level of protection substantially…
- The data subject consents after being informed of the risks
- Transfer is necessary for performance of a contract between the data subject and responsible party
- Transfer is necessary for implementation of pre-contractual measures taken in response to the data subject's request
- Transfer is for the benefit of the data subject and it is not reasonably practicable to obtain consent
- The information is contained in or derived from a public record
What it can do on your machine
Read from SKILL.md and the folder at commit 9b2ef9e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
South Africa Popia loads about 1.9k tokens when it runs, and up to ~4.9k if it reads all its reference files. Until then it costs about 100 tokens; SKILL.md has 923 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from mukul975/Privacy-Data-Protection-Skills at commit 9b2ef9e, republished under its Apache-2.0 licence (© mukul975). 923 words, ~1,887 tokens.
Download SKILL.mdSave it as
.claude/skills/south-africa-popia/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- south-africa-popia
- description
- Implements compliance with South Africa's Protection of Personal Information Act (POPIA), Act No. 4 of 2013. Covers conditions for lawful processing, data subject rights, cross-border transfer restrictions, Information Regulator enforcement, and responsible party obligations. Keywords: POPIA, South Africa, Information Regulator, responsible party, operator, prior authorisation.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- global-privacy-regulations
- metadata.tags
- popia, south-africa, information-regulator, cross-border-transfer, responsible-party
South Africa POPIA Compliance
Overview
The Protection of Personal Information Act (POPIA), Act No. 4 of 2013, is South Africa's comprehensive data protection law. It came into full effect on 1 July 2021 following a one-year grace period after commencement on 1 July 2020. POPIA is modelled broadly on EU data protection principles but is adapted to the South African constitutional framework, specifically Section 14 of the Constitution (right to privacy). The Information Regulator is the independent supervisory authority responsible for enforcement. POPIA applies to any responsible party (controller) domiciled in South Africa or that uses automated or non-automated means within South Africa to process personal information, unless those means are used only to forward information through the Republic.
Key Definitions
| POPIA Term | GDPR Equivalent | Definition |
|---|---|---|
| Personal information | Personal data | Information relating to an identifiable living natural person or identifiable existing juristic person (POPIA uniquely covers juristic persons) |
| Special personal information | Special category data | Religious or philosophical beliefs, race or ethnic origin, trade union membership, political persuasion, health, sex life, biometric information, criminal behaviour (Section 26) |
| Responsible party | Controller | A public or private body or any other person which, alone or in conjunction with others, determines the purpose of and means for processing (Section 1) |
| Operator | Processor | A person who processes personal information for a responsible party in terms of a contract or mandate (Section 1) |
| Data subject | Data subject | The person to whom personal information relates (includes juristic persons) |
| Information Officer | DPO | Head of organisation or designated person responsible for encouraging compliance (Section 55) |
Eight Conditions for Lawful Processing (Sections 8-25)
Condition 1: Accountability (Section 8)
The responsible party must ensure that all conditions for lawful processing are complied with at the time of determining the purpose and means of processing and during the processing itself.
Condition 2: Processing Limitation (Sections 9-12)
- Personal information must be processed lawfully and in a reasonable manner that does not infringe the privacy of the data subject
- Processing must be adequate, relevant, and not excessive (Section 10)
- Consent must be voluntary, specific, and informed; may be withdrawn (Section 11)
- Personal information may be collected directly from the data subject, with exceptions (Section 12)
Condition 3: Purpose Specification (Sections 13-14)
- Personal information must be collected for a specific, explicitly defined, and lawful purpose related to a function or activity of the responsible party
- Records must not be retained longer than necessary unless retention is required by law, reasonably necessary for a lawful purpose, or retention is required under a contract
Condition 4: Further Processing Limitation (Section 15)
Further processing must be compatible with the original purpose. Compatibility is assessed considering the relationship between purposes, nature of information, consequences for the data subject, manner of collection, and any contractual rights.
Condition 5: Information Quality (Section 16)
The responsible party must take reasonably practicable steps to ensure personal information is complete, accurate, not misleading, and updated where necessary.
Condition 6: Openness (Sections 17-18)
- The responsible party must notify the Information Regulator before commencing processing (Section 17, not yet fully enforced)
- Data subjects must be notified when their personal information is collected (Section 18)
Condition 7: Security Safeguards (Sections 19-22)
- Appropriate technical and organisational measures must be in place to prevent loss, damage, unauthorised access (Section 19)
- Operators must be bound by contract to establish and maintain security measures (Section 21)
- Breach notification to the Information Regulator and data subjects is mandatory "as soon as reasonably possible" when there are reasonable grounds to believe a compromise has occurred (Section 22)
Show full SKILL.md (340 more words)Show less
Condition 8: Data Subject Participation (Sections 23-25)
- Data subjects have the right to request confirmation of processing, access to records, correction, and deletion
- Requests must be fulfilled within a reasonable time period
- Fees charged must not be excessive
Cross-Border Transfers (Section 72)
Transfer of personal information outside South Africa is permitted only where:
- The recipient is subject to a law, binding corporate rules, or binding agreement providing an adequate level of protection substantially similar to POPIA
- The data subject consents after being informed of the risks
- Transfer is necessary for performance of a contract between the data subject and responsible party
- Transfer is necessary for implementation of pre-contractual measures taken in response to the data subject's request
- Transfer is for the benefit of the data subject and it is not reasonably practicable to obtain consent
- The information is contained in or derived from a public record
Enforcement and Penalties
The Information Regulator may:
- Issue enforcement notices (Section 95)
- Impose administrative fines up to ZAR 10 million (Section 109)
- Refer matters for criminal prosecution, with imprisonment up to 10 years for certain offences (Section 107)
- Conduct assessments (Section 89)
- Issue codes of conduct (Section 60)
Key Enforcement Actions
- Department of Justice and Constitutional Development (2022): The Information Regulator issued an enforcement notice for failure to implement adequate security measures following a large-scale data breach affecting the Master of the High Court system.
- TransUnion South Africa (2022): Following a breach affecting 54 million records, the Information Regulator investigated and issued compliance directives regarding breach notification obligations and security safeguards.
- Department of Home Affairs (2023): Enforcement notice for non-compliance with data subject access requests and security safeguard conditions.
Integration Points
- breach-72h-notification: POPIA Section 22 breach notification (note: POPIA uses "as soon as reasonably possible" not a fixed 72-hour clock)
- cross-border transfers: Section 72 transfer restrictions apply alongside GDPR Chapter V where dual applicability exists
- vendor-privacy-due-diligence: Operator agreements under Section 21 must include security obligation requirements
- data-inventory-mapping: Section 17 notification to the Information Regulator requires comprehensive processing inventory
© mukul975, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (scripts, references, assets) in skills/privacy/south-africa-popia of mukul975/Privacy-Data-Protection-Skills.
- SKILL.md
- assets/template.md
- references/standards.md
- references/workflows.md
- scripts/process.py
Open the folder on GitHubat commit 9b2ef9e
Compare with similar skills
South Africa Popia next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| South Africa Popia this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| C15tc15t/c15t | 1.9k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| HIPAA Safe Harbor Coverage Auditmaziyarpanahi/openmed | 5.5k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Korean Privacy Termskimlawtech/korean-privacy-terms | 587 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Gdpr ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
HIPAA Safe Harbor Coverage Audit
maziyarpanahi/openmed
Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.
Korean Privacy Terms
kimlawtech/korean-privacy-terms
처리방침·이용약관 자동 생성 스킬 패키지 (v4.0). An agent skill from kimlawtech/korean-privacy-terms.
Gdpr Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert GDPR compliance assistant covering all four core workflows: (1) auditing code and systems for GDPR violations, (2) drafting GDPR-compliant documents such as privacy policies, Data Processing…
Hipaa Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
Pii Contract Analyze
gregmos/PII-Shield
Universal legal document processor with PII anonymization. An agent skill from gregmos/PII-Shield.
More from mukul975/Privacy-Data-Protection-Skills
All 280 skills in this repoAge Gating Services
mukul975/Privacy-Data-Protection-Skills
Implements age-gating mechanisms for online services to restrict access based on user age.
AI Data Retention
mukul975/Privacy-Data-Protection-Skills
Manages AI model retention and machine unlearning requirements.
AI Dpia
mukul975/Privacy-Data-Protection-Skills
Conducts Data Protection Impact Assessments for AI and ML systems per EDPB Guidelines 04/2025 on AI processing.
Dpia Mitigation Plan
mukul975/Privacy-Data-Protection-Skills
Structures risk mitigation planning and residual risk tracking for Data Protection Impact Assessments under GDPR Article 35(7)(d).
Gdpr Accountability
mukul975/Privacy-Data-Protection-Skills
Guides implementation of the GDPR accountability principle under Articles 5(2) and 24, including documentation requirements for policies, DPIAs, RoPA, training records, and breach logs.
Pia Threshold Screening
mukul975/Privacy-Data-Protection-Skills
Conducts pre-DPIA threshold screening to determine whether a full Data Protection Impact Assessment is required under GDPR Article 35.
Related
Categories
Questions about South Africa Popia
What does South Africa Popia do?
Implements compliance with South Africa's Protection of Personal Information Act (POPIA), Act No. South Africa Popia is an agent skill from mukul975/Privacy-Data-Protection-Skills. Implements compliance with South Africa's Protection of Personal Information Act (POPIA), Act No.
When should I use South Africa Popia?
South Africa Popia fits situations like: tasks that involve Privacy and GDPR.
How do I install South Africa Popia in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill south-africa-popia -a claude-code`. Or copy the skill folder (skills/privacy/south-africa-popia in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/south-africa-popia in your project. Claude Code loads it when a task matches its description.
How do I install South Africa Popia in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill south-africa-popia -a codex`. Or copy the skill folder (skills/privacy/south-africa-popia in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/south-africa-popia in your project. Codex loads it when a task matches its description.
Can I use South Africa Popia in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill south-africa-popia -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/south-africa-popia, .gemini/skills/south-africa-popia, .github/skills/south-africa-popia and .opencode/skills/south-africa-popia in your project.
What does South Africa Popia need to run?
Going by SKILL.md and its folder, South Africa Popia needs Python for the scripts in its folder. Our summary lists: Python 3.
Does South Africa Popia access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is South Africa Popia safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does South Africa Popia use?
South Africa Popia is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does South Africa Popia use?
About 1.9k tokens (SKILL.md is roughly 7.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3k tokens, read only when the agent opens those files.
What are the alternatives to South Africa Popia?
Skills that share tags, products or a category with South Africa Popia: C15t (c15t/c15t, 1.9k stars), HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars), Korean Privacy Terms (kimlawtech/korean-privacy-terms, 587 stars) and Gdpr Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains South Africa Popia?
mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 301 GitHub stars. The repository holds 280 skills in this directory. The repository was last updated on March 16, 2026.
Source: mukul975/Privacy-Data-Protection-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.