A.C.E Shield
Anti-Cheat
A.C.E Shield is live: a user-mode check in the A.C.E desktop app (with your consent, only while CS2 runs) plus a server gate on every ranked match. Detections go to human review, never automatic bans.

A.C.E ANTI-CHEAT
Sign in to see your status
Anti-cheat runs in the A.C.E desktop app for Windows.
- Required for matchesYou can only join A.C.E matches while anti-cheat is active.
- User-mode, WindowsRuns inside the A.C.E app. No kernel driver.
- Live heartbeatA signed heartbeat every 15 seconds keeps your status green.
Warning: a detected cheat puts your account on a queue hold for owner review. A confirmed cheat leads to a permanent account and hardware ban. Appeals: /appeal or ace.platform.official@gmail.com.
How the A.C.E anti-cheat works today
- It is a user-mode check inside the optional A.C.E desktop app for Windows. There is no kernel driver.
- It runs only after you accept the consent screen in the app, and only while CS2 is running. You can switch it off in the tray menu; ranked play then requires it to be on again. Start with Windows is opt-in.
- It compares program names, window titles (browser, chat, media and office windows are skipped), CS2 modules and launch options with a list of known cheat tools. Only the matched list entry is sent, never a window title or your full process list. Your Windows username and computer name are not collected.
- The app also checks its own files, security settings and digital signature, and whether anything is debugging it. A modified A.C.E app refuses to start.
- Hardware: one-way hashes of hardware parts are made on your PC (the identifiers never leave it) and re-hashed on our server with a secret key. They are only used to enforce bans, including showing the owner when an account plays on the same PC as a banned account. A shared PC alone never bans or holds anyone.
- During matches on A.C.E servers, the server checks about every 30 seconds that your anti-cheat is still running. A short drop never counts; a session that stays silent for minutes gets a chat warning.
- Match servers compute fair-play statistics (aim, reactions, tracking or pre-aiming hidden players). Together with reports and the checks above they only decide what the owner reviews first.
- Nothing bans automatically. A finding holds your queue access and opens a case. The owner reviews the evidence and either releases you or confirms a violation. Dual-use tools such as debuggers or system monitors count only as a suspicion.
- Appeals: on the appeal page while signed in, where you can follow the status; every decision is backed by a sealed evidence record. What Shield can and cannot catch: the threat model. Questions: ace.platform.official@gmail.com. Details are in the Privacy Policy.
Architecture pillars
Client integrity
A lightweight client verifies the game environment during a match and reports tampering signals.
AvailableServer integrity
Match servers run locked configurations, signed plugins and tamper-evident logs.
AvailableMatch integrity
Every round is recorded with demos and event logs so any result can be reviewed.
In developmentBehaviour analysis
Statistical models flag outlier aim, reaction and information patterns for human review.
In developmentIdentity
Steam OpenID accounts, one player per account, with ban-evasion checks.
In development
Roadmap
- Available
Phase 1 · Architecture
Threat model, data flows and privacy design.
- ✓Privacy rules enforced in code
- ✓Signed client heartbeats flowing (24h)
- ✓Replay-proof heartbeats (one-time server codes)
- ✓Public threat model document
- In development
Phase 2 · Server & match integrity
Locked server configs, demo capture, tamper-evident logs.
- ✓Server plugin (AceBridge) reporting (7d)
- ✓Server-side connect gate enforced
- ○Match demos captured
- ○CS2 file-integrity hashes confirmed by players' PCs
- ✓Locked server configs verified
- ✓Each game server signs with its own key (shared key off)
- ○Shield re-checked every ~30 s during matches
- In development
Phase 3 · Behaviour analysis
Review tooling and first statistical models.
- ✓Review tooling (Overwatch, admin)
- ✓Kill telemetry collected
- ○Reviews completed
- ○Trained statistical model
- ✓Pre-aim, hidden-tracking and cross-match analytics
- ✓In-site appeals (/appeal)
- ○Sealed evidence records for decisions
- In development
Phase 4 · Client integrity
Shield client beta with a public security review.
- ✓User-mode Shield client
- ✓Known-tool detection with owner review (no automatic bans)
- ✓Installs verified against the official build
- ✓Device trust (hashed hardware parts)
- ○Verified updates (no downgrade, exact version)
- ○Signed releases (Windows code signature)
- ○Public security review
- Available
Phase 5 · Competitive beta
Shield required for ranked matches and tournaments.
- ✓Shield required to queue
- ✓Shield required for tournaments
Privacy principles
- We collect only what is needed to protect a match, and say exactly what it is.
- The desktop app sends only a hashed hardware fingerprint, re-hashed on our server with a secret key, and only after you consent.
- Anti-cheat session data is deleted after 90 days unless it is part of an open case or a confirmed ban.
- Every penalty can be appealed and reviewed by a person.
Questions
- Is A.C.E Shield active today?
- Yes. The desktop app (1.8.7+) checks for known cheat tools while CS2 runs, ranked queue requires it, and match servers refuse players the gate cannot verify. A detection puts the account on hold for owner review; there are no automatic bans. Phases still in progress are marked above.
- Will it need kernel access?
- No. The anti-cheat runs in user mode only; there is no kernel driver. Any deeper access would be announced and documented first.
- Does Premium affect anti-cheat?
- No. Integrity rules are identical for every player. Paid plans never buy competitive advantage.
- How do I report a cheater?
- Use the Report a player page (/report) while signed in. Every report is reviewed by a person under section 14 of the rulebook.
