Policies + data subject request
We've designed CharmEngine around GDPR Article 25 (data protection by design). Every policy below is enforceable in code, not just on paper. The data-subject request form at the bottom of this page goes directly to the operator console and is actioned within the 30-day SLA mandated by Article 12.
What we collect + why
Email, tenant settings, brand canon you upload, audit log of operator actions, AI provider usage telemetry. Never special-category data without your explicit Article 9 lawful basis recorded in the audit log.
Right to erasure · 30 days
One endpoint nullifies your PII, deletes your tenant's R2 objects, emits a cryptographic erasure proof. Use the form below or open Mission Control → Privacy → Delete tenant.
Right to portability
Full export as a signed, structured ZIP (Postgres rows + R2 objects + audit ledger entries). Delivered within 30 days. Cryptographic integrity hash included.
Security of processing
Tier-3 multi-tenant isolation (per-tenant Postgres role + RLS), per-tenant KMS DEK wrapping, application firewall + WAF, Hippocrates auto-heal pulse, append-only audit ledger.
Breach notification
72-hour timer from confirmed awareness. Automated detection on Neon audit log, R2 access patterns, Cloudflare WAF anomalies. Affected data subjects notified directly within Article 34 timeframe.
Cross-border transfers
EU-tagged tenants route through Frankfurt only. US sub-processors (OpenAI, Anthropic, Stripe US) operate under SCCs Module 2 + Transfer Impact Assessments published per vendor.
Request your data, or its erasure.
Use this form to exercise any GDPR right (access · rectification · erasure · portability · object · restrict). The request lands in the operator console (admin.charmengine.uk) and is auto-acknowledged via email within 1 working day. Final action SLA is 30 days per Article 12; usually within 72 hours.