I think your examples are muddying up the discussion. Your 2 examples of: >Identity/Software/Systems architecture may be able to enable this - i.e. being able

I think your examples are muddying up the discussion. Your 2 examples of: >Identity/Software/Systems architecture may be able to enable this - i.e. being able to make online transactions without actually identifying oneself. >Starting with: any account you open, you should be able to close and have all relevant information erased ... is not what OP (danaliv) you're replying to nor The Right To Be Forgotten[1] is conceptually about. Your examples are about transactions getting erased. E.g. if a woman creates a Facebook account and posts some selfies, she should later be able to delete that social account and Facebook would erase the associated photos. It would not do further data mining on her profile. RTBF is about erasing negative or embarrassing information. E.g. President George W Bush was arrested for drunk driving in 1976. RTBF would require Google, Bing, New York Times, Wayback Machine,etc to remove that information so people couldn't find it. Bush's arrest isn't a private transaction with a company -- it was a publicized incident that RTBF wants to erase. Would the (ideal) compliance of the law also require citizens who wrote personal emails such as "I won't be voting for Bush because of his drunk driving arrest" to delete that from their email archives? What about discussion forums (Usenet/reddit/HN/blogs/etc) where people talked about his arrest? Erasing the Facebook account is a trivial implementation. In contrast, erasing Bush's arrest from the public mind is only solvable for centralized institutions such as the Google search index or The New York Times archives. All the decentralized nodes of information will not comply. [1]https://en.wikipedia.org/wiki/Right_to_be_forgotten https://en.wikipedia.org/wiki/Right_to_be_forgotten