Effective 14 July 2026. The operator of PCBenchmark.online controls the information described here. Privacy, access, correction and deletion requests can be sent through the contact form. Deployment-specific legal-entity and hosting details must be supplied by the operator before production launch.
The workload runs on your device.
CPU workers, GPU shaders and memory transfers execute in your browser. PCBenchmark does not remotely control your computer, install a service or continue working after the tab is closed. No performance workload begins until you press the start button, and a Stop control remains available while the test runs.
Renderer data is used transiently.
To suggest a GPU name, the benchmark page may read the graphics adapter or WebGL renderer identifier exposed by your browser. It sends that string to the PCBenchmark catalog matcher in a JSON POST request using no-store cache mode. The request is used to return a catalog candidate; the raw renderer string is not persisted with your benchmark report.
Browsers may mask this value, and ambiguous or software-renderer strings may produce no match. A successful match can save the canonical catalog ID and a GPU-name snapshot in a report. You can review or edit the suggested display label before running the benchmark.
What is submitted when a report is created.
- Performance
Raw CPU, GPU, memory, VRAM-transfer and stability measurements.
- Context
Coarse operating-system family, logical worker count, browser RAM class and graphics API. The RAM class is rounded and may be capped; it is not a physical-capacity reading.
- Hardware
Optional CPU/GPU catalog IDs and display-name snapshots you select, type or confirm.
- Versions
Benchmark engine and scoring versions needed to interpret the result.
- Network
The IP address used to submit a completed benchmark, an application-keyed one-way visitor hash and a country-level location code. The IP is encrypted at rest, is never included in the public report and is removed after 30 days.
Network data is used for abuse prevention, country-level service statistics and aggregate daily operations reports. A country may come from a trusted hosting/CDN header or, when configured, from IPinfo Lite. IPinfo then receives the address solely for country lookup. PCBenchmark does not intentionally save your name, email address, full user-agent string, city, precise location or account identity with a benchmark result.
Encrypted server-side session files support CSRF protection and form feedback without adding IP or user-agent metadata to the application session record.
If you separately suggest a missing processor, the submitted model name and optional email/note are stored in the catalog-review inbox. They are not attached to the public benchmark report; the optional email is used only to review that suggestion.
Community details are separate from benchmark reports.
Contact messages store the name, email, subject, message and selected language required to respond. Hardware contributions store the submitted specifications, evidence link and contributor contact details so an administrator can review the proposed catalog change.
Contributor email addresses are never displayed publicly. Ownership must be confirmed through a one-time email link before any name, website or count can become public. Credit is then approved separately for each suggestion, can be withdrawn by an administrator, and counts only approved suggestions with active public credit.
Unlisted by default.
A completed result receives a long, non-sequential URL. Anyone who has that URL can read the hardware labels and measurements in the report, so do not put personal information into the optional label fields. Unlisted reports are not added to the public sitemap or leaderboards.
Minimize first, retain deliberately.
Shareable reports remain in the configured Laravel database so permanent links continue to work; deletion can be requested through the contact form. Encrypted benchmark IP addresses and their keyed visitor hashes are automatically erased after 30 days; the non-identifying country code can remain with the benchmark for aggregate statistics. Resolved contact messages are automatically eligible for deletion after 180 days. Pending review material and contributor records are retained while needed for source verification, abuse prevention, public credit or a deletion request.
Access to contact details and contribution review data is restricted to the management area. Analytics data is processed by Google only under the consent choice described above; mail and hosting processors depend on the operator’s production configuration and must be named here before launch.
Client-provided metrics are validated and scored server-side, but a browser-only run is not cryptographic hardware attestation. Future public rankings will require additional anomaly detection and version-specific integrity signals.
You stay in control.
The page remains informational until you explicitly begin a test.
Cancel the active workloads at any point from the benchmark console.
Review or replace suggested hardware display names before creating a report.
A report link is never posted to a third party automatically.
To access, correct or delete contact/contributor information, withdraw public credit, or request deletion of a report, use the contact form and include the relevant report or contribution reference.