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.
Data protection isn’t just for big tech companies anymore. Whether you’re running an online shop, handling HR records, or offering professional services, dealing with personal data comes with serious legal responsibilities in the UK. The General Data Protection Regulation (GDPR) and the Data Protection Act 2018 put the spotlight on businesses of all sizes to get privacy right. That’s where a privacy manager steps in.
If you’ve ever wondered who should look after your business’s personal data from day one, how to avoid the headache of ICO fines, or what being truly “GDPR compliant” really means, you’re not alone. The privacy manager role has quickly become the go-to solution for making sure your business handles information lawfully, fairly, and safely.
In this guide, we’ll demystify what a privacy manager does, why the position matters (regardless of your business size), and the core steps to embed robust data protection into your day-to-day operations. Let’s break down everything you need to know, so you can focus on growth with confidence that your data protection is properly managed.
- Who Is Responsible For Data Protection In A Company?
- What Is A Privacy Manager And Why Does Your Business Need One?
- Is A Privacy Manager The Same As A Data Protection Officer?
- What Does A Privacy Manager Do Day To Day?
- What Data Privacy Compliance Records And Policies Should You Keep?
- How Quickly Must You Deal With Requests, Complaints And Breaches?
- Worked Example: A Growing Online Shop
- Key Takeaways
Who Is Responsible For Data Protection In A Company?
Legally, the organisation is responsible for complying with UK data protection law. If you trade through a company, that means the company is the data controller for many of its own activities, such as holding customer details, staff records and marketing lists. Directors and senior managers should make sure the business has proper systems in place, but they don't need to do every privacy task personally.
What Is A Privacy Manager And Why Does Your Business Need One?
A privacy manager is the person responsible for making sure your organisation collects, uses, stores, shares and deletes personal data in a lawful and sensible way. Personal data is any information relating to an identifiable person, so it can include names, email addresses, phone numbers, IP addresses, employee files, customer order histories, CCTV footage and support chat records.
- Legal Compliance: They help your business meet the UK GDPR, the Data Protection Act 2018 and PECR requirements.
- Risk Management: They spot gaps early, such as insecure software, vague consent wording or an old marketing list with no lawful basis.
Is A Privacy Manager The Same As A Data Protection Officer?
No. A privacy manager and a Data Protection Officer, often called a DPO, aren't automatically the same thing.
A privacy manager is an internal owner for privacy operations. A DPO is a specific UK GDPR role with legal requirements around independence, expertise, reporting lines and tasks. You must appoint a DPO if your organisation:
- Is a public authority or body, except for courts acting in their judicial capacity.
- Has core activities that require large-scale, regular and systematic monitoring of individuals.
- Has core activities involving large-scale processing of special category data or criminal conviction and offence data.
Special category data includes information about health, racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data used for identification, sex life and sexual orientation.
If you voluntarily appoint someone as your DPO, the same DPO requirements apply as if you were legally required to appoint one. That means you shouldn't use the DPO title casually for a general privacy manager unless the role genuinely meets the UK GDPR standard. The ICO has useful guidance on data protection officers if you're unsure whether your business needs one.
What Does A Privacy Manager Do Day To Day?
A privacy manager turns broad legal obligations into repeatable business processes. Their day-to-day work usually includes:
- Maintaining privacy information: Reviewing and updating your Privacy Policy, staff privacy information and just-in-time notices so they explain what data you collect, why you use it, your lawful basis, who you share it with and how long you keep it.
- Mapping data flows: Keeping a record of personal data collected from customers, staff, contractors, suppliers, website visitors and app users, including where it's stored and who can access it.
- Managing lawful bases: Checking that each use of personal data has a lawful basis, such as contract, legal obligation, legitimate interests or consent.
- Handling subject access requests: Coordinating responses when people ask for copies of their personal data, usually without charging a fee.
- Managing complaints: Recording privacy complaints, investigating them and making sure responses are consistent and timely.
- Running Data Protection Impact Assessments: Completing DPIAs for higher-risk projects, such as new monitoring technology, sensitive data processing or large-scale profiling.
- Checking suppliers: Making sure software providers, marketing agencies, payroll providers and outsourced HR partners have suitable data processing agreements in place.
- Handling breaches: Investigating incidents, deciding whether the ICO and affected individuals need to be told, and keeping a breach log.
- Training staff: Giving your team practical rules on passwords, phishing, email mistakes, device security, access controls and when to escalate concerns.
A notifiable personal data breach must be reported to the ICO without undue delay and not later than 72 hours after your organisation becomes aware of it, unless the breach is unlikely to result in a risk to individuals' rights and freedoms. For a deeper look, see our full guide on data breach reporting.
What Data Privacy Compliance Records And Policies Should You Keep?
Privacy management isn't just about having good intentions. You need evidence that your business is managing data protection properly. The UK GDPR accountability principle expects you to be able to demonstrate compliance, not simply say that you comply.
Your privacy manager should usually maintain:
- A data map or record of processing: What personal data you hold, where it comes from, where it goes, why you use it, your lawful basis and how long it is kept.
- Privacy notices: Customer, website, employee and candidate privacy information, including a clear Privacy Policy.
- Cookie and marketing compliance records: Cookie notices, consent settings and marketing opt-in or opt-out records.
- Consent evidence where consent is used: For example, when and how consent was collected.
- SAR, complaint and breach logs: Records showing what happened, when, who handled it and what decision was made.
- DPIAs: Written assessments for high-risk processing and evidence of risk-reduction steps.
- Supplier due diligence and contracts: Data processing agreements, security questionnaires and records of international transfer checks where relevant.
- Retention schedule: Clear rules for how long you keep different categories of data and who is responsible for deletion.
If your business has fewer than 250 employees, you don't always need full Article 30-style records for every occasional processing activity. However, you do need records for processing that isn't occasional, could risk individuals' rights and freedoms, or involves special category or criminal conviction and offence data.
You should also check whether you need to pay the ICO data protection fee. Currently, for fee-paying controllers, Tier 1 is £52 if turnover is up to £632,000 or there are no more than 10 staff, Tier 2 is £78 if turnover is up to £36 million or there are no more than 250 staff, and Tier 3 is £3,763 if the organisation doesn't meet Tier 1 or Tier 2. Paying by Direct Debit reduces the fee by £5. The ICO's data protection fee page is the best place to confirm whether you need to pay and which tier applies.
How Quickly Must You Deal With Requests, Complaints And Breaches?
Some privacy tasks have strict timeframes, so your privacy manager needs a clear escalation process.
A subject access request, or SAR, must be answered without undue delay and normally within one month. You may be able to extend the time limit by up to two further months if the request is complex or you receive numerous requests, and the clock can pause in limited cases while you ask for clarification. In most cases, you can't charge a fee unless the request is manifestly unfounded or excessive, or the person asks for further copies.
For complaints, the UK GDPR doesn't set one single response period in the same way as SARs, but the Data Protection Act 2018 requires you to acknowledge a data subject complaint within 30 days, take appropriate steps to respond without undue delay and inform the complainant of the outcome. If a complaint points to a possible breach, inaccurate data, unlawful marketing or failure to respect rights, your privacy manager should treat it as a compliance issue rather than just a customer service matter.
For breaches, speed matters. Your privacy manager should identify what happened, what data was involved, how many people are affected, what harm could result and what steps have been taken to contain it. If notification to the ICO is required, the 72-hour clock runs from when your organisation becomes aware of the breach, not when the investigation is complete.
Worked Example: A Growing Online Shop
Imagine a hypothetical online shop with 8 staff, annual turnover of £580,000 and 12,000 customer records in its ecommerce platform. It uses a payment provider, email marketing tool, courier platform, analytics cookies, outsourced payroll and a customer support inbox.
The founder appoints the operations manager as privacy manager and names the founder as the escalation point. In the first month, they discover three practical issues. First, the privacy policy says customer data is kept for 2 years, but the ecommerce platform still holds orders from 6 years ago. Second, the marketing list includes 3,500 contacts, but only 2,100 have clear evidence of consent or soft opt-in where PECR allows it. Third, the courier contract doesn't include clear data processor obligations.
The privacy manager fixes the issues in stages. They update the Privacy Policy so it accurately explains order processing, marketing, cookies, couriers and retention. They create a retention schedule that keeps order records for a justified period, separates accounting records from marketing records, and sets deletion owners. They pause marketing to the 1,400 contacts without adequate evidence until the business can lawfully re-permission or remove them. They also arrange a proper data processing agreement with the courier and check the payroll provider's processing terms.
Because the shop has no more than 10 staff and turnover under £632,000, it appears to fall within the current Tier 1 ICO fee level if it's required to pay, so the privacy manager checks the ICO fee tool and budgets £52, or £47 if paying by Direct Debit. The business knows what data it holds, can answer customer requests, can show suppliers are checked and is less likely to panic when something goes wrong.
Key Takeaways
- A UK business doesn't usually need a role called privacy manager, but it must be able to show accountability for UK GDPR compliance.
- A privacy manager is the day-to-day owner for data mapping, privacy notices, supplier checks, SARs, breaches, DPIAs, retention and staff training.
- A privacy manager isn't automatically a DPO. If you appoint a DPO voluntarily, the full UK GDPR DPO requirements apply.
- Subject access requests usually need a response within one month, and notifiable breaches must be reported to the ICO within 72 hours of awareness unless an exception applies.
- Useful evidence includes a data map, privacy notices, cookie records, supplier DPAs, SAR and breach logs, DPIAs, training records and retention schedules.
If you'd like help with setting up a privacy manager role, reviewing your privacy documents, checking supplier data processing agreements and building a practical data protection compliance process, 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.








