Skip to the content
Eureka The General Data Protection Regulation
EN language

Questions and answers

Eureka's answers

Does the GDPR apply to companies outside the EU?

It can. It applies to processing in the context of the activities of an establishment of a controller or processor in the Union, whether or not the processing takes place in the Union.

A controller or processor not established in the Union is covered when it processes personal data of data subjects who are in the Union and the processing relates to offering them goods or services, whether or not they must pay, or to monitoring their behaviour as far as it takes place within the Union.

Such a controller or processor must, with exceptions, designate in writing a representative in the Union.

Does the GDPR apply to individuals in their private life?

Not to processing by a natural person in the course of a purely personal or household activity.

Recital 18 describes such activity as having no connection to a professional or commercial activity, and gives as examples correspondence, the holding of addresses, and social networking and online activity undertaken within the context of such activities.

It adds that the Regulation still applies to controllers or processors which provide the means for processing personal data for such personal or household activities.

What counts as personal data?

‘Personal data’ means any information relating to an identified or identifiable natural person, the ‘data subject’.

An identifiable person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data or an online identifier, or to factors specific to his or her physical, physiological, genetic, mental, economic, cultural or social identity.

Under recital 26, pseudonymised data that could be attributed to a person with additional information count as personal data; anonymous information is not covered.

The Court of Justice has interpreted this provision; its judgments are listed under Case law on the article's page.

What are the main principles of the GDPR?

Article 5 sets them out. Personal data must be:

  • processed lawfully, fairly and in a transparent manner;
  • collected for specified, explicit and legitimate purposes and not further processed in a manner incompatible with them;
  • adequate, relevant and limited to what is necessary;
  • accurate and, where necessary, kept up to date;
  • kept in identifiable form no longer than necessary, with exceptions for archiving, research and statistics; and
  • processed with appropriate security.

The controller is responsible for, and must be able to demonstrate, compliance (‘accountability’).

What is a legitimate interest?

Under Article 6(1)(f), processing is lawful where it is necessary for the purposes of the legitimate interests pursued by the controller or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject which require protection of personal data, in particular where the data subject is a child.

Public authorities may not rely on it in the performance of their tasks.

Recital 47 points to the data subject's reasonable expectations and gives preventing fraud and direct marketing as examples.

The Court of Justice has interpreted this provision; its judgments are listed under Case law on the article's page.

Can health data or other sensitive data be processed?

The Regulation's term is ‘special categories of personal data’.

Processing of personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs or trade union membership, and of genetic data, biometric data for uniquely identifying a natural person, data concerning health and data concerning sex life or sexual orientation is prohibited unless one of ten cases in Article 9(2) applies.

They include:

  • explicit consent (unless Union or Member State law excludes it);
  • employment and social protection law;
  • vital interests;
  • data manifestly made public by the data subject;
  • legal claims; and
  • public interest, health and research purposes based on law with safeguards.

How long does a controller have to answer a request?

The controller must inform the data subject of action taken on a request under Articles 15 to 22 without undue delay and in any event within one month of receipt of the request.

That period may be extended by two further months where necessary, taking into account the complexity and number of the requests; the controller must tell the data subject of the extension, with the reasons, within one month.

If it does not act on the request, it must say why within one month and mention the possibility of a complaint to a supervisory authority and of a judicial remedy.

Does a request cost anything?

In general, no. Information under Articles 13 and 14 and communications and actions under Articles 15 to 22 and 34 are provided free of charge.

Where requests are manifestly unfounded or excessive, in particular because of their repetitive character, the controller may charge a reasonable fee taking into account the administrative costs, or refuse to act; it bears the burden of demonstrating that character.

For any further copies of the data requested by the data subject, the controller may charge a reasonable fee based on administrative costs.

Can I get a copy of my data?

Yes. The data subject has the right to obtain from the controller confirmation as to whether personal data concerning him or her are being processed and, if so, access to the data and to information such as:

  • the purposes;
  • the recipients;
  • the storage period where possible;
  • any available information on the source; and
  • the existence of automated decision-making under Article 22(1) and (4).

The controller must provide a copy of the personal data undergoing processing; a request made by electronic means is answered in a commonly used electronic form unless the data subject asks otherwise.

The right to a copy must not adversely affect the rights and freedoms of others.

Do I have a ‘right to be forgotten’, and when not?

Article 17 gives a right to erasure, which its heading also calls the ‘right to be forgotten’.

The controller must erase personal data without undue delay where one of six grounds applies, for example:

  • the data are no longer necessary for their purposes;
  • consent is withdrawn and there is no other legal ground; or
  • the data have been unlawfully processed.

The right does not apply to the extent that processing is necessary for:

  • freedom of expression and information;
  • a legal obligation;
  • a public-interest task or official authority;
  • public health;
  • archiving, research or statistics under the conditions of Article 17(3)(d); or
  • legal claims.

Can I object to direct marketing?

Yes. Where personal data are processed for direct marketing purposes, the data subject has the right to object at any time, including to profiling to the extent that it is related to such direct marketing.

After an objection, the personal data must no longer be processed for those purposes. The right must be explicitly brought to the data subject's attention, clearly and separately from other information, at the latest at the first communication.

Can a computer decide about me on its own?

The data subject has the right not to be subject to a decision based solely on automated processing, including profiling, which produces legal effects concerning him or her or similarly significantly affects him or her.

This does not apply where the decision:

  • is necessary for entering into, or performance of, a contract between the data subject and the controller;
  • is authorised by Union or Member State law with suitable safeguards; or
  • is based on the data subject's explicit consent.

In the contract and consent cases, the controller must provide at least the right:

  • to obtain human intervention;
  • to express his or her point of view; and
  • to contest the decision.

When must a personal data breach be notified, to whom, and how fast?

The controller must notify the supervisory authority competent under Article 55 without undue delay and, where feasible, not later than 72 hours after having become aware of the breach, unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons.

A later notification must give reasons for the delay. A processor must notify the controller without undue delay.

Where the breach is likely to result in a high risk, the controller must also communicate it to the data subject without undue delay, unless a condition in Article 34(3) is met.

The controller must document every breach.

Must every business keep records of processing?

Not every one. Each controller must keep a record of processing activities under its responsibility, and each processor a record of all categories of processing activities carried out on behalf of a controller.

The records must be in writing, including in electronic form, and made available to the supervisory authority on request.

This does not apply to an enterprise or an organisation employing fewer than 250 persons, unless its processing:

  • is likely to result in a risk to the rights and freedoms of data subjects;
  • is not occasional; or
  • includes special categories of data or personal data relating to criminal convictions and offences.

Who needs a data protection officer?

The controller and the processor must designate one where:

  • the processing is carried out by a public authority or body, except courts acting in their judicial capacity; or
  • their core activities consist of processing operations which require regular and systematic monitoring of data subjects on a large scale, or of processing on a large scale of special categories of data or personal data relating to criminal convictions and offences.

In other cases they may designate one, and must where Union or Member State law requires it.

Point (c) reads ‘or’ as corrected by the corrigendum of 23 May 2018 (OJ L 127, p. 2); the text first published read ‘and’.

When is a data protection impact assessment needed?

Where a type of processing, in particular using new technologies, is likely to result in a high risk to the rights and freedoms of natural persons, the controller must carry out an assessment before the processing.

It is required in particular for:

  • a systematic and extensive evaluation of personal aspects based on automated processing, including profiling, on which decisions with legal or similarly significant effects are based;
  • large-scale processing of special categories of data or of personal data relating to criminal convictions and offences; and
  • systematic monitoring of a publicly accessible area on a large scale.

Supervisory authorities publish lists of processing operations that require one.

Can personal data be sent to the US or other third countries?

The articles name no country; the same conditions apply to every third country and international organisation.

A transfer may take place where the Commission has decided that the country, a territory or specified sector in it, or the organisation ensures an adequate level of protection.

Without such a decision, the controller or processor must provide appropriate safeguards, such as binding corporate rules or standard data protection clauses, and enforceable data subject rights and effective legal remedies must be available.

Failing both, a transfer may take place only on a derogation in Article 49, such as explicit consent after being informed of the possible risks.

Who enforces the GDPR?

Each Member State must provide for one or more independent public authorities, the ‘supervisory authority’, responsible for monitoring the application of the Regulation.

Each acts on the territory of its own Member State; its tasks include monitoring and enforcing the Regulation and handling complaints, and its powers include imposing administrative fines.

For cross-border processing, the authority of the main establishment or single establishment acts as lead supervisory authority.

The European Data Protection Board, composed of the head of one supervisory authority of each Member State and the European Data Protection Supervisor, ensures the consistent application of the Regulation. Data subjects may also go to court.

Where can I complain?

Every data subject who considers that the processing of personal data relating to him or her infringes the Regulation may lodge a complaint with a supervisory authority, in particular in the Member State of his or her habitual residence, place of work or place of the alleged infringement.

That authority must report on the progress and the outcome. If the competent authority does not handle the complaint or does not inform the data subject within three months, the data subject may go to court against it.

Court action against the controller or processor is also possible, and a not-for-profit body may be mandated to act.

How high can fines be?

Administrative fines must be effective, proportionate and dissuasive in each individual case.

Infringements listed in Article 83(4), such as the obligations of the controller and the processor under Articles 8, 11, 25 to 39, 42 and 43, are subject to fines up to 10 000 000 EUR, or in the case of an undertaking, up to 2 % of the total worldwide annual turnover of the preceding financial year, whichever is higher.

Those in Article 83(5) and (6), such as the basic principles, data subjects' rights, transfers and non-compliance with an order, are subject to fines up to 20 000 000 EUR, or for an undertaking up to 4 %, whichever is higher.

Can I claim compensation?

Any person who has suffered material or non-material damage as a result of an infringement of the Regulation has the right to receive compensation from the controller or processor.

A controller involved in processing is liable for damage caused by infringing processing; a processor only where it has not complied with obligations specifically directed to processors or has acted outside or contrary to the controller's lawful instructions.

Either is exempt if it proves that it is not in any way responsible for the event giving rise to the damage.

The Court of Justice has interpreted this provision; its judgments are listed under Case law on the article's page.

Is the GDPR a regulation or a directive, and does national law still matter?

It is a Regulation, Regulation (EU) 2016/679. Its closing formula says it is binding in its entirety and directly applicable in all Member States.

National law still matters where the Regulation leaves room for it or asks for it. For example, Member States:

  • may adapt the rules for processing based on a legal obligation or a public task;
  • may lower the age for a child's consent to not below 13 years;
  • must reconcile data protection with freedom of expression and information; and
  • must lay down rules on other penalties.

Each Member State also provides for its own supervisory authority.

Since when does the GDPR apply, and what did it replace?

It applies from 25 May 2018. It entered into force on the twentieth day following that of its publication in the Official Journal of the European Union. It repealed Directive 95/46/EC with effect from 25 May 2018. References to that Directive are construed as references to the Regulation, and references to the Working Party established by Article 29 of that Directive as references to the European Data Protection Board.

What is the ‘one-stop-shop’?

The articles do not use the word; recitals 127 and 128 speak of the ‘one-stop-shop mechanism’ for the cooperation between the lead supervisory authority and the other supervisory authorities concerned.

Under the articles, the supervisory authority of the main establishment or single establishment of a controller or processor is competent to act as lead supervisory authority for its cross-border processing, under the procedure in Article 60, and is its sole interlocutor for that processing.

Another authority may handle a case that concerns only its Member State. The rules do not apply to processing by public authorities or private bodies acting on the basis of Article 6(1)(c) or (e).

Does the GDPR apply to journalists and researchers?

Yes, with room for exceptions. Member States must by law reconcile data protection with freedom of expression and information, and for processing for journalistic purposes or academic, artistic or literary expression they must provide for exemptions or derogations from Chapters II to VII and IX where necessary to reconcile the two.

Processing for scientific or historical research or statistical purposes is subject to appropriate safeguards; Union or Member State law may provide for derogations from the rights in Articles 15, 16, 18 and 21 in so far as those rights are likely to render impossible or seriously impair the specific purposes and the derogations are necessary.

Eureka is adding links and definitions…