Protected by design
Your Luau source is compiled into a protected, encrypted delivery format. The original work stays yours; users receive the protected build, never direct access to your editable source.
The conditions for using LuaWarden, access control and creator-owned code.
By accessing and using the LuaWarden infrastructure you confirm that you have read, understood and accepted these terms. We may revise them at any time, and the current version always applies.
• Strictly personal: every whitelist key generated through LuaWarden is personal, unique and non-transferable.
• Hardware locking: each key is bound automatically to the Hardware ID of the first executor that claims it.
• Bypass & abuse policy: attempts to spoof, emulate or bypass HWID verification, or unauthorized resale of keys, result in immediate key revocation and a permanent HWID ban across the network.
We never claim ownership of the scripts you upload. However, it is strictly prohibited to use LuaWarden to protect malicious software, account stealers (loggers), malware, or anything that violates Roblox or Discord Terms of Service.
If a leak, bypass or vulnerability affecting our protection or auth system is disclosed, we move as fast as possible to ship a real-time hotfix and patch the flaw so the integrity of your scripts is restored.
We aim for high uptime, but LuaWarden runs on Cloudflare's free tier and is provided as-is. We are not responsible for losses caused by maintenance, platform changes or hosting outages.
An overview of protected delivery and compatible optimization, without disclosing internal implementation.
Your Luau source is compiled into a protected, encrypted delivery format. The original work stays yours; users receive the protected build, never direct access to your editable source.
Every chunk of a protected build carries checksums that are verified before execution. Edited, truncated or tampered payloads die silently, with no error left to study.
Presets balance protection depth against loading time and runtime cost, from a lightweight pass to a full custom bytecode VM. Results depend on script complexity and the execution environment.
Keys, whitelists, IP locks and server-side authorization decide who receives your protected script. No protection technology can guarantee distributed code will never be inspected.