Skip to content
Legal

Anti-Cheat Circumvention Statement

Last updated: November 18, 2026

This Statement puts on record how Scrappy builds software: no anti-cheat circumvention, no reverse engineering of protected code, no bypassing of technological protection measures.

1. Purpose of this statement

This Statement documents Scrappy's development standards on anti-cheat systems and protected software mechanisms. It exists to affirm clean-room development practices, clarify exactly how our Software operates, and put on record that Scrappy does not engage in anti-cheat circumvention, reverse engineering of protected game code, or bypassing of technological protection measures.

2. No anti-cheat bypassing

The Software operates externally, without touching protected components of game software or anti-cheat platforms.

  • It does not disable, bypass, or interfere with anti-cheat systems or their enforcement.
  • It does not access protected memory regions monitored by anti-cheat.
  • It does not spoof or falsify anti-cheat telemetry.
  • It does not attempt to avoid detection through kernel manipulation or driver modification.

3. External-only operation

The Software is strictly designed to work through external methods: reading publicly accessible system-level information, drawing overlays outside the game process, non-invasive interface automation, and standard OS-level interactions. It does not inject code into game processes, hook or patch game binaries, access encrypted or protected memory, or execute privileged operations intended to evade detection.

4. No access to protected works

Scrappy does not reverse engineer protected game files, intercept game network traffic, decompile proprietary game code, or use leaked or unauthorized SDKs and tooling. Development relies on legitimately purchased copies of the supported games, public documentation, standard operating-system APIs, and clean-room engineering.

5. No circumvention of protection measures

Scrappy does not create or provide tools that circumvent technological protection measures under the Singapore Copyright Act, U.S. DMCA §1201, the EU Copyright Directive, or equivalent laws. The Software is not built to defeat encryption, access controls, integrity verification, security modules, kernel protections, or obfuscation systems — its functionality stays entirely within what the operating system permits.

6. Your responsibility

You are solely responsible for complying with third-party terms and local law, and for not using the Software where such tools are restricted. Scrappy does not encourage or condone using its Software to violate game terms of service, anti-cheat policies, or copyright and licensing agreements. The Software is provided strictly for lawful personal use.

7. Prohibited users

To reduce exposure to misuse and investigative access, use by employees, agents, or contractors of anti-cheat vendors or of the publishers behind our supported games (Embark Studios, Facepunch Studios, Team17 / Bulkhead, Kefir), by individuals acting for security researchers or enforcement divisions, and by persons in or accessing from Sweden, is prohibited. Users must represent that they belong to none of these categories.

8. Development controls

No Scrappy engineer accesses protected code or internal game resources, all testing runs in clean-room conditions, no code is written with intent to bypass security controls, and all modifications stay external to game processes. We review our technical architecture regularly to keep it that way.

9. Limits of this statement

Nothing here grants permission to use third-party software improperly, overrides the Terms of Service, EULA, or Privacy Policy, or guarantees that publishers will not enforce their own terms. This Statement only clarifies Scrappy's development approach and legal posture.

Questions about this document? Reach us onDiscord.