The EU General Data Protection Regulation (GDPR) can apply to a Ukrainian company even if it has no office in the European Union. Offering goods or services to people in the EU, or monitoring their behaviour, is enough. Here is when the GDPR applies, what it requires and which of those requirements fall to IT.
This article is an overview, not legal advice. Decide with your lawyer whether the GDPR applies to a particular processing activity and how to meet its requirements.
When the GDPR applies to a Ukrainian company
The Regulation’s territorial scope is set by Article 3. For a company in Ukraine, three situations matter:
- You have an establishment in the EU. Processing in the context of the activities of a branch or other establishment in the EU falls under the GDPR wherever the servers are.
- You offer goods or services to people in the EU — paid or free (Article 3(2)(a)).
- You monitor the behaviour of people in the EU (Article 3(2)(b)).
A separate case is when you process data on behalf of an EU client as a contractor. The Regulation’s requirements then usually reach you through the data processing agreement the client must sign with its processor under Article 28.
Merely using a cloud provider in the EU, however, does not make a Ukrainian company subject to the GDPR — as the European Data Protection Board (EDPB) explains in Guidelines 3/2018. More in “Moving servers to the EU: when it makes sense”.
Signs that you offer services to people in the EU
The mere accessibility of a website from the EU, an email address on the site or the use of Ukrainian does not prove it. The EDPB advises looking at a combination of factors, including:
- the EU or a specific member state is named in the offer;
- advertising or paid promotion aimed at an EU audience;
- a language or currency of an EU country not generally used in Ukraine;
- a domain name such as .de or .eu;
- contact details intended for customers from EU countries;
- mention of customers from various EU countries;
- delivery of goods to EU countries.
What counts as monitoring behaviour
According to the EDPB guidelines, this includes behavioural advertising, geolocation for marketing, online tracking through cookies or other technologies, profiling, CCTV, and market research based on individual profiles.
What the GDPR requires
If the Regulation applies to you, the main obligations are:
- A legal basis for every processing activity (Article 6) and a clear notice to people about how their data is processed (Articles 13–14).
- People’s rights: access, rectification, erasure, portability, objection (Articles 15–22).
- Records of processing activities (Article 30).
- Security of processing (Article 32) — see below.
- Breach notification: to the supervisory authority without undue delay and, where feasible, within 72 hours (Article 33), and to the people affected if the risk to them is high (Article 34).
- Contracts with processors (Article 28).
- Transfers outside the EU (Chapter V). Ukraine is not on the European Commission’s list of countries with an adequate level of protection, so other mechanisms are needed — for example, standard contractual clauses.
- A representative in the EU (Article 27) — for companies outside the EU that fall under the GDPR by offering services or monitoring behaviour, unless the exemption for occasional processing that does not involve large-scale special categories of data and is unlikely to result in a risk applies.
Fines for some infringements reach EUR 20 million or 4% of total worldwide annual turnover, whichever is higher (Article 83).
What IT must do: Article 32
Article 32 requires appropriate technical and organisational measures that take the risks into account. Among them the Regulation explicitly names:
- pseudonymisation and encryption of personal data;
- confidentiality, integrity, availability and resilience of systems and services;
- the ability to restore access to data in a timely manner after a physical or technical incident;
- regular testing of the effectiveness of the measures.
In practice that means:
- encrypting disks, backups and connections;
- least-privilege access, multi-factor authentication, logs of access to personal data;
- backup with tested restores — see “3-2-1 backup rule: protecting business data”;
- monitoring and an incident response plan that makes the 72 hours achievable;
- controlling data leak channels — email, cloud storage, removable media;
- regular checks and testing of the protection.
Ukrainian law is being updated too: bill No. 8153 is meant to bring the personal data protection law closer to the GDPR — see “Ukraine’s new personal data law: what will change”.
Checklist
- You have determined whether you offer services to people in the EU or monitor their behaviour
- You know where you are a controller and where a processor for EU clients
- Every processing activity has a legal basis and a notice for people
- There are records of personal data processing activities
- Contracts with processors and clients include the Article 28 requirements
- The mechanism for transfers between the EU and Ukraine is defined
- The question of an EU representative is settled with your lawyer
- Personal data is encrypted, access is minimal and logged
- Backups are tested, the response plan allows for the 72 hours
- Protective measures are tested regularly
How Bereg-IT can help
We recommend leaving the legal side of the GDPR — legal bases, contracts, the representative — to a lawyer. We help with the technical side: at a consultation or an audit we assess data protection and compliance, implement protective measures — including DLP to control leak channels, set up backup and monitoring, and SOC as a Service helps detect an incident in time and gather the data needed for a notification.
The first consultation is free. Send a request and an information security specialist will get in touch.
Sources
- Regulation (EU) 2016/679 (GDPR), Articles 3, 6, 13–22, 27, 28, 30, 32–34, 83 and Chapter V: https://eur-lex.europa.eu/eli/reg/2016/679/oj
- EDPB, Guidelines 3/2018 on the territorial scope of the GDPR (Article 3), version 2.1 — factors for offering services and monitoring behaviour: https://www.edpb.europa.eu/documents/guideline/guidelines-32018-on-the-territorial-scope-of-the-gdpr-article-3-version-adopted_en
- European Commission, Adequacy decisions: https://commission.europa.eu/law/law-topic/data-protection/international-dimension-data-protection/adequacy-decisions_en
Blog posts are for information only and are not legal advice. Check legal requirements against the current versions of the documents or with a lawyer.