Claude Skills Guide

GDPR Data Privacy Implementation Checklist for Claude Code

Implementing GDPR compliance in software projects requires systematic attention to data handling, user consent, and privacy controls. Claude Code provides capabilities that help developers build privacy-conscious applications, though ultimate compliance responsibility rests with the development team. This checklist covers practical steps for integrating data privacy protections into your workflow using Claude Code and its ecosystem of skills.

Foundation: Understand Data Flow Before Coding

Before writing any code, map how personal data moves through your system. Document what data you collect, where it travels, who accesses it, and how long you retain it. The supermemory skill helps maintain persistent context across sessions, allowing you to build a comprehensive data inventory that persists throughout the project lifecycle.

Create a simple data flow document:

## User Data Inventory
| Data Type | Source | Storage | Access | Retention |
|-----------|--------|---------|--------|-----------|
| Email     | Signup | DB      | Admin  | Until deletion request |
| IP Address| Server | Logs    | DevOps | 30 days |

This inventory becomes your reference point for implementing specific privacy controls

Skill Selection for Privacy-Conscious Development

Certain Claude skills directly support GDPR implementation. The pdf skill enables automated processing of data subject access requests by extracting relevant information from document repositories. The xlsx skill helps generate compliance reports and data export files required for user data portability requests.

For frontend implementations, the frontend-design skill incorporates accessibility considerations that intersect with privacy requirements—ensuring users can understand and control their data through properly labeled forms and clear consent mechanisms.

The tdd skill supports test-driven development of privacy features, allowing you to write acceptance tests for consent flows, data deletion routines, and access control before implementation begins.

Every piece of personal data collection requires explicit consent. Build consent management into your initial architecture rather than retrofitting it later.

/tdd Create tests for consent state: user cannot be tracked before accepting cookies, consent state persists across sessions, user can withdraw consent at any time

This test-first approach ensures your consent system functions correctly from day one. Store consent records with timestamps and version numbers—if your privacy policy changes, you can demonstrate what users agreed to.

Data Minimization: Collect Only What You Need

GDPR’s data minimization principle requires collecting only information necessary for your specified purpose. Review every field in your data collection forms.

Ask these questions for each data point:

The frontend-design skill can help create forms that use progressive disclosure—showing optional fields only when relevant rather than presenting everything at once.

Build Data Access and Deletion Capabilities

Users must be able to access their data and request deletion. Implement these capabilities early:

// Example: Data access endpoint
app.get('/api/user/data', authenticate, async (req, res) => {
  const userData = await db.users.findById(req.user.id);
  const userActivity = await db.activity.find({ userId: req.user.id });
  
  res.json({
    profile: userData,
    activity: userActivity,
    exports: await db.exports.find({ userId: req.user.id })
  });
});

// Example: Data deletion endpoint
app.delete('/api/user/data', authenticate, async (req, res) => {
  await db.users.softDelete(req.user.id);
  await db.activity.deleteMany({ userId: req.user.id });
  // Handle cascading deletions per your data model
});

The pdf skill can automate generating user data exports in standard formats, making portability requests straightforward to fulfill.

Secure Data Transmission and Storage

Implement encryption for data in transit (TLS) and at rest. Use environment variables for sensitive configuration:

# Never commit these to version control
DATABASE_URL=postgresql://user:password@host/db
ENCRYPTION_KEY=your-256-bit-key

Claude Code can help you configure CI/CD pipeline checks for exposed secrets. Add a pre-commit hook that scans staged files for patterns like private keys or API tokens before they reach production.

Document Your Compliance Journey

Maintain records demonstrating your privacy compliance efforts. This includes:

Use version control to maintain an auditable history of privacy-related decisions. Each change to data handling should include a commit message explaining the privacy rationale.

Regular Privacy Reviews

Schedule periodic reviews of your data handling:

Automate retention enforcement where possible—delete user data automatically after the retention period expires rather than relying on manual processes.

Summary Checklist

Building privacy into your development process from the start costs less than retrofitting compliance later. Claude Code skills provide practical assistance, but the discipline of systematic privacy implementation comes from your development practices.


Built by theluckystrike — More at zovo.one