GDPR, consent and UGC
UGC shows identifiable people, so it is personal data under GDPR. A defensible programme records scoped permission, honours removal requests, and minimises what it holds.
A customer emails to ask you to take her photo off your homepage. You go looking for what she agreed to. You find a DM saying 'yes you can use it', a tag and a cookie banner. None of them records what she said yes to.
In this article
UGC rights conversations usually stop at copyright: who owns the photo. But a customer photo or video also contains an identifiable person. Under GDPR and comparable regimes, that brings data-protection obligations alongside the copyright ones.
Is UGC personal data?
An image of an identifiable individual is personal data. Publishing and storing it is processing that data. None of this makes UGC unusable. Businesses process personal data lawfully every day. It does mean a UGC programme must be built with data protection in mind, plus copyright.
Why do you need two permissions?
Copyright permission says you may use the content. Data-protection law adds that the person should understand and agree to how their data is used. They also keep rights over it afterwards. A good rights request does both at once. It spells out what the content will be used for, which is what informed agreement needs. Our UGC rights and permissions guide covers how to word that request. One request can satisfy both at the point of collection.
What does GDPR mean for UGC in practice?
GDPR in a UGC workflow
- 01
Ask clearly
At the point of permission, say how and where the content will be used.
- 02
Record it
Keep the permission on record, tied to the asset and the person.
- 03
Remove on request
If a person asks for their content to come down, have a process that does it.
- 04
Minimise
Do not hold UGC, or the data around it, longer or wider than you need.
| Question | Copyright permission | Data-protection consent |
|---|---|---|
| What it covers | The right to use the work | How a person’s data is processed |
| Who holds the right | The content creator | The identifiable individual shown |
| Can it be withdrawn? | Per the licence terms | Yes, including erasure in many cases |
| What you must keep | The licence record | Scoped consent + removal process |
The harder edge case: a creator deletes the original post after you have featured it. That is where your own copy and record matter. We cover it in what happens to your gallery when a creator deletes the original.
Sources & notes
- 1European Commission, GDPR overview · Personal data and processing obligations.
- 2UK ICO, guidance on images and personal data · When images count as personal data.
- 3Note · Practical guidance only. This is not legal advice. Confirm with a data-protection specialist in your market.
30 days
GDPR right-to-erasure SLA
End-to-end inc. CDN purges
45 days
CCPA deletion SLA
CPRA
Continue reading
4 pieces in this clusterThese long-form pieces on the Idukki blog link back to this article, go deeper on the cluster.
- Strategy
First-party data strategies post-cookie for ecommerce personalization
Chrome kept third-party cookies, but Safari and Firefox block them by default and consent rules still apply. Where each browser stands in 2026, which first-party signals to collect, and how durable each one really is.
- Strategy
Personalization without creepiness: the data-use line shoppers notice
Shoppers accept personalization when they can guess how you knew. A signal ladder, a pre-launch test and label templates you can ship.
- Strategy
When a creator deletes the original post, what happens to your gallery
If your gallery embeds the live original, a deletion leaves a broken hole. If you hold your own copy and rights record, the licence and the tile both survive.
- Rights and compliance
The UGC rights workflow merchants will wish they had built (and what to do now)
A defensible UGC rights workflow automates detection, outreach and the audit trail, and needs six clauses to hold up. Build it before agents surface your UGC.
More from Rohin Aggarwal
- Rights and compliance
Re-using user-generated content with permission: the complete rights guide
The customer who shot a photo owns its copyright. Neither you nor the platform does. What a usage licence must cover before you re-use user-generated content, plus the music, disclosure and deleted-post traps.
- Strategy
UGC in Amazon A+ Content: what's allowed, what isn't
Customer photos and video belong in your A+ modules, and Amazon's creative policy will reject most of them the way brands naturally prepare them. Here is the exact line between allowed and prohibited, the module dimensions worth memorising, and the rights question almost everyone skips.
- Rights and compliance
No UGC strategy without a rights log
Feeds, widgets, and paid whitelisting all depend on one shared permissions ledger. Here is the minimum viable log for 2027.