Provable deletion with purge receipts
Most platforms say data is deleted. Zumik separates revoking a handle from removing the state behind it, and returns a receipt that states the strongest guarantee each execution profile can actually back up.
Revokes access
A delete makes a handle unusable immediately. It is fast and reversible in the sense that the underlying state may still exist under retention until purged.
Removes state, emits a receipt
A purge job removes the underlying data and returns a signed receipt describing what was removed, under which profile, with what evidence level, and any remaining retention window.
Honest about what each profile can prove.
On managed providers, deletion evidence is bounded by what the provider exposes, we will not invent a guarantee a third party cannot back. On BYOC, where the data plane runs in your cloud, purge evidence can be runtime-confirmed against the KV hierarchy you control.
BYOC runtime profiles{
"purge_job_id": "prg_01JY…",
"scope": "artifact:art_…",
"profile": "byoc_us_east",
"guarantee": "runtime_confirmed",
"namespace_generation": 42,
"remaining_retention_ms": 0,
"completed_at": "2026-06-09T20:31:00Z",
"signature": "…"
}Retention truth beats retention theater.
No resurrection
Purging increments a namespace generation, so re-uploaded content cannot revive a stale cache relationship.
Erasure support
Purge workflows produce the deletion evidence that GDPR and CCPA erasure obligations call for.
Auditable
Every receipt is signed and references the scope and profile, so a reviewer can verify rather than trust.
We would rather tell you the honest limit of a managed profile than market a deletion guarantee we cannot prove. When you need stronger evidence, that is a reason to consider BYOC, backed by replay, not by fear.
Purge semantics, answered.
What is the difference between delete and purge?
Delete revokes a handle so it can no longer be used. Purge removes the underlying state and emits a signed receipt with profile-specific evidence and any remaining retention window.
Can Zumik prove deletion on managed providers?
Zumik states the strongest guarantee a profile can actually prove. On managed providers, evidence is bounded by provider capabilities; on BYOC, purge evidence can be runtime-confirmed.
Does purging affect caches?
Yes. Purging an artifact increments a namespace generation so stale physical cache entries cannot be resurrected, even if the same content is later re-uploaded.
Does this help with right-to-erasure requests?
It is designed to. Purge workflows produce deletion evidence that supports GDPR and CCPA erasure obligations for personal data you store.
Deletion evidence for your security review
Profile-specific purge receipts, opaque handles, and metadata-first defaults. Ask us for the packet.