Book a live demo — see your catalog's review coverage →

Trust & security

Sharing reviews only works if both sides can check it.

REVEX is designed so that a brand, a retailer, and a shopper can each verify why a review appears — and so nobody can quietly change the record.

A permanent origin record on every shared review
Row-level tenant isolation across the network
Public receipt lookup for any review ID

What shoppers see

Every shared review says where it came from

A small label on each review tells shoppers it was written by a verified buyer on the brand's store and shared with permission. Tap it and they get the full receipt. Under the hood: an immutable provenance record keyed to the source review ID.

Marcus T.
Verified buyer

Finally a trail shoe that fits wide feet

Ordered my usual 10.5 and the toe box had room to spare. Twelve miles on rocky switchbacks, zero hot spots.
Size 10.5 WFit True to size

Verified Purchase · Shared by the brand via REVEX

Jenna R.
Verified buyer

Worth every penny for nurses

Three 12-hour shifts in and my back is thanking me. Cushion hasn't flattened out like my last pair did.
Size 8Fit True to size

Verified Purchase · Shared by the brand via REVEX

Daniel K.
Verified buyer

Runs a half size small

Love the look and the grip in the rain, but go up half a size. Exchanged mine and now they're perfect.
Size 11Fit Runs small

Verified Purchase · Shared by the brand via REVEX

Sample reviews · illustrative

Live numbers

The record, as it stands right now

Aggregate integrity figures across the exchange. No reviewer identities, contact details, or private organization data are included.

Verify

Check any review's receipt

Paste a review ID or a provenance link from a product page. The receipt shows the originating merchant, verified-purchase status, content fingerprint, and every logged change.

Controls

How the platform is built

Tenant isolation

Every table is protected by row-level security keyed to organization membership. Cross-organization reads are only possible through explicitly scoped, audited functions.

Least-privilege access

Roles are owner, admin, and member, stored separately from profile data. Privileged operations are verified server-side, never from client state.

Immutable provenance

Review content is hashed at import. Edits are recorded as revisions with actor, field, and timestamp — originals are never overwritten.

Audit logging

Partnership changes, enablements, moderation actions, disputes, and billing blocks are written to an append-only log visible to the organizations involved.

Consent enforcement

Placements are recomputed from live permissions. Revocation retires placements at the next sync — there is no long-lived cache of licensed content.

Practices

Operational commitments

  • Encryption in transit for all traffic; encryption at rest for stored data
  • Signed, expiring links for review collection and provenance receipts
  • Webhook signature verification on every external callback endpoint
  • Secrets stored outside the codebase and scoped per environment
  • Personal data limited to reviewer display name, hashed identity, and optional location
  • Deletion and redaction requests handled at the source record, propagating to placements

Reporting

Found something? Tell us.

Email security@revex.io with details and we will acknowledge within one business day. Please avoid testing against other organizations' data.