Public Notice

Notice

Important information about how Sudo operates, our security practices, and addressing misinformation.

What Sudo Is Overview

Sudo is a Lua script protection platform designed for Roblox developers. We provide obfuscation and delivery services that prevent your scripts from being stolen, decompiled, or redistributed without your permission.

Our system works by compiling your Lua scripts into custom virtual machine (VM) bytecode with multiple layers of protection. Every time a script is requested, it is re-obfuscated with completely new opcodes and variable names. No two outputs are ever the same. This makes it extremely difficult to reverse-engineer through pattern matching.

We also provide a key system that manages access to protected scripts. Users complete verification checkpoints to receive a time-limited key that is bound to their hardware ID (HWID). This prevents key sharing and unauthorized redistribution.

How Our Security System Works Important

There have been claims that Sudo "IP logs" its users. This is false. Here is exactly how the system works:

The system is fully automated. No human being manually looks at, stores, or collects IP addresses. The security system operates entirely on its own with no human intervention.

When you use the key system, your session is tracked using a browser fingerprint (a combination of screen resolution, timezone, language, and hardware info). This fingerprint is used to detect when the same person tries to use multiple accounts or bypass restrictions.

The only time IP-related information is involved is when the automated intrusion detection system identifies suspicious behavior. Here is what triggers it:

Account sharing — When two or more people attempt to log in to the same account from different devices or locations, the system detects the mismatch in browser fingerprints and flags the account.
VPN bypass attempts — When a user tries to circumvent a ban or restriction by using a VPN, proxy, or spoofing their fingerprint, the system detects the inconsistency and flags it.
Key system abuse — When someone attempts to generate multiple keys, share keys, or bypass the checkpoint system using automated tools or scripts.

When suspicious activity is detected, the system does the following:

Step 1: Automatic DetectionThe system identifies the suspicious behavior on its own. No admin is involved.

Step 2: Admin NotificationThe system notifies the admin panel that a potential violation has occurred. The admin sees a summary — not raw IPs.

Step 3: Ban DecisionThe admin is given the option to permanently ban the flagged account. This is the only human decision in the process.

Step 4: EnforcementIf banned, the user's HWID and browser fingerprint are blocked from accessing the service. The ban is permanent and automated going forward.

Nothing is stored for any purpose other than security. We do not sell data, we do not track browsing habits, and we do not share any information with third parties. The only data the system uses is what is necessary to prevent abuse.

Addressing Misinformation Read This

Certain individuals who have had their accounts banned for violating our Terms of Service — specifically for account sharing, attempting to bypass security measures, or distributing leaked source code — have spread false claims about Sudo. These claims are untrue and are motivated by retaliation.

Common false claims and the truth:

Claim: "Sudo IP logs all its users."
False. As explained above, the system uses browser fingerprinting for session management and abuse detection. IPs are not stored, logged, or accessible to anyone. The system is fully automated.

Claim: "The admin can see your personal information."
False. The admin panel shows account usernames, key status, and ban history. It does not display IP addresses, personal information, or any identifying data beyond your chosen username.

Claim: "Sudo steals your data / scripts."
False. You retain full ownership of your Lua scripts. Sudo only processes them for obfuscation purposes. Scripts are not stored permanently — they are obfuscated on-demand and delivered through single-use URLs that expire immediately after use.

People who leak source code, share accounts, or attempt to bypass security are violating our Terms of Service. When their accounts are banned as a result, some choose to spread misinformation to damage the platform's reputation rather than accepting responsibility for their actions.

Why Bans Happen Transparency

Bans are not issued arbitrarily. Every ban is triggered by the automated detection system identifying a clear violation. Here are the reasons an account can be banned:

Account sharing — Giving your login credentials to someone else. The system detects multiple fingerprints using the same account.
Key redistribution — Sharing, selling, or publicly posting your access key. Keys are bound to a single HWID.
Bypass attempts — Using VPNs, proxies, fingerprint spoofers, or automated tools to circumvent the key system or bans.
Source code leaking — Downloading, redistributing, or sharing the platform's proprietary source code.
Reverse engineering — Attempting to decompile, deobfuscate, or analyze the protection system.

If you follow the rules, you will never have an issue. The overwhelming majority of Sudo users have never been flagged or banned. The detection system only activates when there is a genuine violation.

Our Commitment Promise

Sudo is built by developers, for developers. Our goal is to protect your work — not to collect your data. We are committed to:

Keeping all security systems fully automated with minimal human involvement
Storing zero personal data beyond what is necessary for the service to function
Being transparent about how our systems operate
Providing a fair and consistent ban policy based on automated detection, not personal grudges
Continuously improving our security and obfuscation to stay ahead of reversers

If you have questions or concerns, reach out to us on Discord. We're always open to discussing how things work.