Terms of Service

These Terms of Service govern your access to PyDecode, including the website, dashboard, Python bytecode recovery engine, REST API, MCP server, credit system, and related services (the “Service”). By creating an account or using the Service, you agree to these Terms.

You must be at least 18 years old or the age of legal majority where you live. If you use the Service for an organization, you represent that you have authority to bind that organization to these Terms.

Provide accurate account information and protect your password, sessions, API keys, and MCP credentials. API keys are bearer secrets: anyone who possesses one may act within its access scope and consume your credits.

• Use a unique password and revoke credentials you no longer use.
• Do not share an account in a way that defeats security controls.
• Contact playsharp@playsharp.io promptly if you believe an account or key was compromised.

You are responsible for activity performed through your account unless applicable law provides otherwise.

You may upload and analyze only code you own or are expressly authorized to inspect. You are responsible for confirming that your use complies with contracts, licenses, intellectual-property rights, privacy duties, export rules, and applicable law.

You must not use the Service to:

• infringe or misappropriate another person’s rights;
• circumvent access controls without authorization;
• distribute malware or facilitate unlawful harm;
• probe, overload, disrupt, or bypass limits on the Service;
• resell access or credentials without our written permission; or
• submit secrets or personal data unnecessary for recovery.

PyDecode performs static analysis; it does not intentionally execute uploaded bytecode. Recovery is inherently imperfect. Output may be incomplete, structurally approximate, syntactically invalid, or different from the original source.

Treat recovered source as untrusted code. Review it before compiling, executing, publishing, or relying on it. You are responsible for evaluating accuracy and safety for your use case.

Visitors may submit up to three individual supported Python .pyc files, each no larger than 100 KB, without creating an account. The allowance applies per visitor and is also subject to broader network safeguards.

You must not clear, alter, automate around, or otherwise evade the visitor, request-rate, or network limits. We may block trial access when needed to protect availability. Creating an account is the supported way to continue after the allowance is complete.

Decompilation uses credits. The Service calculates a quote from file and archive characteristics, reserves credits when a job is accepted, and may adjust the final amount after safe archive inspection. The ledger shown in your account is the record of grants, reservations, charges, adjustments, and in-product refunds.

• Trial or promotional credits have no cash value.
• Credits are not transferable between accounts.
• Credits do not expire unless an expiration date is displayed in your account. When a balance has an expiration date, we may send a reminder before that date.
• Failed, expired, or rejected jobs may automatically return eligible reserved credits to your PyDecode balance.
• An in-product credit return is different from a refund to your original payment method.

Credit packs are one-time purchases processed by Stripe. The product, currency, taxes, and total displayed by Stripe at checkout control the transaction. We do not receive your complete payment-card number.

Purchases are governed by our Refund Policy. Nothing in these Terms limits a mandatory consumer right that cannot lawfully be waived.

You retain your rights in uploaded files. You grant us a limited right to receive, store, inspect, transform, and return the material only as needed to operate, secure, and support the Service.

Private input and result artifacts are scheduled for deletion after the displayed retention period, currently 12 hours. Account, billing, security, job, and ledger metadata may be retained longer as explained in the Privacy Policy. Download results promptly; expiration is not a backup service.

If a recovery fails, we may retain the failed input and its technical error log for up to 30 days solely to reproduce the failure, improve version or opcode support, secure the Service, and provide support. Access is restricted to authorized administrators, and the retained copy may be purged earlier from the administration system.

As between you and PyDecode, you retain rights you already hold in your input. Your rights in recovered output remain subject to the rights and licenses governing that input; recovery does not create ownership you did not previously have.

The Service’s interface, branding, software, documentation, and original materials are owned by PyDecode or its licensors. These Terms grant only the limited access needed to use the Service.

We may modify limits, features, prices, or supported bytecode as the Service evolves. We aim for reliable operation but do not promise uninterrupted availability or that every file will be recoverable.

The Service relies on providers such as Stripe for payments and Fly.io for hosting. Their services may be governed by separate terms and may experience events outside our control.

We may limit or suspend access when reasonably necessary to protect users, providers, or the Service; investigate misuse or fraud; comply with law; or enforce these Terms. Where practical, we will provide notice and an opportunity to resolve the issue.

You may stop using the Service at any time and request account deletion from Settings. Deletion requires confirmation through the account email. Some transaction and security records may be retained where required or permitted by law.

To the extent permitted by law, the Service is provided “as is” and “as available,” without implied warranties of merchantability, fitness for a particular purpose, non-infringement, or recovery accuracy.

To the extent permitted by law, PyDecode will not be liable for indirect, incidental, special, consequential, exemplary, or lost-profit damages arising from the Service. Our aggregate liability for claims relating to the Service will not exceed the amount you paid to PyDecode during the 12 months before the event giving rise to the claim. These limits do not apply where liability cannot lawfully be excluded or limited.

We may update these Terms as the Service or law changes. We will post the revised date and provide additional notice when required. Continued use after an update takes effect constitutes acceptance where allowed by law.

Questions about these Terms can be sent to playsharp@playsharp.io. Applicable mandatory law and consumer protections remain in effect regardless of anything stated here.