Privacy
EveryRig™ privacy
What the app sends, and when
- Activating a key: the key, this PC's machine code (a scrambled code made from the PC's hardware — not a serial number or
anything personal; it is the same each time, so requests from one PC can be linked), the app version and the PC's name.
- Buying with the app's Buy Pro button: this PC's machine code and a one-time random code go with the order (Stripe keeps them as
the order's reference). While you pay, the app sends the machine code, that one-time code and the PC's name to link the purchase
to this PC, so it can activate itself after you pay.
- Remove license (Settings -> License): the app sends its license to the website, which frees this PC from the key on the server,
so the key can be used on another PC.
- The update check (30 seconds after the app starts, then every 12 hours): the app version and machine code (to check for
updates and count installs). The response includes the latest app version and game-tune database version; the full game
database is not downloaded.
- A game's starting tune: the first time a game starts (then every 60 days, or after a database update) the app sends the
game's name and program names. The website answers with that game's tune only and keeps which games each PC asked for, to
limit requests; the record is deleted after 90 days without a request. The app keeps the tune on your PC, protected for
your Windows user.
- Help from Claude helper link (only if you say yes for that report): the machine code, your license, the names of your games
and your CPU / GPU model, to make the link. The zip itself is never uploaded.
- Game requests (the one-line box in Scan games): only the game name and the app version.
- With each of these: whether the program file is the original one signed by its developer (yes / couldn't tell).
- The 14-day trial: the machine code, so reinstalling doesn't restart the trial.
- Moving to the new machine code (version 2.6.2, made from the motherboard and CPU only): this PC's old and new machine codes,
with the trial check and, once, with your license — so your key, its PC slot and your trial stay with this PC.
- A bug report ("Report a problem"), only when you send one: what you typed, your email if you gave it, your license key, tier
(trial / Pro) and machine code, and the files the app lists before sending — recent log lines, the newest session reports, your
profiles and settings, and the PC check (hardware model names and the names of programs running in the background).
Passwords, login tokens, e-mail addresses and your Windows user name are removed. No serial numbers.
- Frame-rate measuring: the first time, the app downloads Intel PresentMon from Intel's official GitHub page (nothing is sent).
- The VR frame-rate add-on (optional, 2.5.22): it runs on your PC only. It counts the frames OpenXR games send to your headset
and reads the headset's refresh rate for the dashboard — nothing is sent anywhere, and it is never used in anti-cheat games.
- Session summaries and imported Claude tunes — only if you said yes to sharing (see below).
Nothing else leaves your PC. The EveryRig™ app has no ads, no analytics and no trackers. On your PC it only reads what it needs: your
hardware and Windows settings (for setup and the PC check), the folders of your games and programs (to find them and list their
mods — read-only), when SteamVR's log files were last written (to tell whether a headset is on), and what it puts into a
Help from Claude zip — which it only saves on your desktop for you to upload or not.
The Help from Claude zip (made only when you click the button; the app shows what goes in before making it)
- Your hardware, the app's settings, logs and session reports, and the PC check.
- Each game's graphics settings files and which mods / upscalers are installed (with the DLSS / FSR / XeSS file versions).
- Windows gaming settings (Game Mode, GPU scheduling, Game DVR, Memory Integrity, power plan, per-game graphics settings),
VR settings (Virtual Desktop / SteamVR settings files and which headset), your games' NVIDIA driver settings, and the
names of your Microsoft Flight Simulator Community add-ons, and MSFS Map Enhancement's cache settings (2.5.22).
- No personal files or browsing data. Passwords, login tokens, e-mail addresses and your Windows user name are removed — game
settings files can still hold other text you typed, so have a look before you share the zip.
- This report stays on your PC. EveryRig™ doesn't send it anywhere — you choose whether to give it to Claude.
Optional sharing — EveryRig™ learns from every setup (off unless you say yes)
The app asks once. If you share, after each game session of 2 minutes or more it sends a short summary: the game, your GPU and
CPU model and driver version, the tune used, fps and 1% lows, temperatures and load, headset type, any crashes, and which mods
were running. A tune you import from Claude is shared the same way (its stage, fan curve, frame cap, power limit and note). No
name, no files, no account info — but it comes with the machine code, so results from one PC can be linked to each other:
private, not fully anonymous. Shared results are reviewed before anything goes into the database. Turn it on or off any time
in Settings > Share session and tune data; while it's off, none of this is sent.
What this website keeps
- Keys and the machine codes / PC names that use them, first and last seen dates, app versions and whether the copy is the signed original.
- Bug reports, until they're dealt with.
- IP addresses: only briefly, to limit abuse (rate limiting — for example too many key attempts from one address). They are not
linked to keys or reports and are deleted after about 2 days.
- Game requests (the app's Scan games window or everyrig.org/request): only the game name and app version.
- Shared results (only from users who said yes): the session summaries and Claude tunes described above, with the
machine code. Results older than about 90 days are folded into per-game averages and the single rows deleted.
- Reviews you send from everyrig.org/review: the name, rig, rating and text are shown on the home page once approved;
the email (optional) is never shown and is only used to ask you about your review.
- Ryzen tester sign-ups (name, email, hardware), only to contact testers — deleted when testing ends.
- Purchases: payments are handled by Stripe. We receive the buyer's name, email and the amount paid from Stripe — never
card or bank details — and keep them with the Pro key, so we can resend a lost key.
- No cookies of our own except the owner's admin login (Meta's cookie is described below).
The Meta (Facebook) Pixel — this website only, not the app
everyrig.org uses the Meta Pixel so we can see whether our Facebook and Instagram ads bring visitors, and so Meta can show
EveryRig™ ads to people who visited. When you open a page, your browser loads Meta's script, which tells Meta which page you
viewed and — when you click a trial download or Get Pro, or finish a purchase — that event (with the price; never your card
details). Meta may connect this to your Facebook / Instagram account and sets its own cookie (_fbp) for it; Meta's privacy
policy covers what it does with it. The pages with forms (Help, Request a game, Leave a review, Ryzen testers) and the admin
pages don't load it.
To opt out: switch on Global Privacy Control in your browser (EveryRig™ then doesn't load the Pixel at all), block trackers
in your browser, or change your ad settings in your Facebook / Instagram account (Accounts Center > Ad preferences).
Questions or deletion: use the Help page and ask for your data to be removed.