RevolutionMT2 · Crash Reports
Crash report privacy notice
Updated: 13 August 2026
Sending is optional. No report is transferred until you select it and click Send in the RevolutionMT2 patcher.
Controller and purpose
RevolutionMT2 uses these reports only to diagnose client crashes, freezes, incompatibilities and regressions, protect the service against abuse, and measure occurrences of the same technical issue.
Data collected
The report contains the technical logs and settings explicitly listed before sending. Text is redacted and configuration is reduced to an allowlist of graphics and technical settings.
- client version and executable identity;
- crash or freeze type and time;
- redacted logs, stacks and runtime context;
- an unchanged native minidump that may contain process-memory fragments;
- an anti-abuse identifier derived from the network address using HMAC, without storing the raw address.
Legal basis and choices
Processing relies on your explicit consent for each selection. You may choose Later, permanently ignore a local report, or request deletion using the token retained by the patcher.
Retention and security
Completed reports are retained for no more than 30 days. Incomplete uploads expire after 24 hours. Artifacts are validated, encrypted at rest and available only to authorized administrators.
Recipients and transfers
Reports are available to the RevolutionMT2 technical team and hosting providers required to operate the service. They are not sold or used for advertising.
Your rights
You can immediately delete your report with its deletion token. For access, erasure, restriction or consent withdrawal requests, contact official RevolutionMT2 support and provide only the report public ID.