intercom-data-handling

# Intercom Data Handling ## Overview Handle sensitive contact data in Intercom integrations with GDPR/CCPA compliance, data export via the Data Export API, contact deletion, PII redaction in logs, and data retention policies. ## Prerequisites - Understanding of GDPR/CCPA requirements - `intercom-client` SDK installed - Database for audit logging - Familiarity with Intercom's contact and conversation data model ## Data Classification for Intercom | Category | Intercom Fields | Handling | |----------|----------------|----------| | PII | `email`, `name`, `phone`, `location` | Encrypt at rest, redact in logs | | Identifiers | `id`, `external_id`, `user_id` | Use for lookups, no display | | Conversation content | `body`, `conversation_parts` | May contain PII, scan before logging | | Custom attributes | User-defined | Depends on content | | System metadata | `created_at`, `updated_at`, `role` | Standard handling | ## Instructions ### Step 1: GDPR Data Subject Access Request (DSAR) Export all Intercom data for a specific user. ```typescript import { IntercomClient } from "intercom-client"; const client = new IntercomClient({ token: process.env.INTERCOM_ACCESS_TOKEN!, }); async function exportContactData(contactId: string): Promise<{ contact: any; conversations: any[]; tags: any[]; segments: any[]; events: any[]; }> { // 1. Get contact profile const contact = await client.contacts.find({ contactId }); // 2. Get conversations for this contact const co...