What leaves your computer
Four things, all of them because you asked for something:
- When you activate a key — or release its device binding — the key and a hash of your machine fingerprint. Not your serial numbers: a one-way hash that cannot be turned back into them. This is what stops one key running on a hundred machines, and releasing the binding is the same request in reverse.
- When w0a checks for an update — a request for the version file. Like any download, our host sees the request and your address.
- When you send a problem report — what you typed into the box, any contact address you added, your app version, Windows build, CPU and graphics card model, and your licence key and machine-fingerprint hash, which is what the one-report-per-hour limit is counted against. Where the error log is attached, its last lines go with it. Windows user-folder paths, your Windows username and anything shaped like a licence key are stripped out before it leaves. The Privacy Policy lists every field.
- When you claim the one-day Discord trial — the one-time claim code the bot gave you, and the same machine-fingerprint hash. The code is what proves the claim is yours: our server looks up which Discord account it was issued to, asks Discord whether that account is still a member of our server, and records the account's public ID next to the fingerprint hash. That record is the whole enforcement of "once per Discord account, once per device", so it is kept for as long as the trial offer exists. The code is spent on the spot and never written down, and no Discord name is sent or stored at any point.
That is the whole list.
What never leaves
- No usage statistics. Which pages you open, which tweaks you apply, how long the app is running — none of it is sent, and none of it is counted.
- No file names, no folder contents, no game list, no browsing.
- No error log on its own. It is written to
%AppData%\w0a\errors.logon your disk for you, and nothing uploads it in the background — not on a schedule, not when the app crashes. It leaves only inside a report you chose to send: on the Settings card attaching it is a tick box you can clear, and after a crash the app asks first and its last lines go with the report you agreed to. - No advertising identifier, no third-party analytics, no crash reporting service.
Why there is no analytics
Not because we do not want the numbers — because a tool that changes machine-wide settings while phoning home about what it sees is asking for exactly the trust it does not deserve. If we ever add measurement, it will be opt-in, it will be named on this site, and the cookie page will describe it before it runs.
Verifying rather than believing
You do not have to take the above on faith:
- The download's SHA-256 is published before you download it. Checking the download explains how.
- The website blocks itself from loading any script that is not ours — including the one our own hosting provider tries to insert.
Related
Did this page help?
What was missing, or what did not work? We read every one of these.
If this page did not solve it, write to us — say which article you read, and we will fix the article.