Why review syndication needs two keys, not one
Most syndication networks let one party decide where a review appears. That is how retailers end up hosting content they never approved — and how brands lose control of their own words.
By Tony Chiappetta, Founder

One key is a liability
In a single-key network, the syndicator decides where content lands. The brand pushes, the retailer receives, and nobody in the middle can prove the retailer ever agreed to display that source.
REVEX requires two keys for every placement:
- Source approval — the brand (or whoever owns the review) approves the partnership and the scope: all products, a specific brand, or a single SKU.
- Recipient enablement — the retailer explicitly switches that source on for their storefront.
If either key turns, the placement goes dark immediately. No emails, no support tickets.
What that changes in practice
- A retailer can accept reviews from three brands and refuse a fourth, without renegotiating anything.
- A brand can revoke a partner the day a distribution agreement ends, and every placement stops serving within the same sync.
- Auditors get a single answer to "who allowed this content to be here?" — both parties, on the record, with timestamps.
Revocation is a feature, not an incident
Because both keys are stored as first-class state, revocation is an ordinary operation. Placements move to inactive, the review itself is untouched, and the provenance receipt keeps the full history. Nothing gets deleted, so nothing gets lost.
The trade-off we accept
Two keys mean slower initial distribution: a brand cannot force content onto a partner page. We think that is correct. Reviews are borrowed trust — the retailer has to want them, and the brand has to stand behind them.


