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.
In today’s digital-first world, businesses of every size handle personal data – from mailing lists and customer profiles to payment details and employment records. If you’re a business owner, you probably already know privacy and data protection laws matter. But did you know that transparency about how you handle people’s data isn’t just good practice – it’s a legal requirement under the UK GDPR and Data Protection Act 2018?
Being open, honest, and clear about your data activities (what you collect, why, and what happens next) isn’t just ticking a compliance box. It’s how you build trust, avoid regulatory headaches, and ultimately empower your customers. In this guide, we’ll break down exactly what transparency requirements mean, why they’re so vital, and how you can fulfil your duties when handling personal data – whether you’re a startup or an established SME.
Let’s walk through the key principles, legal obligations, practical steps, and real-world tips so you’re protected from day one.
- Which Individual Right Does Transparent Data Handling Support?
- What Does Transparency Mean Under UK GDPR?
- What Privacy Information Must Be Provided Under Articles 13 And 14?
- When Must You Provide Privacy Information?
- Does A Website Privacy Policy Meet The Transparency Requirement?
- How Do Cookies, AI, Profiling And Automated Decisions Fit In?
- Privacy Policy, Data Processing Agreement Or Both?
- Key Takeaways
Which Individual Right Does Transparent Data Handling Support?
The short answer is the right to be informed. Under the UK GDPR, people have a right to be told how an organisation collects and uses their personal data. The Information Commission (ICO) calls this a key transparency requirement, and it sits behind much of what businesses usually put into a Privacy Notice or Privacy Policy.
What Does Transparency Mean Under UK GDPR?
Transparency means being open about your data handling before, or at the time, people need the information. Under Article 12 of the UK GDPR, privacy information must be concise, transparent, intelligible, easily accessible and written in clear and plain language. For official wording, you can also check Article 12 and the ICO's guidance on the right to be informed.
A customer, an employee, a job applicant and a child may each need different wording because the context and audience are different.
For example, a checkout notice could say: We use your name, address and payment details to process your order, deliver your products and manage refunds. Read our Privacy Policy for more detail. Your full Privacy Policy can then explain the lawful basis, retention period, recipients and rights in more detail.
What Privacy Information Must Be Provided Under Articles 13 And 14?
Articles 13 and 14 of the UK GDPR set out what you need to tell people. Article 13 applies when you collect personal data directly from the person, such as through an online form, checkout page, booking system, employment form or phone call. Article 14 applies when you get personal data from somewhere else, such as a third-party list provider, referral partner, public register or another group company.
Your privacy information usually needs to cover:
- Who you are: your business name, contact details and, if you have one, your data protection officer's details.
- What personal data you collect: for example, names, emails, addresses, payment details, account data, HR records, usage data or identity documents.
- Why you use it: your purposes, such as fulfilling orders, managing bookings, paying staff, preventing fraud, sending marketing or improving your service.
- Your lawful basis: for example, contract, consent, legitimate interests, legal obligation, vital interests or public task. Most SMEs mainly rely on contract, legitimate interests, consent and legal obligation.
- Who receives it: named recipients or meaningful categories, such as payment processors, delivery providers, IT hosting providers, accountants, insurers, professional advisers or regulators.
- International transfers: whether personal data is transferred outside the UK and what safeguards apply.
- How long you keep it: either specific retention periods or clear criteria for working this out.
- Individual rights: how people can access, correct, delete, restrict or object to processing, and how they can ask for data portability where it applies.
- Consent withdrawal: where you rely on consent, how people can withdraw it.
- Complaints: your contact route and the person's right to complain to the ICO.
- Whether data is required: whether providing the data is a legal or contractual requirement, and what happens if they don't provide it.
- Automated decisions: whether you make solely automated decisions with legal or similarly significant effects, and what this means for the person.
If you collect data indirectly, you also need to explain the categories of personal data involved and where the data came from.
When Must You Provide Privacy Information?
If you collect personal data directly from the individual, you must provide privacy information when you obtain the data, unless the person already has that information. In a website context, that usually means a short notice beside or near the form, plus a clear link to the full policy before the person submits their details.
If you obtain personal data from another source, you must provide privacy information within a reasonable period and no later than one month. You may need to do it earlier if you first communicate with the person or first disclose their data to someone else. The ICO has practical guidance on when to provide privacy information.
Bought-in data deserves particular care. If your business buys a list of potential B2B contacts, you generally still need to give your own privacy information, even if the list provider says it collected the data lawfully. You should also check whether the marketing itself is permitted under the Privacy and Electronic Communications Regulations, often called PECR.
There are limited exemptions and exceptions, but you shouldn't rely on them casually. If a business says providing privacy information is impossible or would involve disproportionate effort, the ICO expects strong reasoning and safeguards, such as a documented assessment, appropriate technical and organisational measures and published privacy information.
Does A Website Privacy Policy Meet The Transparency Requirement?
A website Privacy Policy is usually essential, but it isn't enough by itself. You need to make people aware of it and give them an easy way to access the relevant information at the point their data is collected or used.
Good transparency often uses a layered approach. The first layer gives the person a short, practical explanation at the point of collection. The second layer links to the fuller policy with the complete Article 13 or Article 14 information. This keeps your forms readable while still giving people the detail the UK GDPR requires.
For children, privacy information needs extra care. The language, layout and timing should be appropriate for the child's age and level of understanding. If your business provides online services likely to be accessed by children, you should also consider the ICO's Children's Code.
How Do Cookies, AI, Profiling And Automated Decisions Fit In?
Transparency becomes even more important when data use isn't obvious. Cookies, pixels, analytics tools, AI systems, profiling and automated decisions can all feel invisible to users unless you explain them properly.
For cookies and similar technologies, you should explain what categories of cookies you use, why you use them and who receives the data. Non-essential cookies, such as advertising cookies, usually require consent under PECR. Since 5 February 2026, analytics cookies used only to produce aggregate statistics can be exempt if you tell users and let them object easily. Your cookie banner shouldn't use confusing design to push people into accepting.
For AI tools and profiling, be specific enough for people to understand the real-world effect. For example, saying we use technology to improve services may be too vague if you're actually using an AI tool to score sales leads, rank job applications or personalise prices.
The Data (Use and Access) Act 2025 received Royal Assent on 19 June 2025. It amends, but doesn't replace, the UK GDPR, the Data Protection Act 2018 and PECR. One important area is solely automated decisions with legal or similarly significant effects. The Act creates a more permissive UK framework, but safeguards still matter, including information for individuals, the ability to make representations, the ability to challenge a decision and human intervention where required. You can view the Act at legislation.gov.uk.
Privacy Policy, Data Processing Agreement Or Both?
A Privacy Policy and a Data Processing Agreement do different jobs. Many businesses need both.
Your Privacy Policy is for individuals. It tells customers, staff, job applicants, subscribers and other people how your business handles their personal data. It helps you meet the right to be informed.
A Data Processing Agreement, often called a DPA, is for business relationships where one party processes personal data for another. For example, if you use a payroll provider, email marketing platform, cloud software provider or outsourced customer support provider, that supplier may be your processor. The UK GDPR requires certain processor terms to be in place.
For example, an online retailer may need a customer Privacy Policy, a staff privacy notice, a cookie policy and DPAs with its website host, email platform, fulfilment provider and returns software provider. The Privacy Policy tells people what happens. The DPAs help control what suppliers can do with the data behind the scenes.
Here is a hypothetical example. Imagine a small UK design studio with 8 staff, 1,200 customer contacts, a website enquiry form, a newsletter list of 2,500 subscribers and a recruitment form that collects CVs. It also uses a US-based email marketing platform and an AI tool to sort inbound enquiries by urgency.
The studio's first draft Privacy Policy says only: We respect your privacy and don't sell your data. That isn't enough. After a data audit, the studio adds a short notice beside its enquiry form explaining that it uses contact details to respond to enquiries and manage quotes. It adds a separate newsletter consent statement, updates its full Privacy Policy with lawful bases and retention periods, explains the US-based platform and transfer safeguards, and adds wording about the AI triage tool. It also creates a job applicant privacy notice saying CVs are kept for 6 months after the recruitment round unless the applicant agrees to a longer talent pool period.
The studio also checks whether it needs to pay the ICO data protection fee. The ICO fee tiers are £52 for tier 1 micro organisations, £78 for tier 2 small and medium organisations and £3,763 for tier 3 large organisations, with tiers depending on factors such as turnover, staff numbers and organisation type. Many businesses need to pay, although exemptions can apply, so it's worth checking the ICO's registration guidance for your circumstances.
Key Takeaways
- Handling people's data transparently maintains the UK GDPR right to be informed.
- Privacy information must be concise, transparent, intelligible, easily accessible and written in clear and plain language.
- A website Privacy Policy is important, but you also need point-of-collection notices and tailored wording for customers, staff, job applicants and children where relevant.
- If you collect data indirectly, such as from a bought list or referral source, you usually still need to provide your own privacy information within the UK GDPR timing rules.
- Cookies, AI tools, profiling and automated decisions need clear explanations, especially where the data use isn't obvious or may significantly affect a person.
- A Privacy Policy informs individuals, while a Data Processing Agreement manages processor relationships. Many SMEs need both.
If you'd like help with drafting Privacy Notices, updating cookie and AI wording, reviewing your Data Processing Agreements or checking your GDPR transparency processes, 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.








