cgc

UGC Usage Rights: What You Can and Cannot Do With Customer Content

Collecting the content is the easy part. Knowing which channels you may run it in, for how long, is where most libraries quietly become unusable.

User-generated content (UGC) usage rights give brands explicit legal permission to reuse, share, and distribute a creator’s content for marketing and paid advertising.

Usage rights are the permissions that decide where a piece of customer content may legally appear. They are not the same as having the file.

Most brands discover the difference at the worst moment: a photograph that performed well organically is about to go behind paid media, and nobody can establish whether that is allowed.

This is general information, not legal advice. Requirements vary by country, and anything at scale deserves a lawyer.

Who Owns Customer Content

Start here, because the answer surprises people.

Under US copyright law, the person who creates a work generally owns it, unless employment, a work-made-for-hire arrangement or a contract says otherwise. For a customer photographing your product on their own phone, the default applies: they own that photograph. You own the product. They own the picture of it.

Receiving a file does not transfer ownership. A customer emailing you a photograph has given you a copy, not the rights to it.

What you are usually getting is a licence, which is permission to use it in defined ways, not a transfer of ownership. That distinction matters because a licence can be limited by channel, by territory, by time, and occasionally withdrawn.

A brand saying "we own this content" almost always means "we have a licence to use it". Worth being precise internally, because the difference determines what you can do next.

What Each Channel Needs

Not all uses carry the same requirement, and the gradient is worth knowing.

Use	Rights needed	Commonly missed
Resharing inside the platform it was posted on	Usually none, the platform's share function covers it	People assume this extends off-platform
Your own website and product pages	A licence covering commercial display	Very often skipped
Email marketing	Same as website	Treated as "not really advertising"
Organic brand social	A licence covering commercial use	Confused with row one
Paid advertising	An explicit licence naming paid media, plus likeness consent	The one most often missing
Packaging and print	A licence plus a term long enough to outlast the print run	Term rarely considered
Third-party retail listings	A licence broad enough to cover onward distribution	Sub-licensing rarely mentioned

Paid advertising is the line. The platforms expect the advertiser to hold the rights for what it runs, and a photograph that is fine on your Instagram grid is a different proposition inside an ad account.

The Three Things a Licence Has to Fix

Channels. Name them. "Marketing use" is ambiguous, and the ambiguity always resolves against the person relying on it. Website, email, organic social, paid social, print, packaging, retail listings.

Term. How long. Perpetual is cleanest for you and the biggest ask. Three years is a common middle. A licence with no stated term creates an argument rather than an answer, and it becomes acute when something is still running on packaging two years later.

Territory. Usually worldwide, because digital advertising does not respect borders and a territory-limited licence is awkward to honour once content is online. It is not unenforceable, it is simply harder to comply with than it looks, so agree to it deliberately rather than by default.

Two more worth settling: whether you may edit it, which you almost certainly need, and whether you must credit the contributor, which is cheap to honour and expensive to get wrong.

Rights Management, and Why Libraries Rot

A rights record is only useful if you can find it against the file six months later.

The common failure is not the absence of permission. It is that permission exists somewhere, in a message thread or a spreadsheet, and nobody can match it to the photograph in time to use it.

Four things keep a library usable:

The permission travels with the file. Not a separate spreadsheet keyed to a filename somebody later renamed.

Every file is searchable by what it shows. Product, use case, setting. A folder of four hundred untagged images is functionally empty, because nobody finds the one they need on the afternoon they need it.

Expiry is visible. If licences have terms, the library has to know which files are approaching the end of theirs. A rights record with no expiry tracking is a rights record that will be wrong eventually.

Withdrawal has a route. If a contributor asks you to stop, you need to find every place it is running. That is a search problem before it is a legal one.

None of this is complicated. It is simply never urgent until the week it is.

Where Brands Get Caught

Treating a public post as a licence. A customer tagging you has given the world permission to look. Platform terms govern the platform, not your ad account.

A DM as documentation. "Sure, go ahead" in a message thread may be genuine agreement and is still poor evidence. It rarely names channels, never names a term, and lives somewhere you cannot search.

Assuming the sender is the owner. A customer forwarding a photograph their partner took cannot license it. Worth asking who took it when the content matters.

Forgetting the people in it. Copyright and likeness are separate permissions. A photograph you have every right to use may still show a person who has agreed to nothing.

Letting the term lapse quietly. Packaging printed under a three-year licence does not stop existing in year four.

Sub-licensing without the right to. Sending content to a retail partner or an agency is onward distribution, and a licence that did not contemplate it may not cover it.

The Second Set of Rights Nobody Budgets For

Everything above is copyright and likeness. If you operate in the UK or the EU there is a parallel regime running alongside it, and a licence does not satisfy it.

A photograph of an identifiable person is personal data. That brings obligations a usage licence does not address: a lawful basis for holding it, keeping it only as long as you need it, and handling erasure requests properly. The ICO's UK GDPR guidance covers this for UK businesses and the EU framework runs in parallel.

Two consequences worth planning for.

A deletion request is not the same as withdrawing a licence. Erasure rights under UK and EU data protection law are qualified rather than absolute, and there are recognised grounds for refusing, but you still need a process rather than an improvisation. You also need to be able to find every copy, which is a search problem before it is a legal one, and it is the strongest argument for a library where content is findable by contributor.

Retention needs a stated position. "We keep customer photographs indefinitely" is a decision you should have made deliberately rather than by default, and a three-year licence sitting alongside indefinite storage is an inconsistency somebody will eventually notice.

Copyright itself is more portable. Most countries operate under the international framework administered by WIPO, so the creator-owns-it default holds across the markets you are likely selling into, subject to local rules on employment and commissioned work.

How 82DASH Fits

82DASH is a customer content library. It collects photos, videos and feedback directly from customers, and a reward lands in their Apple Wallet or Google Wallet when they submit.

Rights are handled at the point of submission rather than afterwards. The campaign carries the usage terms, the customer agrees as they upload, and the agreement stays attached to the file, which is what solves the matching problem described above. Automatic content licensing and usage rights are included on every paid plan.

The practical consequence is that the library stays usable. Content is searchable by what it shows, the permission is attached to the item rather than filed separately, and the tips page on reviewing, tagging and managing submissions covers the day-to-day.

On plans. The free plan covers branded forms and wallet passes, up to 50 submissions a month. Photo and video collection are on the paid plans, and Starter and Growth include a seven-day free trial. Monthly plans start at $50, with around 15% off annually. The pricing page has the current detail.

Underneath it: pay your customers, not creators. The people who already bought from you will photograph the product for the price of a small reward, and their version carries more weight because nobody paid them to hold the opinion.

Start free with forms to Apple and Google Wallet

Isabelle Simon, Communications Lead, 82DASH

FAQs

Who owns UGC, the brand or the customer?

Generally the person who created it. Your customer took the photograph, so they own it. What a brand normally holds is a licence to use it in defined ways, not ownership. Saying "we own this content" is usually shorthand for "we have permission".

Do I need rights to repost a customer's tagged photo?

For resharing inside the same platform using its own share function, usually not. For copying it to your website, into email, or into a paid advertisement, yes. The platform's terms cover what happens on the platform.

What rights do I need to run customer content as an ad?

A licence that explicitly names paid advertising, plus consent from anyone recognisable in it. This is the use most often missing from an agreement, and the one where the exposure is largest.

How long do usage rights last?

As long as the licence says. If it does not say, you have an argument rather than an answer. Perpetual is cleanest, three to five years is a common compromise, and whatever you choose should be written down.

Can a customer withdraw permission?

Depending on the agreement, often yes. Build a route for it: a contact address, a stated timeframe for stopping new use, and an acknowledgement that material already printed or already running cannot always be recalled.

What is UGC rights management?

Keeping track of which content you may use, where, and until when, in a way that can be checked against the file. The hard part is not obtaining permission, it is being able to match permission to a photograph six months later.