Security and data

What we hold, how we protect it, and what retailers can ask us for.

What we hold

• Sellers' catalogs: products, variants, SKUs, UPCs and marketplace item IDs.
• Orders: order number, dates, products, the buyer's first name, and the buyer's email and phone, encrypted. We use the email only to send a review request the seller turned on, and to match reviews to orders.
• Reviews: the text, rating, date, reviewer's display name, photos, and the result of every check.

How it's protected

• Buyer emails and phone numbers, and every connected service's access token, are encrypted at rest with AES-256-GCM.
• Reviews are matched to buyers by a keyed one-way hash of the email, so matching never needs the address itself.
• Passwords and API keys are stored as scrypt hashes. API keys are scoped to what they may do, and none can approve or remove a review or change a retailer's rules.
• Every state-changing request is logged, and the audit trail of decisions about reviews can't be edited or deleted, by design of the database.
• Sessions are HTTP-only cookies; requests from other sites are refused. Every page sets a content security policy.
• Sign-in and public forms are rate limited.

What leaves the platform

Marketplaces receive the review, rating, date, the reviewer's first name and last initial, the product's identifiers, and where the review was first posted. Never emails, phone numbers, addresses, order numbers or any hash.

For retailers

• A data processing agreement, on request.
• The full audit trail for any review you received.
• Removals come to you in the feed, so a review taken down here comes down on your site.

An independent SOC 2 audit is planned. Until then, we'll answer your security questionnaire directly.