Instagram UGC rights requests: two messages, a consent page and the proof to keep
Copy-ready templates for a public comment, a DM and a consent page. Plus what to store as proof and what to do when the answer is no.
A customer posts a photo of your product. You want it on the product page. Two messages, one consent page and a proof record sit between you and that page.
In this article
Using a customer's Instagram photo on your store needs their permission. The legal background is in the UGC rights and permissions guide. This piece is the Instagram version: what to send, in what order, and what to keep. It is a process guide. It is not legal advice.
The sequence
- 01
Comment on the post
Short and public. Names the use and says a DM is coming.
Day 0
- 02
Send the DM
Names each use, the credit and the end date. Carries the consent link.
Same day
- 03
Consent page
Shows the post, the uses and the end date. One yes button.
One tap
- 04
Store the proof
Save the post, the messages, the page text and the time of the yes.
Before it goes live
When to ask
Ask while the post is new and the creator is still reading its comments. A Story disappears after 24 hours, so a Story needs a same-day ask. How to catch Stories in time is in Instagram Stories UGC archiving.
Start with a comment. It lands in the creator's notifications. Instagram puts DMs from accounts they do not follow into message requests. The comment tells them a DM is on its way, so they know to look there.
Message 1: the public comment
Keep it to two lines. Say what you liked, name the use and flag the DM. Leave the details for the DM.
Love this, @[handle]. Could we show it on our [product] page, with credit to you?
I'll send the details by DM.Message 2: the DM with the consent link
This is where the detail goes. Name every use. Say how you will credit them and for how long. Make saying no easy.
Hi [first name], it's [your name] from [brand]. Thanks again for posting your [product].
We'd like to show your post on our [product] page and in one email to customers.
We'll credit you as @[handle], for two years from today.
We won't use it anywhere else without asking again.
If that works for you, tap here to say yes: [consent link]
If not, no problem. Ignore this and we won't use it.Want it in paid ads too? Ask for that by name in this DM. A yes to a product page does not cover ads.
What the consent page says
The link opens a page that repeats the DM in plain words. The creator sees exactly what they are agreeing to and taps once.
[Brand] would like to use your post.
[Preview of the post]
Where it will appear: the [product] page and one email to customers.
Credit: @[handle], shown with the post.
How long: two years, until [date].
Payment: none. (Or: a [amount] store credit.)
You can change your mind at any time.
Email [address] and we'll take it down within [5] working days.
[ Yes, you can use it ] [ No thanks ]- Show the post itself. The creator may have posted several times this month.
- List the uses one by one. No "any marketing purpose" catch-all.
- Give an end date. Two years is a common default. Pick yours and print it.
- Say how to withdraw. An email address and a takedown time you can meet.
What to store as proof
Someone may ask in a year who agreed to what. Save the record before the post goes live on your store.
| What to store | Why |
|---|---|
| Post URL and Instagram media ID | Ties the consent to one post. |
| Creator handle and account ID | Handles can change. The account ID stays the same. |
| A copy of the media as you received it | The creator can edit or delete the post later. |
| The comment and the DM, with dates | Shows what you asked and when. |
| The consent page text, with a version number | Shows exactly what they agreed to. |
| The uses granted and the end date | Keeps a product-page yes out of paid ads. |
| Time of the yes and how it came | A tap on the page or a typed yes in the DM. |
| Withdrawal date, if any | Shows you took it down when asked. |
When they say no, or say nothing
- A no: reply once to thank them. Mark the post declined so nobody on your team asks again.
- No reply to the DM: leave it. Treat silence as a no and do not use the post.
- Do not use it anywhere. That includes ads, emails and a quick repost to your Story.
- A later post is a new ask. If they post again, you can ask about that post.
- A yes withdrawn later: take it down from every place it runs, then log the date.
No problem at all, thanks for letting us know. We won't use it.
Enjoy the [product]!Done. We've taken your post down from our [product] page and our emails.
Thanks for letting us use it.Have the customer's order email? The email version of this ask is in a rights-request email sequence people reply to.
Related reading
- 1Idukki: The complete UGC rights and permissions guide
- 2Idukki: How to build a rights-request email sequence people reply to
- 3Idukki: How to legally collect UGC from Instagram and TikTok
- 4Instagram Help Center: how Stories work · Stories expire after 24 hours unless saved to Highlights.
Continue reading
8 pieces in this clusterThese long-form pieces on the Idukki blog link back to this article, go deeper on the cluster.
- Buyer's guides
The best Covet alternatives in 2026: eight options for Shopify stores
Instafeed, EmbedSocial, Taggbox, Foursixty, Judge.me, Loox, Tolstoy and Idukki against Covet.pics. Entry prices, what each bill counts, product tags and video. We make Idukki.
- Embedding
How to make your Instagram feed shoppable on your own site
A shoppable Instagram feed puts your Instagram posts on your site, tagged with your products. Seven steps from connecting the account to counting orders, and how it differs from Instagram Shopping.
- Buyer's guides
The best UGC rights management tools in 2026: five tools and what each records
Flowbox, Taggbox, EmbedSocial, Foursixty and Idukki compared. How each asks creators, what it stores and which plan carries rights. We make Idukki.
- Buyer's guides
Foursixty alternatives in 2026: five options and what each one costs
Covet, EmbedSocial, Moast and Idukki against Foursixty's three plans. Where TikTok galleries, customer uploads, rights requests and Klaviyo sit on each price list. We make Idukki.
- Strategy
Repurposing customer support videos and unboxings as marketing assets
Support teams and customers already make the videos a product page is missing: assembly walkthroughs, fit checks, what is in the box. Who owns each kind, what consent you need, how to clean a clip for the PDP, and a monthly workflow that moves the good ones from the help desk to the storefront.
- Strategy
Instagram Stories UGC: archiving and reusing 24-hour content properly
Stories vanish in 24 hours by design. Catching, clearing and archiving customer Stories before they disappear is a workflow problem, not a content problem.
- Strategy
How to Embed an Instagram Feed on BigCommerce (Step-by-Step)
How to put a shoppable Instagram feed on a BigCommerce store: connecting the store with a store-level API account, placing the embed with Page Builder's HTML widget (or Script Manager when that fits), what Instagram's API changes mean for your account, and how to fix the usual faults.
- Strategy
How to Embed an Instagram Feed on WooCommerce (Step-by-Step)
How to add a shoppable Instagram feed to a WooCommerce store: connecting WooCommerce's REST API, placing the embed with a Custom HTML block or the Site Editor's Single Product template, what Instagram's API changes mean, and the WordPress-specific faults (sanitised scripts, optimisation plugins) that break feeds.
More from Rohin Aggarwal
- Strategy
PDP before and after UGC: 8 teardowns and what changed
Eight illustrative product page teardowns, before and after customer content. What moved, where it sits on the page, and a checklist to run on your own.
- Strategy
A kitchen table in Egham, why I built Idukki
Day job: SAP architect on UK government software. Night job: founder of a UGC platform. The Venn diagram of those two communities is roughly one person.
- Strategy
The Death of Impression-Based Pricing: A Finance Director's Case
Impression-based pricing made sense while impressions tracked funnel impact. They stopped. A finance director's argument for outcome-based commercial models in the agentic era.