# Is user-generated content safe to repost?

> Not by default. A customer tagging a brand or posting publicly doesn't hand over the right to republish their content, so reposting safely means getting clear, recorded permission first & crediting the creator.

Updated: 2026-10-05.

## Why a public post isn't a free-to-use post

A customer who posts a photo publicly & tags a brand has shared it with their audience, not licensed it to the brand. The creator still owns the image, & republishing it on a brand account is a separate use that normally needs their permission.

The tag is an invitation to notice the post. It isn't consent to repost it, edit it, or use it in an ad.

## What clear permission actually looks like

- A direct message or comment where the creator says yes to a specific post & a specific use
- A saved record of that reply, since a verbal OK is hard to prove later
- Agreement on how they want to be credited, usually their handle in the caption
- A narrower yes for ads, since paid use often needs explicit consent beyond an organic repost

Asking is quick & most people say yes happily. The point is having the answer in writing before the post goes live, not chasing it after someone objects.

## Why a native repost tool doesn't settle it

Some platforms offer a share or remix feature that keeps the original creator attached. That's a reasonable way to amplify a post inside the platform's own rules, but it doesn't cover downloading the image & publishing it as new content elsewhere.

Using the platform's built-in sharing, where it exists, is the lower-risk route. Re-uploading someone else's file as your own post is the one that needs written permission.

## Handling a creator who says no, or doesn't answer

No answer is not a yes. If a creator doesn't reply, the safe default is to leave the content alone & find another example. A brand account reposting without a reply is the situation that tends to turn into a complaint.

Having a few pre-cleared examples ready means a declined or ignored request never leaves a gap in the content plan. DunSocial's media library is a practical place to keep those cleared assets together, so a draft pulls from material already approved rather than something borrowed in a hurry.

## Keeping a record that holds up

Permission is only useful if someone can find it later. Saving the screenshot of the reply, the creator's handle & the date next to the asset turns a one-off favour into a record anyone on the team can check.

A short note in the asset's description, who approved it & where the message lives, takes seconds. DunSocial keeps uploaded media attached to the workspace rather than to one person's device, so that record stays available to the whole team, not just whoever sent the original request.

## A reasonable team routine

Decide one standard ask, a short message naming the post, the use & the credit, & use it every time. Reviewing any UGC post before it goes live is then a quick check against that record.

Because DunSocial keeps a draft on the calendar until someone approves it, a reposted customer photo has a natural review point where the permission record gets checked, not assumed.

## Related guides

- [Can you use copyrighted music or images in social media posts?](https://www.dunsocial.com/hub/social-media-compliance-and-brand-safety/can-you-use-copyrighted-music-or-images-in-social-media-posts.md)
- [How to disclose sponsored social media posts](https://www.dunsocial.com/hub/social-media-compliance-and-brand-safety/how-to-disclose-sponsored-social-media-posts.md)
- [What should a social media content policy include?](https://www.dunsocial.com/hub/social-media-compliance-and-brand-safety/what-should-a-social-media-content-policy-include.md)
- [How to build a content bank for social media](https://www.dunsocial.com/hub/social-media-content-creation/how-to-build-a-content-bank-for-social-media.md)

## About this document

This is the Markdown representation of https://www.dunsocial.com/hub/social-media-compliance-and-brand-safety/is-user-generated-content-safe-to-repost. The HTML version of the same page is at the same URL. You can also request Markdown from any page by sending `Accept: text/markdown`.

Machine-readable summary of the whole site: https://www.dunsocial.com/llms.txt

## Company

- Product: DunSocial, https://www.dunsocial.com
- Legal entity: THISUX PRIVATE LIMITED, Chennai, Tamil Nadu, India
- Support: support@dunsocial.com
- Open the app: https://app.dunsocial.com/login