Can a Private Blockchain Comply with “Right to Be Forgotten” Rules If It Is Immutable?

Direct compliance is challenging because the "Right to Be Forgotten" (RTBF) requires the deletion of personal data, which contradicts blockchain immutability. Compliance is achieved by storing personal identifying information (PII) off-chain and only storing an encrypted hash or a non-identifying reference on the blockchain.

When an RTBF request is made, the PII is deleted from the off-chain storage, rendering the on-chain hash meaningless without the corresponding data.

What Is a ‘Dark Pool’ and How Does It Mitigate Information Leakage for Block Trades?
What Regulatory Frameworks Govern Front-Running in Traditional Options and Derivatives Markets?
Can ZKPs Be Used to Hide the Identity of the Trader as Well as the Trade Details?
How Does the Immutable Nature of Blockchain Conflict with Regulatory “Right to Erasure” (GDPR)?
What Is the Difference between an On-Chain and an Off-Chain Cryptographic Proof?
What Constitutes “Inside Information” in the Context of a Crypto Asset Listing?
What Are the Limitations of Achieving DVP for Large, Off-Chain OTC Crypto Derivative Trades?
How Is ‘Data Immutability’ Reconciled with the ‘Right to Be Forgotten’ under GDPR?

Glossar