Privacy Policy Generator Service Entry
nisrulz/app-privacy-policy-generator
Adds a new third-party service to the app privacy policy generator: a YAML entry, a 160 by 160 logo, a rebuild of the generated script and the validation checks.
Systematic application of the eight privacy design patterns per Hoepman: minimize, hide, separate, abstract, inform, control, enforce, and demonstrate.
Install Applying Privacy Design Patterns
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill applying-privacy-design-patterns -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills applying-privacy-design-patterns --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/applying-privacy-design-patterns .claude/skills/applying-privacy-design-patterns && 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 "applying-privacy-design-patterns" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/applying-privacy-design-patterns into .claude/skills/applying-privacy-design-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "applying-privacy-design-patterns", 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/applying-privacy-design-patternsType 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 applying-privacy-design-patterns -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills applying-privacy-design-patterns --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/applying-privacy-design-patterns .agents/skills/applying-privacy-design-patterns && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "applying-privacy-design-patterns" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/applying-privacy-design-patterns into .agents/skills/applying-privacy-design-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "applying-privacy-design-patterns", 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 applying-privacy-design-patterns -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills applying-privacy-design-patterns --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/applying-privacy-design-patterns .cursor/skills/applying-privacy-design-patterns && 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 "applying-privacy-design-patterns" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/applying-privacy-design-patterns into .cursor/skills/applying-privacy-design-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "applying-privacy-design-patterns", 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/applying-privacy-design-patterns--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 applying-privacy-design-patterns -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills applying-privacy-design-patterns --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/applying-privacy-design-patterns .gemini/skills/applying-privacy-design-patterns && 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 "applying-privacy-design-patterns" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/applying-privacy-design-patterns into .gemini/skills/applying-privacy-design-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "applying-privacy-design-patterns", 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 applying-privacy-design-patternsInstalls 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 applying-privacy-design-patterns -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/applying-privacy-design-patterns .github/skills/applying-privacy-design-patterns && 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 "applying-privacy-design-patterns" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/applying-privacy-design-patterns into .github/skills/applying-privacy-design-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "applying-privacy-design-patterns", 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 applying-privacy-design-patterns -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 applying-privacy-design-patterns --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/applying-privacy-design-patterns .opencode/skills/applying-privacy-design-patterns && 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 "applying-privacy-design-patterns" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/applying-privacy-design-patterns into .opencode/skills/applying-privacy-design-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "applying-privacy-design-patterns", 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
applying-privacy-design-patterns- GitHub stars
- 297
- Token cost
- ~2.9k tokens
- SKILL.md length
- 1,270 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Systematic application of the eight privacy design patterns per Hoepman: minimize, hide, separate, abstract, inform, control, enforce, and demonstrate.
- Works in 8 steps: MINIMIZE → HIDE → SEPARATE → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, The Eight Privacy Design…, Pattern Selection Methodology and Key Regulatory References
- Runs Python scripts from its folder
What it does
Applying Privacy Design Patterns is an agent skill from mukul975/Privacy-Data-Protection-Skills. Systematic application of the eight privacy design patterns per Hoepman: minimize, hide, separate, abstract, inform, control, enforce, and demonstrate. Covers pattern selection methodology per processing activity, mapping to GDPR principles, and practical implementation guidance for privacy-by-design system architecture.
Its SKILL.md is about 2.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 Development, covering Privacy and GDPR and Design patterns. 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
- Tasks that involve Design patterns
Example prompts
- “/applying-privacy-design-patterns”
Requirements
- Python 3
Workflow steps
8 steps, taken from the step headings in SKILL.md.
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
Applying Privacy Design Patterns loads about 2.9k tokens when it runs, and up to ~4.5k if it reads all its reference files. Until then it costs about 89 tokens; SKILL.md has 1,270 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). 1,270 words, ~2,878 tokens.
Download SKILL.mdSave it as
.claude/skills/applying-privacy-design-patterns/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- applying-privacy-design-patterns
- description
- Systematic application of the eight privacy design patterns per Hoepman: minimize, hide, separate, abstract, inform, control, enforce, and demonstrate. Covers pattern selection methodology per processing activity, mapping to GDPR principles, and practical implementation guidance for privacy-by-design system architecture.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- privacy-by-design
- metadata.tags
- privacy-design-patterns, hoepman, minimize-hide-separate, privacy-architecture, by-design
Applying Privacy Design Patterns
Overview
Privacy design patterns provide reusable architectural solutions for implementing data protection principles in system design. Jaap-Henk Hoepman's framework (2014, expanded in "Privacy Design Strategies: The Eight Strategies for GDPR Compliance") defines eight privacy design strategies organized into two categories: data-oriented strategies (minimize, hide, separate, abstract) that focus on the processing of personal data itself, and process-oriented strategies (inform, control, enforce, demonstrate) that focus on the organizational processes surrounding data processing.
These patterns directly implement GDPR Article 25(1) data protection by design and map to specific GDPR principles under Article 5.
The Eight Privacy Design Patterns
Data-Oriented Strategies
1. MINIMIZE
Principle: Limit the processing of personal data as much as possible.
GDPR mapping: Article 5(1)(c) data minimization, Article 25(2) by default.
Sub-patterns:
| Sub-pattern | Description | Implementation |
|---|---|---|
| Select before collect | Determine which data is necessary before designing collection interfaces | API allowlists, form field audits |
| Exclude | Remove unnecessary data elements from collection | Schema validation rejecting non-required fields |
| Strip | Remove identifying information as soon as possible after collection | Pseudonymization at ingestion boundary |
| Destroy | Delete data as soon as the purpose is fulfilled | TTL-based automated deletion |
Prism Data Systems AG Implementation:
The customer onboarding API at Prism Data Systems AG validates incoming requests against a strict allowlist. The /api/v2/register endpoint accepts only email, display_name, and country_code. The date_of_birth field is collected only during age verification and is converted to a boolean is_age_verified within 24 hours, with the raw date destroyed.
2. HIDE
Principle: Protect personal data, or make it unlinkable or unobservable.
GDPR mapping: Article 5(1)(f) integrity and confidentiality, Article 32(1)(a) encryption and pseudonymisation.
Sub-patterns:
| Sub-pattern | Description | Implementation |
|---|---|---|
| Encrypt | Apply cryptographic protection to data at rest and in transit | AES-256-GCM field-level encryption, TLS 1.3 |
| Hash | Replace identifiers with irreversible digests | SHA-256 for log anonymization |
| Mix | Combine data from multiple subjects to prevent singling out | k-anonymity, differential privacy noise |
| Obfuscate | Add noise or perturbation to prevent precise inference | Differential privacy, data masking |
| Dissociate | Break the link between data and identity | Pseudonymization with separated key storage |
Prism Data Systems AG Implementation: All personally identifiable fields are encrypted with per-field AES-256-GCM Data Encryption Keys (DEKs) managed in AWS KMS. Customer identifiers entering the analytics pipeline are pseudonymized via HMAC-SHA256 with keys stored in a Hardware Security Module physically separated from analytics infrastructure.
3. SEPARATE
Principle: Process personal data in a distributed fashion, preventing correlation.
GDPR mapping: Article 5(1)(b) purpose limitation, Article 25(1) by design.
Sub-patterns:
| Sub-pattern | Description | Implementation |
|---|---|---|
| Isolate | Process different categories of data in separate systems | Purpose-partitioned databases, microservice isolation |
| Distribute | Spread data across multiple locations to prevent single-point access | Federated learning, SMPC, sharding |
Prism Data Systems AG Implementation: Prism Data Systems AG maintains purpose-partitioned PostgreSQL databases: the authentication database stores only credential-related data, the billing database stores only financial data, and the analytics warehouse stores only pseudonymized event data. No single database contains a complete profile of any customer. Cross-purpose joins require explicit compatibility assessment per Article 6(4).
4. ABSTRACT
Principle: Limit the detail of personal data as much as possible.
GDPR mapping: Article 5(1)(c) data minimization, Recital 26 anonymization.
Sub-patterns:
| Sub-pattern | Description | Implementation |
|---|---|---|
| Summarize | Replace detailed data with aggregated summaries | Aggregate reporting with minimum group size 11 |
| Group | Generalize values to broader categories | Age ranges instead of exact ages, region instead of postal code |
| Perturb | Add randomness to exact values | Differential privacy, random rounding |
Prism Data Systems AG Implementation: Customer age is stored as a 5-year bracket (e.g., "25-29") rather than exact date of birth. Geographic data is generalized from full postal code to canton-level. Analytics dashboards enforce a minimum group size of 11 records per cell, with smaller groups suppressed and displayed as "< 11."
Process-Oriented Strategies
5. INFORM
Principle: Inform data subjects about the processing of their personal data.
GDPR mapping: Articles 12-14 transparency obligations.
Sub-patterns:
| Sub-pattern | Description | Implementation |
|---|---|---|
| Supply | Proactively provide privacy information | Layered privacy notices, just-in-time notifications |
| Notify | Alert data subjects about processing events | Email notifications for new data access, breach notifications |
| Explain | Provide meaningful explanations of processing logic | Explainable AI outputs, processing purpose descriptions |
Prism Data Systems AG Implementation: A layered privacy notice is presented at every data collection point. The first layer is a plain-language summary (Flesch-Kincaid grade 8). The second layer provides full Article 13 information. Just-in-time notifications appear when a new feature requires additional data: "To activate bulk export, Prism Data Systems AG needs to process your API usage history."
Show full SKILL.md (544 more words)Show less
6. CONTROL
Principle: Provide data subjects with control over the processing of their personal data.
GDPR mapping: Articles 15-22 data subject rights, Article 7(3) consent withdrawal.
Sub-patterns:
| Sub-pattern | Description | Implementation |
|---|---|---|
| Consent | Obtain and manage consent for each processing purpose | Granular consent UI with unticked defaults |
| Choose | Allow data subjects to select processing options | Privacy preference center |
| Update | Enable data subjects to correct their data | Self-service profile editing |
| Retract | Enable data subjects to withdraw consent or request erasure | One-click consent withdrawal, erasure request workflow |
Prism Data Systems AG Implementation:
The Privacy Preference Center at account.prism-data.ch/privacy provides data subjects with granular controls: per-purpose consent toggles, data download (portability), correction interface, and one-click erasure request. Consent withdrawal takes effect within 24 hours and triggers downstream processing cessation.
7. ENFORCE
Principle: Commit to processing personal data in a privacy-friendly way, and enforce this.
GDPR mapping: Article 24 controller responsibility, Article 25(1) by design, Article 28 processor contracts.
Sub-patterns:
| Sub-pattern | Description | Implementation |
|---|---|---|
| Create | Define and publish privacy policies and standards | GDPR policy framework, data classification standard |
| Maintain | Regularly update and enforce privacy policies | Quarterly policy reviews, automated compliance checks |
| Uphold | Implement technical enforcement of privacy rules | Purpose-based access control (OPA), automated retention |
Prism Data Systems AG Implementation: Privacy policies are enforced technically through Open Policy Agent (OPA) rules that evaluate every data access request against the purpose registry. The CI/CD pipeline includes a privacy gate that blocks deployment of services failing the data minimization assessment. Processor contracts include standard contractual clauses reviewed semi-annually.
8. DEMONSTRATE
Principle: Demonstrate compliance with privacy policies and applicable regulations.
GDPR mapping: Article 5(2) accountability, Article 30 records of processing, Article 35 DPIA.
Sub-patterns:
| Sub-pattern | Description | Implementation |
|---|---|---|
| Record | Maintain comprehensive records of processing activities | Article 30 register, consent logs, DPIA repository |
| Audit | Conduct regular privacy audits | Quarterly internal audits, annual external audit |
| Report | Generate compliance reports for regulators and management | DPO quarterly report, board privacy report |
Prism Data Systems AG Implementation: All data access events are logged in an immutable audit trail with: timestamp, requester identity, purpose declaration, data categories accessed, and authorization decision. The Article 30 register is maintained as a living document updated within 5 business days of any processing change. DPIAs are conducted for all high-risk processing and reviewed annually.
Pattern Selection Methodology
Step 1: Map Processing to GDPR Principles
For each processing activity, identify which GDPR principles are most relevant:
| GDPR Principle | Primary Pattern | Supporting Patterns |
|---|---|---|
| Data minimization (Art. 5(1)(c)) | MINIMIZE | ABSTRACT, HIDE |
| Purpose limitation (Art. 5(1)(b)) | SEPARATE | ENFORCE |
| Storage limitation (Art. 5(1)(e)) | MINIMIZE (Destroy) | ENFORCE |
| Integrity & confidentiality (Art. 5(1)(f)) | HIDE | ENFORCE |
| Transparency (Art. 5(1)(a)) | INFORM | DEMONSTRATE |
| Lawfulness (Art. 5(1)(a)) | CONTROL | ENFORCE |
| Accuracy (Art. 5(1)(d)) | CONTROL (Update) | INFORM |
| Accountability (Art. 5(2)) | DEMONSTRATE | ENFORCE |
Step 2: Assess Pattern Applicability
Score each pattern's applicability (1-5) for the specific processing activity.
Step 3: Select and Combine
Select the highest-scoring patterns. Most processing activities require a combination of 3-5 patterns applied at different architectural layers.
Key Regulatory References
- GDPR Article 5 — Principles relating to processing of personal data
- GDPR Article 25(1) — Data protection by design
- GDPR Article 25(2) — Data protection by default
- EDPB Guidelines 4/2019 on Article 25 Data Protection by Design and by Default
- Hoepman, J.-H. (2014). "Privacy Design Strategies." IFIP SEC. Extended in "Privacy Design Strategies: The Eight Strategies for GDPR Compliance" (2022).
© 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/applying-privacy-design-patterns 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
Applying Privacy Design Patterns 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 |
|---|---|---|---|---|---|---|
| Applying Privacy Design Patterns this skillmukul975/Privacy-Data-Protection-Skills | 297 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Privacy Policy Generator Service Entrynisrulz/app-privacy-policy-generator | 4.7k | — | ~351 | Automated safety check: Pass | AGPL-3.0 | |
| Vercel Composition Patternssupabase/supabase | 111k | 58 repos | ~726 | Automated safety check: Pass | MIT | |
| Swiftui View RefactorDimillian/Skills | 4k | 5 repos | ~2k | Automated safety check: Pass | MIT | |
| RTK Rust Design Patternsrtk-ai/rtk | 83k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Effect Client WrapperUsefulSoftwareCo/executor | 4.1k | 1 repos | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
- Official
Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
Swiftui View Refactor
Dimillian/Skills
Refactor and review SwiftUI view files with strong defaults for small dedicated subviews, MV-over-MVVM data flow, stable view trees, explicit dependency injection, and correct Observation usage.
RTK Rust Design Patterns
rtk-ai/rtk
Describes seven Rust design patterns for the RTK CLI filter modules, with when to use each, RTK examples, and notes on when a pattern is overkill.
Effect Client Wrapper
UsefulSoftwareCo/executor
Pattern for wrapping third-party SDK clients (Stripe, Resend, AWS, etc.) with Effect.
Architecture Patterns
KartikLabhshetwar/better-shot
Deep dive into software architecture for macOS. An agent skill from KartikLabhshetwar/better-shot.
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 Applying Privacy Design Patterns
What does Applying Privacy Design Patterns do?
Systematic application of the eight privacy design patterns per Hoepman: minimize, hide, separate, abstract, inform, control, enforce, and demonstrate. Applying Privacy Design Patterns is an agent skill from mukul975/Privacy-Data-Protection-Skills. Systematic application of the eight privacy design patterns per Hoepman: minimize, hide, separate, abstract, inform, control, enforce, and demonstrate.
When should I use Applying Privacy Design Patterns?
Applying Privacy Design Patterns fits situations like: tasks that involve Privacy and GDPR; tasks that involve Design patterns.
How do I install Applying Privacy Design Patterns in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill applying-privacy-design-patterns -a claude-code`. Or copy the skill folder (skills/privacy/applying-privacy-design-patterns in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/applying-privacy-design-patterns in your project. Claude Code loads it when a task matches its description.
How do I install Applying Privacy Design Patterns in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill applying-privacy-design-patterns -a codex`. Or copy the skill folder (skills/privacy/applying-privacy-design-patterns in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/applying-privacy-design-patterns in your project. Codex loads it when a task matches its description.
Can I use Applying Privacy Design Patterns 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 applying-privacy-design-patterns -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/applying-privacy-design-patterns, .gemini/skills/applying-privacy-design-patterns, .github/skills/applying-privacy-design-patterns and .opencode/skills/applying-privacy-design-patterns in your project.
What does Applying Privacy Design Patterns need to run?
Going by SKILL.md and its folder, Applying Privacy Design Patterns needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Applying Privacy Design Patterns 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 Applying Privacy Design Patterns 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 Applying Privacy Design Patterns use?
Applying Privacy Design Patterns 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 Applying Privacy Design Patterns use?
About 2.9k tokens (SKILL.md is roughly 12k 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 1.6k tokens, read only when the agent opens those files.
What are the alternatives to Applying Privacy Design Patterns?
Skills that share tags, products or a category with Applying Privacy Design Patterns: Privacy Policy Generator Service Entry (nisrulz/app-privacy-policy-generator, 4.7k stars), Vercel Composition Patterns (supabase/supabase, 111k stars), Swiftui View Refactor (Dimillian/Skills, 4k stars) and RTK Rust Design Patterns (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Applying Privacy Design Patterns?
mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 297 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.