Home Download & Verification
Download and verification
How you will get Fate Tracker, and how to confirm the file you received is exactly the one that was published.
The customer download is delivered by Gumroad. After checkout it is in your receipt email and in your Gumroad library. Builds shared before the release are never offered here.
Current verified release
| Version | 0.7.8 |
|---|---|
| Verified | September 6, 2026 |
| Automated safety checks | 271 passed at packaging |
| System | Windows 11 (tested). Windows 10 is not advertised as supported until it has been directly tested |
| Customer package | Fate-Tracker-Build-Memory-0.7.8-Customer-Windows.zip |
| Published checksum (SHA-256) | 31E7EAA9B41192C1D7810F9DABA3BCF607965061ABB0F6EF4335A19B9B5521B0 |
This is the release the download is built from. The customer package is assembled from it through an explicit allow-list, signed, and given its own published checksum.
Getting Fate Tracker, step by step
The normal way to get Fate Tracker takes four steps, and none of them needs any technical knowledge:
- Buy from the official Fate Tracker checkout, run by Gumroad. Only the checkout linked from this website is official.
- Download from your purchase email or your Gumroad library. Both carry the same file.
- Check the installer says Fate Tracker. When you open it, Windows shows the product name and the publisher. The publisher reads Sean Marshall.
- Follow the ordinary installation steps. The installer walks you through it.
The customer installer is code-signed before sale. The verified publisher name shown by Windows is published here alongside the checksum when the signed package goes on sale.
Optional technical verification
You do not need this. It exists for customers who like to confirm a file for themselves before opening it.
Every published download will have a SHA-256 checksum published beside it: a long code that acts like a fingerprint for that exact file. If you know how to produce a checksum on your computer, you can compare the code you get with the published one. They should match exactly.
If you check and the codes do not match, do not run the file. Download it again from the official page, and if it still differs, report it before opening it.
Ordinary customers can skip this section entirely and rely on steps 1 to 4 above.