Privacy and data handling

Who to contact

ReplayProof is developed by James Primeau in Jacksonville, Florida. For privacy questions or to request deletion of correspondence held by us, email ReplayProof@gmail.com. Do not send passwords, API keys or sensitive reports.

The website

ReplayProof adds no advertising, analytics scripts, signup forms or tracking cookies to this website. Cloudflare hosts it and may process IP addresses and connection information to deliver and protect the site. See Cloudflare’s privacy policy.

The browser screen preview does not run the verifier or make model requests. It is a demonstration of the interface.

Test data on your computer

The Windows app uses your entered decision and task, confirmed expectations and selected settings to run the bundled test. The offline simulator makes no model requests. ReplayProof has no integrated analytics or automatic report upload to its developer.

Run materials are written to temporary local files and are normally removed when the run completes. An interruption can leave files behind. Electron may keep application cache files. Cleanup and deletion are not secure erasure.

Optional model connections

Gemini: after you enter your key and confirm access, selected test state and questions are sent to Google’s Gemini API. Google handles those requests under its applicable API terms and privacy practices. Use your own account and check its data settings and costs. See Gemini API terms.

Local model: after confirmation, requests go to the loopback server and model you configure. ReplayProof does not download or start model software. A server running on your computer may itself retain or forward data; check that server’s configuration and policies.

Each live run makes at most four requests with no automatic retries. The app records requests, answers and selected response metadata in the report.

Credentials

Gemini and optional local-server keys are kept separately in application memory until you forget them or close the app. Key entry fields clear after submission. ReplayProof does not intentionally save these credential fields in reports or configuration files. Keys are sent to the selected provider to authorize requests. Never put a credential in test text or model-description fields, which are included in reports.

Evidence reports and retention

Saving a report is your choice. JSON reports include test inputs, expectations, requests, responses, comparison results, run materials and metadata. They remain at the location you choose until you remove them. Reports already saved are not overwritten by the app.

Inspect and remove sensitive information before sharing a copy. ReplayProof’s developer cannot retrieve or delete files kept only on your computer. Uninstalling the app does not remove reports you exported elsewhere.

Email and support

Email sent to ReplayProof is processed through Gmail and used to respond to inquiries and support requests. Emailing does not subscribe you to a mailing list. We retain correspondence for follow-up unless you request deletion, subject to any applicable retention requirements. See Google’s privacy policy.

Purchases

This website links to ReplayProof in the Microsoft Store. Purchasing and installation take place through Microsoft Store. This website does not collect payment details or process checkout. See Microsoft’s privacy statement for its data practices. For app support, contact ReplayProof using the email above.