Yes, I’ve had quite a few conversations over this topic and it is a complex nuanced one that is going to evolve over time. From what I understand right to be forgotten cases fall into two cases for us:
-
“Factual data that is not personally identifying” falls under the clause of “archiving purposes in the public interest”. We will reject requests to remove this sort of data, but if a person can reasonably argue that they might come to harm because of us having the data, we will take this data down.
-
“Factual data that is personally identifying”, primarily birth dates. If a person in our database requests that we remove this data, we are required to comply.
And you can see that “come to harm” is a laughably vague concept, which requires us to evaluate each situation on a case by case basis. But, let me give two examples for this:
-
A person used to perform in a certain type of band (e.g. Brony [0]) and this fact is causing them to be bullied later in life. We had a “person Joe Blow performed as Brony King on…” type of relationship. We agreed that in order to help out, we removed the link to Joe Blow, but kept the data on the brony band.
-
A person used to be married to someone else and now has gotten a divorce and is bitter about the divorce. Now they wish to expunge all records of their marriage and demand that we remove the link stating their marriage. This person is just angry about having been in that marriage but could not demonstrate that this was causing them harm and we did not remove the link.
In these cases we need to make a judgement call on whether or not we consider this a reasonable request and possibly that if we do not comply that this person could come to harm. The situation is so vague to be nearly unworkable, but we have no choice but to act accordingly until future court cases further clarify the situation.
My understanding is that our current operations, including artist intent, are legally defensible and reasonably informed about the current laws that apply to us.