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.
Whether you’re running an online store, managing client data, or employing a team in the UK, the General Data Protection Regulation (GDPR) is a reality every business owner must face. As data protection laws tighten and customers demand transparency, there’s no skirting around compliance - especially when it comes to the paperwork. Getting your GDPR documentation right isn’t just bureaucratic “box ticking” - it’s your best tool for proving you take privacy seriously (and avoiding a world of pain if the ICO ever comes calling).
If you’re looking to set up your GDPR compliance foundation, keep reading - this guide takes you through the absolute must-have documents for GDPR compliance regulations in the UK, explaining what goes in them, who they’re for, and where most businesses slip up.
What Is A GDPR Compliance Pack In The UK?
A GDPR compliance pack is the bundle of documents, records and processes your business uses to show it handles personal data lawfully. There's no statutory document called a GDPR compliance package, and the ICO doesn't require every small business to use the same template. What matters is that your documents match what your business actually does with personal data.
GDPR compliance regulations are built around accountability. That means you need to comply with the law and be able to show how you comply.
Does UK GDPR Apply To Your Business?
The UK GDPR, alongside the Data Protection Act 2018, applies to personal data. Personal data is any information that can identify a living person, directly or indirectly. It's broader than many business owners expect.
You're likely handling personal data if you collect or store:
- customer names, emails, phone numbers or delivery addresses
- staff, contractor or job applicant records
- supplier contacts or sole trader details
- payment and order histories
- IP addresses, cookie IDs or analytics identifiers
- CCTV footage, call recordings or access logs
- health information, equality monitoring data or criminal record information
It doesn't matter whether you're a company, sole trader, charity, ecommerce store, consultancy, agency, clinic, SaaS business or franchise. If you decide why and how personal data is used, you're usually a controller. If you process personal data for another business on their instructions, you may be a processor. Many businesses are both, depending on the activity.
The risks aren't only regulatory. Poor data protection documentation can delay supplier onboarding, block enterprise contracts, weaken customer trust and make a data breach much harder to manage. The ICO can also issue significant penalties for serious breaches, including fines of up to £17.5 million or 4% of annual worldwide turnover, whichever is higher.
Which GDPR Documents Are Mandatory, Best Practice Or Triggered?
Not every GDPR document is mandatory for every business. A good business compliance package separates documents you need now from documents you only need when a particular risk or activity arises.
Documents and records most businesses will need include:
- Privacy notices: you must give people clear information about how you use their personal data. Most businesses need at least a website or customer privacy notice, and employers should also give staff and job applicants appropriate privacy information.
- Lawful basis records: you need to know and record why each use of data is lawful, such as contract, legal obligation, legitimate interests or consent.
- Retention rules: UK GDPR requires you not to keep personal data longer than necessary, so you need a clear way to decide and evidence retention periods.
- Processor contract terms: Article 28 terms are needed where a supplier processes personal data on your behalf as a processor. For an ecommerce platform, payment provider or email platform, first identify whether the supplier is acting as your processor, an independent controller or another role.
- Subject access request procedure: individuals can ask for access to their personal data, and you usually have one month to respond.
- Personal data breach procedure: if a breach is likely to risk people's rights and freedoms, you usually need to notify the ICO within 72 hours of becoming aware of it. If there's a high risk to individuals, you may also need to tell them without undue delay.
- Complaints procedure: since 19 June 2026, controllers have had to facilitate data protection complaints, acknowledge complaints received on or after that date within 30 days, take appropriate steps to respond and inform the complainant of the outcome.
Extra documents may be triggered if your business does certain things. You may need a Data Protection Impact Assessment for high risk processing, an appropriate policy document if you rely on certain conditions for special category data or criminal offence data, cookie and direct marketing records under PECR, a CCTV policy, an international transfer safeguard, or an employee monitoring or AI assessment.
You may also need to pay the ICO data protection fee unless an exemption applies. The amount depends on your organisation's size and type, and the ICO's data protection fee page is the best place to confirm the current fee and exemptions.
The Core GDPR Documents Your Company Can't Skip
1. Privacy Policy Or Privacy Notice
Your privacy policy is your public explanation of how you collect and use personal data.
Your privacy notice should cover:
- Who you are: your business name and contact details.
- What data you collect: for example names, emails, account details, payment information, delivery addresses, staff records, cookies or analytics data.
- Where the data comes from: such as website forms, purchases, enquiries, recruitment applications, referrals or third party platforms.
- Why you use it: each purpose, such as fulfilling orders, providing services, managing staff, sending marketing or meeting legal obligations.
- Your lawful basis: the legal reason for each purpose.
- Who you share data with: for example payment providers, hosting providers, accountants, delivery companies, CRM tools or professional advisers.
- International transfers: whether data leaves the UK and what safeguard you rely on.
- Retention periods: how long you keep each category, or the criteria you use to decide.
- Individual rights: access, rectification, erasure, restriction, objection, portability and complaint rights where applicable.
- How to contact you: including the route for privacy queries and complaints.
If you operate online, your website's terms and privacy policy should line up with your real checkout, marketing, analytics and customer support processes. For a more detailed breakdown, see our privacy policy guide.
2. Data Protection Policy
A privacy notice is for the outside world. A data protection policy is for your team. It sets out how your business handles personal data internally, so staff know what to do and managers can enforce consistent standards.
Your data protection policy should cover:
- who owns data protection compliance in the business
- how staff should collect, access, use and share personal data
- password, device, remote working and access controls
- rules for using personal email, messaging apps and file sharing tools
- how to handle subject access requests, erasure requests and complaints
- how to report suspected breaches internally
- training expectations and consequences of non compliance
This is especially important if you're growing your team. For more on the role of internal policies, see our guide on workplace policies and staff handbooks.
3. Record Of Processing Activities Or Data Register
A Record of Processing Activities, often called a RoPA, is your map of what personal data your business uses. A full Article 30 RoPA is required if you have 250 or more employees. Businesses with fewer than 250 staff may still need Article 30 records for processing that isn't occasional, is likely to risk people's rights and freedoms, or involves special category or criminal offence data.
If you're documenting higher risk data flows, our guide to privacy impact assessments explains how DPIAs fit into risk management.
Worked Example: An Online Retailer Building A GDPR Package
Imagine you run a UK ecommerce store called Brighton Home Co. You have 8 employees, around 12,000 customer accounts, a Shopify style store, a payment provider, an email marketing platform, Google Analytics, a courier integration and CCTV in your small warehouse.
- Customer orders: you collect names, email addresses, delivery addresses and order histories to fulfil contracts. Your privacy notice explains this, your data register records it, and your retention schedule says how long order records are kept.
- Payments: your payment provider may be an independent controller for some payment processing and a processor for other services. You check the supplier terms instead of assuming one role applies to everything.
- Email marketing: you record whether each subscriber opted in, what they were told at the time and how they can unsubscribe. You keep consent or soft opt in evidence as part of your marketing records.
- Analytics and cookies: you update your cookie notice and consent tool so cookies that require consent aren't dropped without the right consent.
- Staff data: you issue a staff privacy notice, restrict access to HR files and set retention periods for recruitment records and payroll documents.
- CCTV: you add signage, document why CCTV is used, limit who can access footage and decide how long footage is kept.
- Breach response: when an employee accidentally sends an order export to the wrong supplier, your breach procedure tells them who to notify internally, how to assess risk and whether ICO notification is needed within 72 hours.
With these documents in place, the pack actually works. If a wholesale partner asks for your data protection documentation, you can send your privacy notice, security summary and processor list quickly. If a customer makes a subject access request, your team knows the one month deadline and where to search. If the ICO asks questions, your records show the decisions you made and why.
How To Keep GDPR Documents Up To Date
GDPR compliance isn't a set and forget task. Your documents should change when your business changes. New software, AI tools, tracking pixels, offshore support teams, HR systems, delivery partners, payment tools and marketing campaigns can all alter your data protection position.
A sensible review process includes:
- Annual reviews: check your privacy notices, data register, retention schedule and supplier list at least once a year.
- Change reviews: review documents before launching a new product, entering a new market, adding a new platform or changing marketing practices.
- Logs: keep records of breaches, complaints and subject access requests, even where the issue is resolved quickly.
The Data (Use and Access) Act 2025 has introduced changes that affect some data protection processes, including the complaint handling rules that apply from 19 June 2026. The ICO's overview of the Data (Use and Access) Act 2025 is a useful place to monitor implementation.
Templates and GDPR compliance software can help you organise information, but they can't decide your lawful basis, assess supplier roles or judge whether a DPIA is needed. A contract review can also help where supplier terms involve personal data processing.
For a more holistic setup, our GDPR compliance package is designed for UK small businesses that want the core documents tailored to how they operate.
Key Takeaways
- There's no single statutory GDPR compliance pack, but most UK businesses need a practical bundle of notices, internal rules, records, procedures and supplier documents.
- Your core GDPR documents should usually include a privacy notice, data protection policy, data map or RoPA, retention rules, breach procedure, SAR procedure and complaint process.
- A full Article 30 RoPA is required for organisations with 250 or more employees, and smaller businesses may still need records depending on the nature and risk of their processing.
- Extra documents may be triggered by high risk processing, special category data, criminal offence data, CCTV, cookies, direct marketing, international transfers, AI tools or employee monitoring.
- From 19 June 2026, controllers must facilitate data protection complaints, acknowledge them within 30 days, take appropriate steps to respond and inform the complainant of the outcome.
- GDPR documents should be reviewed at least annually and whenever your systems, suppliers, marketing or data use changes.
If you'd like help with preparing your GDPR compliance pack, reviewing your privacy notices, setting up your data protection procedures or checking your supplier contracts, you can reach us at 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.
Build privacy controls around the real data flow
What should the business document next?
Map the purpose, roles, lawful basis, notices, processor terms, retention, rights requests and incident response before relying on a policy alone.








