Nothing goes live until a human says so.
Review reported and flagged UGC in one queue: approve, hold or remove, with rights gating so un-cleared content never reaches your storefront.
Needs your live workspace connected. This is a real in-app module, not a demo form.
The review queue
One screen, three decisions.
Each flagged piece carries its source, the reason it surfaced and its rights status, so a call takes a glance, not a hunt. The rows below are representative sample data shown to illustrate the layout, not a customer's real content.
| Source | Tagged product | Why it surfaced | Rights | Suggested action |
|---|---|---|---|---|
| @maya.k | Airlift Overcoat Brown | Flagged: competitor logo in frame | Cleared | On hold |
| @liv.j | White Sweater Green Stripes | Reported by visitor: off-brand | Requested | On hold |
| @iris.skin | Bodycon Sunscreen SPF 50 | Auto-flag: unverified health claim | None | Remove |
| @run.club | Tennis Cardigan Spring/Summer | Clean: rights cleared, on-brand | Cleared | Approve |
| @store.live | Women Oval Sunglasses | Reported by visitor: wrong product | Cleared | Approve |
How it works
A deliberate gate, not a vibe check.
Most tools let UGC auto-publish and hope nothing slips. This holds the gate shut until a person, and a cleared right, opens it.
Every report lands in one queue
Visitor reports, auto-flags from the safety classifier and your own team holds all route to the same review surface. Nothing depends on someone happening to spot it in a feed. The queue is the single place a flagged piece waits for a human decision.
Approve, hold or remove, with a reason
Each decision is a deliberate action, not a silent toggle. Hold takes a piece off the storefront while you chase a rights response. Remove pulls it everywhere it was embedded at once. Every action writes who did it, when, and why.
Rights gating before anything goes live
A piece without a cleared rights response cannot be published, the gate is on by default. Requested-but-unanswered content stays in hold, so consent is settled before a customer photo appears next to your buy button.
Visitor reports, auto-flags and team holds review in the same place, not scattered across feeds and inboxes.
Rights gating is on by default: un-cleared content cannot reach your storefront, full stop.
Every decision writes who, when and why, so brand-safety calls are auditable after the fact.
Brand-safety controls
Three controls that catch problems early.
Set them once and the queue does the sorting, so your team reviews the genuine edge cases instead of every single post.
Auto-flag
A safety classifier pre-sorts incoming UGC so obvious problems surface at the top of the queue instead of slipping through.
Block rules
Block by keyword, handle or competitor mention. Anything matching never reaches the live queue, it goes straight to held.
Audit trail
Every approve, hold and remove is logged with the actor and timestamp, so a brand-safety review has a paper trail to read.
Part of the Idukki platform
Moderation and rights are the same gate.
A held piece waiting on consent and a flagged piece waiting on review share one queue. Rights management handles the consent request; moderation handles the brand-safety call. Both have to clear before a customer sees the content next to your buy button.
- Rights gating on by default: un-cleared UGC cannot publish
- Remove pulls a piece from every widget it was embedded in at once
- Every approve, hold and remove is logged with actor and timestamp
Stop renting six tools. Ship one.
Spin up your first widget in 4 minutes. Migrate from Bazaarvoice, EmbedSocial, Tolstoy or Videowise in a day. Your CFO will love us. Your CRO already does.
- No credit card
- Cancel anytime
- SOC 2 + GDPR
