ToolypetMCP
advanced6 minutescross hub

Data Privacy & Compliance Kit

Implement data privacy: encrypt PII, hash identifiers, generate secure tokens, and configure privacy-respecting headers.

privacygdprencryptioncompliancepii

Cuándo usar esta receta

GDPR, CCPA, and HIPAA compliance requires encryption, pseudonymization, and access control for personal data. This workflow sets up the technical foundations.

Pasos

1

Encrypt PII at rest

Indicación:Encrypt PII data: email address 'user@example.com' with AES-256 for GDPR-compliant storage
2

Pseudonymize identifiers

Indicación:Hash user identifiers with SHA-256 + salt for pseudonymization in analytics
3

Per-category encryption keys

Indicación:Generate data encryption keys for each data category: PII, financial, health records
4

Privacy-respecting CSP

Indicación:Generate CSP that blocks third-party trackers — no connect-src to analytics domains
5

Block PII page indexing

Indicación:Generate robots.txt blocking crawlers from user profile and account pages

Preguntas frecuentes

What data must be encrypted for GDPR?

GDPR recommends encryption for all personal data. At minimum: names, emails, addresses, phone numbers, IP addresses, financial data, and health data. Encryption is a key 'appropriate technical measure'.

What's the difference between anonymization and pseudonymization?

Anonymization is irreversible — data can never be linked back to an individual. Pseudonymization is reversible with a key. GDPR still applies to pseudonymized data but not anonymized data.

Recetas relacionadas