Agent skill · data analytics · jeremylongshore
clay-data-handling
Implement GDPR/CCPA-compliant data handling for Clay enrichment pipelines.
Why this skill is useful
Provides specific data handling procedures and validation scripts for GDPR/CCPA compliance that the AI wouldn't reliably generate on its own.
What it needs
Requires clay account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Clay Data Handling Overview Manage lead data through Clay enrichment pipelines in compliance with GDPR, CCPA, and data privacy best practices. Clay enriches records with PII (emails, phone numbers, LinkedIn profiles, job titles), requiring careful handling of consent, retention, and export controls. Prerequisites Clay account with enriched tables Understanding of GDPR/CCPA requirements for B2B data Data retention policy defined by your legal team CRM or database for enriched data storage Instructions Step 1: Classify Enriched Data by Sensitivity Step 2: Validate Input Data Before Enrichment Step 3: Deduplicate Before Enrichment Step 4: Add Retention Metadata to Enriched Data Step 5: GDPR-Compliant Export Step 6: Data Subject Rights Implementation Error Handling Issue Cause Solution ------- ------- ---------- High duplicate rate Same list imported twice Run dedup before sending to Clay Invalid emails in export Bad source data Validate with Zod before import Expired data in CRM No retention cleanup Schedule weekly expiration check Missing consent basis No legal basis tracked Add consentbasis to all records GDPR deletion incomplete Data in multiple systems Track all systems in data map Output Maintain a data-handling record containing source and purpose, consent or other lawful basis, sensitivity classification, allowed tables/destinations, retention/deletion schedule, access owner, data-subject request status, and redacted audit reference. This guidance does not replace legal review for a specific jurisdiction or use case. Examples Before importing a prospect list, verify the allowed purpose and retention rule, then map each downstream CRM and warehouse copy for deletion coverage. For a deletion request, use the hashed audit record, remove the approved systems of record, confirm manual Clay-table cleanup, and report completion without exposing the individual’s data in the ticket. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clay-data-handling--2d27c1