Agent skill · marketing growth · jeremylongshore
klaviyo-data-handling
Implement Klaviyo data privacy, GDPR/CCPA compliance, and PII handling
Why this skill is useful
Adds specific workflows and code snippets for handling GDPR/CCPA compliance with Klaviyo's Data Privacy API that the AI wouldn't reliably generate on its own.
What it needs
Requires klaviyo-api installed locally. Requires klaviyo account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Klaviyo Data Handling Overview Handle profile data, PII, and privacy compliance with Klaviyo's Data Privacy API, GDPR right-to-deletion, CCPA requests, and safe logging patterns. This skill covers five workflows: GDPR profile deletion, Data Subject Access Requests (DSAR), PII redaction in logs, consent management, and compliance audit logging. The GDPR deletion skeleton is inline below. The deeper step-by-step code — DSAR export, PII redaction, consent management, and audit logging — lives in references/implementation.md so this file stays scannable. Read the summary here, then drill into the reference for full copy-ready code. Prerequisites klaviyo-api SDK installed API key with data-privacy:write scope (for deletion requests) Understanding of GDPR/CCPA requirements Audit logging infrastructure Klaviyo Data Privacy API Klaviyo provides a dedicated Data Privacy API for GDPR/CCPA profile deletion. When you delete a profile via this API, Klaviyo performs a full GDPR erasure — the profile is permanently removed and cannot be recovered. Instructions The workflow has five steps. Step 1 (deletion) is shown in full here because it is the highest-risk, most-requested operation. Steps 2–5 follow the same session pattern and are fully implemented in references/implementation.md. Step 1: GDPR Profile Deletion (Right to Erasure) Request deletion with exactly one identifier (email, phone, or profile ID). Providing more than one returns an error. Deletion is irreversible, so always audit-log the request. The multi-identifier form (email / phone / profile ID with validation) is in references/implementation.md § Step 1. Step 2: Data Subject Access Request (DSAR) Export every profile attribute, event, and list membership for a subject (GDPR Article 15) using ProfilesApi + EventsApi. Full exportProfileData() in references/implementation.md § Step 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/klaviyo-data-handling