Last reviewed: 16 November 2026. This guide reflects the provisions of the Data (Use and Access) Act 2025 in force on that date. It is not legal advice.
Who the UK GDPR applies to
If your startup collects, stores or uses personal data, the UK GDPR applies to you. There is no exemption for small businesses or for companies that only collect email addresses.
Most of the work is record-keeping a small team can do itself.
What changed in 2026
The Data (Use and Access) Act 2025 amended the UK GDPR in stages. As of November 2026:
- A seventh lawful basis. “Recognised legitimate interests” was added as Article 6(1)(ea) on 5 February 2026.
- Subject access time limits. The one-month limit now sits in a new Article 12A, inserted by section 76 of the Act.
- A complaints process. Since 19 June 2026 every controller must give people a way to complain to it about how their data is handled, and must acknowledge a complaint within 30 days (section 103).
- A new regulator. The Information Commissioner’s functions passed to the Information Commission on 30 September 2026 (SI 2026/1015). Its website is still ico.org.uk, and this guide calls it “the regulator”.
The commencement dates are in SI 2026/82.
The essentials
1. Know what data you collect
Make a data inventory:
| Data Category | What | Why | Where Stored | How Long |
|---|---|---|---|---|
| User accounts | Email, name | Service delivery | Database | Account lifetime |
| Analytics | Page views, device | Site improvement | Analytics tool | 90 days |
| Payments | Handled by Stripe | Billing | Stripe | Per Stripe policy |
A spreadsheet is enough for a startup.
2. Have a privacy notice
Tell users:
- Who you are (company name, registration number, contact details)
- What data you collect and why
- The lawful basis for each type of processing
- Who you share data with, including sub-processors
- How long you keep data
- Their rights under the UK GDPR
- How to contact you and how to complain
Article 12 requires this to be “concise, transparent, intelligible and easily accessible” and written in “clear and plain language”.
3. Choose a lawful basis
Each use of personal data needs a lawful basis from Article 6. There are now seven:
- Consent. The person has given clear, informed consent.
- Contract. You need the data to perform a contract with the person.
- Legal obligation. The law requires you to process the data.
- Vital interests. To protect someone’s life.
- Public task. For a task in the public interest.
- Recognised legitimate interests. A fixed list of purposes set out in the legislation, such as preventing crime and safeguarding.
- Legitimate interests. You have a legitimate reason that is not overridden by the person’s rights.
Startups commonly rely on contract for account data and legitimate interests for product improvement.
4. Secure the data
The UK GDPR requires “appropriate technical and organisational measures”. For a startup:
- Encrypt data in transit with HTTPS
- Encrypt data at rest, which most cloud databases offer
- Use strong authentication
- Limit access to the people who need it
- Keep software updated
5. Handle requests from individuals
People can ask for:
- Access to their personal data. You must respond within one month, which can be extended by two further months for complex or numerous requests.
- Rectification of inaccurate data
- Erasure
- Portability, meaning their data in a machine-readable format
- Restriction of processing
- Objection to processing based on legitimate interests
Set up a dedicated address such as privacy@yourcompany.com and write down the procedure. The same address can receive complaints.
6. Report breaches
If a personal data breach is likely to result in a risk to individuals, you must notify the regulator without undue delay and, where feasible, within 72 hours of becoming aware of it (Article 33). If the risk is high, you must also tell the people affected.
Keep a record of every breach, including those you do not have to report.
Common mistakes
- “We are too small for GDPR to apply.” Size does not create an exemption.
- “We don’t collect personal data.” Email addresses, IP addresses and device identifiers are personal data.
- “Our analytics tool handles compliance.” You are the controller and the tool is a processor. Compliance is your responsibility.
- “We use consent for everything.” Consent is often not the best basis and is harder to manage than the alternatives.
- “We copied a privacy policy from another site.” Your notice must describe what you do.
The data protection fee
Most organisations that process personal data must pay an annual data protection fee to the regulator. As of November 2026 the fee for tier 1 is £52 a year, or £47 by direct debit. Tier 1 covers organisations with a turnover of £632,000 or less, or with no more than 10 staff, and charities. Tier 2 is £78 and tier 3 is £3,763 (regulation 3 of the Data Protection (Charges and Information) Regulations 2018). You can pay at ico.org.uk/registration. Check there for the current amount.
If you want an outside assessment, our GDPR Compliance Audit gives a gap analysis with a prioritised fix list.
Sources
- UK GDPR, Articles 6, 12, 25 and 33, as amended.
- Data (Use and Access) Act 2025, sections 70, 76 and 103.
- SI 2026/82: commencement of the data protection provisions on 5 February 2026 and of the complaints duty on 19 June 2026.
- SI 2026/1015: transfer of functions to the Information Commission on 30 September 2026.
- Data Protection (Charges and Information) Regulations 2018, regulation 3: fee tiers and amounts, as amended from 17 February 2025.
