First Product: Zombie Delete

Zombie Delete FAQ ----------------- What is Zombie Delete? Zombie Delete provides cryptographic proof that data was actually deleted, not merely hidden or flagged. It verifies deletion events and issues auditable receipts without taking control of your data. Zombie Delete is primarily built for enterprise, institutional, and infrastructure use, but it is also used by SMEs and, in some contexts, individual users. Core concepts ------------- What is the difference between MKT Delete and ZKP Delete? Both methods rely on the same underlying deletion event, but differ in how proof is presented. MKT Delete produces a transparent proof by exposing cryptographic state changes before and after deletion. ZKP Delete builds on the same mechanism but wraps it in zero knowledge cryptography, allowing the deletion to be proven without revealing the data, database structure, or metadata. Use MKT Delete when auditability and transparency are required. Use ZKP Delete when the same proof is needed but must remain private. Who is Zombie Delete for? ------------------------- Who can use Zombie Delete? Zombie Delete is designed primarily for regulated organisations, Web2 and Web3 platforms, infrastructure providers, and institutions that require verifiable deletion. SMEs are significant users, particularly those handling personal or sensitive data. Individuals can also use Zombie Delete through supported workflows, demonstrations, and consumer facing integrations. Uniqueness and scope -------------------- Can other systems do this? As far as we are aware, no existing system provides cryptographic proof of deletion across both traditional databases and decentralised systems, with optional zero knowledge privacy, in a single verifiable framework. Zombie Delete is built around original deletion verification techniques and architectures that have been formally documented and protected, allowing us to offer strong guarantees while remaining interoperable with existing systems. Tombstones and receipts ----------------------- What is a tombstone and what does it do? A tombstone is a cryptographic replacement for deleted data. It removes access to the original content while preserving referential integrity, so systems continue to function without retaining personal or sensitive information. Once applied, the original data path is permanently severed. What does a cryptographic deletion receipt prove? A deletion receipt proves that a specific record transitioned from a live state to a tombstone at a defined point in time. It binds the before and after states so the deletion cannot be silently reversed or disputed later. Why do deletion receipts change behaviour? Because deletion becomes a provable event rather than a trust based claim. When organisations know deletions can be independently audited, there is a strong incentive to perform deletions correctly, consistently, and on time. Merkle Tree Delete (MKT) ------------------------ What is Merkle Tree Delete? Merkle Tree Delete proves deletion by comparing cryptographic fingerprints of a system before and after a delete using Merkle trees. How does Merkle Tree Delete work? A Merkle tree is built from hashed records and its root is recorded. After deletion or tombstoning, the tree is rebuilt. The difference between the two roots, together with the Merkle path, proves that the exact record was removed. What types of Merkle Tree Delete are supported? On chain Merkle Tree Delete on the Internet Computer Protocol, where data is stored and deleted atomically on chain. In this model, Zombie Delete can perform the deletion on your behalf. Off chain Merkle Tree Delete, which works with traditional databases and storage systems such as SQL, NoSQL, and object storage, where you perform the deletion and Zombie Delete verifies it. Do you delete our data? In off chain systems, no. You perform the deletion and Zombie Delete verifies it. On chain, such as on ICP, Zombie Delete can execute and verify atomic deletion as part of the protocol flow. Zero Knowledge Proof of Deletion (ZKPD) --------------------------------------- What is Zero Knowledge Proof of Deletion? Zero Knowledge Proof of Deletion is a privacy preserving layer on top of Merkle Tree Delete. It proves that a specific deletion verified by MKT occurred, without revealing the data, the Merkle tree, or any other records. When should Zero Knowledge Proof of Deletion be used? When deletion must be provable but nothing about the data or system should be disclosed to the verifier. Do you see user data? No. Merkle Tree Delete operates on hashed representations only, and Zero Knowledge Proof of Deletion adds an additional privacy layer. Deletion receipts and verification ---------------------------------- Can auditors verify receipts? Yes. Receipts can be shared with auditors, regulators, users, or counterparties. Optional blockchain anchoring enables independent verification. Post Quantum Ready Delete (PQRD) -------------------------------- What is Post Quantum Ready Delete? Post Quantum Ready Delete ensures that deletion proofs created today remain secure in a future where quantum computers exist. Zombie Delete is designed with quantum resistant cryptography in mind. This is a forward looking safeguard, not a current operational requirement.