Privacy, in plain language.
This notice describes how the current FrameCheck beta handles information. The beta is still being evaluated and is not a finished public service.
What FrameCheck collects
Browsing the estimator does not require a FrameCheck account. A benchmark submission contains the hardware, game and graphics settings, test method, performance values, test date, confirmations, and evidence that the contributor chooses to send. A name or handle and email address are optional. The email is used only when a result needs clarification and is not intentionally published.
For an uploaded evidence file, FrameCheck stores the file together with its original name, file type, size, storage path, and a cryptographic hash used for integrity and duplicate checks. Cloudflare Turnstile, Cloudflare hosting, Supabase, and ordinary web infrastructure may process technical information such as IP address, browser or device information, security signals, and request timestamps.
The “Save this PC” and repeat-submission features store choices in the visitor’s browser. FrameCheck does not receive that locally saved configuration unless it is later included in a submission.
How information is used
- Operating the estimator and reviewing benchmark submissions.
- Checking the published methodology, evidence, and possible duplicate results.
- Publishing approved performance measurements and improving estimates.
- Detecting spam, abuse, security problems, and technical failures.
- Contacting a contributor when an optional email was supplied and clarification is needed.
FrameCheck does not currently sell personal information or use benchmark submissions for targeted advertising.
What may become public
Pending submissions and privately uploaded evidence are restricted to the moderation workflow. If a submission is approved, its technical benchmark data, test date, optional contributor name or handle, and any public evidence link may be displayed or made available through FrameCheck. Contributor email addresses and privately uploaded evidence files are not intentionally published.
Do not use a real name as your contributor credit unless you want that name associated with an approved result. A link to evidence on another service is governed by that service’s settings and policies.
Storage, providers, and retention
Application data, administrator authentication, and uploaded evidence are hosted with Supabase. The website and bot-protection checks use Cloudflare. These providers process information to supply hosting, storage, authentication, security, and delivery services.
Approved results are retained while they are useful to the estimator. Pending and rejected submissions, moderation events, and evidence may be retained while needed for review, abuse prevention, troubleshooting, and data integrity. An administrator can permanently delete rejected submissions and their uploaded evidence. Beta records may also be corrected or removed as the project changes.
Your choices and beta contact
You can avoid providing a name, email, or directly uploaded file by submitting anonymously and using only evidence you are comfortable sharing. You can remove locally saved PC data with the site’s forget control or by clearing site data in your browser.
During this limited invitation-only beta, contact the person or account that gave you access if you need to request correction or deletion of a submission. Do not submit identifying information if that contact route is unavailable. A dedicated monitored privacy address will replace this beta process before access is opened broadly.