Compliance With EU's 'Right to be Forgotten' Law

I was wondering, has anyone at Keybase had done any research into whether or not Keybase can comply with European Union privacy laws, such as the "Right to be Forgotten"? Even if a company is not located in the EU, if it does business with any EU citizens (such as Keybase users who live in the EU), it must comply with EU laws and regulations. Google recently lost a case in the EU where they said that, in certain cases, EU citizens have the right to make Google remove information about them from Google's search results. Of course, Keybase is an entirely different sort of application compared to a search engine. I'm not a lawyer, and I don't know whether or not Keybase would be subject to the EU's "Right to be Forgotten" law (the right is not absolute, and the EU courts have to decide on a case-by-case basis if the right applies in any particular case), but since the EU has a lot of member countries and if any Keybase users live in a member country than Keybase might be subject to EU jurisdiction in matters like this. Given that removing someone from the history of Keybase would be severely difficult (and now that the data is being pushed to the Bitcoin blockchain, completely impossible), it might be prudent for Keybase to have a lawyer who is experienced with EU 'Right to be Forgotten' law look over how Keybase works and let you all know if there are any potential legal issues that you might encounter if any of your users reside in the EU.

Has Keybase had a lawyer knowledgeable in EU law look into this before? If so, did they have any concerns?

@zQueal
@gabriel
@songgao

The issue names no files, tests, or code entry points. Start by reviewing the described Keybase data history and Bitcoin blockchain behavior, then determine whether EU right-to-be-forgotten obligations apply and whether removal is technically possible. Done would require a documented legal and product decision, not a small code change.

Written by the indexing model from the issue text.