Privacy policy explained: what to look for under UK GDPR and GDPR
Most people scroll past a privacy policy in a second. That is a pity, because a privacy policy is one of the few documents a company is legally forced to write for your benefit. With the privacy policy explained section by section, it becomes a short checklist: who holds your data, why, on what legal basis, who else gets it, how long they keep it and what you can do about it. Once you know that structure, most notices can be read in five minutes.
The rules come from the GDPR in the EU and the UK GDPR in the UK, read with the Data Protection Act 2018. The two texts are still close. Where the UK has moved away, mainly through the Data (Use and Access) Act 2025, this guide says so.
Privacy policy explained: what the document actually is
A privacy policy, or privacy notice, is a public statement by an organisation about the personal data it collects and what it does with it. Personal data means anything that identifies you directly or indirectly: your name and email, but also an IP address, a device ID, a loyalty card number or your location history.
The notice does not give the company permission to do anything. It is not a contract and you do not sign it. Its job is to tell you, so that you can decide whether to hand the data over and know which rights to use later.
That is why a box reading “I agree to the privacy policy” means very little in legal terms. Agreeing to information is not the same as consenting to a specific use.
The right to be informed under UK GDPR
The duty behind every privacy notice is the right to be informed. Article 12 of the UK GDPR says the information has to be concise, transparent, intelligible and easy to access, written in clear and plain language, and especially clear where it is aimed at children. Articles 13 and 14 then list what has to be in it.
Article 13 applies when the company collects data from you directly, for example when you fill in a sign-up form. You must get the information at the moment of collection.
Article 14 applies when the company got your data from somewhere else: a data broker, a partner company, a public register. In that case it must tell you within a reasonable period, and at the latest within one month. If it uses the data to contact you, it must tell you at that first contact.
The UK regulator, the Information Commissioner’s Office, publishes a plain checklist of the required content in its guidance on the right to be informed. It is a good reference if you want to check a notice against the law.
What a privacy policy must include, and what to look for
Strip away the formatting and every compliant notice has to cover the same ground. The list below follows Articles 13 and 14 and shows what to look for under each item.
| Item | What to look for |
|---|---|
| Who the controller is | Company name and contact details, plus the data protection officer if there is one |
| Purposes | Each reason the data is used, in specific words |
| Lawful basis | The legal ground for each purpose |
| Legitimate interests | If relied on, what those interests are |
| Recipients | Who receives the data, by name or by category |
| International transfers | Whether data leaves the UK or EU and what safeguards apply |
| Retention | How long data is kept, or the criteria used to decide |
| Your rights | Access, rectification, erasure, restriction, objection, portability |
| Withdrawing consent | How to do it, where consent is the basis |
| Complaints | Your right to complain to the regulator |
| Statutory or contractual need | Whether you must provide the data and what happens if you don’t |
| Automated decisions | Whether decisions are made about you without human involvement, and the logic |
| Source of the data | Required where the data was not collected from you |
A notice that skips one of these is incomplete. A notice that covers all of them in vague words (“we may share data with selected partners for business purposes”) may still fail the plain-language test.
Lawful basis: the part most people skip
Every use of personal data needs a lawful basis under Article 6. There are six in the EU GDPR: consent, contract, legal obligation, vital interests, public task and legitimate interests. A good notice links each purpose to one of them, rather than listing all six in a block at the end.
The basis matters because it decides which rights you have. If the company relies on consent, you can withdraw it at any time and the processing has to stop. If it relies on contract, for example to deliver an order, the right to data portability applies. If it relies on legitimate interests, you have the right to object, and the company then has to show its reasons override yours.
The UK added a seventh basis. Since 5 February 2026, the Data (Use and Access) Act 2025 lets organisations rely on recognised legitimate interests for a fixed list of purposes, such as crime prevention, national security, emergencies and safeguarding vulnerable people. For those purposes the usual balancing test does not apply. It does not cover ordinary marketing.
Legitimate interests in practice
This is the basis to read most carefully. Companies often use it for analytics, fraud checks, network security and direct marketing to existing customers. Some of that is reasonable. A notice that puts profiling for advertising or sharing with data brokers under legitimate interests deserves a second look, and you can object to direct marketing at any time, with no reason needed.
How to read a privacy policy in five minutes
You do not need to read every word. Here is the privacy policy explained as a routine you can run on any website, in a practical order:
- Find the controller. Check the company name matches the service you are using. Apps are often run by a different legal entity, sometimes in another country.
- Read the purposes list. Look for anything you would not expect from that service, such as a recipe app that collects precise location.
- Find the sharing section. Note whether data goes to advertising partners, data brokers or “affiliates” across a large group.
- Check retention. “As long as necessary” with no criteria is weak. A period in months or years, or a clear trigger such as account closure plus six years for tax records, is what the law expects.
- Look for international transfers. For UK and EU users, data sent to countries without an adequacy decision needs safeguards such as standard contractual clauses.
- Locate the rights section and the contact. Write down the email or form for data requests. You will need it if you later make a subject access request.
Use your browser’s find function and jump to the passages on sharing, partners, selling, retention and transfers. Those are the parts that matter most.
Privacy policy vs cookie policy
The two are often confused because many sites put them side by side in the footer. They come from different laws.
A privacy policy covers all personal data the organisation handles, online and offline, under the GDPR or UK GDPR. A cookie policy covers cookies and similar technologies that store or read information on your device. Those are governed by a separate law: the ePrivacy Directive in the EU and the Privacy and Electronic Communications Regulations 2003 (PECR) in the UK.
The cookie rules apply even if no personal data is involved. Most cookies do collect personal data, so both laws usually apply at once. In practice the cookie policy lists each cookie, who sets it, what it does and how long it lasts, while the banner asks for consent. How those banners work, and what changed for low-risk cookies in the UK, is covered in cookie banners explained.
Red flags in a privacy policy
Some wording should slow you down. None of these is automatically unlawful, but each is worth a closer look.
- “We may sell your data” or “share it with third parties for their own marketing”. This is legal only with a proper basis, usually consent, and you should be asked separately.
- No retention periods at all. The law requires either a period or the criteria for deciding one.
- Consent bundled into the terms. Consent under the GDPR must be freely given, specific and separate from other matters. “By using this site you consent to everything” does not meet that bar.
- Every purpose under one basis. A notice that says all processing relies on consent, or all on legitimate interests, has usually not done the analysis.
- No controller address or contact. You cannot use your rights without a contact point.
- Rights mentioned but made difficult. Requests accepted only by post to an overseas address, or a demand for excessive ID, can be a sign of obstruction.
- Out-of-date notice. References to laws that no longer apply, such as the old Data Protection Act 1998, suggest nobody has reviewed it.
A thin or confusing notice is also a sign that you may get a slow answer when you try to use your rights under GDPR.
What the Data (Use and Access) Act 2025 changed for UK notices
The Act did not replace the UK GDPR. It amended it, and most of the data protection changes took effect on 5 February 2026. Three points matter for readers of privacy notices.
First, the new recognised legitimate interests basis described above may now appear in UK notices. Second, the duty to give Article 14 information has a wider exemption where telling people would involve disproportionate effort, for example with old research datasets; the organisation must then publish the information instead. Third, from 19 June 2026 every controller must have a way to receive data protection complaints, acknowledge them within 30 days and tell you the outcome. Expect to see a complaints route in UK notices that did not have one before.
For people in the EU, the GDPR text has not changed in the same way, and the six lawful bases remain the full list.
What to do when a privacy policy falls short
If a notice is missing, vague or contradicts what the service really does, you have options. You can ask the company directly what it does with your data, which is free and must be answered. You can object to specific uses, withdraw consent where that is the basis, or ask for erasure. If you think your data has already been mishandled, write down what happened and when, keep copies of every message, and ask the company in writing what data was involved.
Complaints go to the organisation first. If it does not answer properly, go to the ICO in the UK or your national data protection authority in the EU; the European Data Protection Board lists them all. This guide keeps the privacy policy explained at a general level and is not legal advice. Citizens Advice, the European Consumer Centres Network (ECC-Net) and the ICO can help with individual cases.
A last practical point. Many apps have a separate privacy notice in their app store listing, and it does not always match the one on the company website. When the two disagree, the one you were shown at the point of collection is the one the company has to stand behind.
Questions and answers
Is a privacy policy a legal requirement?
Yes, in practice. Any organisation that collects personal data about people in the UK or EU must give them the information listed in Articles 13 and 14 of the GDPR or UK GDPR. The law does not say it has to be called a privacy policy, but a published privacy notice is the usual way to meet that duty. A website that collects names, emails or tracking data and has no notice at all is breaking the rules.
What is the difference between a privacy policy and a privacy notice?
Mostly the audience. A privacy notice is the outward-facing document that tells you, the person whose data is used, what happens to it. A privacy policy can also mean an internal document telling staff how to handle data. Websites tend to use the two terms for the same public page, and regulators such as the ICO usually say privacy notice.
Do I have to accept a privacy policy to use a website?
No. A privacy notice is information, not a contract, so there is nothing to accept. A tick box saying you agree to the privacy policy does not create consent for anything. Where a company needs your consent, for example for marketing emails or advertising cookies, it has to ask for it separately and clearly, and you must be able to refuse.
Can a company change its privacy policy without telling me?
It can update the notice, but if it wants to use your data for a new purpose that is not compatible with the original one, it must tell you before it starts. For bigger changes, many organisations email existing users. A new purpose that relies on consent needs fresh consent. Check the date at the top or bottom of the notice to see when it last changed.
How long should a privacy policy be?
There is no word count in the law. Article 12 requires the information to be concise, transparent, intelligible and easily accessible, in clear and plain language. Regulators accept layered notices: a short summary first, with links to the detail. A very long notice is not unlawful by itself, but one that buries the key facts in vague text may fail the plain-language test.
Where can I complain about a privacy policy?
Start with the organisation itself, using the contact details in the notice or the data protection officer if it has one. In the UK, controllers must have a process for data protection complaints from 19 June 2026 and acknowledge them within 30 days. If that does not resolve it, you can complain to the ICO in the UK or to the data protection authority in your EU country.
