ErasureDocs
Guides

FAQ

Common product questions — grounded in shipped behaviour.

FAQ

Yes. Publish, SDK, receipts, and publish Evidence stand alone without Rights.

Can I use only Rights?

Yes, if operators create cases (or intake is used). You still need Systems (and Data Maps for SQL/document modules). Consent is optional for pure deletion ops.

Why do I need Data Maps?

Map-backed Systems do not guess tables/collections. A Data Map defines resources, identifiers, and DELETE vs SKIP. Without a map, start readiness fails for those systems.

Why not delete directly from the UI?

Direct SQL in a browser is unsafe and poorly audited. Rights + worker + maps give verification gates, retries, timelines, and Evidence.

How does Evidence differ from Activity or logs?

ActivityEvidenceServer logs
Event timeline on a requestStructured exportable packageDebug/ops noise

Evidence is not a sealed legal cryptographic archive in Beta.

What does VERIFIED mean?

PathMeaning
Public OTPSubject proved control of email
OperatorOperator asserted verification

Do not conflate the two in compliance narratives.

Why is Operational Readiness not green?

Common causes: no enabled Systems, empty SQL map, degraded health, worker offline, unpublished consent. See Operational readiness and Troubleshooting.

Why does the SDK say origin_not_allowed?

New projects enable Allowed origins by default. List hosts under Develop → Allowed origins. Empty patterns fail closed when the allowlist is on.

Yes for optional purposes on the same browser (prefs / hosted / withdrawOptional()). Required purposes stay on. Each change creates a new receipt.

Is ACCESS or CORRECT supported?

Not as first-class product types today. DELETE is the Rights fulfillment type.