This notice applies when a player connects to a participating DFBHD server protected by Devil-Guard Server and HawkSync, including players who do not have a Devil-Guard website account or Devil-Guard PC installed.
HawkSync/Devil-Guard Server can observe the player name presented to the game server, the IP address actually used for the DFBHD connection, the protected server/port, connection timing and server-side enforcement results.
Where the server operator enables IP intelligence, the observed game IP may be classified for signals such as VPN, proxy, Tor or relay and associated network/provider information. The server policy determines whether a category leads to enforcement.
A game-server IP cannot be converted into a Windows GDID. If Devil-Guard PC is not installed/running, the protected server can still record the server-observed player name/IP and applicable network/enforcement information, but it does not obtain a verified Windows GDID from that player.
Where the player has a registered, signed Devil-Guard PC identity and the live evidence is sufficient to match it safely, the website can associate the server-observed game IP with that verified device identity under the published PC Monitoring and Privacy notices.
Depending on published server rules, a participating server may allow the join, provide a grace period, deny/kick the live player, create a Devil-Guard-owned HawkSync restriction, or apply scoped inbound/outbound DFBHD firewall rules.
Eligible restrictions can be appealed. After a final council decision, detailed case-linked evidence and session material is minimised under the Data Retention policy while a compact ban-history record remains; an upheld active restriction keeps the minimum identifiers still required to enforce it.
Participating server operators should make this notice and their own game/server rules reasonably accessible to players, for example from the server website, rules page or join/MOTD information where technically practical.
