webflow-data-handling

# Webflow Data Handling ## Overview Handle sensitive data correctly when working with the Webflow Data API v2. Covers PII in form submissions, ecommerce customer data, CMS content classification, GDPR/CCPA compliance patterns, and data retention policies. ## Prerequisites - Understanding of GDPR/CCPA requirements - Webflow API token with `forms:read`, `ecommerce:read` scopes - Database for audit logging - Scheduled job infrastructure for data cleanup ## Webflow Data Classification | Source | Data Type | PII Risk | Handling | |--------|-----------|----------|----------| | Form submissions | Email, name, phone, message | High | Encrypt at rest, redact in logs | | Ecommerce orders | Name, email, address, payment | High | Never log, minimal retention | | CMS items | Blog posts, team bios, products | Low-Medium | May contain names/photos | | Site analytics | Page views, sessions | Low | Aggregate when possible | | API tokens | Access credentials | Critical | Never log, rotate quarterly | ## Instructions ### Step 1: PII Detection in Form Submissions ```typescript 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{4}[- ]?\d{4}[- ]?\d{4}\b/g }, ]; function detectPII(text: string): Array<{ type: string; found: boolean }> { return PII_PATTERNS.map(p => ({ type:...