SaaS GDPR compliance: processor duties, DPAs and when a SaaS company needs a DPO
A SaaS company is a processor for personal data it processes on behalf of its customers, and a controller for data it uses for its own purposes. As a processor it needs an Article 28 contract (DPA) with each customer and Article 30(2) records, and it needs a DPO only if an Article 37(1) trigger applies to its own core activities.[1]
This guide is for US software companies with customers or users in the EU. It sticks to what the GDPR and the EDPB guidance say. For a quick first answer on your own case, use the DPO and EU representative checker.
Is your SaaS company a controller or a processor?
The GDPR defines the two roles in Article 4:[1]
- Controller (Art. 4(7)): the person or body that, alone or jointly with others, determines the purposes and means of the processing of personal data.
- Processor (Art. 4(8)): a person or body that processes personal data on behalf of the controller.
When a customer uploads its own customers' or employees' data and your product processes it on the customer's behalf, the customer is the controller and you are the processor for that data. When you decide the purposes and means yourself, for example for your own marketing, you are a controller for that processing. The EDPB's guidelines on controller and processor explain that the roles depend on the actual activities in a specific situation, so one company can be a processor for some processing and a controller for other processing.[2]
The Article 28 contract (DPA)
Processing by a processor must be governed by a contract or other legal act that binds the processor to the controller (Art. 28(3)). In SaaS this is usually called a data processing agreement, or DPA.[1] The contract must set out the subject matter, duration, nature and purpose of the processing, the type of personal data, the categories of data subjects and the controller's obligations and rights. It must also require the processor to:
- process the data only on the controller's documented instructions;
- ensure that people authorized to process the data are bound by confidentiality;
- take the security measures required by Article 32;
- respect the conditions for engaging sub-processors (Art. 28(2) and 28(4));
- help the controller respond to data subject rights requests;
- help the controller with security, breach notification, DPIAs and prior consultation (Arts. 32 to 36);
- delete or return all personal data at the end of the service, as the controller chooses; and
- make available the information needed to demonstrate compliance, and allow for audits.
Before that, the controller may only use processors that provide sufficient guarantees of appropriate technical and organizational measures (Art. 28(1)).[1] Under Article 28(2), a processor may not engage another processor without the controller's prior specific or general written authorization.
Records of processing for processors (Article 30(2))
Each processor, and where applicable its representative, must keep a record of all categories of processing it carries out on behalf of a controller (Art. 30(2)).[1] The record must contain:
- the name and contact details of the processor and of each controller it acts for, and, where applicable, of their representatives and DPOs;
- the categories of processing carried out on behalf of each controller;
- transfers of personal data to a third country or international organization, where applicable; and
- where possible, a general description of the technical and organizational security measures.
Article 30(5) exempts organizations with fewer than 250 employees, but not if the processing is likely to result in a risk to people's rights and freedoms, is not occasional, or includes special category or criminal offense data.[1] Check each of these conditions before relying on the exemption.
When does a SaaS company need a DPO?
Article 37(1) says "the controller and the processor" shall designate a DPO when one of three triggers applies.[1] For a SaaS company the relevant ones are usually:
- (b) core activities that consist of processing which requires regular and systematic monitoring of people on a large scale; or
- (c) core activities that consist of processing special category data (Art. 9) or criminal offense data (Art. 10) on a large scale.
The test applies to the processor in its own right. The EDPB-endorsed DPO guidelines (WP243) explain that, depending on who meets the criteria, sometimes only the controller, sometimes only the processor, and sometimes both must designate a DPO.[3] When processing customer data is what the product does, it can be a core activity of the SaaS company. The guidelines list examples of regular and systematic monitoring such as behavioral advertising, email retargeting, location tracking by apps and fitness or health tracking via wearables.[3]
If no trigger applies and no national law requires one, the GDPR does not require a DPO. The guidelines recommend documenting that analysis.[3] If you do need one, Article 37(6) allows a DPO under a service contract: see how outsourced DPO services work and the published prices for outsourced DPOs.
EU representative for a US SaaS company
A US SaaS company with no EU establishment comes under the GDPR when it offers its service to people in the EU or monitors their behavior there (Art. 3(2)). It must then usually designate an EU representative in writing under Article 27, which applies to controllers and processors, unless the Article 27(2) exemption applies.[1] The EDPB's guidelines on territorial scope explain both the targeting test and the representative.[5]
Published EU representative prices start at ≈ $320*1 per year (REP27 Base, excl. VAT).[6] The EU representative guide, with prices from 6 providers, explains who needs one and what it does.
SaaS GDPR checklist
A short list drawn from the articles above. It is a starting point, not a full program.
- Map which processing you do as a controller and which as a processor.
- Have an Article 28 DPA with each customer, and with each of your own sub-processors.
- Keep Article 30 records for both roles, unless the narrow 30(5) exemption clearly applies.
- Assess the Article 37(1) triggers for your own core activities, and document the result.
- If you have no EU establishment but target or monitor people in the EU, designate an Article 27 representative.
Selling to US health care customers too? The HIPAA privacy officer guide explains covered entities and business associates. Selling to schools? See ed tech privacy compliance.
Frequently asked questions
Is a SaaS company a controller or a processor under GDPR?
It can be both. It is a processor for personal data it processes on behalf of its customers, and a controller for processing where it decides the purposes and means itself. The role is decided per processing activity.[1][2]
Does a SaaS company need a DPO?
Only if an Article 37(1) trigger applies to its own core activities, or national law requires one. Article 37(1) applies to processors as well as controllers, so a SaaS processor whose core activities involve large-scale regular and systematic monitoring, or large-scale special category data, needs a DPO.[1][3]
What is a DPA in SaaS?
A data processing agreement: the contract that Article 28(3) requires between a controller and a processor. It must cover, among other things, processing only on documented instructions, confidentiality, security, sub-processors, help with data subject requests, and deletion or return of data at the end of the service.[1]
Does a US SaaS company need an EU representative?
Usually, if it has no EU establishment and Article 3(2) brings it under the GDPR, unless the Article 27(2) exemption applies. Article 27 applies to controllers and processors.[1]
Next steps
- Run the DPO checker for a rough first answer.
- Read the guide to DPO as a service.
- See what outsourced DPO providers charge.
Currency notes
Amounts marked ≈ were published in another currency and are shown in US dollars, converted at 1 EUR = 1.0990 USD (ECB euro reference rate) from the ECB euro foreign exchange reference rates of , and rounded to the nearest $10. The amounts themselves (fees, fine limits, insurance cover) are set in the original currency, so the dollar figure is approximate and moves with exchange rates.
- ≈ $320: published as €290, converted at 1 EUR = 1.0990 USD (ECB euro reference rate, ).
Sources
- Regulation (EU) 2016/679 (General Data Protection Regulation), official text on EUR-Lex (accessed )
- EDPB Guidelines 07/2020 on the concepts of controller and processor in the GDPR (accessed )
- Article 29 Working Party, Guidelines on Data Protection Officers (WP243 rev.01), endorsed by the EDPB (accessed )
- Article 29 Working Party, Guidelines on Data Protection Officers (WP243 rev.01), full text (PDF) (accessed )
- EDPB Guidelines 3/2018 on the territorial scope of the GDPR (Article 3) (accessed )
- REP27, Pricing (accessed )
- European Central Bank, euro foreign exchange reference rates (rates of 20 November 2026, used to convert prices to US dollars) (accessed )