C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Implements the right to be forgotten in search engines under GDPR Article 17 and the CJEU Google Spain ruling (C-131/12).
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill search-engine-erasure -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills search-engine-erasure --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/search-engine-erasure .claude/skills/search-engine-erasure && 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 "search-engine-erasure" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/search-engine-erasure into .claude/skills/search-engine-erasure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search-engine-erasure", 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/search-engine-erasureType 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 search-engine-erasure -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills search-engine-erasure --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/search-engine-erasure .agents/skills/search-engine-erasure && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "search-engine-erasure" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/search-engine-erasure into .agents/skills/search-engine-erasure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search-engine-erasure", 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 search-engine-erasure -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills search-engine-erasure --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/search-engine-erasure .cursor/skills/search-engine-erasure && 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 "search-engine-erasure" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/search-engine-erasure into .cursor/skills/search-engine-erasure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search-engine-erasure", 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/search-engine-erasure--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 search-engine-erasure -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills search-engine-erasure --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/search-engine-erasure .gemini/skills/search-engine-erasure && 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 "search-engine-erasure" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/search-engine-erasure into .gemini/skills/search-engine-erasure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search-engine-erasure", 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 search-engine-erasureInstalls 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 search-engine-erasure -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/search-engine-erasure .github/skills/search-engine-erasure && 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 "search-engine-erasure" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/search-engine-erasure into .github/skills/search-engine-erasure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search-engine-erasure", 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 search-engine-erasure -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 search-engine-erasure --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/search-engine-erasure .opencode/skills/search-engine-erasure && 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 "search-engine-erasure" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/search-engine-erasure into .opencode/skills/search-engine-erasure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search-engine-erasure", 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.
search-engine-erasureImplements the right to be forgotten in search engines under GDPR Article 17 and the CJEU Google Spain ruling (C-131/12).
Search Engine Erasure is an agent skill from mukul975/Privacy-Data-Protection-Skills. Implements the right to be forgotten in search engines under GDPR Article 17 and the CJEU Google Spain ruling (C-131/12). Covers delisting request procedures, criteria assessment balancing privacy against public interest, and geographic scope determination. Activate for right to be forgotten, search delisting, Google Spain, de-indexing queries.
Its SKILL.md is about 3.3k 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.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 9b2ef9e. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Search Engine Erasure loads about 3.3k tokens when it runs, and up to ~4.9k if it reads all its reference files. Until then it costs about 92 tokens; SKILL.md has 1,371 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.
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.
The full file from mukul975/Privacy-Data-Protection-Skills at commit 9b2ef9e, republished under its Apache-2.0 licence (© mukul975). 1,371 words, ~3,348 tokens.
.claude/skills/search-engine-erasure/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.The right to be forgotten in the search engine context refers to the right of individuals to request that search engine operators delist (remove from search results) links to web pages containing personal data about them. This right was established by the CJEU in Google Spain SL v AEPD (Case C-131/12) and subsequently codified in GDPR Article 17. It requires a balancing exercise between the data subject's privacy rights and the public's right to access information. This skill provides the assessment criteria, request procedures, and operational workflows for both data controllers (whose content may be subject to delisting) and organizations assisting data subjects with delisting requests.
The Court of Justice of the European Union held that:
The Court clarified the territorial scope of de-indexing:
Article 17(1) establishes six grounds for erasure. In the search engine context, the most commonly invoked grounds are:
Article 17(3) establishes exceptions, particularly:
Adopted 7 July 2020, these guidelines provide 13 criteria for assessing delisting requests.
The following criteria must be evaluated when assessing a delisting request. The assessment is a balancing exercise — no single criterion is determinative:
| # | Criterion | Assessment Question | Weight Factors |
|---|---|---|---|
| 1 | Role in public life | Does the data subject play a role in public life? | Public figures (politicians, senior executives, public officials) have reduced expectation of delisting for information related to their public role |
| 2 | Nature of information | What type of personal data is involved? | Special category data (Art. 9) weighs heavily toward delisting; criminal conviction data requires careful balancing |
| 3 | Accuracy of information | Is the information accurate and up-to-date? | Inaccurate information strongly favours delisting |
| 4 | Relevance | Is the information still relevant to the public interest? | Information that was once relevant may become irrelevant over time |
| 5 | Age of information | How old is the information? | Older information generally weighs toward delisting, unless there is a continuing public interest |
| 6 | Source of information | Who published the original content? | Journalistic sources and official government publications weigh against delisting |
| 7 | Context of publication | Was the information published voluntarily by the data subject? | Self-published information may weigh against delisting |
| 8 | Sensitivity | How sensitive is the information? | Health data, sexual orientation, political opinions — higher sensitivity favours delisting |
| 9 | Impact on data subject | What impact does continued indexing have? | Significant harm (employment, reputation, safety) favours delisting |
| 10 | Access context | What is the context in which users access the information via search? | Name-based searches are more intrusive than topic-based searches |
| 11 | Minor | Is the data subject a minor (or was the data published when they were a minor)? | GDPR Recital 65: data subjects who were children at the time have a strengthened right to erasure |
| 12 | Criminal data | Does the information relate to criminal proceedings? | Spent convictions favour delisting; ongoing proceedings may not; national rehabilitation legislation applies |
| 13 | Legal obligation | Is there a legal obligation to index the information? | Court orders, regulatory requirements to maintain public registers |
[Delisting Request Received]
│
▼
[Preliminary Assessment]
│
├── Is the data subject identifiable from the search results? ──► No ──► Reject (no personal data at issue)
│
├── Is the request against a search engine operator? ──► No ──► Redirect to content publisher (separate Art. 17 request)
│
└── Yes to both ──► [Full EDPB 13-Point Assessment]
│
▼
[Apply Balancing Test]
│
├── STRONG DELISTING CASE:
│ - Data subject is a private individual
│ - Information is inaccurate or outdated
│ - Information is sensitive (Art. 9 categories)
│ - Data subject was a minor when information published
│ - Significant demonstrable harm from continued indexing
│ - Information was not self-published
│ ──► APPROVE delisting
│
├── STRONG REFUSAL CASE:
│ - Data subject is a prominent public figure
│ - Information relates to their public role
│ - Information is accurate and current
│ - Strong public interest in access to the information
│ - Information published by journalistic source
│ - Legal obligation to maintain the information
│ ──► REFUSE delisting (cite specific public interest justification)
│
└── BORDERLINE CASE:
- Mixed factors present
──► [Detailed written balancing assessment required]
──► [Consider partial delisting or time-limited delisting]
──► [Consult DPO and Legal counsel]Each major search engine maintains a dedicated form for delisting requests:
DELISTING REQUEST — SEARCH ENGINE
Organization Support Reference: DELIST-YYYY-NNNN
Data Subject: [Name]
Search Engine: [Google / Bing / Other]
Date of Request: [YYYY-MM-DD]
URLs REQUESTED FOR DELISTING:
1. [Full URL] — Reason: [Specific reason per EDPB criteria]
2. [Full URL] — Reason: [Specific reason per EDPB criteria]
GROUNDS FOR DELISTING (cite applicable Art. 17(1) ground):
□ Art. 17(1)(a) — Data no longer necessary for original purpose
□ Art. 17(1)(c) — Data subject objects; no overriding legitimate grounds
□ Art. 17(1)(d) — Unlawful processing
□ Other: [specify]
SUPPORTING INFORMATION:
- Relationship to Orion Data Vault Corp: [employee/customer/former employee/other]
- Nature of information: [describe what the search results reveal]
- Impact of continued indexing: [describe harm]
- Age of information: [when was the content published?]
- Public role: [any public-facing role that may be relevant?]
- Previous attempts to resolve: [contact with content publisher?]
IDENTITY VERIFICATION:
- [Attach government-issued ID — to be submitted to search engine only]
- [Orion Data Vault Corp can verify employment/customer relationship if needed]| Response | Action |
|---|---|
| Delisting approved | Verify URLs no longer appear in name-based searches from EU locations; log outcome; notify data subject |
| Delisting refused | Review reasoning; assess whether to escalate; advise data subject of right to complain to DPA |
| Partial delisting | Review which URLs were accepted/refused; assess remaining URLs; advise data subject |
| Request for more information | Provide requested information within 14 days |
| No response (6+ months) | Escalate: lodge complaint with relevant DPA |
If a search engine refuses a delisting request, the data subject may complain to the supervisory authority:
Following C-507/17 (Google v CNIL), delisting must be implemented on:
The search engine must implement measures to prevent EU/EEA users from circumventing delisting:
In exceptional circumstances, a DPA or national court may order global delisting. This remains controversial and is assessed case-by-case. Factors favouring global scope include:
Delisting from search results does NOT remove the original content from the source website. For complete erasure:
| Record | Retention Period | Purpose |
|---|---|---|
| Delisting request and assessment | 3 years from final outcome | Demonstrate compliance with Art. 17 |
| Search engine correspondence | 3 years from final outcome | Evidence of due diligence |
| DPA complaint (if any) | 6 years from final outcome | Legal records |
| Balancing assessment documentation | 3 years from final outcome | Demonstrate EDPB criteria application |
| Outcome verification (screenshots) | 1 year from delisting confirmation | Verify ongoing effectiveness |
© 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
SKILL.md and 4 other files (scripts, references, assets) in skills/privacy/search-engine-erasure of mukul975/Privacy-Data-Protection-Skills.
Open the folder on GitHubat commit 9b2ef9e
Search Engine Erasure 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 |
|---|---|---|---|---|---|---|
| Search Engine Erasure this skillmukul975/Privacy-Data-Protection-Skills | 297 | — | ~3.3k | 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 | 586 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Gdpr ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 943 | 1 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 943 | 1 repos | ~2.3k | Automated safety check: Pass | MIT |
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
maziyarpanahi/openmed
Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.
kimlawtech/korean-privacy-terms
처리방침·이용약관 자동 생성 스킬 패키지 (v4.0). An agent skill from kimlawtech/korean-privacy-terms.
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…
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
gregmos/PII-Shield
Universal legal document processor with PII anonymization. An agent skill from gregmos/PII-Shield.
mukul975/Privacy-Data-Protection-Skills
Implements age-gating mechanisms for online services to restrict access based on user age.
mukul975/Privacy-Data-Protection-Skills
Manages AI model retention and machine unlearning requirements.
mukul975/Privacy-Data-Protection-Skills
Conducts Data Protection Impact Assessments for AI and ML systems per EDPB Guidelines 04/2025 on AI processing.
mukul975/Privacy-Data-Protection-Skills
Structures risk mitigation planning and residual risk tracking for Data Protection Impact Assessments under GDPR Article 35(7)(d).
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.
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.
Categories
Implements the right to be forgotten in search engines under GDPR Article 17 and the CJEU Google Spain ruling (C-131/12). Search Engine Erasure is an agent skill from mukul975/Privacy-Data-Protection-Skills. Implements the right to be forgotten in search engines under GDPR Article 17 and the CJEU Google Spain ruling (C-131/12).
Search Engine Erasure fits situations like: tasks that involve Privacy and GDPR.
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill search-engine-erasure -a claude-code`. Or copy the skill folder (skills/privacy/search-engine-erasure in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/search-engine-erasure in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill search-engine-erasure -a codex`. Or copy the skill folder (skills/privacy/search-engine-erasure in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/search-engine-erasure in your project. Codex loads it when a task matches its description.
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 search-engine-erasure -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/search-engine-erasure, .gemini/skills/search-engine-erasure, .github/skills/search-engine-erasure and .opencode/skills/search-engine-erasure in your project.
Going by SKILL.md and its folder, Search Engine Erasure needs Python for the scripts in its folder. Our summary lists: Python 3.
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.
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.
Search Engine Erasure 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.
About 3.3k tokens (SKILL.md is roughly 13k 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.5k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Search Engine Erasure: C15t (c15t/c15t, 1.9k stars), HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars), Korean Privacy Terms (kimlawtech/korean-privacy-terms, 586 stars) and Gdpr Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 943 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.