REQUIREMENTS AND SUPPORT
Start with one clear check.
Explore the offline example first, then configure an optional model connection.
Updated October 14, 2026. ReplayProof is available in the Microsoft Store. See the listing for current pricing and availability in your region.
What you need
- A Windows x64 computer running Windows 10 version 2004 (build 19041) or later, or Windows 11. Check the Microsoft Store listing for system requirements.
- No account, key or model for the offline simulator.
- For Gemini: your own working API key and Internet access. Provider charges are separate.
- For a local model: an already running LM Studio-compatible server, loaded model and exact model ID. No model or server is included. Required model memory depends on your chosen model.
First check
Get ReplayProof from the Microsoft Store, install it and open the app.
- Choose Offline simulator and enter a fictional decision and task.
- Confirm your expected values and run Everything is retained.
- Inspect the comparisons. The bundled complete control should pass all eight checks.
- Choose The unfinished task is lost and confirm again. The deliberate loss should fail three task checks: five of eight pass.
- Save the JSON evidence report using a new filename.
The website’s screen preview cannot run these checks. They run in the Windows app.
Understanding the result
- PASS: all declared checks passed in this run.
- FAIL: a required comparison did not match. For the deliberate loss control, failure is the expected observation.
- UNSUPPORTED: the requested comparison cannot be performed by this setup.
- INCONCLUSIVE: available evidence could not establish a verdict. Check the reported reason and connection settings.
A successful run does not establish general model quality, existing chat-session restoration, cold restart, crash recovery or storage durability.
Connection and saving help
For a local connection, ensure the server is running, the model is loaded, and the model ID matches exactly. Use http://127.0.0.1:PORT/v1/chat/completions with the server’s port. An unavailable server is inconclusive.
A live run can take several minutes. Each run makes at most four requests without automatic retries. If access or output is invalid, inspect the reason before starting a new run.
If a report cannot be saved, choose a writable folder and a new filename. Existing evidence is never overwritten. Reports include your test text; inspect them before sharing.
Contact support
Email ReplayProof@gmail.com with your app version, Windows version, connection type, selected condition and the error description. Include what you expected and what happened. Omit credentials and confidential information.
Support is provided by the developer as available; no guaranteed response time is offered. Read Privacy and data handling before sharing information.