What leaves your machine, what runs on it
What Simhive sends to the pool when you sim, what it runs on your PC for others, and how results are checked. No account, no name, no realm.
Sent to the pool when you sim #
Gear, talents, spec and fight settings. Never the character's name or realm (stripped before it leaves), nothing about you. That is what is on the public Armory anyway. Results come back only to you.
Run on your PC for others #
SimulationCraft on plain-text inputs, one batch at a time, with the threads you allow. Every input is checked first: anything naming a file, a path or the network is refused before simc sees it, and simc itself is a build with networking compiled out. The binary comes from the public build channel at the pool's commit, checksum verified, never from the pool.
Checked both ways #
New machines are probed with a known batch, and a share of live work is quietly re-simmed on a trusted machine. Wrong numbers get a machine benched, never into your report.
What the pool keeps #
- Your member name, the machines under it, and the iterations they gave and used over the last 30 days. That is the score.
- Reports you chose to publish, until you delete them or nobody has opened them for 180 days.
- Nothing you simmed. History lives on your disk, or in the History of your connected machine when you sim from the browser.
Analytics #
The public pages count visits on the server side: path, referrer, language, and the address and browser string a visitor's browser sends anyway, hashed into a visitor id by the analytics software, which stores neither. No script on the page, no cookies for it, nothing on the pages behind sign-in.
Who can change what on your machine #
Threads, pause and the name a machine shows under, and only if your app's policy lets the pool do so. The default: only a pool that issued your token as one of its own machines; members' machines are theirs alone. Never the pool a machine connects to or its token.