Privacy Policy

1. Local-First Diagnostic Architecture

Browser capability inspections, WebAssembly checks, and WebGPU benchmark routines run locally. CoinMiners does not upload a device report automatically. You may choose to save a report to your signed-in account; that action uploads the report only after you check the separate consent box and press Save.

2. What Information We Inspect Locally

When you initiate a device scan or benchmark, your browser queries standard web APIs:

• Logical Concurrency: navigator.hardwareConcurrency to estimate available worker threads.
• Graphics Acceleration: navigator.gpu.requestAdapter() to verify WebGPU compute availability.
• Memory Hint: navigator.deviceMemory coarse memory estimate (if supported).
• User Agent: Basic browser and operating system identifiers.

Scan results remain in your browser unless you export them or explicitly save a report to your account. A saved report can include these capability details, the browser user agent, benchmark results, and any included device notes. The Report page lists saved reports and lets you open or delete them.

3. Zero In-Browser Mining or Covert Workloads

CoinMiners does not mine cryptocurrency in the browser and does not load Monero web miners, CoinHive variants, or covert background scripts. Synthetic browser benchmarks run only after you explicitly start them on the Benchmark page and can be stopped there; they are not mining measurements. Repository source also includes a Native RandomX development worker behind a foreground daemon. A queued session cannot start compute without a separate local terminal confirmation and a server-approved TLS pool configuration; the public pool allowlist is empty and no signed public client is released. The browser feasibility page reads feature support only and does not run CPU work.

4. Device and Resource Use Consent

Opening the site does not start a benchmark or mining workload. Browser synthetic benchmarks start only when you press their control and can be stopped from the page. Native session compute starts only after the daemon owner confirms locally; its current worker uses one CPU thread and RandomX light-cache mode. The separate full-memory Native benchmark uses roughly 2.1 GiB and requires its own local confirmation. Browser checks may inspect coarse CPU thread, memory, graphics, and operating-system hints locally. Wall power and component temperature are not measured by this site and remain UNKNOWN unless you supply a value.

5. Third-Party Analytics and Trackers

CoinMiners does not use analytics pixels or commercial ad network SDKs. Referral links are optional: if you accept the attribution notice, the site stores a random first-party browser identifier and referral claim token locally, records a hashed identifier with the campaign visit, and may link that campaign to your account after sign-in. Declining prevents the referral visit from being recorded; you can clear the site's local storage to remove the saved referral state.

6. Account and Optional Cloud Data

Sign-in is provided through Supabase Auth. Referral attribution is attached to the authenticated account only after a verified sign-in and uses the user ID from that session; it is one-time per account and expires after the campaign attribution window. Referral visits and account registrations are activity measures, not payable commissions. Cloud-saved reports are scoped to your account and can be deleted from the Report page. Do not upload report details you do not want stored online.

7. Native Device Binding and Benchmark Reports

If you sign in and request a device binding code, CoinMiners stores a one-time code hash and expiry. A development native client may register a device name, operating system, and hashed installation identifier; the server stores only a hash of the short-lived device credential. You can revoke a bound device from the Devices page. The current native CLI does not yet perform enrollment or upload reports.

A client upload requires a separate explicit consent flag. An uploaded benchmark report can include CPU model, operating system, RandomX version, measured hash count, duration, thread count, and locally measured H/s. Reports are account-scoped and marked as unverified client measurements; they are not pool-accepted work and are not used for automatic earnings. The account interface lists uploaded reports; report deletion is not provided by this release.