Privacy

Website analytics

ReReview uses GA4 and PostHog on rereview.co to understand anonymous website traffic patterns such as pageviews, navigation flow, and high-level feature usage. We use this data to improve the site, not to build personal profiles.

What the extension stores locally

The extension stores a random install identifier and short-lived creator lookup cache entries in chrome.storage.local. This keeps repeated YouTube page loads fast and lets the backend apply basic abuse limits to unknown-creator scoring requests.

What the extension sends to ReReview

When you view a YouTube watch page or creator page, the extension sends the visible channel URL and, when available, the YouTube channel ID to rereview.co. It also sends the random install identifier. ReReview uses that data to return an existing trust result or to enqueue scoring for an unknown creator.

Pseudonymous extension analytics

ReReview may record pseudonymous product-analytics events such as extension installs, trust lookups, trust-chip renders, trust-detail opens, and clicks through to a ReReview creator page. These events help us understand whether the extension is useful and whether the creator-scoring pipeline is healthy. We do not use them to build personal profiles, and we do not send private page content, messages, or passwords through this analytics flow.

The analytics vendors receive a hashed install identifier plus low-cardinality event metadata. When we need creator-level reporting, we send hashed creator references rather than exact YouTube channel URLs.

What ReReview keeps server-side

ReReview stores creator records, creator scores, ingestion audit events, and standard server logs. For extension-triggered unknown creators, we may also store limited request metadata such as the install identifier, IP-derived rate-limit checks, timestamps, the requested channel identity, and pseudonymous extension analytics delivery metadata. These records support quota enforcement, abuse prevention, operational debugging, and product analytics.

What ReReview does not do

• We do not require a user account to use the extension.
• We do not sell extension user data.
• We do not read private messages, passwords, or non-YouTube browsing history.
• We do not claim ownership of creator content; we evaluate public content that creators publish.

Public creator data

ReReview creator pages are built from public channel data, public videos, and ReReview-authored trust analysis. If a creator believes a public page is inaccurate, the correction path is described in our Editorial Policy.

Questions

For methodology details, see the Methodology page. For correction requests or policy questions, use the public contact links in the site footer.