Writing a Scan Policy for Your Community Server

Asking players for a scan works best when everyone knows the rules in advance. A written policy keeps decisions consistent between admins, protects honest players from arbitrary bans and makes appeals easier. This guide helps you write one.

1. Decide when you ask for a scan

• Always: before scrims, cups and matches with prizes, and for players joining a clan or team.
• On suspicion: after several reports from different players, or when an admin who watched the player asks for it.
• Optional: for regulars who want a "verified" role. A good scan history is a reward, not only a test.

Don't demand scans in the middle of an argument or as revenge for a lost round. Players accept rules that are applied the same way to everyone.

2. Decide what counts as proof

• Only accept a scan link or PIN that you open yourself. Screenshots can be edited. See Sharing a scan with a PIN.
• The scan should be made by a player signed in with Steam (verified) and match the SteamID on your server.
• Set a time window, for example "made within the last 30 minutes" for matches. The scan page shows the scan time, the game and the server the player was on (LIVE if connected during the scan).
• For matches, add a pre-match check link right before the start, and ask players to keep AACGuard Live running.

3. Decide what each verdict means on your server

• CLEAN: the player may play. A clean scan is not a lifetime pass; you can still ask again later.
• SUSPICIOUS: not a ban reason on its own. Read the findings, ask the player about them, ask for a second scan or a pre-match check. See Reading a scan result.
• CHEAT DETECTED: read the findings first. Check their dates (guide) and the game they belong to. If they are recent and for your game, act according to your rules.
• Refusing a scan: decide in advance. Many communities treat refusing a scan they announced in their rules the same as failing it.

4. Give players a way to appeal

Mistakes happen, on both sides. Link players to the appeal on their scan page (how appeals work) and tell them how to contact your own staff. Write down who decides appeals on your server and how long it takes.

5. Respect privacy

• Don't post players' scan logs in public channels. Link the scan page instead; it already hides personal details.
• Use the scan for anti-cheat decisions only, not to comment on what other software someone has installed.

Template you can copy

Anti-cheat rules
1. Admins may ask any player for an AACGUARD scan before scrims, cups and matches, or after repeated reports. Download it only from aacguard.com.
2. Send the scan link or the 6-digit PIN to the admin. Screenshots are not accepted. Scans must be made while signed in with the same Steam account you play with, within 30 minutes of the request.
3. CLEAN: you may play. SUSPICIOUS: an admin reviews the findings and may ask for a second scan. CHEAT DETECTED: an admin reviews the findings; recent cheats for this game lead to a ban.
4. Refusing a requested scan, or leaving the server to avoid it, is treated as a failed scan.
5. Keep AACGuard Live running during matches.
6. Appeals: use the appeal button on your scan page and open a ticket on our Discord. Bans are reviewed within 7 days.

Adjust the numbers to your community. Post the rules where players see them before they join, for example in your server's MOTD and on your server page.