Skip to content
SCULKANTICHEAT
Sign up
Published by
Sculk AntiCheat

Prices on www.sculkac.com are in Australian dollars.

Sculk AntiCheat — End-User Licence Agreement

Last updated: 20 September 2026. This agreement covers installing and running the Sculk AntiCheat software — the Minecraft server plugin and the FiveM server resource. Purchasing terms live in the Terms of Service.

1. Licence grant

You may install and run the software on the number of servers your tier allows (Minecraft — Free: one server; Premium: one server per licence; Network: unlimited backend servers behind one proxy. FiveM — monthly and yearly subscriptions: one server per licence; grandfathered FiveM Server: one server; grandfathered FiveM Network: unlimited servers operated by the same owner). The software is licensed, not sold; we keep all rights not granted here.

FiveM licences are sold as recurring subscriptions (monthly or yearly) that renew automatically until cancelled. Cancelling stops future renewals and the licence stays active until the end of the period already paid for. If a renewal payment fails, the licence stops and the resource loses protection at its next heartbeat; paying the renewal (or resubscribing) restores the same key immediately. Grandfathered one-time FiveM licences never renew and never expire.

2. Restrictions

  • No redistribution of the jar, in original or modified form, public or private.
  • No sharing, renting, or pooling of licence keys across owners.
  • No reverse engineering, except where law grants that right regardless of this agreement.
  • No use of the plugin to build a competing detection product.

3. Server data

The software analyses player traffic on your server in memory. Detection and moderation records do not stay only on your infrastructure: the resource sends them to Sculk so they appear in your dashboard, can be reviewed by your staff, and survive a server wipe. What is transmitted to and stored on our systems is:

  • Moderation events — the player’s in-game name and identifier, which detection fired, the reason, and the acting staff member.
  • Bans — the player’s in-game name, their identifiers, their hardware tokens, and their IP address.
  • Screen captures — when your staff request one, or automatically when a warn, kick or ban happens if you have turned that on (it is off by default), an image of the player’s game view, stored against their name and identifier.
  • Server and licence metadata — your licence key hash, platform and resource version.
  • Identity links — if a player runs /link, the resource sends us the identifiers your server observed for them, so that a completed Discord sign-in can be joined to that machine. What is stored, how long it is kept, and why these links are held per licence and never shared with other customers are set out in the Privacy Policy.

Bans can be shared between customers, and you decide in both directions. While Config.GlobalBanSharing is on — the default — bans your server issues are contributed to a cross-server database and offered to other Sculk-protected servers. Set it to false and your bans stay on your server. Publishing your players’ identifiers to other operators is your call, not a condition of using the software.

Bans issued elsewhere are never applied to your server automatically. Config.GlobalBanApply, on by default, controls whether you receive the shared feed at all; set it to false and the feed is ignored entirely. A received shared ban is filed as a review signal naming the player, the detection and the evidence. It refuses nobody, and no setting makes it enforce — the old auto-enforcement option was removed from the software. Only your own detections or your own staff ban a player on your server. Your own bans are unaffected by any of this.

Bans you have already published are withdrawn by unbanning locally: the withdrawal is sent back to the shared database ahead of everything else queued, whether or not sharing is still switched on, and servers holding the record drop it. Nothing you contribute is one-way.

You remain the controller of your players’ data and we process it to provide the service. You are responsible for telling your players that an anticheat is in use and what it records, where your jurisdiction requires it. Retention periods and your rights are set out in our Privacy Policy.

4. Updates

Updates may change check behaviour, config formats (with migration notes in the changelog), and system requirements. Staying on old versions is allowed but unsupported.

5. Termination

The licence ends if you materially breach this agreement (chiefly: redistribution or key sharing). On termination you must remove the plugin from your servers. Sections 3, 6, and 7 survive termination.

6. No warranty

The plugin is provided "as is". We do not warrant that it will detect every cheat, never flag a legitimate player, or run without interruption. You are responsible for punishment decisions made on your server, including reviewing ban waves before or after they run.

7. Liability

To the maximum extent the law allows, our total liability under this agreement is limited to what you paid for the licence.

Sculk AntiCheat is not an official Minecraft product and is not approved by or associated with Mojang or Microsoft. FiveM and Cfx.re are trademarks of their respective owners; Sculk is independent and not affiliated with them.