License Terms (EULA)

1 · The grant

These License Terms apply to software products only — the FiveM resources and bundles sold on this site. Physical merchandise is sold as goods, is not licensed, and nothing in this document applies to it.

Each software purchase grants one non-exclusive, non-transferable license to run the product for a single community — meaning the server or set of servers operated as one community under the purchasing Cfx account. There is no numeric server cap inside a single community: live, development, and test servers of that one community are covered by the one license (see §2). Multiple unrelated communities require multiple licenses. Free products are licensed on the same terms at zero cost.

Escrowed components are delivered and enforced through the Cfx.re keymaster/escrow system bound to your Cfx account; open components are delivered as source.

2 · What you may do

Run the product on your community's live, development, and test servers. Modify the open components (config, locales, bridge glue, exports usage) for your own community's use. Build your own resources against the documented public exports and APIs.

3 · What you may not do

Resell, redistribute, sublicense, rent, share, or publicly post any part of the product (including modified open components); attempt to decompile, defeat, or extract escrowed components; use the product to build a competing derivative for distribution; remove license or attribution mechanisms. "Leaking" a product — making it available to anyone outside your community — terminates the license immediately.

4 · Updates and versions

A license includes all updates within the purchased major version (for example, 1.x). Major-version upgrades may be offered free or at an upgrade price at our discretion. Changelogs are public and dated; we never silently swap what a version contains.

5 · Revocation — and how it actually works

Licenses are revoked automatically if a purchase is refunded or charged back: our order system marks the order, revokes the associated grants, and records the action on an append-only audit ledger. Revocation for acceptable-use violations (including leaking) follows notice to your purchase email where practicable. Revocation is a state change on our ledger — we don't delete purchase history, we terminate the right to use.

6 · Warranty scope for licensed software

The product warranty is defined by the Terms of Service (§6–7). In short: we stand behind measured claims we publish, we fix severity-1 defects within our published SLA, and remedies are limited to fix, replacement, or the refund paths in the Refund Policy.