Skip to main content
GDPR compliance guide for companies: obligations and step-by-step plan

GDPR compliance guide for companies: obligations and step-by-step plan

Written By
16 min read

TLDR

The GDPR applies to every organisation that processes personal data of EU residents, regardless of size or where it is established. Core obligations are a legal basis for each processing activity, handling data subject requests within 30 days, data processing agreements with every external processor, reporting qualifying data breaches to the Dutch Data Protection Authority within 72 hours, and a record of processing activities. Fines reach EUR 20 million or 4% of global annual turnover for the most serious infringements. Start by mapping your data.

You process customer data. Perhaps you have for years. Then comes the moment when someone asks: "And your GDPR compliance, how does that work?" That could be a customer who wants a data processing agreement, an investor digging deeper during due diligence, or an (internal) audit on the horizon. Sometimes it is simply the realisation that your organisation has grown and that you need something structured. Whatever the trigger, the GDPR is a law, and it is better to know what that means now than when something goes wrong.

This article explains what the GDPR involves, who it applies to, what your obligations are, and how to get started step by step.

What is the GDPR and who does it apply to?

The GDPR (General Data Protection Regulation) is the European privacy legislation that has been in force since 25 May 2018. Formally: EU 2016/679. The regulation applies directly in all EU member states, without national transposition being needed. In the Netherlands, the Dutch Data Protection Authority (Autoriteit Persoonsgegevens, AP) enforces compliance.

The GDPR governs how organisations may collect, store, use and share personal data of EU residents. The definition of "personal data" is broad: a name, email address, IP address, phone number, location data, essentially anything with which you can directly or indirectly identify a person falls under it.

The GDPR applies to every organisation that processes personal data of EU residents. Where your organisation is established makes no difference. An American SaaS company with European customers falls under it too.

Within the GDPR there are two key roles:

  • Data controller: you determine the purpose and means of the processing. If you decide which customer data you collect and what for, you are the controller.
  • Data processor: you process personal data on behalf of a controller. Think of a payroll administration office or a cloud provider hosting your data.

There is no minimum threshold in terms of company size. Small companies and startups that process personal data must also comply with the GDPR.

One of the concrete obligations is the RoPA (Record of Processing Activities). This is an internal overview in which you record which personal data you process, for which purpose, with whom you share it and how long you keep it. It follows from Article 30 of the GDPR and is often the first document a supervisory authority asks for during an inspection.

Organisations with fewer than 250 employees are exempt from the RoPA obligation, unless the processing is regular, involves special categories or carries a high risk. The core obligations apply to everyone.

The core obligations

Legal bases

Every processing of personal data needs a legal basis. You may not simply process data because it is convenient. The GDPR recognises six bases:

  1. Consent - the data subject has agreed freely, specifically, in an informed way and unambiguously. Consent may not be set as a condition for a service, and must be easy to withdraw.
  2. Performance of a contract - the processing is necessary to carry out a contract with the data subject.
  3. Legal obligation - you are required to process the data under laws or regulations.
  4. Vital interests - the processing is necessary to protect someone's life.
  5. Public task - relevant for government bodies and public organisations.
  6. Legitimate interest - your organisation has a legitimate interest that outweighs the privacy interests of the data subject. This is a balancing exercise you must be able to substantiate.

Document for each processing activity which basis you use. If your basis is consent, make sure you can demonstrate that consent.

Data subject rights

People whose personal data you process have legal rights. You are obliged to respect those rights and handle requests in good time: in principle within 30 days.

The rights are:

  • Right of access - someone may request which data you hold about them and what you use it for.
  • Right to rectification - incorrect data must be corrected.
  • Right to be forgotten - in certain cases you must erase data on request.
  • Right to restriction of processing - someone can ask you to stop the processing temporarily.
  • Right to data portability - transferring data to another service provider, in a readable format.
  • Right to object - data subjects can object to processing based on legitimate interest or for direct marketing.

Set up an internal process for handling these requests. Who receives them? Who assesses them? Who ensures they are carried out? Without a working process you will not meet the 30-day deadline.

Data processing agreements

Do you work with external parties that process personal data on your behalf? Then you are obliged to conclude a data processing agreement. This is not optional, it is a hard requirement of the GDPR.

Think of: cloud providers, CRM suppliers, marketing platforms, payroll processors, and IT administrators with access to your systems. For each of these parties you need a written agreement setting out what they may do with the data, how they secure it, and how they report a data breach to you.

Reporting data breaches

A data breach is any security incident in which personal data is unintentionally or unlawfully exposed, lost, altered, or made accessible to unauthorised people. Think of a stolen laptop, a phishing attack in which customer data was taken, or a misaddressed email with privacy-sensitive attachments.

If a data breach poses a risk to the data subjects, you must report it to the Dutch Data Protection Authority within 72 hours. If the risk is high, you must also inform the data subjects themselves. 72 hours is relatively short. Without a documented internal process (who does what, who decides, who reports) you will almost certainly miss that deadline. Draw up a basic protocol before you need it.

Record of processing activities

The record of processing activities (also: RoPA - Records of Processing Activities) is an internal document in which you keep track of all processing activities. For each activity you record:

  • Which personal data you process
  • For which purpose
  • On which legal basis
  • How long you keep the data
  • Who has access to it
  • Whether there is any transfer outside the EU/EEA

For organisations with 250 or more employees the record of processing activities is mandatory. For smaller organisations it is mandatory if the processing is regular, involves special categories of data, or carries a high risk. In practice we recommend every organisation keep one, because it is the basis for almost all your other GDPR obligations.

Special categories of personal data

The GDPR provides an extra level of protection for sensitive categories of data. These are:

  • Health data
  • Biometric data (for identification purposes)
  • Genetic data
  • Race or ethnic origin
  • Political opinions
  • Religious or philosophical beliefs
  • Trade union membership
  • Data on sexual behaviour or sexual orientation

In principle you may not process this data, unless you fall under one of the legal exceptions. In that case you must take additional technical and organisational measures. If your company processes this kind of data on a large scale, chances are you also need a Data Protection Officer (DPO).

Enforcement and fines

The GDPR is enforced by national supervisory authorities. In the Netherlands that is the Dutch Data Protection Authority. They can open investigations, issue binding instructions and impose fines.

The fine framework has two levels:

  • Up to EUR 10 million or 2% of global annual turnover (whichever is higher) for less serious infringements, such as missing data processing agreements or an incomplete record of processing activities.
  • Up to EUR 20 million or 4% of global annual turnover for the most serious infringements, such as breaching core principles or data subject rights.

A few well-known fines by way of illustration: Meta was reportedly fined EUR 1.2 billion in 2023 by the Irish Data Protection Commission (DPC) for unlawful transfer of personal data to the US. Amazon reportedly received a fine of EUR 746 million in 2021. WhatsApp reportedly paid EUR 225 million for transparency infringements.

These are exceptions, large companies with large breaches. But smaller organisations also receive fines, and the reputational damage of an enforcement process is disproportionately large for an SME.

GDPR compliance in practice

Building compliance feels overwhelming if you see it as one big block. It becomes manageable once you break it up. Here is a workable order.

Step 1 - Map your data. What kind of personal data do you collect, from whom, for which purpose, where does that data sit, and who has access to it? This is your foundation. Without this overview you cannot carry out any of the following steps properly.

Step 2 - Determine your legal bases. For each processing activity, work out which basis you are relying on. Is it consent? A contract? A legitimate interest? Record the choice and the reasoning.

Step 3 - Write or update your privacy notice. Your privacy notice is what data subjects see. Make sure it matches your actual processing: who you are, what you collect, why, how long you keep it, and which rights people have.

Step 4 - Conclude data processing agreements. Make a list of all external parties that process personal data for you. Check whether you have a valid data processing agreement with each of them. If one is missing, that is your first priority.

Step 5 - Set up a process for data subject requests. Who receives an access request? Who assesses whether it is justified? Who carries it out? Make sure this is assigned internally before anyone submits a request.

Step 6 - Draw up a data breach protocol. Write down who does what when a data breach is discovered. Who decides whether it must be reported? Who reports it to the AP? The 72-hour deadline starts as soon as you become aware of the breach.

Step 7 - Build your record of processing activities. Record all processing activities in a structured register. Start with the processing that carries the greatest risk or involves the most data.

Step 8 - Check international transfers. Do you send personal data outside the EU/EEA? Then you need an additional mechanism, such as Standard Contractual Clauses (SCCs) or an adequacy decision for the receiving country. Think of tools that store data on American servers.

A risk assessment helps you prioritise: which processing carries the most risk and therefore deserves the most attention? And you record the controls you implement so that you can demonstrate at an audit what you have done.

GDPR and other frameworks

The GDPR rarely stands alone. Many organisations working on the GDPR also have to deal with ISO 27001 (the international standard for information security) or with NIS2, the European directive for network and information security. The overlap is noticeable.

ISO 27001 requires a risk assessment and controls for information security that overlap directly with the GDPR requirements for securing personal data. NIS2 sets comparable requirements for incident response and risk management. If you tackle three frameworks separately, you do a lot of work twice.

A governance, risk and compliance approach (GRC) brings those frameworks together in one structure. You carry out one risk assessment, implement measures that cover several frameworks, and maintain one set of documentation. That is more efficient and gives a better overall picture.

One of the strengths of Tidal Control is exactly this: managing GDPR, ISO 27001, NIS2 and other frameworks in a single platform. The policy centre holds your privacy notice and data processing agreements. The risk register covers your GDPR-related risks. Tidal's controls show you which measures fit and have been implemented. The issues module tracks data subject requests and data breach procedures.

Not sure where to start?

Take the free Quickscan → and find out in five minutes where your organisation stands on GDPR compliance.

Frequently asked questions about GDPR compliance

Does the GDPR also apply to small companies?

Yes. There is no minimum threshold for company size. Every organisation that processes personal data of EU residents falls under the GDPR. Organisations with fewer than 250 employees have lighter documentation obligations in certain situations. For them, the record of processing activities is only mandatory if the processing is regular, involves special categories or carries a high risk. The core obligations apply in full.

What is the difference between a controller and a processor?

A controller determines the purpose and means of the processing: you decide which data you collect and what for. A processor processes personal data on behalf of a controller, without determining the purpose itself. A cloud provider hosting your customer data is a processor. You are the controller. There must be a data processing agreement between the two.

What counts as a data breach?

A data breach is any breach of security leading to unintentional or unlawful loss, unauthorised access, destruction, alteration, or disclosure of personal data. A stolen laptop with customer data, a misaddressed email, or access by an unauthorised employee all count. Not every breach has to be reported, only breaches that pose a risk to the data subjects.

When do I need a Data Protection Officer (DPO)?

A DPO is mandatory for government bodies, organisations that process special categories of personal data on a large scale, and organisations that systematically monitor people on a large scale. Many commercial companies do not fall under this, but appointing a DPO (internal or external) can still be useful if you work intensively with privacy-sensitive data.

How long may I keep personal data?

The GDPR has no fixed retention periods. These depend on the purpose of the processing and any legal obligations. The principle is: you do not keep data longer than necessary for the purpose for which you collected it. Define a retention period for each category and record it in your record of processing activities and privacy notice. Do not forget to actually erase data once the period has expired.


Want to know where your organisation stands on GDPR compliance and get help mapping this out? Schedule an introduction with our team →

Subscribe now for monthly updates: what's new at Tidal, framework news, and compliance resources.

By submitting your email you agree to our Privacy Policy.