Alex is Sprintlaw’s co-founder and principal lawyer. Alex previously worked at a top-tier firm as a lawyer specialising in technology and media contracts, and founded a digital agency which he sold in 2015.
Using a CRM can make your business feel much more organised. Your leads, customer notes, email history, sales pipeline and follow-ups are finally in one place.
But because your CRM usually stores personal data, it also raises a practical UK GDPR question: do you need a Data Processing Agreement with the CRM provider?
The good news is that this doesn't have to be complicated. For most UK businesses, the answer comes down to whether the CRM provider is processing personal data for you, and whether your contract has the clauses Article 28 of the UK GDPR requires.
Do I Need A Data Processing Agreement With My CRM Provider?
Yes, you usually need a Data Processing Agreement if your CRM provider processes personal data on your behalf.
Under the UK GDPR and the Data Protection Act 2018, a business using a CRM will often be the controller. That means you decide why and how personal data is used, such as storing customer contact details, tracking enquiries or sending follow-up emails.
Your CRM provider will often be the processor. That means it handles that personal data for you, based on your instructions, through its software and hosting services.
If that controller and processor relationship exists, Article 28 of the UK GDPR says you need a written contract containing certain processor terms. In everyday language, that contract is often called a Data Processing Agreement, or DPA.
This can be:
- a standalone DPA you sign separately
- a data processing addendum attached to the CRM's main terms
- processor clauses built into the CRM's subscription agreement
What matters isn't the document title. What matters is whether the required processor terms are actually there.
For example, if you run a small consultancy in Manchester and use a CRM to store client names, emails, phone numbers, meeting notes and invoice contact details, your CRM provider is likely processing personal data for you. You should check whether its terms include a proper DPA before you start uploading customer data.
Is My CRM Provider A Controller Or A Processor?
It depends on what the CRM provider does with the data, but most CRM providers are processors for your customer data.
A CRM provider is usually a processor where it stores, organises, backs up, transmits or analyses personal data so you can manage your customer relationships. You remain the business deciding the purpose of the data use.
For example, you decide to collect a lead's email address so your sales team can follow up. The CRM simply gives you the tool to store and manage that information. That points to a processor relationship.
Sometimes, though, the CRM provider may also be an independent controller for limited purposes. This can happen where it uses personal data for its own account administration, fraud prevention, legal compliance, security monitoring or product analytics. Some providers explain this split in their privacy policy or data protection addendum.
A Simple Way To Test It
Ask yourself these questions:
- Who decides why the customer data is collected? If it's your business, you're likely the controller.
- Who decides what happens to the customer data day to day? If you decide what records to create, update or delete, that points to you being the controller.
- Is the CRM provider mainly providing software, storage and support? If yes, it's likely acting as your processor for that data.
- Can the CRM provider use your customer data for its own marketing or sell it on? If yes, you need to look closely at the terms because that may go beyond ordinary processing.
If the arrangement is mixed, your contract may need both processor terms and clear wording about when each party acts as an independent controller.
What Personal Data In A CRM Triggers UK GDPR Duties?
Any information that identifies, or could identify, a living person can trigger UK GDPR duties, and CRMs often hold a lot of it.
In a CRM, personal data might include:
- names, job titles and workplace contact details
- personal email addresses and mobile numbers
- customer notes, preferences and enquiry details
- call recordings, email threads and meeting notes
- purchase history, quotes, invoices and support tickets
- marketing consent records and unsubscribe status
- IP addresses, device data or website behaviour linked to a person
Business contact details can still be personal data if they relate to an identifiable person. For example, jane.smith@examplecompany.co.uk is personal data even though it's a work email address.
You also need to be careful with sensitive or higher-risk information. The UK GDPR calls some of this special category data, such as health information, racial or ethnic origin, religious beliefs, trade union membership or biometric data used for identification.
Most CRMs don't need special category data. If your team is typing sensitive notes into customer profiles, that can increase your risk and may affect what security controls you need.
Worked Example: A Local Fitness Studio
Maya runs a fitness studio in Leeds with 850 contacts in her CRM. The CRM stores names, email addresses, phone numbers, membership status, attendance notes and marketing preferences.
The studio pays 25 pounds per user each month for 4 staff accounts, so the CRM costs 100 pounds per month before VAT. From a data protection angle, the key point isn't the price. It's that the CRM provider is hosting and organising personal data for Maya's business.
Maya checks the CRM's terms and finds a data processing addendum. It says the provider will process data only on her documented instructions, use appropriate security measures, help with data subject requests and notify her of personal data breaches without undue delay. That's the right starting point. She still needs to check whether the addendum covers international transfers and sub-processors.
What Should A CRM Data Processing Agreement Include?
A CRM Data Processing Agreement should include all mandatory processor terms under Article 28 of the UK GDPR.
At a practical level, this means the DPA should clearly explain what the CRM provider can and can't do with your customer data. It should also give you enough visibility over security, sub-processors, deletion and support with compliance requests.
A good DPA for a CRM or SaaS provider should cover:
- Subject matter and duration: what services the CRM provides and how long processing continues.
- Nature and purpose of processing: for example, hosting, storing, organising, analysing and backing up CRM records.
- Types of personal data: such as names, contact details, notes, purchase history and marketing preferences.
- Categories of data subjects: such as customers, leads, suppliers, staff contacts or business partners.
- Your documented instructions: the provider should only process personal data as you instruct, unless UK law requires otherwise.
- Confidentiality: people authorised to access the data must be under confidentiality duties.
- Security measures: technical and organisational measures should be suitable for the risk, such as access controls, encryption, backups and logging.
- Sub-processors: the provider shouldn't appoint others without the required authorisation and flow-down obligations.
- Help with compliance: support for data subject requests, security obligations, breach handling and data protection impact assessments where relevant.
- Deletion or return: what happens to the personal data when the service ends.
- Audit and information rights: enough information for you to check compliance, usually through reports, certifications or reasonable audit rights.
A data processing schedule or template can be useful as a starting point, but processor terms work best when they're tailored to the software, the data involved and the provider's actual security setup.
A Fill-In Outline To Use Before Drafting
If you're preparing instructions for a lawyer or reviewing a CRM provider's template, this outline can help you collect the right details. It isn't a finished legal document, and a lawyer should tailor it before you use it.
- Parties: write the legal names of your business and the CRM provider.
- Roles: state when your business is controller and when the provider is processor.
- Services: describe the CRM services, support, hosting and integrations.
- Processing Details: list the purpose, duration, data types and data subject categories.
- Instructions: explain that processing must follow your documented instructions.
- Security: summarise access controls, encryption, backups, incident management and staff controls.
- Sub-Processors: set out approval, notice and objection processes.
- International Transfers: record where data may be accessed or stored and what transfer mechanism applies.
- Assistance: cover help with requests, breaches, DPIAs and regulator enquiries.
- End Of Contract: set out return, deletion, backups and certification of deletion where appropriate.
What Should I Ask My CRM Provider Before Signing?
You should ask for the CRM's DPA, security information, sub-processor list and international transfer details before you upload customer data.
Most established CRM providers already have a data processing addendum. The issue is whether it fits your business and whether it leaves any gaps you can't accept.
Here are practical questions to ask:
- Do your terms include an Article 28 processor agreement? Ask for the current version and check whether it forms part of the contract automatically or needs signing.
- Where is the data hosted and accessed from? You need to know if personal data leaves the UK.
- Who are your sub-processors? This might include cloud hosting providers, support tools, email infrastructure and analytics services.
- How will you notify us of a personal data breach? You may need to assess whether to notify the Information Commissioner's Office within 72 hours of becoming aware of a notifiable breach.
- Can we export and delete our data when the contract ends? This matters if you later move to another CRM.
- What security controls are included on our plan? Some controls, such as single sign-on or audit logs, may only be available on higher tiers.
- Do you use our customer data to train AI models or improve your products? If yes, check whether that use is optional, anonymised, aggregated or outside your instructions.
You should also check the main subscription terms, not just the DPA. Limitation of liability, service availability, support response times, suspension rights and termination rights can all affect your business if the CRM goes down or data is lost.
What If My CRM Provider Is Outside The UK?
You can use an overseas CRM provider, but you need to check the UK GDPR rules on international transfers.
A transfer can happen when personal data is stored outside the UK, accessed by support teams overseas, or made available to sub-processors in another country.
If data goes to a country covered by UK adequacy regulations, the transfer may be allowed on that basis. If not, you may need an appropriate transfer tool, such as the UK's International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses.
You may also need a transfer risk assessment. This is a practical review of whether the personal data will receive a level of protection that's close enough to the UK standard, taking into account the country, the data, the provider's security measures and the contract terms.
For many small businesses, this comes up when using popular US-based SaaS tools. The CRM may have UK or EU data centres, but support access, backups or sub-processors can still involve other countries.
Don't assume that a well-known provider has everything covered for your setup. Ask where your account data is hosted, whether you can choose a region, and which transfer documents apply.
Common Mistakes To Avoid
The biggest mistake is assuming the CRM's standard terms are enough without checking whether they contain UK GDPR processor clauses.
Other common mistakes include:
- Uploading data before reviewing the DPA: once your team starts using the CRM, it can be harder to unwind the arrangement.
- Forgetting integrations: email marketing tools, calendars, call recording apps and automation platforms may create extra processors.
- Using one shared login: this makes it harder to control access and track who did what.
- Keeping old leads forever: your retention approach should match your privacy notice and business need.
- Recording sensitive notes casually: staff may add health, financial or personal comments that don't belong in the CRM.
- Ignoring breach processes: if something goes wrong, you need to know who contacts whom, what records to keep and how quickly you'll be told.
- Not checking exit rights: make sure you can export data in a usable format and have it deleted when you leave.
A simple internal CRM policy and privacy policy can help. Tell your team what can be entered into the CRM, who can access it, how to handle deletion requests and who to notify if there's a suspected breach.
If your CRM holds a lot of customer data, special category data or data about children, it's worth getting tailored advice before you rely on standard SaaS terms.
Key Takeaways
- You usually need a Data Processing Agreement if your CRM provider processes personal data for your business.
- The DPA should meet Article 28 of the UK GDPR and cover instructions, security, sub-processors, assistance, deletion and audit rights.
- Your CRM provider is usually a processor for customer data, but it may be an independent controller for some of its own business purposes.
- Check where your CRM stores and accesses data, especially if the provider or its sub-processors are outside the UK.
- Review the main SaaS terms as well as the DPA, because liability, support, termination and data export rights matter too.
- Templates can help you plan, but CRM data processing terms should be tailored to your data, tools and risk profile.
If you'd like help with reviewing your CRM provider's terms, drafting a tailored Data Processing Agreement, checking international transfer wording or updating your privacy documents, you can reach us at 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.
Get your customer-facing terms right
What should your privacy and online terms cover?
If you collect customer data, sell online or run marketing campaigns, your public terms and privacy documents should match the real customer journey.






