European Union: Deconstructing WP29 RTBF Guide And A Look To The Future

Last Updated: 9 February 2015
Article by Nuria Pastor

On 26 November 2014, the Article 29 Working Party (WP29) issued Guidelines on the interpretation of the Court of Justice of the European Union (CJEU) ruling on Google Spain v the Spanish Data Protection Authority and Mario Costeja Gonzalez ('the Ruling'), setting out a list of common criteria that European data protection authorities (DPAs) would take into account when considering the right to be forgotten ('RTBF') in relation to complaints received from individuals. According to Nuria Pastor, Senior Associate at Fieldfisher London, the Guidelines are in line with the Ruling but they further elaborate on certain legal and practical aspects of it and, as a result, offer invaluable insight into the DPAs vision of the future of the RTBF.

Preliminary observations

While the Guidelines help to frame the current debate regarding the content and limits of the RTBF, it is also useful to understand what the RTBF is not.

First, the RTBF is not entirely a new right. The Data Protection Directive 95/46/EC ('the Directive') does not regulate the RTBF as such but it recognises two rights on which the RTBF is based, namely the right to erase and the right to block one's personal data. Article 17 of the draft General Data Protection Regulation (GDPR) provides explicitly for a RTBF which is based on the existing right of erasure, although it is defined more broadly.

Second, the RTBF is not an absolute right and it is limited by other fundamental rights.

Last, but not least, the RTBF does not concern only search engines.

So far, it is mainly search engines who have been under intense scrutiny by DPAs regarding the manner in which they implement the findings of the Ruling in practice. However, non-search engine controllers are also receiving RTBF requests.

The legal test

The Guidelines do not discuss the CJEU's interpretation of Articles 12 (right to erasure) and 14 (right to blocking) of the Directive on which the RTBF is founded. However, they acknowledge the fact that the conditions laid down by these rights must be met in order to be able to exercise the RTBF.

The WP29 confirmed that search engines are controllers in their own right and their processing activities are separate from those of the website publishers that originally published the information.

The WP29 also argues that, as a general rule, the rights of individuals must prevail over the economic interests of the search engines and the right of the general public to access such information. However, it also acknowledges the necessity to find a balance between the different rights at stake. The outcome of this balancing exercise may depend on the nature of the personal data processed and the interest of the public to access information depending on the role of the individual in public life.

Furthermore, it describes the set of criteria that the DPAs will use in order to assess complaints, such as the role of the individual in public life; the accuracy of the personal data; the sensitive nature of the data; whether the individual is a minor; any prejudice caused to the individual; the relevance of the personal data; whether the individual has withdrawn his/her consent for the processing of his/her personal data; whether the controller originally published the personal data on the basis of a legal obligation, etc.

The WP29 emphasises that the criteria (1) are a 'flexible working tool' that will have to be applied on the basis of national legislation; (2) are likely to be combined with one another; and (3) must be implemented in light of the interest of the general public in having access to the information.

Territorial scope

In line with the Ruling, the Guidelines argue that Google's personal data processing operations as a search engine are carried out in the context of Google's establishments in EU countries, and therefore, the local laws of the EU member states where those establishments are located, will apply. As a result, WP29 argues that:

  • national DPAs may take actions against the local subsidiaries of the search engine;
  • individuals may exercise their rights before the national subsidiaries of the search engines; and
  • individuals cannot be forced to deal with other establishments of the search engines.

The WP29 also indicates that its Chair will contact search engines in order to clarify 'which EU establishment should be contacted by the competent DPA', which seems to indicate that DPAs might allow a certain degree of centralisation on the part of the search engines when dealing with the DPAs. This echoes some aspects of the draft GDPR under which controllers would be allowed to identify a 'main EU establishment' for the purpose of dealing with DPAs.

One of the most controversial conclusions in the Guidelines is that limiting the de-listing to the EU domains of the search engines cannot be considered sufficient to satisfactorily guarantee the rights of the data subjects, and therefore, de-listing decisions should be implemented in all domains, including '.com'.

The above confirms the trend of extending the application of EU privacy laws (and regulatory powers) beyond the traditional interpretation of current territorial scope rules under the Directive and will present search engines with legal uncertainly and operational challenges.

Material scope

The WP29 confirms that the Ruling only affects searches carried out by using the name of the individual and that the de-listed information may still be available through the search engines via other search criteria and on the website of the publishers that originally published the information.

The Guidelines argue that the precedent set out by the judgment against Google only applies to generalist search engines and not to search engines with a limited scope of action (for instance, search engines within a website).

However, controllers should not be complacent. Both EU-based and non-EU-based search engine and non-search engine controllers are already receiving these types of requests. Furthermore, under the draft GDPR, individuals would be able to exercise their RTBF before any data controller so it is only a matter of time before the scope of this right becomes broader.

What will happen in practice?

In its Guidelines, the WP29 advises that:

  • Individuals should be able to exercise their rights using 'any adequate means' and cannot be forced by search engines to use specific electronic forms or procedures;
  • Search engines must follow national data protection laws when dealing with requests;
  • Both search engines and individuals must provide 'sufficient' explanations in their requests/decisions;
  • Search engines must inform individuals that they can turn to the DPAs if they decide not to de-list the relevant materials;
  • Search engines should be encouraged to publish their de-listing criteria;
  • Search engines should not inform users that some results to their queries have been de-listed (WP29's preference is that this information is provided generically); and
  • Search engines should not inform website publishers that originally published the information about the fact that some pages have been de-listed in response to a RTBF request.


The WP29 emphasises that the impact on the freedom of expression of original publishers and users will be 'very limited'. Only time will tell whether this is the case. What we know now is that:

  • EU data protection law is clearly heading towards the establishment of a legal regime that enhances the rights of individuals. However, the RTBF is not an automatic right and its regulation under the draft GDPR is still far from being agreed.
  • European DPAs support the findings of the Ruling. The Guidelines, to a certain extent, reduces the level of legal uncertainly surrounding the Ruling.
  • The Ruling interprets Articles 12 and 14 of the Directive broadly and takes into account the way in which the RTBF is regulated in Article 17 of the draft GDPR.

As a result, the case law that will gradually develop around this precedent may influence the DPAs' future interpretation of the RTBF under the Regulation.

Controllers subject to EU data protection law, especially those that are not search engines, face challenging times. Whilst a full regulation of the RTBF under the GDPR is delayed by the slow progress of the legislative process, EU Regulators are inclined to make decisions with the forthcoming Regulation in mind. Controllers are therefore are advised to:

  • Closely follow the decisions and the views of the EU Regulators as they develop.
  • If they think they are likely to receive RTBF requests (or indeed have already started to receive them) put procedures in place in order to efficiently deal with RTBF requests. Such procedures should be based on the national data protection laws they are subject to today and take into account the criteria set out in the Opinion.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on

Click to Login as an existing user or Register so you can print this article.

In association with
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at and we will use commercially reasonable efforts to determine and correct the problem promptly.