adobe-data-handling

# Adobe Data Handling ## Overview Handle sensitive data correctly when integrating with Adobe APIs. Key concerns include Firefly content policy compliance, PII in PDF extraction results, credential redaction in logs, and GDPR/CCPA compliance using Adobe Privacy Service API. ## Prerequisites - Understanding of your data classification requirements - Adobe SDK with appropriate API access - Database for audit logging - Familiarity with GDPR/CCPA obligations ## Instructions ### Step 1: Data Classification for Adobe API Data | Category | Examples | Handling | |----------|----------|----------| | **Credentials** | `client_secret`, access tokens | Never log; rotate regularly | | **User Content** | Uploaded images, PDFs | Encrypt at rest; delete per retention policy | | **Generated Content** | Firefly outputs, processed PDFs | Time-limited URLs (24h); cache intentionally | | **Extraction Results** | PDF text, tables, structured data | May contain PII; scan and redact | | **API Metadata** | Job IDs, request IDs, timestamps | Safe to log; useful for debugging | ### Step 2: PII Detection in PDF Extraction Results PDF Extract API returns raw text that may contain customer PII: ```typescript // src/adobe/pii-scanner.ts const PII_PATTERNS = [ { type: 'email', regex: /[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}/g }, { type: 'phone', regex: /\b\d{3}[-.]?\d{3}[-.]?\d{4}\b/g }, { type: 'ssn', regex: /\b\d{3}-\d{2}-\d{4}\b/g }, { type: 'credit_card', regex: /\b\d{4}[- ]?\d{...