Thursday, July 31, 2014

Google details the process it uses for “right to be forgotten” requests


Google details the process it uses for “right to be forgotten” requests


Back in May, the European Union put a law into place that it believed would protect an individual’s “right to be forgotten”. This meant that anyone could request to have themselves removed for a search engine’s results, and all search engines would have to comply with the rules.


Naturally being the biggest search engine on the internet, Google has been the most public subject of this new law. Today, the company has revealed which countries have made the most requests for links to be removed from search results. Google also made public the process it uses for delisting links.


Google says that the Dutch have made 5,500 requests, the Italians have made 7,500 requests, the Spanish have made 8,000 requests, the British have made 12,000 requests, the Germans have made 16,500 requests, and the French have topped the list with 17,500 requests.


Of the thousands of requests that have been made across the European Union, Google has delisted about 53% of the as requested. Another 32% of the requests have been denied and the search results are still available. The remainder are requests where the decision is pending while Google requests more information from the requester.


Once an individual has filled in the online form with the details of the search terms they want delisted, each request has to be evaluated individually by Google employees, something that requires a “significant hiring effort” according to Google.


Guided by a panel of independent experts, which includes the founder of Wikipedia Jimmy Wales, they have to evaluate “whether the search results in question include outdated or irrelevant information about the data subject, as well as whether there’s a public interest in the information”.


Read more about the story at The Verge.


The post Google details the process it uses for “right to be forgotten” requests appeared first on Uberly.






via Uberly http://ift.tt/1qvwiON

No comments: