Agent skill · software engineering · jeremylongshore
intercom-data-handling
Implement Intercom data handling for GDPR, contact export, data retention,
Why this skill is useful
Adds executable TypeScript functions for GDPR-compliant data handling in Intercom that are not publicly documented.
What it needs
Requires intercom-client installed locally. Requires intercom account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Intercom Data Handling Overview Handle sensitive contact data in Intercom integrations with GDPR/CCPA compliance: data export via the Data Export API, contact deletion with an audit trail, PII redaction in logs, and data retention policies. This skill gives you a lean map of the five workflows here; the full copy-ready TypeScript lives in references/implementation.md and worked usage in references/examples.md. Prerequisites Understanding of GDPR/CCPA requirements intercom-client SDK installed Database for audit logging Familiarity with Intercom's contact and conversation data model Authentication Every call authenticates with an Intercom access token via a Bearer header. Store it as INTERCOMACCESSTOKEN in the environment — never hardcode it and never log it: Grant the token the minimum scopes needed (read contacts/conversations for export, write/delete for erasure). Rotate it if it ever appears in a log or a diff. Data Classification for Intercom Category Intercom Fields Handling ---------- ---------------- ---------- PII email, name, phone, location Encrypt at rest, redact in logs Identifiers id, externalid, userid Use for lookups, no display Conversation content body, conversationparts May contain PII, scan before logging Custom attributes User-defined Depends on content System metadata createdat, updatedat, role Standard handling Instructions The five workflows below compose into a compliant Intercom data lifecycle. Follow the summary here, then open references/implementation.md for the complete function bodies. 1. DSAR export — exportContactData(contactId) gathers the contact profile, all conversations (with parts), tags, segments, and data events into one bundle. This is the "give me all my data" request. 2. Right to deletion (Article 17) — deleteContactData(contactId) exports for the audit trail first, then deletes from Intercom and every local cache, and records a PII-free audit entry (email is hashed, not stored). 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/intercom-data-handling