July 18, 2018 | 5min read
GDPR Data Protection. Things to Remember for US Companies
GDPR—General Data Protection Regulation—is a unified system of personal data protection, introduced in the whole European Union and active since May 25, 2018. Although particular member states have some freedom in adjusting their national laws, it is safe to assume that personal data processing rules are substantially the same in all EU states. It’s also important to remember that the GDPR protects the rights and freedoms of EU residents, not necessarily EU citizens.
Acting at the intersection of European and American market, we are close to the clients whose products or services are available to customers from the EU territory. GDPR has already become one of the top subjects—it impacts a variety of business aspects but also the processes of services and product design. We’ve invited Krzysztof Muciak, an advocate from JSLegal, to analyze the most important aspects of GDPR that have to be taken into consideration by US companies acting in the EU.
- If the companies offer goods or services to persons, whom the personal data concerns, who are in the territory of the EU
Legal note: In order to determine if this applies to your business, the intention of the data controller (entrepreneur) is reconstructed; the mere accessibility of the controller’s website in the EU, of an email address or of other contact details, or the use of a language generally used in the third country where the controller is established, is insufficient to ascertain such intention. The factors such as the use of a language or a currency generally used in one or more EU member states with the possibility of ordering goods and services in that other language, or the mentioning of customers or users who are in the EU, may make it apparent that the controller envisages offering goods or services to data subjects in the EU.
- If the companies monitor behavior of such persons, when their behavior takes place within the EU
Legal note: The processing of personal data of data subjects who are in the EU by a controller or processor not established in the EU should also be subject to the GDPR when it is related to the monitoring of the behavior of such data subjects in so far as their behavior takes place within the EU. In order to determine whether a processing activity can be considered to monitor the behavior of data subjects, it should be ascertained whether natural persons are tracked on the internet including potential subsequent use of personal data processing techniques which consist of profiling a natural person, particularly in order to take decisions concerning her or him or for analyzing or predicting her or his personal preferences, behaviors, and attitudes.
The GDPR requirements for data controllers (entities deciding on the purpose and means of personal data processing) are broad and consist of those regarding (in particular):
- keeping the data secure
- always having a valid legal basis for processing, such as consent, necessity to perform a contract or comply with a legal obligation, as well as justified interest of the controller
- informing the data subject about details of the processing of their data, including purposes of the processing, recipients of the data, retention periods and the possibility to use any of data subject’s rights encompassed by the GDPR
- collecting only the categories of data which are necessary to fulfill a particular purpose of processing, and storing them for no longer than necessary for those purposes
- promptly responding to data subjects’ requests, resulting from exercising their rights encompassed by the GDPR
- informing the relevant personal data protection authority about any data security breaches (in some cases it is also necessary to inform the data subjects themselves)
As Polidea delivers software services and our core is mobile development, we’ve looked through the requirements for developers of apps and solutions that process personal data. Two rules are of the biggest importance:
- Privacy by design rule - implementing appropriate technical and organizational measures such as pseudonymization, data minimisation to integrate the necessary safeguards into the processing.
Legal note: Taking into account the state of the art, the cost of implementation and the nature, scope, context and purposes of processing as well as the risks of varying likelihood and severity for rights and freedoms of natural persons posed by the processing, the controller shall, both at the time of the determination of the means for processing and at the time of the processing itself, implement appropriate technical and organisational measures. These measures, such as pseudonymization, which are designed to implement data-protection principles, such as data minimisation, in an effective manner and to integrate the necessary safeguards into the processing in order to meet the requirements of the GDPR and protect the rights of data subjects.
- Privacy by default rule - implementing appropriate technical and organizational measures to ensure that, by default, only personal data which are necessary for each specific purpose of the processing are actually processed.
Legal note: The controller shall implement appropriate technical and organizational measures for ensuring that, by default, only personal data which are necessary for each specific purpose of the processing are processed. That obligation applies to the amount of personal data collected, the extent of their processing, the period of their storage and their accessibility. In particular, such measures shall ensure that by default personal data are not made accessible without the individual’s intervention to an indefinite number of natural persons.
The failure to comply with the GDPR requirements may result in a personal data protection authority’s intervention. It may be a recommendation to take or refrain from certain actions, a warning and/or a fine. The maximum amount of the fine may be up to 20 000 000 EUR, or in the case of a company, up to 4 % of the total worldwide annual turnover of the preceding financial year, whichever is higher.
Head of Marketing
Advocate, Associate, JSLegal