If you run a SaaS business with customers in the UK or EU, UK GDPR and EU GDPR apply to you, and probably in more than one way. Plenty of founders assume compliance means a privacy policy and a cookie banner. It doesn’t.

This post covers the GDPR obligations SaaS founders miss most, from contracts and sub-processors to user rights and product design. It ends with the order to tackle them in if you’re starting from scratch.

Contents

  1. You Are Probably Both a Controller and a Processor
  2. Your Customer DPAs Are Legally Required
  3. Sub-Processors Are Your Responsibility Too
  4. DSARs Apply to Your User Data Too
  5. Your Analytics and Marketing Stack Has GDPR Implications
  6. Privacy by Design Is Not Optional
  7. What to Prioritise If You Are Starting from Scratch

You Are Probably Both a Controller and a Processor

Most SaaS companies wear two hats. When your customers upload their own data into your platform, such as their customer lists, employee records, or support tickets, you process it on their behalf. For that data, you’re a processor, and your customer is the controller.

For everything else, you’re the controller. That covers your own account records, billing details, sales leads, website visitors, and any product analytics you use for your own purposes.

Why the Distinction Matters

Each role carries different duties and different exposure. Under Article 82, a processor is liable for damage only where it breaks its processor duties or acts outside the controller’s instructions. Your contracts, insurance cover and internal processes should all reflect which role you hold for each type of data.

When You Become a Controller Without Meaning To

The line moves when you use customer data for your own ends. Training an AI model on it, building benchmarks across tenants or mining it for product decisions all make you a controller for that use. You then need your own lawful basis, and your customer contract has to allow it, or you’ve stepped outside your instructions.

Your Customer DPAs Are Legally Required

Under GDPR, B2B SaaS businesses can’t process customer data on a handshake. Article 28 requires a written contract between controller and processor, and that’s the data processing agreement SaaS customers expect to sign or review.

The DPA must set out what you process, why, for how long and for whom. It must also commit you to:

  • Acting only on instructions: You process data only as your customer directs, including for international transfers.
  • Confidentiality and security: Your staff are bound to confidentiality, and your security meets the standard in Article 32.
  • Help with rights and breaches: You support your customer with access requests, breach reporting and impact assessments.
  • Deletion or return: You delete or hand back customer data when the contract ends.
  • Audits: You provide the information your customer needs to check compliance, and allow audits.

Why a Click-Through Rarely Covers It

Many SaaS terms mention data protection in a line or two and stop there. That falls short of what Article 28 lists. Enterprise buyers will spot the gap during due diligence, so a standalone DPA saves time on every deal.

Plan for International Transfers

Your DPA also needs to cover where data goes. If you host in the US or use support staff overseas, each restricted transfer needs a valid route, such as UK adequacy, the UK Extension to the EU-US Data Privacy Framework, or the International Data Transfer Agreement. Customers will ask which route you rely on for each sub-processor.

Sub-Processors Are Your Responsibility Too

Stripe, AWS, Intercom and HubSpot are all sub-processors if they touch your customers’ data. So are your hosting provider, email service, and support tools. This is one of the most common founder blind spots in SaaS data protection.

Article 28 sets three rules for them. You need your customer’s written authorisation before using a sub-processor, which can be general rather than case by case. If it’s general, you must tell customers about new or replacement sub-processors and give them the chance to object. You must also pass the same data protection obligations down to every sub-processor by contract.

Keep a Public Sub-Processor List

The simplest way to meet the notice duty is a sub-processor page that lists each provider, what it does and where it processes data. Pair it with a way for customers to subscribe to changes. You stay fully liable to your customers if a sub-processor fails, so check each one’s security and contract terms before you add it.

DSARs Apply to Your User Data Too

Data subject rights reach into your product. People can ask to access their data, take a copy in a portable format under Article 20, or have it erased. You normally have one month to respond.

Your role decides who answers. Requests about your own users and leads come to you as controller. Requests about data your customers hold in your platform go to them, but you must help them respond, because that’s part of your DPA.

Build Rights Handling into the Product

Multi-tenant platforms make this harder, because one person’s data can be spread across several tables, backups, and logs. Build export and deletion tools early, scoped to each tenant, and test them before your first big customer asks. Retrofitting them at scale costs far more than designing them in.

Your Analytics and Marketing Stack Has GDPR Implications

Your website and product tools collect personal data too, and UK users bring a second law into play. The Privacy and Electronic Communications Regulations (PECR) apply alongside UK GDPR and cover cookies, tracking and electronic marketing.

Cookies and Analytics

The ICO’s final April 2026 storage and access technologies guidance lets you use analytics without consent, but only for statistics that improve your service. Third-party tools such as Google Analytics 4 qualify only if the provider acts as your processor and uses the data for that purpose alone. Advertising and retargeting tags still need consent.

Marketing Emails

PECR treats business and individual inboxes differently. You can email corporate subscribers without consent, as long as you identify yourself and offer an easy opt-out. Sole traders and some partnerships count as individuals, so they need consent or a valid soft opt-in.

Privacy by Design Is Not Optional

Article 25 requires data protection by design and by default. In practice, that means three things for a SaaS product:

  • Data minimisation: Collect only the fields each feature needs.
  • Private defaults: New accounts start with the most privacy-friendly settings, and users opt in to more sharing.
  • Retention limits: Data expires on a schedule, rather than living forever in your database and backups.

Building It into Your Sprints

Add a short privacy check to your definition of done. When a feature touches personal data, ask what it collects, who can see it, how long it’s kept, and whether it needs a DPIA. Keep the answers in the ticket, so you have a record when a customer or the ICO asks.

Breach Reporting Runs Through Your Customers

Security incidents also change shape in SaaS. As a processor, you must tell affected customers about a breach without undue delay, so they can decide whether to report it to the ICO within 72 hours. Set out your notice period in the DPA and rehearse it, because a slow alert from you shortens their deadline.

What to Prioritise If You Are Starting from Scratch

Getting GDPR for SaaS right is easier early, while your stack and contracts are still small. Early fixes cost far less than late ones under GDPR. SaaS startup teams can work through this list in order:

  1. DPAs: Publish a standard DPA that meets Article 28, ready for every customer.
  2. Privacy notice: Explain what you collect as a controller, why, and who receives it.
  3. Sub-processor list: Publish it and set up change notices.
  4. Rights requests: Build a process and product tools for access, export, and deletion.
  5. Consent mechanism: Set up cookie controls that separate exempt analytics from advertising tags.
  6. Security measures: Document access controls, encryption and incident response to the Article 32 standard.

Good SaaS privacy compliance builds trust as well as meeting the law. Enterprise buyers ask for most items on this list during due diligence, and having them ready shortens your sales cycle. It also gives you a base to build on when you add EU customers, new markets or certifications such as ISO 27001.

Not Sure Where Your Product Stands?

Our team reviews your contracts, sub-processors and product controls against UK GDPR and EU GDPR, then gives you a ranked list of fixes. For SaaS data privacy, UK founders get advice that fits how their product actually handles data, not a generic template. Good SaaS compliance, UK or EU, starts with knowing exactly what your platform does with personal data.

Get a SaaS GDPR compliance review from KEWDATA.

Leave A Comment

Receive the latest news in your email
Table of content
Related articles