Skip to content
NewProduct Q&A: shoppers ask on your product page and get your answers.See how it works
IdukkiIdukki
Rights and compliance

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.

The request says where the content will run, and the answer is kept against the post.

What does GDPR mean for UGC in practice?

GDPR in a UGC workflow

  1. 01

    Ask clearly

    At the point of permission, say how and where the content will be used.

  2. 02

    Record it

    Keep the permission on record, tied to the asset and the person.

  3. 03

    Remove on request

    If a person asks for their content to come down, have a process that does it.

  4. 04

    Minimise

    Do not hold UGC, or the data around it, longer or wider than you need.

Four steps, from the first request to the day the content comes down.
QuestionCopyright permissionData-protection consent
What it coversThe right to use the workHow a person’s data is processed
Who holds the rightThe content creatorThe identifiable individual shown
Can it be withdrawn?Per the licence termsYes, including erasure in many cases
What you must keepThe licence recordScoped consent + removal process
Copyright permission versus data-protection consent.

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

  1. 1European Commission, GDPR overview · Personal data and processing obligations.
  2. 2UK ICO, guidance on images and personal data · When images count as personal data.
  3. 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

Compliance benchmarks across UGC programmes.
#ugc#rights-management#gdpr#compliance

Continue reading

4 pieces in this cluster

These long-form pieces on the Idukki blog link back to this article, go deeper on the cluster.

More from Rohin Aggarwal