End User Licence Agreement (EULA)
Version: 2026-09-02
NitroCart and other catalogue Products (the Software) are licensed, not sold. Exclusive rights remain with the rightholder.
1. Licence grant
1.1. Subject to full payment and compliance with this EULA and the AUP, the Licensor grants a non-exclusive right to:
- install and use the Software on the instances / domains / IPs of the paid tier;
- use documentation solely to operate that instance.
1.2. Except where a mandatory rule allows (and only to that extent), you may not sublicense, rent as an unauthorised white-label, circumvent technical protection, forge licence responses, extract keys, or reverse-engineer beyond mandatory interoperability rules (e.g. analogues of Civil Code art. 1280).
1.3. Open-source components remain under their licences (BSD, MIT, Apache, LGPL, etc.). Third-party notices may appear in THIRD-PARTY-LICENSES.
2. Disclosure: remote licence check, grace, revocation
2.1. The Software periodically contacts the Licensor’s licensing infrastructure (and/or authorised nodes) to validate the key (licence check / tick). After the offline grace period without a successful check, features may be limited or disabled (including storefront and admin, depending on build).
2.2. The Licensee agrees in advance that such checks, limits and disablement are licence conditions, disclosed before payment, not a hidden defect.
2.3. Revocation or non-renewal may follow, without limitation: non-payment; EULA/AUP breach; legal, court or sanctions requirements; key compromise; unlicensed instances; payment fraud; refusal to provide information required by law.
2.4. Revocation does not require a refund except where mandatory law so provides. There is no separate refund policy.
2.5. Install data that may be sent: technical server id, IP, build version, licence status, service headers. Details may be refined in the Privacy Policy.
2.6. The Licensor does not warrant 100% SLA of check nodes. Prolonged outage of all nodes may trigger grace. The Licensee must back up their own shop data; licence outage does not create a duty for the Licensor to store or restore the Licensee’s content.
3. Telemetry and Monitor
3.1. If ecosystem monitoring is enabled, the install may send diagnostic events (health, truncated error text). The Licensee must make such transfer lawful on their side (including 152-FZ / GDPR as operator of their shop if logs might contain their customers’ data).
3.2. Disabling a monitor channel, where the build allows it, does not waive licence compliance.
4. No assistance in offences — allocation of roles
4.1. The Software is a general-purpose tool (building online shops and related infrastructure). The Licensor does not control the Licensee’s content or transactions.
4.2. Any use of the Software in breach of criminal, administrative, civil, tax, advertising or sanctions law is solely the Licensee’s. Developers and the Licensor are not accomplices, organisers or accessories merely by supplying software.
4.3. The Licensor has no duty to police the legality of the Licensee’s business and no duty to prevent, detect or report the Licensee’s unlawful acts except where a mandatory rule of law independently requires it.
5. AS IS
No warranty of merchantability, uninterrupted operation, error-free code, security of the Licensee’s environment, or fitness for a particular purpose. Updates, patches, new formats and ecosystem features are at the Licensor’s discretion and may be changed, delayed or withdrawn without liability.
6. Termination
Material breach terminates the licence automatically. The Licensee must delete the Software and keys. Liability caps, indemnity and unlawful-use clauses survive.
7. Export and sanctions
The Licensee warrants they are not a prohibited party and will not use the Software for sanctioned end-uses. Sanctions evasion is a material breach.