
ai-training-lawfulness
Assesses lawful basis for AI training data processing per EDPB April 2025 report on LLMs and general-purpose AI. Covers legitimate interest balancing tests, consent challenges for ML training, public dataset assessment, and web scraping lawfulness. Keywords: AI training data, lawful basis, EDPB LLM, legitimate interest, consent, web scraping.
- Installs
- 45
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/mukul975/privacy-data-protection-skills --skill ai-training-lawfulness- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads ai-training-lawfulness automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Lawful Basis for AI Training Data
Overview
The processing of personal data for AI model training constitutes a distinct processing operation requiring its own lawful basis under GDPR Art. 6(1). The EDPB Guidelines 04/2025 and the coordinated ChatGPT Taskforce findings establish that AI training creates unique lawful basis challenges: the scale of data collection, the difficulty of obtaining meaningful consent for open-ended AI training purposes, the tension between legitimate interest and data subject expectations, and the complexity of determining lawfulness for web-scraped and third-party datasets. This skill provides the comprehensive lawful basis assessment framework for AI training data processing, addressing each Art. 6(1) basis as applied to ML training contexts.
Fundamental Principles
AI Training as Personal Data Processing
The EDPB has confirmed that AI model training constitutes processing of personal data under Art. 4(2) GDPR when:
- Training datasets contain personal data (directly or indirectly identifiable natural persons)
- The model is trained on data that includes personal data, even if the intent is to learn general patterns
- The resulting model retains the capability to generate or reproduce personal data from training sets
- Personal data is used in any pipeline stage: collection, cleaning, annotation, augmentation, validation, testing
The controller cannot avoid GDPR obligations by claiming the model has "learned" rather than "stored" personal data. The processing occurs at the point of training, regardless of whether the model can later reproduce specific records.
Purpose Specification for AI Training
Art. 5(1)(b) requires that personal data be collected for specified, explicit, and legitimate purposes. For AI training, this means:
- "Training an AI model" is insufficiently specific — the controller must articulate the specific capability being developed
- "Improving our services" through AI training must be disaggregated into concrete purposes
- Each purpose must be documented before training begins, not retroactively justified
- The purpose must be communicated to data subjects in privacy notices per Arts. 13-14
Lawful Basis Analysis for AI Training
Art. 6(1)(a) — Consent
Requirements for Valid AI Training Consent
| Requirement | AI Training Application |
|---|---|
| Freely given | Data subjects must have genuine choice; consent cannot be bundled with service access unless AI training is necessary for the service |
| Specific | "AI training" alone is insufficient — must specify what type of model, for what purpose, what data elements are used |
| Informed | Must explain how personal data will be used in training, retention period for training data, risk of model memorization, inability to fully delete data from trained models |
| Unambiguous | Clear affirmative action; pre-ticked boxes or implied consent from terms of service are insufficient |
| Withdrawable | Controller must provide mechanism to withdraw consent; but model already trained on the data presents technical challenge |
Consent Challenges in AI Training
- Granularity problem: AI training often uses all available data — difficult to obtain specific consent for each data element's use in training
- Withdrawal complexity: Once a model is trained on personal data, true erasure requires model retraining or verified machine unlearning
- Purpose evolution: Foundation models and transfer learning mean the model may be repurposed — original consent may not cover downstream uses
- Scale impracticality: Obtaining consent from millions of data subjects whose data appears in web-scraped training corpora is practically impossible
- Power imbalance: When AI service use requires consent to training (e.g., "use our AI assistant and your conversations train our model"), consent may not be freely given
When Consent Works for AI Training
- Users explicitly opt into a research programme where AI model training is a primary purpose
- Users contribute data to a specific AI system with clear disclosure (e.g., "your feedback trains this recommendation engine")
- Fine-tuning on user-provided data where the user understands and consents to the training purpose
Art. 6(1)(b) — Contract Necessity
AI training can rely on contractual necessity only when:
- The AI model training is genuinely necessary for performing the contract with the data subject
- The data subject has entered into a contract that requires AI-powered features
- The training cannot be separated from the service delivery
Limitations per EDPB:
- General improvement of AI systems through aggregate training is not "necessary" for any individual contract
- Training a general-purpose model that benefits future users is not necessary for the current data subject's contract
- Fine-tuning based on individual user interactions may qualify if the personalised model is part of the contracted service
Art. 6(1)(f) — Legitimate Interest
This is the most commonly relied-upon basis for AI training. The EDPB requires a rigorous three-part assessment:
Part 1: Legitimate Interest Identification
The controller must identify a specific, real, and lawful interest:
| Interest Type | Example | EDPB Assessment |
|---|---|---|
| Commercial product improvement | Training a fraud detection model to protect customers | Generally legitimate — concrete benefit to data subjects |
| Research and development | Training models for medical imaging analysis | Legitimate if research purpose is genuine and specific |
| General AI capability | Training a foundation model for general-purpose use | Scrutinised — interest must be articulated with specificity |
| Competitive advantage | Training to match competitor AI capabilities | Legitimate commercial interest but weak in balancing |
Part 2: Necessity Assessment
| Question | Assessment Criteria |
|---|---|
| Is AI training necessary for the identified interest? | Could the interest be pursued without training on personal data? |
| Could anonymised data achieve the same result? | Has the controller tested model performance with anonymised data? |
| Could synthetic data supplement or replace personal data? | Has synthetic data generation been evaluated? |
| Is the volume of personal data proportionate? | Has the minimum effective dataset been determined? |
| Could federated learning avoid centralising personal data? | Has distributed training been assessed? |
Part 3: Balancing Test
Factors weighing in favour of the controller:
- Training data is publicly available (but this alone is not decisive)
- Model serves a beneficial purpose (fraud prevention, medical research)
- Strong technical safeguards applied (differential privacy, access controls)
- Data subjects can exercise opt-out rights effectively
- Training data is pseudonymised before use
Factors weighing in favour of data subjects:
- Data was not collected with AI training in mind — processing is far from original expectations
- Large-scale data collection from diverse sources without data subjects' awareness
- Special category data is present or can be inferred from training data
- Children's data is present in the training corpus
- No practical opt-out mechanism exists
- Model may memorize and regurgitate personal data
- Web scraping bypasses data subjects' choices about data sharing
EDPB Position on Legitimate Interest for AI Training
The EDPB Guidelines 04/2025 establish that:
- Legitimate interest for AI training is not automatically available — it requires case-by-case assessment
- Web scraping of personal data for AI training faces a particularly high bar
- The scale of data collection is a relevant factor — larger datasets require stronger justification
- The controller must demonstrate necessity: evidence that personal data is required rather than anonymised or synthetic alternatives
- Effective opt-out mechanisms are expected as a minimum safeguard
- The balancing test should consider the cumulative impact of multiple AI developers scraping and training on the same data subjects' data
Art. 6(1)(e) — Public Interest
Available to public bodies and organisations performing tasks in the public interest:
- Academic research institutions training AI models for publicly beneficial research
- Government agencies training AI for public service delivery
- Must have a basis in national or Union law
- Proportionality requirements apply
Special Situations
Web-Scraped Data
The EDPB has given specific guidance on web scraping for AI training:
- Robots.txt is not consent: Compliance with robots.txt does not establish lawful basis
- Public availability is not a lawful basis: Data being publicly accessible does not mean it can be freely used for AI training
- Reasonable expectations: Data subjects who post content online do not reasonably expect it to be used for AI training
- Children's data: Web-scraped data likely contains children's data — heightened protections apply
- Technical measures: Data subjects who implement privacy settings have expressed a preference against broad data use
Assessment framework for web-scraped training data:
| Factor | High Lawfulness Indicator | Low Lawfulness Indicator |
|---|---|---|
| Data source | Explicitly open-licence data (CC0, public domain) | Personal profiles, social media, private websites |
| Data type | Factual, non-personal content | Identifiable personal information, photos, opinions |
| Data subject expectations | Data published with intent for wide reuse | Data shared in specific context (social media, forums) |
| Safeguards | Differential privacy, PII filtering pre-training | No preprocessing to remove personal data |
| Opt-out | Effective and accessible opt-out mechanism | No opt-out or technically impractical opt-out |
| Transparency | Privacy notice covers AI training use | No notice to data subjects about AI training |
Third-Party Datasets
When using datasets obtained from third parties:
- Upstream lawful basis verification: The controller must verify that the data provider had a lawful basis to collect and share the data
- Contractual warranties: Obtain warranties from the provider regarding lawful collection, consent scope, and right to license for AI training
- Due diligence: Conduct reasonable due diligence on the provider's data collection practices
- Chain of accountability: The AI developer remains a controller responsible for lawful processing, even if the data was provided by a third party
Public Datasets
Academic and government datasets require assessment:
- Is personal data present? (Many datasets contain inadvertent personal data)
- What was the original purpose of the dataset? Is AI training compatible?
- Does the dataset licence permit commercial AI training?
- Has the dataset been ethically reviewed for consent and privacy?
- Are there known issues (bias, PII leakage, consent gaps)?
Training Data Retention
Art. 5(1)(e) storage limitation applies to AI training data:
- Training data must not be retained longer than necessary for the training purpose
- Once the model is trained, is continued retention of training data justified?
- If training data is retained for retraining, what is the maximum retention period?
- Model artefacts (weights, embeddings) that encode personal data are also subject to retention limits
- Deletion verification: can the controller demonstrate that training data has been effectively deleted?
Data Subject Rights for Training Data
| Right | AI Training Application | Technical Challenge |
|---|---|---|
| Access (Art. 15) | Data subject can request confirmation that their data was used in training and receive a copy | Identifying specific records in large training datasets |
| Rectification (Art. 16) | Inaccurate personal data in training sets must be corrected | Correction may require model retraining |
| Erasure (Art. 17) | Data subjects can request deletion of their data from training sets | Requires machine unlearning or model retraining |
| Objection (Art. 21) | Data subjects can object to processing based on legitimate interest | Controller must cease processing unless compelling grounds override |
| Restriction (Art. 18) | Processing must be restricted while accuracy or objection is contested | May require quarantining data from training pipeline |
Enforcement Precedents
- Garante v. OpenAI (2023): Temporary processing ban — no lawful basis identified for ChatGPT training data. Ordered OpenAI to identify Art. 6(1) basis for training data, implement age verification, and provide opt-out mechanism.
- CNIL v. Clearview AI (SAN-2022-019, 2022): EUR 20M fine — web scraping of biometric data without lawful basis. No consent, legitimate interest balancing test not conducted.
- Datatilsynet (Norway) v. Meta (2023): Temporary ban on using Norwegian user data for AI training — legitimate interest basis not sufficiently documented; balancing test inadequate.
- DPC (Ireland) v. Meta (2024): Investigation into use of public Facebook/Instagram posts for AI training under legitimate interest basis. Meta paused EU AI training following DPC engagement.
- EDPB Taskforce on ChatGPT (2024): Coordinated finding that legitimate interest for LLM training requires comprehensive balancing test, transparency, and effective opt-out — mere assertion of legitimate interest is insufficient.
Integration Points
- ai-dpia: Training data lawfulness feeds into DPIA Phase 2 assessment
- ai-data-subject-rights: Rights exercise mechanisms for training data
- ai-data-retention: Retention and deletion requirements for training datasets
- ai-transparency-reqs: Transparency obligations regarding training data use
FAQ
What does the ai-training-lawfulness skill do?
Assesses lawful basis for AI training data processing per EDPB April 2025 report on LLMs and general-purpose AI. Covers legitimate interest balancing tests, consent challenges for ML training, public dataset assessment, and web scraping lawfulness. Keywords: AI training data, lawful basis, EDPB LLM, legitimate interest, consent, web scraping.
How do I install ai-training-lawfulness?
Run npx skills add https://github.com/mukul975/privacy-data-protection-skills --skill ai-training-lawfulness in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/ai-training-lawfulness/ (personal) or .claude/skills/ai-training-lawfulness/ (project).
Which AI agents can use ai-training-lawfulness?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is ai-training-lawfulness safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains ai-training-lawfulness?
It is published by mukul975 in mukul975/privacy-data-protection-skills. It has 45 recorded installs.
More from mukul975/privacy-data-protection-skills
brazil-lgpd
mukul975/privacy-data-protection-skills
Guides compliance with Brazil's Lei Geral de Proteção de Dados (LGPD, Lei 13.709/2018). Covers the 10 lawful bases under Art. 7, DPO appointment, ANPD enforcement, data subject rights under Arts. 17-22, and international transfer mechanisms. Keywords: LGPD, Brazil data protection, ANPD, lawful bases, data subject rights, international transfers.
analytics-cookie-consent
mukul975/privacy-data-protection-skills
Managing consent for analytics cookies and implementing privacy-preserving measurement. Covers GA4 privacy configuration, consent mode fallback behavior, aggregate reporting alternatives, and cookieless measurement approaches.
audit-report-writing
mukul975/privacy-data-protection-skills
Guides privacy audit report writing including executive summary drafting, findings classification (critical, high, medium, low), evidence referencing, root cause analysis documentation, recommendation formulation, management response tracking, and report distribution protocols. Covers report structure from scope definition through appendices and sign-off. Keywords: audit report, findings documentation, executive summary, recommendations, report structure, privacy audit deliverables.
gdpr-compliance-audit
mukul975/privacy-data-protection-skills
Guides a comprehensive organisational data protection audit against key GDPR requirements including Articles 5, 24, 25, 28, 30, 32, 35, and 37. Includes 50+ control points covering principles, accountability, security, and governance. Activate when performing compliance audits, preparing for supervisory authority inspections, or assessing organisational GDPR maturity. Keywords: data protection audit, compliance audit, GDPR audit, control points, accountability.
conducting-gdpr-dpia
mukul975/privacy-data-protection-skills
Guides the end-to-end GDPR Data Protection Impact Assessment process under Article 35, including mandatory trigger identification per Art. 35(3), DPIA content requirements per Art. 35(7), and EDPB WP248rev.01 methodology. Activate for systematic profiling, large-scale special category processing, or large-scale public monitoring. Keywords: DPIA, Article 35, impact assessment, WP248, data protection, risk assessment.
backup-retention-erasure
mukul975/privacy-data-protection-skills
Manages backup and archive data under retention schedules and erasure obligations. Covers the technical infeasibility exception for backup deletion, backup cycle alignment with retention periods, restore-and-delete procedures, and interim protective measures during backup retention. Activate for backup deletion, archive erasure, backup retention, restore and delete, technical infeasibility queries.
Popular ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available