Terms for responsible use of the SCYNEXUS platform.
These terms describe the current MVP rules for accessing SCYNEXUS and creating or operating an accountable main chain.
These Terms are an MVP publication based on the current platform terms template. The applicable legal entity, jurisdiction, dispute forum, contact details, and effective production date still require legal approval. During local testing, acceptance is recorded only in the browser and is not represented as production-grade legal evidence.
1. Scope and eligibility
By accessing the platform or creating a main chain, you agree to follow these Terms. If acting for an organization, you must have authority to represent it.
You must be legally capable of entering agreements, permitted to use the platform in your jurisdiction, and able to provide accurate identity or compliance information when requested.
2. Account and main-chain responsibility
You are responsible for credentials, keys, devices, recovery methods, local chain storage, and activity performed through your account.
A new main chain must have an accountable owner. Creating one does not grant authority over another person's work, identity, intellectual property, or records.
3. Acceptable use
Do not submit unlawful, fraudulent, misleading, infringing, malicious, or privacy-violating material. Do not bypass security controls, disrupt availability, manipulate validation or disputes, or use the platform for prohibited trade or financial activity.
4. Materials, ownership, and operational rights
You retain ownership of material you lawfully submit unless a separate agreement says otherwise. You must have the rights needed to submit it.
You allow SCYNEXUS to process, store, transmit, verify, and maintain submitted material as needed to operate workflows, preserve audit trails, enforce agreements, and comply with law.
5. Records, evidence, and validation limits
Hashes, timestamps, signatures, checkpoints, validation outputs, and audit records may support operational, evidentiary, compliance, or dispute processes.
Cryptographic or validation records do not guarantee truth, regulatory acceptance, legal sufficiency, successful commercialization, uninterrupted availability, or a particular dispute outcome.
6. Enforcement and service availability
Access may be restricted, suspended, or terminated to address security, fraud, legal, operational, or policy risks. MVP functions may change or remain unavailable while the platform is under construction.
7. Intellectual property and liability
SCYNEXUS software, documentation, protocol designs, and brand assets remain owned by SCYNEXUS or its licensors. These Terms do not grant a license beyond permitted platform use.
The platform is provided on an as-is and as-available basis, subject to mandatory law. Users remain responsible for independent legal, technical, safety, regulatory, and commercial review.
8. Disputes, changes, and contact
Project-specific contracts may define evidence, dispute, appeal, and settlement rules. Final governing-law and dispute provisions will be published only after legal review.
Material changes to these Terms should be presented before a new acceptance is requested. Formal legal contact details will be added before production release.
When Create a new main chain is selected in the Auth Service, you must confirm that you have read and accept these Terms before continuing. Reopening an existing main chain does not create a new acceptance event.
This public page summarizes the current Platform Terms of Use template and does not replace a signed project-specific agreement.