No licence model has yet been selected. The alternatives below are drafting options, not an operative licence grant or a change to any existing release. Existing lawful licences continue on their own terms. Do not publish a new download until one model, its scope and acceptance method have been approved.
Option A — proprietary freeware EULA
1. Parties and scope
The licensor is ЧП «Делькредо» (Ukraine), [registered address and number], contact info@stowmate.pro. This EULA would cover [product, version, package hash, platform and effective date]. “Freeware” means no licence fee is charged for the identified release; it does not mean open-source software or public-domain material.
2. Proposed licence grant
Subject to the approved release terms, the licensor grants the licensee a non-exclusive licence to install and use the identified software for its own personal or internal professional / vessel operations. Proposed scope: [number of users, vessels and installations; employee / contractor permissions; offline copies; duration and territory — select explicitly]. Commercial use in the licensee’s own shipping operations is distinct from selling or distributing the software. Reasonable backup copies are permitted. Ownership of the software is not transferred.
3. Restrictions and mandatory exceptions
Except as expressly authorised, do not sell, sublicense, rent, commercially host for third parties, or redistribute the licensor’s proprietary software; remove rights notices; impersonate the licensor; circumvent access controls; or reproduce or adapt protected material beyond the licence scope. Do not decompile, disassemble or reverse-engineer proprietary code except to the extent permitted by mandatory applicable law. Nothing restricts non-waivable rights, including lawful backup, observation, study or testing, legally permitted error correction, or decompilation needed for interoperability where the legal conditions are satisfied. Lawful exhaustion or transfer rights, where applicable, are not excluded. Restrictions in this paragraph do not override rights granted directly by third-party open-source licences.
4. Inputs, records and outputs
The licensee keeps its rights in its inputs and resulting operational records. It is responsible for having authority to process and submit those records and for checking their accuracy. The licensor receives no ownership of vessel or crew data merely because the software processes it. Rights to embedded templates, standards, third-party datasets and pre-existing report elements remain separate. Generated output is not a certificate, professional approval or evidence of compliance solely because it was generated by the software.
5. Intended use and safety
The software assists qualified maritime personnel. The Safety notice forms part of the proposed release information. Verify vessel-specific inputs, approved CSM limits, flag/company requirements, applicable rules and generated outputs. Do not use an unchecked result as the sole basis for a safety-critical decision.
6. Updates, support and later paid versions
Support, supported versions, security-update arrangements and end-of-support dates: [specify per release before issue]. No indefinite support commitment is created by this draft, and mandatory security or conformity obligations are not disclaimed. Future paid products or services will require separate transparent offers and terms. No fee is retroactively imposed on a copy already supplied under an effective free licence. Any proposed change to existing rights requires a lawful basis and any required notice or agreement.
7. Warranty and liability
Subject to mandatory law and any express agreed commitments, no promise is made that every defect will be absent or that the software suits every vessel or operation. No term excludes or limits liability for fraud, intentional misconduct, gross negligence, death or personal injury, mandatory product liability, or any other liability that cannot lawfully be limited. Mandatory consumer remedies and data-protection rights remain unaffected. Any proposed limitation of ordinary contractual loss must be separately assessed under [governing law] for the actual B2B/B2C supply; no zero-liability or “price paid = zero” cap is included in this draft.
8. Termination and preservation
For a material breach, the licensor may terminate rights only in accordance with the approved terms and applicable law, giving [reasonable cure period] where appropriate. On lawful termination, stop the unauthorised use and remove proprietary copies, while preserving legally required records and permitted data exports. There is no right to erase the licensee’s operational data as a penalty. Third-party licences continue according to their own terms.
9. Transfer, law and acceptance
A successor provision must preserve existing rights and follow the process in the Legal notice; it is not automatic consent to an unidentified future counterparty. Proposed governing law: [select with Ukrainian and relevant EU counsel]. Mandatory consumer protections and legally available courts are preserved. [Select a valid release/download acceptance process, retain the accepted version and provide a durable copy; merely linking these drafts is not proof of agreement.]
Option B — open-source distribution
Selected licence: [exact licence name, version and SPDX identifier]. Identify the covered code, source repository, copyright holders, dependencies, source-delivery obligations and any excluded trademarks, standards, templates or datasets. Do not call a product open source until the selected licence is actually applied and its necessary source is made available.
If this option is selected, replace Option A for the covered code with the actual licence text. Do not add proprietary no-resale or no-decompilation restrictions that contradict it. Copyleft, source-offer and notice obligations must be met where applicable. Selling services or later offering a differently licensed new version does not revoke rights already granted under an effective open-source licence. Dual licensing requires the necessary rights in all relevant contributions.
Mandatory exceptions — drafting reference
Directive 2009/24/EC, Articles 5 and 6 and Article 8, requires careful treatment of lawful-user exceptions. Have counsel check the applicable national implementation and exhaustion rules; do not replace the exception wording with an absolute ban. Official text.