Devil-Guard can automatically evaluate signed protection status and network classifications and can instruct a participating Devil-Guard Server to perform a server-scoped action. This page describes the information used, likely consequences and human-review safeguards.
Configured rules may use signed PC-attestation status, executable approval, detection signals, the HawkSync-observed player name/IP, account/alias correlation, allowlists and IP-intelligence categories such as VPN, proxy, Tor or relay.
Server operators independently configure which classifications or protection failures trigger enforcement. A network service being classified as VPN/proxy/Tor/relay is a signal; the server policy determines the response.
On a participating server the result can include a grace period, allow/deny decision, HawkSync-managed ban, live kick, and paired inbound/outbound Windows Firewall rules scoped to the selected DFBHD UDP port/application/interface.
A PC detection can be saved while a user plays elsewhere, but Devil-Guard cannot enforce against that player on a non-participating server because it has no administrative control there.
Eligible restrictions can be appealed. Council/Admin users can review the available evidence and vote. The current council rule requires the configured approval threshold before an overturn is applied.
Users can challenge a restriction, provide context/evidence, request correction of inaccurate personal information, and—where applicable—exercise rights relating to automated decisions. A final council decision is retained in the compact ban history.
Devil-Guard publishes this information now so users can understand automated processing before Australia’s additional APP privacy-policy transparency obligations for certain automated decisions commence on 10 December 2026. Where GDPR Article 22 applies to a solely automated decision with significant effects, applicable safeguards can include human intervention, an opportunity to express a view and a way to contest the decision.
