Anti-cheat / Fair Play Agreement (FAIRPLAY-1.2)

Strike Fighter League · FAIRPLAY-1.2 · effective 2026-10-15

# SFL Fair Play Agreement

This Agreement is between you and Strike Fighter League Inc., a Delaware corporation ("SFL"). It protects fair competition for every pilot.

# 1. Scope

Clause 3 applies from the day you accept this Agreement. Clauses 2 and 4 apply to SFL Sessions. An "SFL Session" is any time you are connected to an SFL server, flying an SFL qualification run, or completing an SFL entry or verification step.

In this Agreement, the "Competition Rules" are the SFL Competition Charter and the SPINS that SFL publishes for each event, as the SFL Code of Conduct describes.

# 2. Prohibited aids

You will not use, install, or run during any SFL Session:

(a) cheats, hacks, trainers, injectors, or memory editors;

(b) any mod, script, file, or setting that the Competition Rules prohibit, or that gives an advantage the Competition Rules do not make available to every pilot;

(d) any tool that shows you information the sim does not show in normal play, such as hidden aircraft positions.

# 3. Prohibited practices

You will not:

(a) exploit a bug, glitch, or server weakness for advantage (report it to SFL instead);

(b) let anyone else fly on your account or under your callsign, or fly for anyone else;

(d) register or verify a DCS UCID that is not yours;

(e) collude with another pilot to fix a result;

(f) use a live broadcast or spectator feed to gain information during a match; or

(g) tamper with, disable, spoof, or reverse engineer any SFL verification tool, server, recording, or score file.

# 4. Verification

SFL may verify you when you enter an event and during SFL Sessions. Verification consists of:

(a) confirming your DCS UCID with the SFL UCID-Verify Tool, which temporarily configures your DCS installation, captures only the verification data it needs, and restores your installation when it exits;

(b) checks of your DCS installation, your installed mods, and the files that matter to fair play;

(d) a hardware profile of your computer: your operating system, your processor, your graphics card, and the amount of memory installed;

(e) a cheat-tool check: whether any program running on your computer is on SFL's fixed list of programs that can give an unfair advantage, recorded as yes or no only;

(f) when an event requires the SFL Virtual Pilot Kit, sampling of your stick, throttle, and rudder signals during SFL Sessions, to check fair play; and

(g) any other check the Competition Rules describe for a specific event, within the scope of Schedule A of the SFL Pilot Terms and Conditions.

SFL describes its checks, and what each one collects, before you enter. Within that description, SFL may run any of these checks at any time during an SFL Session, including spot checks, without separate notice for each check.

The checks read your DCS installation and its mods, the state of DCS while you fly, your connection, the hardware profile in (d), the yes-or-no result in (e), and the samples in (f). They collect nothing else from your computer. The checks never read your computer's name or the name of your Windows user account. The cheat-tool check compares the programs running on your computer with SFL's list and records only yes or no. It never records the name of any program, and never reads what a program contains or displays, its window titles, its files, or its command line. Verification never collects your passwords or the credentials of any account, and never reads your personal files, documents, messages, or browsing data.

Verification never uses your webcam or any face-camera feed. The broadcast face camera is for broadcast only. It is not used in qualification runs. If you qualify for the live bracket, it is a condition of competing in it, as section 6.1 of the SFL Pilot Terms and Conditions describes.

Section 7 and Schedule A of the SFL Pilot Terms and Conditions describe the SFL verification tools in full.

# 5. SFL Virtual Pilot Kit

When an event requires the SFL Virtual Pilot Kit (VPK), SFL presents the VPK's own terms when you enter that event (section 8 and Schedule B of the SFL Pilot Terms and Conditions). Those terms describe what the VPK inspects, and how it temporarily changes your DCS installation for a session and restores it when it quits.

# 6. Security Data

"Security Data" means data produced or read by the checks in clause 4 and by the VPK's integrity function, including: DCS installation, configuration, version, and state readings; installed-mod inventories and integrity results; the hardware profile and the cheat-tool check result; control-input samples; inspection results and integrity logs; and the network latency and speed-test baselines.

SFL uses Security Data only for competition integrity, fairness adjudication, verification, and event scheduling. SFL never uses it for marketing. SFL never sells Security Data, never licenses it, and never includes it in any licensed or research dataset.

No Security Data is ever reclassified as, combined into, or delivered as Competition Materials (the recordings and footage of your flying used for broadcast and coverage) or as Control-Input Telemetry (a record of your stick, throttle, rudder, and other control inputs), even where the underlying signals are similar.

The control-input samples in clause 4(f) are Security Data. They stay on your computer or go only to SFL's Security Data store. They are not Control-Input Telemetry. SFL does not use the samples to identify or verify who is flying.

SFL keeps Security Data for 12 months from the event, then deletes it, unless SFL preserves it for a specific investigation. The same period applies to control-input samples wherever they are held, including those saved on your computer. The SFL Privacy Notice states the same period.

# 7. Refusal

If you refuse a verification step, SFL may treat you as ineligible for that event.

# 8. Enforcement

A breach of this Agreement is also a breach of the SFL Code of Conduct. Sanctions and appeals follow Code of Conduct clauses 5 and 6. A cheating finding may also void your results and prizes for the affected events, and may lead to a permanent ban.

# 9. Third-party software

Your DCS installation, and any other software you use, stays governed by its own license terms. You are responsible for complying with them. This Agreement grants no rights in any third-party software.

# 10. Part of the Terms

This Agreement forms part of the SFL Pilot Terms and Conditions from the first version of those Terms that lists it. Until then, this Agreement governs you on its own, from the day you accept it at registration or on your account page, and SFL changes it the same way it changes the SFL Code of Conduct (Code of Conduct clause 7).

How SFL handles your data: SFL Privacy Notice (PRIVACY-NOTICE-2.1).