Respond to data subject access requests (DSARs)
How to handle data subject access requests under UK GDPR. Covers the one-month response deadline, identity verification, exemptions …
How to write a privacy notice that complies with UK GDPR. Covers required content, plain language requirements, when to provide it, and how to use layered notices for complex processing.
You must write a privacy notice explaining how you collect and use personal data. It must be clear and easy to understand. Include details like why you need the data, who you share it with, and how long you keep it. You must provide this notice when you collect data directly or within one month if you get it from another source.
How to handle data subject access requests under UK GDPR. Covers the one-month response deadline, identity verification, exemptions …
How to write and maintain a privacy notice that meets UK GDPR requirements. Covers mandatory content under Articles …
How to comply with UK GDPR and the Data Protection Act 2018. Covers ICO registration, lawful bases for …
How to send compliant marketing emails under PECR and UK GDPR. Covers consent requirements, the soft opt-in exception …
How to complete the NHS Data Security and Protection Toolkit (DSPT) annual self-assessment if you handle NHS patient …
A privacy notice (also called a privacy policy) tells people how you collect and use their personal data. Under UK GDPR, you must provide this information clearly and accessibly.
Your privacy notice is not just a legal requirement. It builds trust with customers and employees by being transparent about what you do with their information.
You need a privacy notice if you process personal data. This includes customer names, addresses, or contact details, employee records, website visitor data (including cookies), marketing lists, CCTV footage, and any information that identifies or could identify a living person.
Most businesses need at least one privacy notice. You may need separate notices for different audiences (customers, employees, website visitors).
UK GDPR requires you to be transparent about how you process personal data. This is one of the seven key data protection principles:
Transparency means telling people what you do with their data in a way they can understand. A privacy notice is the main way you fulfil this obligation.
UK GDPR Articles 13 and 14 specify what information you must include. The requirements differ slightly depending on whether you collect data directly from the person or from another source.
You must tell them:
When you obtain personal data from a third party (such as a lead generation company or public register), you must also tell people where you got their data from (name the source or type of source) and what categories of data you received.
You must provide this information within a reasonable period (no later than one month), or at the time of first communication if you use the data to contact them.
Your privacy notice must state which lawful basis applies to each type of processing. You cannot process personal data without a valid lawful basis.
Be specific in your notice: Do not just say you rely on 'legitimate interests' without explaining what those interests are. For example: "We process your purchase history for our legitimate interest in improving our product recommendations."
Special category data: If you process health data, religious beliefs, or other special category data, you need both a lawful basis AND an Article 9 condition. Explain both in your privacy notice.
Your privacy notice must explain the rights individuals have over their personal data. Make clear how they can exercise these rights.
Make it actionable: Do not just list the rights. Tell people how to exercise them (email address, online form, postal address). State your response timeframe (one month for most requests).
UK GDPR requires privacy information to be provided in a concise, transparent, intelligible and easily accessible form, using clear and plain language.
Replace legal jargon with plain English. Say 'we share your data with' not 'we disclose personal data to third-party processors'.
Aim for 15-20 words per sentence. Break up complex information into bullet points.
Say 'we collect your name and email address' not 'personal data is collected by us'.
Ask someone unfamiliar with data protection to read your notice. If they cannot explain what you do with their data, rewrite it.
Provide privacy information at the time you collect data (before or at the point of collection). Link to your privacy notice on every online form. Make it accessible from every website page (usually in the footer). For data from third parties, provide information within one month or at first communication.
If your data processing is complex, use a layered approach:
Your privacy notice must reflect your current processing activities. Review and update it when you start collecting new types of data, use data for new purposes, share data with new organisations, change retention periods, implement new technologies, or when the law changes.
Version control: Date your privacy notice and keep previous versions. If someone queries how you handled their data two years ago, you need to show what your notice said at that time.
Do not say 'we keep data as long as necessary'. Give specific timeframes: '7 years for financial records', '2 years after your last purchase'.
Do not say 'we may share your data with partners'. Name specific organisations or describe categories clearly.
State which lawful basis applies to each processing purpose. Do not just say 'we process your data lawfully'.
Your privacy notice must reflect YOUR processing. Generic templates need customising to your specific activities.
The ICO provides a free privacy notice generator to help small organisations create a compliant notice. It asks questions about your processing activities and generates a customised notice. The tool is suitable for straightforward processing. If your data use is complex, you may need professional advice.