> For the complete documentation index, see [llms.txt](https://docs.zaroguard.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zaroguard.com/terms-and-service.md). # Terms & Service ## Terms of Service **Effective date: August 3, 2026** These Terms of Service govern access to and use of ZaroGuard, also referred to as Zaro, including its website, dashboard, APIs, key system, script-protection tools, staged script-delivery system, and related services. The Privacy Policy forms part of these Terms and explains how ZaroGuard processes information. It is available at Privacy Policy. By accessing or using ZaroGuard, submitting a script for protection, creating or using an access key, or executing a ZaroGuard-protected script, you agree to these Terms. If you do not agree, do not use the service. ### 1. Eligibility and Authority You may use ZaroGuard only if you are legally permitted to do so in your location and are able to agree to these Terms. If you use ZaroGuard for another person, team, or organization, you represent that you have authority to bind them to these Terms. You are responsible for ensuring that your use of ZaroGuard, Roblox, an executor, protected scripts, and third-party services complies with all laws, platform rules, licenses, and agreements that apply to you. ### 2. The Service ZaroGuard provides tools that may include: * a developer dashboard and API; * script protection and obfuscation; * storage and delivery of protected script payloads; * staged loaders, temporary delivery links, execution tokens, and chunk delivery; * access keys, user lists, key-system settings, subscriptions, and plan limits; * HWID-based access controls, blacklists, bans, anti-tamper checks, and runtime validation; * execution logs, analytics, stage heartbeats, incomplete-progression monitoring, and client diagnostics; and * optional Discord authentication and webhook notifications. Features may differ by subscription tier, account, script, executor, configuration, or service availability. ZaroGuard may add, modify, limit, suspend, or discontinue features when reasonably necessary for maintenance, security, compatibility, abuse prevention, or operation of the service. ZaroGuard does not guarantee that obfuscation makes a script impossible to inspect, copy, reverse engineer, or bypass. No protection or anti-tamper system is completely secure. ### 3. Accounts, Access Keys, and Authentication You must provide accurate and current information when registering, authenticating, purchasing or receiving access, or configuring the service. You are responsible for protecting your access key, account session, Discord account, webhook URLs, API credentials, passwords, and other authentication information. You must not sell, share, publish, or transfer credentials unless ZaroGuard expressly allows it. Activity performed through your account or credentials may be treated as authorized by you until you notify ZaroGuard of unauthorized access. Contact support promptly if you believe an account, key, webhook, or session has been compromised. ZaroGuard may require Discord authentication, CAPTCHA verification, session validation, or additional security checks before granting access. ### 4. Developer Scripts and Content As between you and ZaroGuard, you retain the rights you lawfully hold in scripts and content you submit. You grant ZaroGuard a limited right to process, transform, obfuscate, store, cache, reconstruct, and deliver that content only as reasonably necessary to operate, secure, maintain, and improve the requested service. The original raw script is processed to create a protected or obfuscated payload. ZaroGuard stores the resulting protected payload in database chunks for authorized delivery and may keep temporary cached copies. ZaroGuard does not intentionally retain the original raw upload after the protection process is completed. Depending on the configured workflow, script content may be processed using local tools or third-party obfuscation services. Additional information is provided in the Privacy Policy. You represent and warrant that: * you own the submitted content or have all permissions required to process and distribute it; * your content and its intended use do not violate law, intellectual-property rights, privacy rights, platform rules, or agreements applicable to you; * your script does not contain malware, destructive functions, credential theft, unauthorized surveillance, undisclosed logging, or code intended to harm users or systems; * you provide any notices and obtain any consent required for data collection performed independently by your script; and * information, webhook URLs, user notes, and access lists you submit are lawful and accurate. ZaroGuard does not review or approve every protected script and is not responsible for the behavior, accuracy, safety, legality, or availability of developer-provided code. The developer remains responsible for their script and its users. ### 5. Protected-Script Users A protected script may require staged verification before its protected payload runs. These stages may validate script status, temporary tokens, HWID or client identifiers, Roblox identity, executor identity, request order, delivery completion, and runtime activity. Users must not interfere with, skip, replay, forge, hook, suppress, or manipulate these checks. Users receive only a limited, revocable right to execute an authorized protected script for its intended purpose. This does not transfer ownership of the script, loader, protection system, or ZaroGuard service. A script developer is an independent party. Any promises, purchases, support, data collection, or disputes relating to the developer's underlying script are between the developer and the user unless ZaroGuard expressly states otherwise. ### 6. Acceptable Use You must not, directly or indirectly: * bypass, disable, tamper with, hook, spoof, replay, or evade ZaroGuard security or execution checks; * reverse engineer, decompile, disassemble, dump, decode, extract, pirate, copy, leak, resell, or redistribute protected scripts, loaders, tokens, or protected code without authorization; * obtain or attempt to obtain another user's scripts, account data, access keys, webhooks, sessions, HWIDs, or private information; * probe, scan, attack, overload, flood, spam, scrape, or disrupt the website, APIs, databases, networks, tunnels, or service providers; * forge headers, fingerprints, Roblox identities, Discord identities, request origins, stages, heartbeats, or execution results; * upload malware, credential stealers, destructive code, unlawful content, or code designed to collect information without required notice or consent; * use ZaroGuard to violate intellectual-property, privacy, consumer-protection, computer-misuse, or other applicable laws; * use automated systems against the service except through an API or integration expressly provided for that purpose; * interfere with another developer's scripts, users, subscriptions, webhooks, or access controls; or * assist, encourage, sell tools for, or knowingly enable any prohibited activity. Reasonable security research requires prior written authorization from ZaroGuard and must remain within the authorized scope. If you did bypass,fold,spam etc you will get ip banned for life ### 7. Security Enforcement and Automated Decisions ZaroGuard uses automated and manual security systems. The service may deny a request, stop execution, kick a client, invalidate a token, blacklist an HWID, apply a global ban, disable a script, restrict an account, or record a security event when it detects suspected tampering, spoofing, replay, missing stages, identity mismatch, abuse, or unauthorized access. Automated detections may occasionally be incorrect. A user or developer may request review through the official ZaroGuard support channel. Submitting an appeal does not guarantee reversal and does not suspend restrictions while review is pending. Severe or repeated violations may result in immediate suspension or termination without advance notice. ZaroGuard may preserve relevant records when reasonably necessary to investigate abuse, enforce restrictions, resolve disputes, or comply with law. ### 8. Subscriptions, Limits, and Payments Some features require a subscription, access key, or assigned plan. Plans may impose limits on scripts, obfuscations, users, executions, storage, features, or duration. Current limits shown in the dashboard, purchase page, invoice, or direct offer are part of the applicable plan. Access may begin when a key or subscription is activated and may end when its configured duration expires. Expired access may prevent uploading, editing, rebuilding, or managing scripts. ZaroGuard may send expiration notices, but failure to receive a notice does not extend access. Unless a purchase page or written offer expressly says otherwise, purchasing one access period does not guarantee automatic renewal, future pricing, permanent access, or availability of every present feature. Questions about an incorrect payment, duplicate charge, or refund request must be submitted through official support with sufficient transaction information. Refund eligibility depends on the terms presented for the purchase, the circumstances, and applicable law. ZaroGuard does not guarantee a refund merely because a user changed their mind, failed to use the service, used an incompatible executor, or violated these Terms. You must not make fraudulent payments, abuse refunds, or file a dishonest chargeback. ZaroGuard may suspend access while a payment dispute is investigated. ### 9. Webhooks and Third-Party Services ZaroGuard can send execution, denial, security, and subscription events to Discord webhooks configured by developers or administrators. You are responsible for securing webhook URLs and for ensuring that your webhook use complies with Discord's rules and applicable privacy requirements. The service also depends on third parties such as Cloudflare, Discord, CAPTCHA providers, geolocation services, hosting providers, and obfuscation providers. ZaroGuard does not control and is not responsible for third-party downtime, DNS failures, API changes, account restrictions, processing, or terms. Links or integrations do not mean that ZaroGuard endorses all third-party content or conduct. ### 10. Privacy Use of the service is subject to the Privacy Policy. Developers must not use ZaroGuard data, analytics, HWIDs, Roblox identities, countries, diagnostics, or webhook events to harass, discriminate against, expose, or unlawfully track users. Developers who independently collect information through their scripts are responsible for providing their own notices and satisfying all applicable privacy obligations. ### 11. Suspension, Termination, and Script Removal You may stop using ZaroGuard at any time. Developers may remove or disable scripts using available controls. ZaroGuard may suspend or terminate an account, key, subscription, script, HWID, IP address, token, or access to the service when reasonably necessary because of: * a violation of these Terms; * security risk, fraud, abuse, or suspected unauthorized activity; * nonpayment, payment reversal, or subscription expiration; * a legal request or legal obligation; * harm to ZaroGuard, its infrastructure, providers, developers, or users; or * discontinuation of a service or feature. Where practical and safe, ZaroGuard may provide notice or an opportunity to appeal. Immediate action may be taken when delay could create risk. Termination ends your permission to use the affected service. Provisions concerning ownership, restrictions, liability, enforcement, disputes, and retained security records survive when their nature requires it. ### 12. Service Availability and Changes ZaroGuard is provided on an as-available basis. Requests may fail because of executor limitations, DNS or network problems, Cloudflare or hosting outages, third-party APIs, Roblox changes, rate limits, maintenance, obfuscator incompatibility, or user-script resource requirements. ZaroGuard may deploy updates, rotate tokens, rebuild protected stages, modify security checks, or temporarily restrict traffic without advance notice when needed to protect or restore the service. You are responsible for keeping backups of your original scripts and configuration. ZaroGuard is not a source-code backup service and should not be the only place where a developer keeps important code. ### 13. Disclaimers To the maximum extent permitted by applicable law, ZaroGuard is provided as is and as available, without warranties of uninterrupted availability, error-free operation, compatibility with every executor or client, complete security, merchantability, fitness for a particular purpose, or non-infringement. ZaroGuard does not guarantee that a protected script cannot be copied or bypassed, that every attack will be detected, that every automated decision will be correct, or that third-party services will remain available. Nothing in these Terms excludes a warranty or right that cannot legally be excluded. ### 14. Limitation of Liability To the maximum extent permitted by applicable law, ZaroGuard and its operators will not be liable for indirect, incidental, special, consequential, exemplary, or punitive loss, or for loss of profits, revenue, data, scripts, users, reputation, access, or business opportunity arising from use of or inability to use the service. ZaroGuard is not responsible for developer-provided scripts, independent logging added by developers, executor behavior, Roblox enforcement, third-party outages, leaked credentials, insecure webhook configuration, or use that violates these Terms. Where liability cannot be excluded, it will be limited to the amount the affected customer paid to ZaroGuard for the service during the three months immediately before the event giving rise to the claim, unless applicable law requires a different amount. ### 15. Responsibility for Claims To the extent permitted by law, you are responsible for losses, claims, or costs arising from your scripts, content, unlawful data collection, infringement, credential misuse, violation of these Terms, or misuse of the service. This section does not require a consumer to waive rights that cannot legally be waived. ### 16. Changes to These Terms ZaroGuard may update these Terms when services, security requirements, providers, or legal requirements change. The effective date will be updated when revised Terms are published. Material changes apply prospectively after publication. Continued use after revised Terms become effective constitutes acceptance of the revised Terms. If you do not agree to a revision, stop using the service. ### 17. Disputes and Contact Before starting a formal dispute, contact ZaroGuard through the official Discord support channel and provide enough information to investigate the issue. Both sides should attempt in good faith to resolve the matter informally. If informal resolution is unsuccessful, disputes will be handled by a court or other forum with authority under applicable law. These Terms do not select a specific country or state whose law applies because no governing jurisdiction has been published by ZaroGuard. For account, payment, security, copyright, privacy, or Terms questions, contact ZaroGuard through the official ZaroGuard Discord support channel listed on the ZaroGuard website or documentation.