Enforcement modes¶

Choose the ban-evasion mode in /config or the web dashboard. Both modes automatically ban a verifying member when EvadeGuard finds a qualifying high-confidence match. A separate blacklisted-community check can also trigger an automatic ban in either mode.

Automatic enforcement can affect legitimate users. A shared household or recycled network can create a network match, and no signal proves who controls an account. Make sure your moderators know how to handle questions and mistaken bans.

Ban evasion¶

EvadeGuard compares a verifying account with accounts currently recorded as banned from that same server. It imports the server's current ban list when the bot starts or joins, and updates records when it sees ban or unban events. A matching account is automatically banned when the match meets the enforcement threshold.

High-confidence account links are based on a matching first-party verification cookie or residential-network signal. A matching browser/user-agent or coarse device signal alone is too weak to trigger a ban. Mobile/cellular and institutional network matches are also low-weight and cannot trigger a ban by themselves. VPN, proxy, and Tor detections are blocked separately during verification; they do not by themselves mean the account is banned from Discord.

Use this mode when you want to reject accounts linked to a current ban in your server, rather than every account linked to a previously verified member.

Strict — No Alts¶

Strict mode compares the verifying account with accounts that previously completed verification in the same server. A qualifying high-confidence account link triggers an automatic ban, even when the earlier account is not on the server's current ban list.

Use this mode only if your server intends to prevent linked alternate accounts from verifying. Review the potential impact on shared devices and networks before enabling it.

Blacklisted communities¶

Blacklisted-community enforcement is separate from the mode above. If a server owner lists a Discord community ID and Discord reports that the verifying account belongs to that community during sign-in, EvadeGuard requests an automatic ban from the server performing verification. This does not ban the account from the listed community. The bot needs Ban Members and sufficient role hierarchy to perform the ban.

Other signals¶

During verification, EvadeGuard may compare network, browser, device, and Discord community-membership signals to identify unusual account overlap. Common or very large communities are excluded. Community overlap is a low-weight signal and cannot trigger an automatic ban by itself.

Temporary verification records are automatically cleaned up after they expire and pass the service's 30-day retention window. Some separate security records, such as active ban markers, enforcement events, and account links formed from high-confidence signals, are retained separately. See the privacy and data guide and full privacy policy for details.