Setting up a potential international “conflict of laws” dispute, France’s privacy regulator (CNIL) rejected Google’s arguments against expanding the “right to be forgotten” (RTBF) to the company’s global index. Google had been limiting RTBF removals to European domains such as Google.fr.
Privacy regulators in Europe have argued that the ability to access the “removed” content from Google.com effectively undermines RTBF. The French have threatened sanctions if Google fails to remove RTBF links from all its domains globally.
While there is some legitimacy to the French and European arguments about RTBF circumvention — nevermind that the links and content still exist on the source websites — France is effectively trying to impose European law on Google across the globe. From that point of view the French action is not only legally unjustified it creates a dangerous precedent that other countries may try to follow in an effort to globally censor content they don’t like. My perennial example is the Chinese government trying to reach out globally and censor content about the Tiananmen Square massacre.
While the French and European objectives with RTBF are well-intentioned and seek to find a balance between the public right to know and individual privacy, there are many other nations whose motives are not so benevolent.
Google has asserted that CNIL does not have the jurisdiction and authority to impose a global ban on disputed RTBF links. CNIL disagrees with this characterization and sees itself simply trying to enforce the law in France and Europe.
Google has recourse to more appeals. It’s possible that the case would wind up in front of the European Court of Justice Luxembourg, which gave birth to RTBF a year ago. If that court agreed with CNIL and its asserted authority to regulate Google.com, the matter would then presumably become one for international diplomacy.
The post Right To Be Forgotten: French Argue They Have Authority To Regulate Google Globally appeared first on Search Engine Land.
from SEO Rank Video Blog http://ift.tt/1NP1Oqn
via IFTTT
No comments:
Post a Comment