C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Vendor termination data return and deletion procedures per GDPR Article 28(3)(g).
Install Vendor Termination Data
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill vendor-termination-data -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills vendor-termination-data --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/vendor-termination-data .claude/skills/vendor-termination-data && 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 "vendor-termination-data" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/vendor-termination-data into .claude/skills/vendor-termination-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-termination-data", 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/vendor-termination-dataType 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 vendor-termination-data -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills vendor-termination-data --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/vendor-termination-data .agents/skills/vendor-termination-data && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vendor-termination-data" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/vendor-termination-data into .agents/skills/vendor-termination-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-termination-data", 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 vendor-termination-data -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills vendor-termination-data --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/vendor-termination-data .cursor/skills/vendor-termination-data && 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 "vendor-termination-data" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/vendor-termination-data into .cursor/skills/vendor-termination-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-termination-data", 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/vendor-termination-data--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 vendor-termination-data -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills vendor-termination-data --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/vendor-termination-data .gemini/skills/vendor-termination-data && 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 "vendor-termination-data" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/vendor-termination-data into .gemini/skills/vendor-termination-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-termination-data", 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 vendor-termination-dataInstalls 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 vendor-termination-data -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/vendor-termination-data .github/skills/vendor-termination-data && 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 "vendor-termination-data" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/vendor-termination-data into .github/skills/vendor-termination-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-termination-data", 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 vendor-termination-data -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 vendor-termination-data --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/vendor-termination-data .opencode/skills/vendor-termination-data && 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 "vendor-termination-data" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/vendor-termination-data into .opencode/skills/vendor-termination-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-termination-data", 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
vendor-termination-data- GitHub stars
- 297
- Token cost
- ~2.3k tokens
- SKILL.md length
- 988 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Vendor termination data return and deletion procedures per GDPR Article 28(3)(g).
- Works in 3 steps: Data Inventory and Mapping → Data Export Format and Method → Data Validation
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Termination Triggers, Data Return Process and Data Deletion Process, plus 3 more sections
- Runs Python scripts from its folder
What it does
Vendor Termination Data is an agent skill from mukul975/Privacy-Data-Protection-Skills. Vendor termination data return and deletion procedures per GDPR Article 28(3)(g). Covers data extraction formats, deletion certification requirements, transition planning, residual data handling, and post-termination verification.
Its SKILL.md is about 2.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.
When your agent uses it
- Tasks that involve Privacy and GDPR
Example prompts
- “/vendor-termination-data”
Requirements
- Python 3
Workflow steps
3 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
Vendor Termination Data loads about 2.3k tokens when it runs, and up to ~4.4k if it reads all its reference files. Until then it costs about 64 tokens; SKILL.md has 988 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). 988 words, ~2,282 tokens.
Download SKILL.mdSave it as
.claude/skills/vendor-termination-data/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- vendor-termination-data
- description
- Vendor termination data return and deletion procedures per GDPR Article 28(3)(g). Covers data extraction formats, deletion certification requirements, transition planning, residual data handling, and post-termination verification.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- vendor-privacy-management
- metadata.tags
- vendor-termination, data-return, deletion-certification, art-28-termination, data-portability
Vendor Termination Data Return and Deletion
Overview
GDPR Article 28(3)(g) requires that at the choice of the controller, the processor shall "delete or return all the personal data to the controller after the end of the provision of services relating to processing, and delete existing copies unless Union or Member State law requires storage of the personal data." This termination obligation ensures that personal data does not persist at a former processor beyond the legitimate processing period.
The EDPB Guidelines 07/2020 (paragraph 108) emphasize that this obligation extends to all copies, backups, and derived data — not just production data. The deletion must be verifiable, and the controller should obtain written certification.
At Summit Cloud Partners, the Vendor Termination Data Protocol provides a structured process for managing data return and deletion when vendor relationships end.
Termination Triggers
| Trigger | Description | Timeline Considerations |
|---|---|---|
| Contract expiry (non-renewal) | MSA/DPA term ends without renewal | 90-day notice per DPA |
| Termination for convenience | Controller elects to terminate | Per MSA notice period |
| Termination for cause | Material DPA breach by processor | Immediate or per cure period |
| Service migration | Controller moves to alternative provider | Overlap period for data migration |
| Vendor insolvency | Processor enters insolvency proceedings | Emergency data retrieval |
| Regulatory order | Supervisory authority orders cessation | Per order timeline |
Data Return Process
Step 1: Data Inventory and Mapping
Before initiating return, confirm the complete scope of personal data held by the processor:
| Data Category | Location | Format | Volume | Retention Basis |
|---|---|---|---|---|
| Production data | Primary database | Structured (SQL/JSON) | [Volume] | DPA processing |
| Backup data | Backup storage | Encrypted backup files | [Volume] | Business continuity per DPA |
| Log data | Log storage | Semi-structured (JSON/text) | [Volume] | Security monitoring |
| Derived/aggregated data | Analytics system | Structured | [Volume] | Processing output |
| Metadata | Various systems | Structured | [Volume] | System operation |
| Cached data | CDN/cache layers | Various | [Volume] | Performance |
Step 2: Data Export Format and Method
Standard Export Formats:
| Data Type | Preferred Format | Alternative Format | Notes |
|---|---|---|---|
| Structured data | CSV with defined schema | JSON, XML, Parquet | UTF-8 encoding required |
| Documents | Original format (PDF, DOCX) | ZIP archive | Preserve directory structure |
| Images/media | Original format (PNG, JPEG) | ZIP archive | Preserve metadata |
| Logs | JSON lines (JSONL) | CSV | Include timestamps |
| API-accessible data | Direct API extraction | Bulk export endpoint | Paginated if large |
Export Methods:
| Method | When to Use | Security Requirements |
|---|---|---|
| Encrypted file transfer (SFTP) | Large datasets | TLS 1.2+, PGP encryption |
| Secure API extraction | Structured, API-accessible data | OAuth 2.0, TLS 1.3 |
| Encrypted portable media | Very large datasets without bandwidth | AES-256 encryption, tracked courier |
| Cloud-to-cloud migration | Cloud provider transition | Encrypted transfer, access audit |
Step 3: Data Validation
Upon receiving returned data, Summit Cloud Partners validates:
| Validation Check | Method | Pass Criteria |
|---|---|---|
| Completeness | Record count comparison | Returned count matches source count |
| Integrity | Checksum verification (SHA-256) | Checksums match vendor-provided manifest |
| Format compliance | Schema validation | All fields present per agreed schema |
| Encoding | Character encoding verification | UTF-8 without corruption |
| Sample verification | Random sample manual review | Data content matches expectations |
Data Deletion Process
Deletion Scope
The processor must delete ALL copies of personal data, including:
- Production data — Primary databases and data stores
- Backup data — All backup copies including off-site backups
- Disaster recovery copies — DR site data
- Log data — Application logs, access logs, audit logs containing personal data
- Cached data — CDN caches, application caches, database caches
- Derived data — Analytics outputs, aggregated data containing personal data
- Metadata — System metadata referencing personal data
- Archived data — Any archived copies
- Sub-processor data — Data at all sub-processors
Show full SKILL.md (434 more words)Show less
Deletion Methods
| Data Location | Deletion Method | Verification |
|---|---|---|
| Databases (SQL) | DELETE + VACUUM or DROP TABLE | Query confirmation; storage analysis |
| Object storage (S3/Blob) | Delete all objects + bucket | Bucket listing verification |
| File systems | Secure overwrite (NIST 800-88) | Disk analysis confirmation |
| SSD/Flash storage | Crypto-erase (destroy encryption key) | Vendor attestation |
| Backup tapes | Degaussing or physical destruction | Destruction certificate |
| Application caches | Cache flush + TTL expiry confirmation | Application verification |
| Log systems | Targeted log deletion or retention expiry | Log query confirmation |
| Sub-processors | Cascade deletion instruction | Sub-processor deletion certificate |
Deletion Timeline
| Phase | Activity | DPA Standard Timeline |
|---|---|---|
| T+0 | Controller elects deletion (or return + deletion) | Upon termination notice |
| T+0 to T+30 | Data return completed (if return elected) | 30 calendar days |
| T+30 to T+60 | Production data deletion | 60 calendar days from termination |
| T+60 to T+90 | Backup and archive deletion | 90 calendar days from termination |
| T+90 | Deletion certification issued | 90 calendar days from termination |
Deletion Exceptions
Article 28(3)(g) permits continued storage where "Union or Member State law requires storage of the personal data." Exceptions must be:
| Requirement | Processor Action |
|---|---|
| Documented in writing | Processor identifies specific legal requirement |
| Limited to required data | Only data subject to legal retention requirement |
| Isolated from production | Retained data moved to restricted storage |
| Time-limited | Retained only for legally required duration |
| Notified to controller | Controller informed of retention and legal basis |
Deletion Certification
The processor must provide a written deletion certification containing:
| Field | Content |
|---|---|
| Certifying party | Name and title of authorized processor representative |
| Controller name | Summit Cloud Partners |
| DPA reference | Reference to terminated DPA |
| Deletion scope | Description of all data deleted (categories, locations, formats) |
| Deletion date(s) | Date each deletion action was completed |
| Deletion method(s) | Technical method used for each data location |
| Sub-processor deletion | Confirmation that all sub-processors have also deleted data |
| Exceptions | Any data retained under legal obligation (with legal basis citation) |
| Certification date | Date of certification |
| Signature | Authorized officer signature |
Transition Planning
For service migrations, a transition plan ensures continuity while managing data protection obligations:
| Phase | Activity | Duration |
|---|---|---|
| Planning | Define data migration scope, format, timeline | 4-6 weeks |
| Parallel operation | Old and new vendor operate simultaneously | 2-4 weeks |
| Migration | Data transferred from old to new vendor | 1-2 weeks |
| Validation | Verify complete and accurate migration | 1 week |
| Cutover | Switch production to new vendor | 1 day |
| Decommission | Terminate old vendor; initiate deletion | Per DPA timeline |
| Deletion verification | Confirm old vendor data deletion | 90 days |
Key Regulatory References
- GDPR Article 28(3)(g) — Deletion or return of personal data upon termination
- GDPR Article 17 — Right to erasure (informs deletion standards)
- GDPR Article 5(1)(e) — Storage limitation principle
- EDPB Guidelines 07/2020 — Paragraph 108 on termination data obligations
- NIST SP 800-88 Rev. 1 — Guidelines for Media Sanitization
- ISO/IEC 27001:2022 — A.8.10 Information deletion
© 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/vendor-termination-data 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
Vendor Termination Data 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 |
|---|---|---|---|---|---|---|
| Vendor Termination Data this skillmukul975/Privacy-Data-Protection-Skills | 297 | — | ~2.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 |
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 Vendor Termination Data
What does Vendor Termination Data do?
Vendor termination data return and deletion procedures per GDPR Article 28(3)(g). Vendor Termination Data is an agent skill from mukul975/Privacy-Data-Protection-Skills. Vendor termination data return and deletion procedures per GDPR Article 28(3)(g).
When should I use Vendor Termination Data?
Vendor Termination Data fits situations like: tasks that involve Privacy and GDPR.
How do I install Vendor Termination Data in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill vendor-termination-data -a claude-code`. Or copy the skill folder (skills/privacy/vendor-termination-data in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/vendor-termination-data in your project. Claude Code loads it when a task matches its description.
How do I install Vendor Termination Data in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill vendor-termination-data -a codex`. Or copy the skill folder (skills/privacy/vendor-termination-data in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/vendor-termination-data in your project. Codex loads it when a task matches its description.
Can I use Vendor Termination Data 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 vendor-termination-data -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vendor-termination-data, .gemini/skills/vendor-termination-data, .github/skills/vendor-termination-data and .opencode/skills/vendor-termination-data in your project.
What does Vendor Termination Data need to run?
Going by SKILL.md and its folder, Vendor Termination Data needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Vendor Termination Data 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 Vendor Termination Data 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 Vendor Termination Data use?
Vendor Termination Data 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 Vendor Termination Data use?
About 2.3k tokens (SKILL.md is roughly 9.1k 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 2.1k tokens, read only when the agent opens those files.
What are the alternatives to Vendor Termination Data?
Skills that share tags, products or a category with Vendor Termination Data: 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 Vendor Termination Data?
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.