Terms of Service

Last updated: July 2026

These terms govern your use of rymga Lock Master, operated by rymga ("we", "us"). By requesting access or using the service, you agree to them. If you don't agree, don't use it.

1. The service

Lock Master obfuscates Java bytecode you submit and returns a protected build. It is provided as a cloud service with a command-line client. Features, plans and limits may change over time.

2. Access & eligibility

The service is invite-only. Access is granted at our discretion after you request it, and we may decline or revoke access. You must be able to form a binding contract and provide accurate information in your request. You're responsible for keeping your account and API keys secure.

3. Acceptable use

You agree that software you submit for obfuscation:

• breaks no applicable law;
• is not malware and is not intended to harm, deceive or gain unauthorized access to systems;
• does not violate any third party's rights or terms (including platform or marketplace terms).

You may not resell, sublicense, or use the service to build a competing obfuscation service, nor attempt to disrupt, reverse-engineer or abuse the service or its infrastructure.

4. Manual configuration

The service requires you to write and tune a configuration for your project. It is a tool, not a one-click button, and results depend on how you configure it and on the nature of your code.

5. Licenses, tokens & payment

Plans grant a monthly token allowance (use-it-or-lose-it) and a number of seats; token packs are one-off and do not expire. The token cost of a job is metered by the size of the build. Payments are processed by Stripe; by subscribing you authorize recurring charges until you cancel. Prices may change with notice for future billing periods. Refunds are governed by our refund policy.

6. Your content

You retain all rights to the software you submit. You grant us only the limited, temporary rights needed to process it and return a result. We do not execute your code, and we do not retain your submitted or produced JARs beyond what's needed to deliver the job. See our privacy policy.

7. No warranty

The service is provided "as is". No obfuscation is 100% unbreakable, and we make no guarantee that protected code cannot be reversed, nor that the service will be uninterrupted or error-free. You are responsible for testing every protected build before you ship it.

8. Support scope

Support covers defects in the obfuscation engine only. It does not cover programming errors in your own code, general Java assistance, or issues caused by configurations we didn't recommend.

9. Limitation of liability

To the maximum extent permitted by law, we are not liable for indirect, incidental or consequential damages, or for loss of profits, data or goodwill. Our total liability for any claim is limited to the amount you paid us for the service in the three months before the claim.

10. Termination

You may stop using the service at any time and cancel from billing. We may suspend or terminate access for breach of these terms. Provisions that by their nature should survive termination (e.g. sections 6–9) survive.

11. Changes

We may update these terms; material changes will be communicated. Continued use after a change means you accept the updated terms.

12. Contact

Questions about these terms: [email protected].