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

How to Repost Customer Content on Instagram (Legally)

Reposting a customer's photo without permission is copyright infringement, tag or no tag. The clean permission flow, what counts as consent, and how to do it at scale.

A customer tags you in a photo of your jacket on a mountain ridge. Someone on your team screenshots it for the feed. Nobody asks the customer. That is how a takedown letter starts.

Screenshotting a tagged photo and posting it to your feed feels harmless, even flattering to the customer. It is also copyright infringement in most of the world, and brands get letters about it. Doing it properly costs one comment and thirty seconds. Here is the legal shape of reposting and the permission flow that keeps you clean. Then, how to run it across hundreds of posts.

Copyright vests in the person who takes the photo or films the video, automatically, at the moment of creation. Your hashtag in their caption is not a licence. Neither is a tag of your account. Instagram's terms grant a display licence to Instagram alone. The myths to unlearn: "credit in the caption" is not permission (it is attribution attached to an infringement), "everyone reposts" is not a defence, and deleting-when-asked does not erase what came before it. The full legal framework, including music-licence traps on video, is in the UGC rights and permissions guide.

The safe lanes Instagram gives you

When a customer tags your account in a Story, Instagram offers "Add to your story": that reshare lives inside the platform's own terms, keeps the creator's handle attached, and expires with the Story. Collab posts and remixes are similarly native. These are the low-ceremony options, and for ephemeral thank-you content they are usually enough. What they never cover: pulling the media out of Instagram, feed reposts of someone's post via screenshot or downloader, and any use in paid ads or on your website.

The permission flow for everything else

The industry-standard flow is a public comment or DM asking for rights with a clear yes-mechanism: "We love this! Can we share it on our channels? Reply #yesYourBrand to say yes to our terms: link." The reply is your consent event. Three elements make it hold up. Specificity: say where you will use it (social, website, ads); consent for one is not consent for all. A linked terms page: what they are agreeing to, in plain words. The record: who agreed, to what, when, with a link to the original post.

The permission flow

  1. 01

    Ask in public

    Comment or DM with the reply hashtag and where you will use it.

  2. 02

    Link the terms

    A plain-words page saying what they agree to.

  3. 03

    Get the yes

    Their reply with your hashtag is the consent event.

  4. 04

    Keep the receipt

    Log who agreed, to what, when, with a link to the post.

For paid ads, raise the bar: written permission naming ad usage, ideally with a duration. Ad platforms can demand proof of rights, and creators reasonably expect ad usage to be paid; a surprise appearance in an ad campaign is how goodwill becomes a dispute.

Running it at scale

The flow above is fine for five posts a month and unmanageable at fifty. This is the part Idukki automates: it finds the posts that tag or mention you, sends the rights request as a comment on the original, detects the creator's approval, and logs the consent (who, what scope, when, which post) against the asset. Approved content flows into your website galleries and campaigns with the audit trail attached, and un-approved content simply never surfaces. Moderation sits in the same pipeline (how the filter works), so scale does not mean risk.

Illustration of the rights flow in Idukki.

One more etiquette rule that doubles as strategy: always keep the creator's handle visible, and tell them where their content went. Creators whose content you treat well post about you again, and some become the repeat contributors a customer creator program is built from.

Sources

  1. 1Idukki: UGC rights and permissions guide · The legal framework this article summarises
  2. 2Instagram terms of use · Licence granted to the platform, not to third parties
#instagram#ugc-rights#repost#compliance

Continue reading

2 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