Shield (“Shield”, “we”, “us”) provides a JavaScript and HTML code-protection service. This page explains what Shield is, what it is not, and the limits of its protections. Reading this in full is part of responsibly using the service.
No guarantee of unbreakability
Shield raises the cost and time required to reverse-engineer your code. It does not make code mathematically impossible to recover. Any JavaScript that executes in a browser can in principle be observed, stepped through, instrumented, and reconstructed by a sufficiently determined attacker with sufficient resources.
We do not warrant that obfuscated output cannot be deobfuscated, reverse-engineered, decompiled, fingerprinted, defeated, bypassed, or analyzed by automated tools, large language models, manual reverse engineers, or future technology.
Obfuscation is not encryption
Obfuscation transforms code so that it is harder to read; the original behavior is preserved. Secrets embedded in client-side code (API keys, tokens, credentials, business rules that drive billing) remain recoverable in principle even after obfuscation. Do not rely on Shield to keep secrets from a determined attacker who controls the runtime in which your code executes.
Security-critical decisions (authentication, authorization, rate-limiting, payment) must be enforced on infrastructure you control, not in client code.
No warranty of fitness
The service is provided “as is” and “as available.” To the maximum extent permitted by law, we disclaim all warranties, whether express or implied, including merchantability, fitness for a particular purpose, non-infringement, and any warranties arising from course of dealing or usage of trade.
Lawful use only
You are responsible for the code you submit and for ensuring that its obfuscation and distribution comply with all applicable laws and third-party licenses. Shield is not a tool for hiding malicious payloads, evading anti-abuse systems, or circumventing interoperability rights granted by law to legitimate users.
Submitting malware, spyware, credential stealers, ransomware, phishing kits, or any code intended to harm users or violate their privacy is prohibited and grounds for immediate termination.
Third-party services and dependencies
Shield’s runtime defenses optionally call third-party services (for example, geolocation lookups via ipapi.co for geo and IP locks). We do not control those services and cannot guarantee their availability or accuracy. The corresponding access locks fail open or closed depending on the strictness level you select.
Not legal or security advice
Nothing on this site, in our documentation, or in our communications constitutes legal, regulatory, or professional security advice. Consult qualified counsel and security professionals before deploying any obfuscation strategy as part of a broader compliance or risk-management program.
Limitation of liability
To the maximum extent permitted by law, Shield, its operators, contributors, and affiliates shall not be liable for any indirect, incidental, consequential, special, exemplary, or punitive damages arising out of or in connection with your use of the service, including but not limited to loss of data, loss of revenue, business interruption, or loss of goodwill, even if advised of the possibility of such damages.
Our aggregate liability for any direct damages is capped at the amount you paid us in the twelve (12) months immediately preceding the event giving rise to the claim.