DSAR & compliance
+ New DSAR intakeThe operator's compliance overview across all federations — DSAR, DPIA, retention, residency and incidents. Requests arrive by email/phone/supervisory authority where the requester has no login. 30-day SLA with a documented extension of up to 2 months.
7
open DSARs
● 1 with < 7 d to deadline
12
DPIAs
● 2 overdue reviews
1
retention anomaly
● row outliving its TTL
1
residency drift
● FIPJP federation
Cross-tenant DSAR tracker →
Intake/triage/execution · 30-day SLA · deadline countdown
GDPR snapshot →
Support triage · 13 redacted categories (never a DSAR response)
DPIA register (Art. 35) →
Risk assessment L×S · overdue reviews
Retention drift →
Configured TTL vs. oldest observed row
Data residency →
Required vs. actual region per tenant · never auto-fixed
Art. 33/34 incident notification →
72-hour window · dry run → dispatch · immutable log
Cross-tenant DSAR tracker
Allaccessexporterasure
Allreceivedvalidatedin_progresscompletedrejected
📭 No DSARs in this view.
⏳ Loading…
DSAR intake & case handling
Re-execute on completed → soft conflict (gdpr_already_completed). Execution is idempotent. Every mutation is audit-logged (WORM hash chain); drift is never auto-remediated.