Privacy Policy

Last updated: October 3, 2026.

Necessary local storage

Core browsing and PC Builder use do not require an account. A saved build can be stored in your browser local storage; a shared build URL contains selected component slugs and no account identity. Your shopping-region preference can be stored in a first-party cookie.

Optional build contributions and feedback

Build contributions and feedback collection are currently paused. The checkbox remains off by default. Selecting the checkbox alone sends nothing; only the Share this build button sends selected component IDs, the server-recorded live revision IDs, a random submission ID, a timestamp, the tool name, methodology version and reported compatibility/power statuses and missing-evidence counts. We use these contributions to improve hardware coverage and compatibility rules, not advertising profiles. Reported results are untrusted observations, not verified scores.

You may turn build sharing off at any time to prevent further submissions. Nothing is sent when you browse, select parts, save a build or copy a link. Previously submitted contributions remain stored; there is no account or device identifier to associate them with you. Contributions are not combined with advertising or analytics identifiers.

Feedback is a separate explicit action. It includes your selected components and rule results plus a fixed feedback reason. No name, email, free-text message, IP address, browser fingerprint or device identifier is stored in RigPrism contribution tables. Your browser necessarily connects to Supabase, whose infrastructure receives ordinary network metadata such as IP addresses; its operational logging is separate from these tables. Feedback and build contributions require no personal information.

Browser benchmark

CPU tests run in a browser worker; supported GPU tests use WebGPU on your device. Timings and selected model stay in memory until you explicitly submit an enabled contribution. Closing or refreshing the page clears that local result. A browser benchmark is not a verified hardware identity or gaming FPS measurement.

Help improve RigPrism

Advertising consent does not enable build sharing, benchmark contributions, feedback or community ratings. These have separate explicit actions and off-by-default contribution controls. Production collection remains paused.

Optional benchmark sharing and community game ratings

Running the browser benchmark computes locally and sends no benchmark result. Help improve RigPrism defaults off. An explicit submission, when collection is enabled, sends your selected public component ID, a random submission ID, suite version, three timing samples per workload, median, variance, checksums, foreground/interruption flags, a coarse browser-engine major version and execution backend. It does not include the full user agent, IP, email, hardware fingerprint, browsing history or advertising identifiers. The selected model is self-reported and the result remains untrusted until operator review.

Game ratings require a separate submit action and consent. We store the game ID, a 1–5 rating, a random submission ID, timestamp and a random game-specific duplicate-prevention token. This token is kept in your browser local storage; it is not shared across games. Clearing browser storage removes local duplicate prevention but does not remove a previously submitted vote. Anonymous votes do not establish unique humans or verified playtime.

Turning sharing off prevents subsequent submissions; it does not erase an already received submission. Canceling an in-flight request cannot guarantee the server has not received it. Raw results and voter tokens are private; only qualified aggregate measurements and real vote summaries are publicly readable. Collection has rate and total-capacity limits and no automatic retention period is claimed. Supabase infrastructure receives ordinary network metadata, separately from these application tables. Contact us about privacy requests.

Data access inquiries and future aggregate reuse

Data access inquiries use an email link and open your own email application; no licensing inquiry form or CRM tracker is installed on this site. We receive information you choose to send to contact@rigprism.com to respond to your inquiry. Please do not send secrets or private benchmark submissions.

We do not sell raw benchmark submissions, build contributions or voter tokens. Current contribution permission supports the stated improvement purposes, not automatic commercial reuse. A future aggregate data product requires an explicit purpose disclosure, rights review and an assessment of re-identification risk before any such collection or release. Removing direct identifiers or meeting a benchmark sample threshold alone does not establish anonymity. This preparation changes neither your contribution controls nor permissions already given.

Steam review summaries

RigPrism stores only public aggregate Steam review counts, score descriptions and retrieval timestamps. We do not store or display individual review text, SteamIDs, authors, profiles or playtime, and do not connect your Steam account. Offline refreshes contact Valve; browsing a game does not contact the Steam API. Cached summaries can become outdated. Following the source link connects you to Steam and its privacy policy applies. Aggregate snapshots are served through Cloudflare’s global network; no Steam user personal data is collected.

Cookie and consent preferences

Theme preference, an explicitly saved PC build and a shopping-region selection support features you request. They are independent of advertising consent. See the Cookie Policy for storage names, durations and deletion controls.

Google Privacy & messaging is the planned authoritative advertising consent manager. It is not configured on this staging site. Cookie Settings in the footer opens Google preferences when available and explains the disabled state otherwise. There is no separate RigPrism advertising consent cookie or second banner.

Analytics

Analytics is currently off; staging is excluded even if an analytics flag is set. Optional Google Analytics or Cloudflare Web Analytics requires publisher configuration and affirmative applicable consent before its script loads. Google Consent Mode defaults advertising storage, analytics storage, advertising user data and personalization to denied. No pre-consent analytics pings are sent by this preparation. Google Analytics, if activated later, can use its own cookies; its collection and retention settings must be reviewed before activation.

Affiliate and retailer links

When commerce features are enabled, RigPrism can request product/price data from affiliate or retailer providers such as Sovrn or eBay. When you follow an eligible commerce link, the provider and retailer receive normal web-request information. Sovrn real-time Bid Check, when used for a click, requires the actual visitor IP address and browser User-Agent to evaluate that click; RigPrism does not store those values in its own commerce-click table. Third-party privacy policies apply to their processing.

External providers

Sovrn, eBay and Open Icecat integrations are disabled. Offer images, if an approved provider is activated, are retailer-listing images with a separate permission gate; they are not promoted into canonical product images. A future provider activation requires rights, regional consent and retention review. Coarse commerce click logging is separately disabled; infrastructure may still receive ordinary network metadata.

Advertising and consent

Display advertising and analytics are disabled by default. Advertising scripts require an approved publisher setup and a configured Google-certified IAB TCF CMP. RigPrism does not invent consent or use a decorative consent banner. Manual ad slots render only after explicit purpose/vendor consent and near-viewport activation. You can revisit or withdraw consent through the configured CMP; reload the page after withdrawal to clear already loaded third-party code. Provider and retailer privacy policies apply to outbound shopping links.

Admin access

Operator sessions use a secure, HTTP-only cookie. Public users do not receive an account cookie from RigPrism V1.

Contact

Privacy requests can be sent through the Contact page or contact@rigprism.com.