C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Implements automated data deletion workflows for GDPR Article 17 right to erasure and retention period expiry.
Install Auto Deletion Workflow
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill auto-deletion-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills auto-deletion-workflow --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/auto-deletion-workflow .claude/skills/auto-deletion-workflow && 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 "auto-deletion-workflow" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/auto-deletion-workflow into .claude/skills/auto-deletion-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-deletion-workflow", 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/auto-deletion-workflowType 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 auto-deletion-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills auto-deletion-workflow --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/auto-deletion-workflow .agents/skills/auto-deletion-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "auto-deletion-workflow" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/auto-deletion-workflow into .agents/skills/auto-deletion-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-deletion-workflow", 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 auto-deletion-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills auto-deletion-workflow --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/auto-deletion-workflow .cursor/skills/auto-deletion-workflow && 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 "auto-deletion-workflow" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/auto-deletion-workflow into .cursor/skills/auto-deletion-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-deletion-workflow", 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/auto-deletion-workflow--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 auto-deletion-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills auto-deletion-workflow --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/auto-deletion-workflow .gemini/skills/auto-deletion-workflow && 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 "auto-deletion-workflow" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/auto-deletion-workflow into .gemini/skills/auto-deletion-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-deletion-workflow", 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 auto-deletion-workflowInstalls 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 auto-deletion-workflow -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/auto-deletion-workflow .github/skills/auto-deletion-workflow && 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 "auto-deletion-workflow" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/auto-deletion-workflow into .github/skills/auto-deletion-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-deletion-workflow", 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 auto-deletion-workflow -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 auto-deletion-workflow --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/auto-deletion-workflow .opencode/skills/auto-deletion-workflow && 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 "auto-deletion-workflow" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/auto-deletion-workflow into .opencode/skills/auto-deletion-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-deletion-workflow", 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
auto-deletion-workflow- GitHub stars
- 297
- Token cost
- ~3.9k tokens
- SKILL.md length
- 977 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Implements automated data deletion workflows for GDPR Article 17 right to erasure and retention period expiry.
- Works in 4 steps: Immutability: Deletion confirmation… → Retention of confirmation records: 3… → No personal data in logs: Confirmation… → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Legal Foundation, Automated Deletion Architecture and Deletion Workflow Procedures, plus 4 more sections
- Runs Python scripts from its folder
What it does
Auto Deletion Workflow is an agent skill from mukul975/Privacy-Data-Protection-Skills. Implements automated data deletion workflows for GDPR Article 17 right to erasure and retention period expiry. Covers cascading deletion across dependent systems, dependency handling for referential integrity, confirmation logging, and audit trail generation. Activate for automated deletion, erasure automation, data purge, retention expiry queries.
Its SKILL.md is about 3.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 auto-deletion-workflow skill to implement automated data deletion workflows for GDPR Article 17 right to erasure and retention period expiry”
- “/auto-deletion-workflow”
Requirements
- Python 3
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Immutability: Deletion confirmation records are written to an append-only audit log (write-once storage or blockchain-anchored hash).
- Retention of confirmation records: 3 years from deletion date (sufficient to demonstrate compliance if challenged).
- No personal data in logs: Confirmation records reference data subjects by pseudonymised identifier only — never by name, email, or other…
- Searchability: Records must be searchable by deletion reference, data subject hash, trigger type, system, and date range.
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
Auto Deletion Workflow loads about 3.9k tokens when it runs, and up to ~5.3k if it reads all its reference files. Until then it costs about 93 tokens; SKILL.md has 977 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). 977 words, ~3,929 tokens.
Download SKILL.mdSave it as
.claude/skills/auto-deletion-workflow/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- auto-deletion-workflow
- description
- Implements automated data deletion workflows for GDPR Article 17 right to erasure and retention period expiry. Covers cascading deletion across dependent systems, dependency handling for referential integrity, confirmation logging, and audit trail generation. Activate for automated deletion, erasure automation, data purge, retention expiry queries.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- data-retention-deletion
- metadata.tags
- automated-deletion, right-to-erasure, gdpr-article-17, data-purge, retention-expiry
Automated Data Deletion Workflow
Overview
Automated deletion workflows ensure that personal data is removed from all systems when retention periods expire or when a valid erasure request is received under GDPR Article 17. Manual deletion at scale is error-prone and fails to meet the storage limitation principle consistently. This skill defines the architecture, logic, and operational procedures for building automated deletion pipelines that handle cascading dependencies, maintain referential integrity, produce audit-grade confirmation logs, and satisfy both scheduled retention expiry and on-demand erasure requests.
Legal Foundation
GDPR Article 17(1) — Right to Erasure
The data subject shall have the right to obtain from the controller the erasure of personal data concerning him or her without undue delay, and the controller shall have the obligation to erase personal data without undue delay where one of the specified grounds applies.
GDPR Article 5(1)(e) — Storage Limitation
Personal data shall be kept for no longer than is necessary for the purposes for which the personal data are processed. Automated deletion is the primary technical measure for enforcing this principle at scale.
GDPR Article 25(1) — Data Protection by Design
The controller shall implement appropriate technical and organisational measures designed to implement data-protection principles, such as data minimisation, in an effective manner. Automated deletion is a core by-design control.
GDPR Article 30(1)(f) — Envisaged Time Limits for Erasure
Records of processing activities must include, where possible, the envisaged time limits for erasure of the different categories of data. Automated deletion systems operationalize these envisaged time limits.
Automated Deletion Architecture
Deletion Trigger Types
| Trigger Type | Source | SLA | Priority |
|---|---|---|---|
| Retention expiry | Retention schedule metadata reaching calculated deletion date | Within 30 days of expiry | Standard |
| Data subject erasure request | Verified Art. 17 request via DSAR workflow | Within 30 calendar days of verified request | High |
| Consent withdrawal | Consent management platform event | Within 30 days (best practice: 72 hours) | High |
| Account closure | Customer account termination event | Per retention schedule (post-closure retention period) | Standard |
| Purpose completion | Processing purpose fulfilled, no further legal basis | Within 30 days of purpose completion | Standard |
| Legal hold release | Litigation hold lifted by Legal counsel | Within 14 days of hold release | Standard |
System Architecture
┌─────────────────────────────────────────────────────────────┐
│ DELETION ORCHESTRATOR │
│ ┌──────────────┐ ┌──────────────┐ ┌──────────────────┐ │
│ │ Trigger │ │ Dependency │ │ Execution │ │
│ │ Engine │ │ Resolver │ │ Engine │ │
│ │ │ │ │ │ │ │
│ │ - Scheduled │ │ - FK mapping │ │ - System agents │ │
│ │ - Event-driven│ │ - Cascade │ │ - API calls │ │
│ │ - On-demand │ │ rules │ │ - Direct DB ops │ │
│ │ - Hold check │ │ - Orphan │ │ - File system │ │
│ │ │ │ handling │ │ purge │ │
│ └──────┬───────┘ └──────┬───────┘ └────────┬─────────┘ │
│ │ │ │ │
│ └────────┬────────┘ │ │
│ ▼ │ │
│ ┌──────────────────────────┐ │ │
│ │ Deletion Job Queue │─────────────────┘ │
│ │ (Priority-ordered) │ │
│ └──────────────────────────┘ │
│ │ │
│ ▼ │
│ ┌──────────────────────────┐ ┌──────────────────────────┐ │
│ │ Confirmation Logger │ │ Audit Trail Generator │ │
│ │ - Per-system status │ │ - Immutable audit log │ │
│ │ - Completion timestamp │ │ - Deletion certificate │ │
│ │ - Verification hash │ │ - Regulatory report │ │
│ └──────────────────────────┘ └──────────────────────────┘ │
└─────────────────────────────────────────────────────────────┘Deletion Workflow Procedures
Workflow 1: Scheduled Retention Expiry Deletion
[Daily Retention Scan — 02:00 UTC]
│
▼
[Query all records where calculated_deletion_date <= TODAY + 30 days]
│
▼
[For each record approaching expiry]
│
├── [Check: Active litigation hold?]
│ ├── Yes ──► [Skip — log hold reference, notify Legal]
│ └── No ──► Continue
│
├── [Check: Active regulatory investigation?]
│ ├── Yes ──► [Skip — log investigation reference]
│ └── No ──► Continue
│
├── [Check: Pending data subject request referencing this data?]
│ ├── Yes ──► [Coordinate with DSAR workflow]
│ └── No ──► Continue
│
├── [Check: Retention exception approved?]
│ ├── Yes ──► [Skip — log exception reference and expiry]
│ └── No ──► Continue
│
▼
[Add to deletion job queue with priority: STANDARD]
│
▼
[On calculated_deletion_date: Execute deletion]Workflow 2: On-Demand Erasure Request Deletion
[Verified Art. 17 Erasure Request Received]
│
▼
[Data Discovery — Identify all instances of data subject's data]
│
├── Primary databases (CRM, ERP, HR system)
├── Data warehouse and analytics platforms
├── File storage (SharePoint, network drives, cloud storage)
├── Email and communication systems
├── Backup and archive systems
├── Third-party processor systems
└── Logs and audit trails
│
▼
[Generate Deletion Manifest]
Reference: DEL-YYYY-NNNN
Data Subject: [Pseudonymised reference]
Systems identified: [List with record counts]
Exceptions identified: [Any Art. 17(3) exceptions]
Estimated completion: [Date]
│
▼
[DPO Review and Approval]
├── Approved ──► [Add to deletion job queue with priority: HIGH]
└── Exceptions found ──► [Partial deletion — exclude excepted data]
│
▼
[Execute deletion across all identified systems]Workflow 3: Cascading Deletion Logic
When deleting a primary record, dependent records across related systems must also be deleted. The cascading deletion resolver handles referential integrity:
[Primary Record Identified for Deletion]
│
▼
[Load Dependency Map for Record Type]
│
▼
[Resolve Dependencies — Depth-First Traversal]
│
├── [Level 0: Primary record]
│ Example: Customer record in CRM
│
├── [Level 1: Direct dependents]
│ Example: Orders, support tickets, consent records
│
├── [Level 2: Secondary dependents]
│ Example: Order line items, payment records, shipping records
│
└── [Level 3+: Tertiary dependents]
Example: Invoice line items, refund records
│
▼
[For each dependent record]
│
├── [Shared dependency?]
│ (Record also linked to other primary records not being deleted)
│ ├── Yes ──► [Nullify foreign key — do NOT delete]
│ └── No ──► [Add to deletion manifest]
│
├── [Legal retention override?]
│ (Dependent record has its own statutory retention requirement)
│ ├── Yes ──► [Anonymize link to primary record, retain dependent]
│ └── No ──► [Add to deletion manifest]
│
└── [Aggregated/statistical record?]
(Record contributes to aggregated reporting)
├── Yes ──► [Anonymize — remove personal identifiers, retain aggregate]
└── No ──► [Add to deletion manifest]
│
▼
[Execute deletion in reverse order (deepest dependents first)]
Level 3+ ──► Level 2 ──► Level 1 ──► Level 0Dependency Map Template
The following dependency map is configured for Orion Data Vault Corp:
| Primary Entity | Dependent Entity | Relationship | Deletion Action | Retention Override |
|---|---|---|---|---|
| Customer | Orders | 1:N | Cascade delete (after statutory retention) | 6 years — HMRC |
| Customer | Support Tickets | 1:N | Cascade delete | 3 years — limitation period |
| Customer | Consent Records | 1:N | Cascade delete | Retain suppression record |
| Customer | Marketing Preferences | 1:1 | Cascade delete | Retain opt-out on suppression list |
| Customer | Account Audit Log | 1:N | Anonymize (nullify customer reference) | 7 years — audit retention |
| Order | Order Lines | 1:N | Cascade delete | Follows order retention |
| Order | Payment Records | 1:N | Anonymize | 6 years — financial records |
| Order | Shipping Records | 1:N | Cascade delete | Follows order retention |
| Order | Invoices | 1:N | Anonymize | 6 years — tax records |
| Employee | Payroll Records | 1:N | Cascade delete (after statutory retention) | 6 years — PAYE Regulations |
| Employee | Performance Reviews | 1:N | Cascade delete | Duration of employment + 6 years |
| Employee | Access Logs | 1:N | Anonymize | 2 years — security retention |
Confirmation Logging
Deletion Confirmation Record Structure
Every deletion execution produces an immutable confirmation record:
DELETION CONFIRMATION RECORD — Orion Data Vault Corp
-----------------------------------------------------
Reference: DEL-2026-0142
Trigger: Retention expiry / Art. 17 request / Consent withdrawal
Data Subject Reference: DS-HASH-a3f8c2e1
Request Date: 2026-02-15 (if applicable)
Execution Date: 2026-03-14
Completed Date: 2026-03-14T14:23:07Z
SYSTEMS PROCESSED:
┌─────────────────────────┬──────────┬───────────────┬──────────────────┐
│ System │ Records │ Action │ Status │
├─────────────────────────┼──────────┼───────────────┼──────────────────┤
│ CRM (Salesforce) │ 1 │ Hard delete │ Confirmed │
│ ERP (SAP) │ 47 │ Hard delete │ Confirmed │
│ Data Warehouse (BQ) │ 312 │ Hard delete │ Confirmed │
│ Email (Exchange) │ 23 │ Hard delete │ Confirmed │
│ File Storage (S3) │ 8 │ Hard delete │ Confirmed │
│ Backup (Veeam) │ N/A │ Flagged │ Pending (cycle) │
│ Analytics (Mixpanel) │ 156 │ Hard delete │ Confirmed │
│ Support (Zendesk) │ 12 │ Hard delete │ Confirmed │
│ Audit Log │ 89 │ Anonymized │ Confirmed │
│ Payment (Stripe) │ 5 │ Anonymized │ Confirmed │
└─────────────────────────┴──────────┴───────────────┴──────────────────┘
THIRD-PARTY NOTIFICATIONS (Art. 19):
- Processor A (Analytics SaaS): Notified 2026-03-14, confirmed 2026-03-16
- Processor B (Email service): Notified 2026-03-14, confirmed 2026-03-15
- Processor C (Payment gateway): Notified 2026-03-14, pending
EXCEPTIONS APPLIED:
- Financial records (invoices): Anonymized, retained until 2032-03-14 (6-year statutory period)
- Audit log entries: Anonymized, retained until 2033-03-14 (7-year audit retention)
BACKUP DELETION:
- Backup system: Next full rotation cycle completes 2026-06-12
- Expected complete erasure from backups: 2026-06-12
VERIFICATION:
- Post-deletion scan completed: 2026-03-14T14:45:00Z
- Residual data found: None
- Verification hash: SHA-256:e3b0c44298fc1c149afbf4c8996fb924...
Executed by: Deletion Orchestrator v3.2 (automated)
Reviewed by: [DPO Name] (for Art. 17 requests only)Show full SKILL.md (424 more words)Show less
Audit Trail Requirements
- Immutability: Deletion confirmation records are written to an append-only audit log (write-once storage or blockchain-anchored hash).
- Retention of confirmation records: 3 years from deletion date (sufficient to demonstrate compliance if challenged).
- No personal data in logs: Confirmation records reference data subjects by pseudonymised identifier only — never by name, email, or other direct identifier.
- Searchability: Records must be searchable by deletion reference, data subject hash, trigger type, system, and date range.
Error Handling and Retry Logic
Deletion Failure Handling
| Failure Type | Action | Retry | Escalation |
|---|---|---|---|
| System unavailable | Queue for retry | 3 attempts at 1h, 4h, 24h intervals | Alert IT Operations after 3 failures |
| Permission denied | Log error, flag for manual review | No automatic retry | Escalate to system administrator |
| Referential integrity violation | Route to dependency resolver | Re-resolve dependencies, retry | Escalate to DPO if unresolvable |
| Partial deletion (some records failed) | Log successful deletions, retry failed | 3 attempts | Escalate to IT + DPO |
| Third-party processor non-response | Send reminder at 7 days | Follow up at 14 days | Escalate to DPO + Legal at 21 days |
| Backup system — cannot delete from active backup | Flag for next rotation cycle | Monitor backup rotation schedule | Alert if not completed within 90 days |
Rollback Considerations
Deletion is inherently irreversible. Therefore:
- Pre-deletion snapshot: For Art. 17 requests, take a temporary encrypted snapshot of the data to be deleted. Retain for 72 hours after deletion execution to allow for error correction. Auto-destroy after 72 hours.
- Staged execution: For large-scale retention expiry deletions (>10,000 records), execute in batches of 1,000 with verification between batches.
- Dry-run mode: All new deletion rules must be tested in dry-run mode for 30 days before activation. Dry-run produces the deletion manifest and confirmation record without executing actual deletion.
Monitoring and Reporting
Key Metrics
| Metric | Target | Measurement |
|---|---|---|
| Retention expiry deletion completion rate | 99.5% within 30 days of expiry | Monthly |
| Art. 17 erasure request completion rate | 100% within 30 calendar days | Per request |
| Average deletion execution time | < 4 hours (end-to-end across all systems) | Per execution |
| Failed deletion rate | < 0.5% | Monthly |
| Backup deletion completion rate | 100% within backup rotation cycle | Per rotation |
| Third-party processor confirmation rate | 100% within 14 days | Per notification |
Quarterly Compliance Report
The automated deletion system generates a quarterly report containing:
- Total records deleted by trigger type (retention expiry, Art. 17, consent withdrawal, etc.)
- Deletion completion rates against SLA targets
- Exceptions applied (with legal basis breakdown)
- Failed deletions and resolution status
- Third-party processor compliance rates
- Backup deletion status and outstanding items
- Trend analysis (volume growth, system coverage, performance)
© 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/auto-deletion-workflow 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
Auto Deletion Workflow 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 |
|---|---|---|---|---|---|---|
| Auto Deletion Workflow this skillmukul975/Privacy-Data-Protection-Skills | 297 | — | ~3.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 | 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 |
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 Auto Deletion Workflow
What does Auto Deletion Workflow do?
Implements automated data deletion workflows for GDPR Article 17 right to erasure and retention period expiry. Auto Deletion Workflow is an agent skill from mukul975/Privacy-Data-Protection-Skills. Implements automated data deletion workflows for GDPR Article 17 right to erasure and retention period expiry.
When should I use Auto Deletion Workflow?
Auto Deletion Workflow fits situations like: tasks that involve Privacy and GDPR.
How do I install Auto Deletion Workflow in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill auto-deletion-workflow -a claude-code`. Or copy the skill folder (skills/privacy/auto-deletion-workflow in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/auto-deletion-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Auto Deletion Workflow in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill auto-deletion-workflow -a codex`. Or copy the skill folder (skills/privacy/auto-deletion-workflow in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/auto-deletion-workflow in your project. Codex loads it when a task matches its description.
Can I use Auto Deletion Workflow 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 auto-deletion-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/auto-deletion-workflow, .gemini/skills/auto-deletion-workflow, .github/skills/auto-deletion-workflow and .opencode/skills/auto-deletion-workflow in your project.
What does Auto Deletion Workflow need to run?
Going by SKILL.md and its folder, Auto Deletion Workflow needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Auto Deletion Workflow 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 Auto Deletion Workflow 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 Auto Deletion Workflow use?
Auto Deletion Workflow 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 Auto Deletion Workflow use?
About 3.9k tokens (SKILL.md is roughly 16k 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.3k tokens, read only when the agent opens those files.
What are the alternatives to Auto Deletion Workflow?
Skills that share tags, products or a category with Auto Deletion Workflow: 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.
Who maintains Auto Deletion Workflow?
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.