H-Script Open Source Demo

Official demo terms of use

Terms for the official demo and open-source code, including the boundaries of responsibility between repository owners, project contributors, and third-party installation operators.

Revision dated August 11, 2026 H-Script 1.0.0 MIT
01

Demo status and purpose

These terms apply only to the official H-Script demonstration installation.

  • The demo is provided solely to evaluate the H-Script interface, architecture, and capabilities.
  • The demo is not a bank, investment platform, payment service, or offer of financial services.
  • Demo functions, data, settings, and availability may be changed, restricted, or reset without prior notice.
  • By using the demo, you accept these terms. If you disagree, stop using the website.
02

Open source and license

H-Script is open-source software distributed under the MIT License.

  • Under its terms, the MIT License permits use, copying, modification, merging, publication, distribution, sublicensing, and sale of copies of the software.
  • The copyright notice and MIT permission notice must remain in all copies or substantial portions of the software.
  • Source code, documentation, and the public demo are provided for independent review and use under the license.
  • If these terms conflict with LICENSE on rights to the software code, LICENSE controls.
03

User and operator responsibility

Anyone deploying H-Script is independently responsible for that installation and how it is used.

  • Before production use, you must independently assess code fitness, security, dependencies, and legal compliance.
  • A third-party operator is responsible for its server, configuration, updates, backups, access controls, integrations, user data, and operations.
  • Repository owners and project contributors do not operate or control independent installations and are not responsible for their operators' actions.
  • A third-party operator must prepare its own terms, privacy policy, security measures, and mandatory disclosures for its users.
  • The person deploying or using an installation bears the consequences of its configuration, modifications, extensions, and commercial use.
04

Demo accounts and data

The demo environment is not intended to store real or confidential information.

  • Do not enter real personal data, passwords from other services, private keys, payment details, or trade secrets.
  • Use unique test credentials and do not rely on long-term retention of a profile or its results.
  • Test accounts, records, and settings may be changed or deleted during an update or demo reset.
  • Access may be temporarily restricted for maintenance, infrastructure protection, or abuse prevention.
05

Demonstration operations

Financial modules and figures in the official demo simulate CMS behavior.

  • Demo balances, deposits, accruals, rates, payment operations, and statistics do not evidence movement of real funds.
  • Demo figures are not a promise of returns, financial advice, an offer, or a guarantee of results.
  • Do not send real money, cryptocurrency, or payment details to any requisites shown in the demo environment.
  • Connecting real gateways and processing operations in an independent installation are performed at the operator's risk and responsibility.
06

Data, logs, and telemetry

Technical request and installation information may be processed to operate and protect the demo.

  • The demo may log request time, IP address, user agent, security events, and technical errors.
  • H-Script system telemetry concerns installation status and is not intended to transmit passwords or individual financial-operation content.
  • Confidentiality, permanent retention, and recovery are not guaranteed for data voluntarily entered into the public demo environment.
  • Independent installation operators determine their own data processing and must publish their own privacy policy.
07

Vulnerabilities and security research

Open code and a public demo do not imply that the software is error-free or authorize unrestricted testing.

  • Report a discovered vulnerability confidentially through the repository's private security channel with clear reproduction steps.
  • Without separate written authorization, denial of service, mass scanning, social engineering, persistence, data modification, and access to another person's data are prohibited.
  • Do not publish details, exploit code, or obtained data before coordinated disclosure and a reasonable review period.
  • Reporting a vulnerability does not create a right to a bounty, compensation, or remediation by a specific deadline unless separately agreed.
  • Repository owners independently determine the priority, method, and timing of review and do not guarantee remediation of every reported issue.
08

Prohibited use

The demo must not be used to harm the project, infrastructure, other users, or third parties.

  • Unauthorized access, vulnerability exploitation, bypassing restrictions, and taking control of another person's account or data are prohibited.
  • Malicious code, spam, excessive automated requests, and actions disrupting service stability are prohibited.
  • Fraud, unlawful operations, impersonation of an official project representative, and use of another person's details are prohibited.
  • The demo must not be used as a production service for third parties, to accept real funds, or to store important data.
09

No warranty and limitation of liability

The software and official demo are provided “as is” and “as available.”

  • No express or implied warranty is given, including merchantability, fitness for a particular purpose, non-infringement, security, or absence of errors.
  • Uninterrupted operation, compatibility, data retention, absence of vulnerabilities, support, audit, and release of fixes are not guaranteed.
  • To the maximum extent permitted by law, the authors, copyright holder, repository owners, and contributors are not liable for claims, damages, or other consequences arising from use or inability to use the software or demo.
  • This limitation includes consequences of errors, known and unknown vulnerabilities, data loss, lost profits, modifications, dependencies, and third-party installations.
  • Nothing in these terms excludes liability or rights that cannot be excluded under applicable law.
10

Changes and feedback

The current version of these terms is published on this page.

  • These terms may be updated when the demo, project, risks, license, or mandatory requirements change.
  • A new version applies when published unless it states a different effective date.
  • Send general demo questions through project documentation and public channels; submit vulnerability details only through a private security channel.
  • Continued demo use after publication means acceptance of the updated terms to the extent permitted by law.

Documentation and license

Before deployment, review the source code, documentation, and full MIT License text in the repository.

GitHub MIT License