Personal data breaches: notify the Commission within 72 hours and keep a record
A breach likely to risk people’s rights must be notified to the Information Commission without undue delay and, where feasible, within 72 hours. Every breach must be documented.
Applies when
You are a controller of personal data.
On your store
Keep audit logs and alerting that let you detect breaches and establish their scope quickly.
Check yourself
Have a written breach response procedure and a breach register.
Official sources
not later than 72 hours after having become aware of it
Under-13s: parental consent where consent is the legal basis
For online services offered directly to children, consent from a child under 13 is not enough: it must be given or authorised by a parent, and you must make reasonable efforts to verify that.
Applies when
The service is offered directly to children and relies on consent.
On your store
Add an age check at sign-up and a parental-authorisation flow for under-13s if you rely on consent.
Check yourself
Decide whether the service is offered directly to children.
Official sources
the processing of the personal data of a child shall be lawful where the child is at least 13 years old
The controller shall make reasonable efforts to verify in such cases that consent is given or authorised by the holder of parental responsibility over the child
Where you rely on consent (cookies, marketing, optional data uses), users must be able to withdraw it at any time, as easily as they gave it, and you must be able to show they consented.
Applies when
Any processing is based on consent.
On your store
Keep a persistent “Cookie settings” / “Privacy choices” entry point (footer or account settings).
Store consent records (what, when, which version of the notice).
Put an unsubscribe link in every marketing email and honour it automatically.
Official sources
the controller shall be able to demonstrate that the data subject has consented to processing of his or her personal data
Let people complain to you about their data, e.g. through an electronic complaint form
Data subjects can complain to the controller first. You must make complaining easy (the Act gives an electronic complaint form as an example), acknowledge each complaint within 30 days, and respond without undue delay.
Applies when
You are a controller of personal data.
On your store
Offer a data-protection complaint route: a web form, plus an email/postal alternative.
Send an automatic acknowledgement and track complaints so you can respond and report progress.
Check yourself
Set up an internal process and owner for data-protection complaints.
Official sources
providing a complaint form which can be completed electronically and by other means
Be able to act on access, erasure and other data-subject requests
You must facilitate data-subject rights (access, rectification, erasure, restriction, objection, portability) and act on requests in time. The law does not require a self-service button, but the system must be able to find, export and delete a person’s data.
Applies when
You store personal data about identifiable people.
On your store
Provide a way to export a user’s data and to delete an account together with its personal data (including in third-party systems).
Make deletion cascade (database relations, file storage, search indexes, email lists) and keep only what another law requires.
Check yourself
Document how requests are received, verified and completed within the time limit (Article 12A).
Official sources
The controller shall facilitate the exercise of data subject rights
Privacy notice with the information UK GDPR Article 13 lists
When you collect personal data, tell people who you are and how to contact you, why and on what legal basis you use the data, who receives it, international transfers, how long you keep it, their rights (including withdrawing consent), their right to complain to you and to the Information Commission, and whether providing the data is required.
Applies when
The product collects any personal data (accounts, forms, analytics, payments, support).
On your store
Publish a privacy notice at a stable URL (e.g. /privacy) and link it from the footer and from every data-collection form.
Cover each Article 13 item: identity and contact, purposes and legal basis, recipients, transfers, retention, rights, consent withdrawal, complaints to you (s.164A DPA 2018) and to the Commission, statutory/contractual need, automated decision-making.
Write it in plain language; the Article 12 standard is concise, transparent, intelligible and easily accessible.
Check yourself
Confirm that the notice matches what the code and vendors actually do.
Official sources
in a concise, transparent, intelligible and easily accessible form, using clear and plain language
Third-party services that receive personal data: contracts and disclosure
Vendors that process personal data for you (hosting, email, payments, analytics, AI APIs, error tracking) need a contract meeting Article 28, and the privacy notice must name the recipients or categories of recipients and any transfers outside the UK.
Applies when
Personal data is sent to any external service.
On your store
Keep an inventory of SDKs and APIs that receive personal data; minimise what you send (e.g. strip emails from error reports and AI prompts).
List those recipients (or their categories) and transfer safeguards in the privacy notice.
Check yourself
Sign or accept each vendor’s data processing agreement and check where it stores data.
Official sources
the recipients or categories of recipients of the personal data, if any
Controllers and processors must protect personal data with security appropriate to the risk, for example encryption and pseudonymisation, resilience, recovery and regular testing.
Applies when
You store or transmit personal data.
On your store
Hash passwords with a slow algorithm (argon2, bcrypt, scrypt); never store them in plain text.
Use HTTPS everywhere, keep secrets out of the repository, and restrict database access.
Back up data and test restores.
Check yourself
Run periodic security testing and access reviews.
Official sources
appropriate technical and organisational measures to ensure a level of security appropriate to the risk
Overseas businesses: appoint a UK GDPR representative
UK GDPR applies to a business outside the UK that offers goods to people in the UK. Such a business must designate a representative in the UK in writing, unless its processing is only occasional, low-risk and does not involve special category or criminal-offence data on a large scale. A regular online shop rarely counts as occasional.
Applies when
The business is established outside the UK and sells to people in the UK.
What to do
Name the UK representative and how to contact them in your privacy notice.
Check yourself
Check whether your processing is occasional and unlikely to result in a risk; if not, appoint a representative before selling.
Official sources
the offering of goods or services, irrespective of whether a payment of the data subject is required, to such data subjects in the United Kingdom