Effective October 25, 2026
Running benchmarks does not require a user account, name, email address, mailing address, phone number, payment information, contacts, files, photos, or precise location. Contact and Bug Report forms allow an optional reply email address.
When you choose to run a benchmark, Omegari sends technical information needed to run, validate, and rank the benchmark. This may include the CPU or GPU model, GPU memory, operating system, system architecture, logical core count, device class, browser information when applicable, Omegari client and engine versions, benchmark type, timing, throughput, and benchmark result data required to operate the service.
The desktop client also creates a random installation identifier. The identifier is generated by Omegari, is not based on your real-world identity, and is used to associate benchmark requests from the same installation. It is stored locally on your device and with Omegari's device records. It is not displayed publicly.
Omegari does not use network information as benchmark data. Like any Internet service, the network infrastructure must process an IP address while a request is being delivered and while rate limits and security controls are applied. Omegari disables routine Nginx access logging. Limited network or request information may still appear in server error or security logs when needed to diagnose failures, attacks, or abuse.
Omegari uses the information described above to provide benchmark work, validate submissions, calculate benchmark performance, maintain benchmark history and rankings, detect misuse, and operate and secure the service.
If you submit a Contact or Bug Report form, Omegari emails your message, subject, optional reply address, and any reproduction steps to its operator through its email provider. Form submissions are not stored in the Omegari benchmark database. Messages can remain in the receiving email inbox and email provider according to their retention settings.
Cloudflare Turnstile checks submissions for automated abuse. Cloudflare may process technical request and browser information to perform this verification. Omegari also applies IP-based rate limiting to public form submissions.
Public benchmark pages may show technical hardware information and benchmark results, including device model, GPU memory when applicable, operating system, architecture, logical core count, benchmark type, client version, timing, and performance. Omegari does not publicly display the random client identifier or network addresses.
Omegari does not sell benchmark or device information and does not use it for advertising or third-party marketing. Infrastructure providers may process information as necessary to host, deliver, protect, and operate the Omegari service.
Benchmark results and related technical device records may be retained to maintain benchmark history and rankings. Routine Nginx access logs are disabled. Limited error or security logs may be retained as needed for troubleshooting, abuse prevention, and service operation.
Omegari uses HTTPS/TLS for data transmitted between clients and the service and uses operational access controls and security measures intended to protect the service and its data.
Benchmark information is submitted when you choose to run a benchmark. You can stop future submissions by not running additional benchmarks or by uninstalling the desktop client.
On Windows, the desktop client's random identifier is stored in
%LOCALAPPDATA%\Omegari\client.json. On Linux it is stored under
$XDG_CONFIG_HOME/omegari/client.json, or ~/.config/omegari/client.json
when XDG_CONFIG_HOME is not set. You can view the identifier there or reset it by
deleting that file; a new random identifier will be created the next time the client runs.
Resetting the local identifier does not remove benchmark records that were already submitted.
Omegari does not maintain user accounts or identity profiles. Public benchmark information can be viewed through the Omegari website.
If Omegari's data practices materially change, this policy will be updated and the effective date above will be revised.
