FINAL EFFECTIVE VERSION

Version 2026-08-03.2

2.1 General provisions

2.1.1 This Public Offer is an offer by PE ROHOVYI VALERII, trading as MYRQELON Interactive Technologies, to enter into an electronic contract for IT services, digital services, digital content or a software right of use on the terms below.

2.1.2 The Offer is addressed to adults, individual entrepreneurs and legal entities having the legal capacity and authority required to enter into the contract.

2.1.3 A consumer retains the mandatory protections of the law of the consumer's habitual residence to the extent they cannot lawfully be excluded. Nothing in this Offer limits non-waivable consumer rights.

2.1.4 If the parties agree a separate specification, commercial proposal, statement of work, invoice or individual electronic agreement, that document prevails for scope, timing, price, milestones, acceptance and intellectual property. This Offer applies to matters not otherwise agreed.

2.2 Definitions

- **Provider** means PE ROHOVYI VALERII / MYRQELON Interactive Technologies;

- **Customer** means the person accepting the Offer or on whose behalf it is accepted;

- **Consumer** means an individual acting mainly outside a trade or profession;

- **Services** means development, design, integration, consulting, audit, setup, support, automation and other IT work;

- **Digital Product** means software, a file, template, module, digital content, licence or another digitally supplied result;

- **SaaS** means time-limited access to software functionality over a network;

- **Order** means an electronically submitted request containing the scope, price and other essential terms;

- **Specification** means the agreed description of functionality, deliverables, milestones, timing, acceptance criteria and intellectual-property terms;

- **Acceptance** means full and unconditional acceptance of the Offer under section 2.4;

- **Business Day** means a day other than Saturday, Sunday or an official non-working day at the Provider's place of business, taking account of bank operations.

2.3 Contract scope

2.3.1 The Provider shall supply the agreed Services, Digital Product or SaaS access, and the Customer shall accept proper performance and pay the agreed price.

2.3.2 The contract scope is determined by the information displayed immediately before ordering and the electronic confirmation: name, description, scope, price, currency, schedule, milestones, delivery format, limitations, support, licence and acceptance criteria.

2.3.3 Advertising, portfolios, demonstrations and preliminary estimates do not guarantee an identical outcome unless the relevant characteristics are included in the Order or Specification.

2.3.4 The Provider does not guarantee profit, revenue, search ranking, approval by a third-party platform or continuous operation of third-party services unless an express guarantee is stated in an individual agreement.

2.4 Electronic contract formation and Acceptance

2.4.1 Before ordering, the Customer can review the essential terms, price, accepted payment methods, restrictions, this Offer, Website Terms, Payment Policy and Cancellation and Refund Policy.

2.4.2 Acceptance is completed by the combination of:

1. entering information required for the Order;

2. selecting a mandatory, unchecked box accepting the legal documents;

3. activating **“Order and pay”**, **“Confirm order with obligation to pay”** or another unambiguous payment-obligation button;

4. where shown, confirming a one-time code sent to email or phone; and

5. successful payment or the Provider's confirmation where payment by invoice is selected.

2.4.3 Consent boxes are not pre-ticked. Marketing consent is separate and optional.

2.4.4 Where the Consumer asks for a paid service to start during an applicable withdrawal period, the Consumer makes a separate express request. For immediate supply of digital content not supplied on a tangible medium, the Consumer separately consents to supply and acknowledges the legally applicable effect on the right of withdrawal.

2.4.5 The system records evidence of Acceptance, including Order number, UTC timestamp, language, exact checkbox text, document versions and hashes, IP address, user agent, one-time-code reference where used, and payment status.

2.4.6 Following the Order, the Customer receives an electronic confirmation containing the number, scope, price, timing, payment status and links to the accepted document versions in a form capable of being stored and reproduced.

2.4.7 Input errors may be corrected before the final button is activated. After ordering, an error must be reported promptly to support@myrqelon.com or billing@myrqelon.com.

2.5 Orders, Specifications and scope changes

2.5.1 A standard product or service is ordered on the terms displayed on its page and at checkout.

2.5.2 For a custom project, the Specification may be approved by email, through the customer account or with a one-time code. Where applicable it shall state:

- functional and non-functional requirements;

- platforms, integrations and dependencies;

- Customer-supplied materials;

- deliverables, formats and acceptance criteria;

- milestones, timing and review points;

- price, currency and payment schedule;

- intellectual-property transfer or licence scope;

- support, defect correction and exclusions.

2.5.3 A request changing the agreed scope is a change request. The Provider informs the Customer of the impact on price and time before implementation. Electronic approval is sufficient.

2.5.4 Where performance depends on Customer data, access, content, decisions or approval, deadlines extend by the delay and the reasonable time required to resume work.

2.6 Price, taxes and invoices

2.6.1 The price is stated at checkout, on the product page, in the Specification or invoice. Before ordering, the Customer is shown the total amount payable to the Provider, excluding possible charges or currency conversion applied independently by the Customer's bank.

2.6.2 Tax treatment and the composition of the price depend on applicable law, the Provider's tax status and the relevant invoice. Any mandatory tax that must be separately charged is disclosed before payment or in the invoice.

2.6.3 Custom work may use full prepayment, milestone payments, a deposit or time-based billing as stated in the Order.

2.6.4 A time or budget estimate is binding only within the expressly agreed assumptions and tolerance.

2.7 Card payments through monobank

2.7.1 Card payments are processed by JSC UNIVERSAL BANK/monobank or another provider clearly identified at checkout. The Provider does not store the full card number or CVV in its systems.

2.7.2 Redirecting to a payment page, reserving funds or receiving an intermediate status is not final payment. Payment is complete after a verified final successful invoice status.

2.7.3 The Provider may verify status through the API, signed webhook and/or merchant cabinet. In a conflict, the bank-confirmed transaction state prevails.

2.7.4 Where fiscalisation is enabled, a receipt is produced through the connected fiscal solution and supplied electronically.

2.7.5 Repeated button activation must not create duplicate charging. A confirmed duplicate amount is refunded after reconciliation.

2.8 Bank transfers, SEPA and SWIFT

2.8.1 A transfer must use only the account and currency stated in the valid invoice or official payment instructions.

2.8.2 Payment is complete only when the full amount is actually credited to the Provider. The date of the payer's instruction is not the receipt date.

2.8.3 Unless the invoice states otherwise, the Customer bears the payer-bank and intermediary-bank charges and must ensure that the full invoiced amount is received. A shortfall must be paid before work starts.

2.8.4 EUR SEPA transfers generally take 1-5 Business Days; EUR or USD SWIFT transfers generally take 3-5 Business Days. These are estimates and may be extended by intermediary banks, compliance, currency controls, sanctions screening or non-working days.

2.8.5 Third-party payment is permitted only after notice and provision of sufficient information to identify the payer and link the payment to the Order.

2.8.6 The payment reference should match the invoice, for example: `Payment for software development services under Invoice No. MYR-2026-001 dated 3 August 2026. Customer: Example Company Ltd.`

2.9 Start, timing and delivery

2.9.1 Unless otherwise stated, work starts after contract formation, receipt of agreed prepayment, and receipt of required materials and access.

2.9.2 Deadlines are calendar or Business Days as stated. Estimates may change due to scope changes, Customer delay, third-party services, force majeure or required security review.

2.9.3 Services may be delivered remotely. Deliverables may be transferred by email, repository, cloud storage, customer account, server or another agreed channel.

2.9.4 The Customer shall timely provide accurate information, lawful content, minimum-privilege access and authorised contacts.

2.10 Acceptance of deliverables

2.10.1 Acceptance criteria are set out in the Order or Specification. If no separate period is stated, within five Business Days after notice of readiness the Customer shall either accept or provide one consolidated list of specific non-conformities against the agreed criteria.

2.10.2 A request outside the agreed criteria is a change request, not a defect.

2.10.3 If no reasoned objection is provided within the period and the Customer starts production or commercial use, the deliverable is treated as accepted, except for latent defects and where mandatory law prevents this presumption.

2.10.4 Confirmed non-conformities are corrected within a reasonable time. Re-acceptance is limited to the corrected part.

2.11 Digital content, SaaS and subscriptions

2.11.1 Compatibility, functionality, technical requirements, licence term, updates and support are disclosed before ordering.

2.11.2 A Digital Product is supplied in the version and package stated in the Order. Updates are included only for the agreed support/subscription period or where required by mandatory law.

2.11.3 A subscription or automatic renewal exists only if checkout clearly states the frequency, amount or calculation method, term, cancellation method and next charge date, and the Customer gives a separate unambiguous confirmation. Otherwise the Order is not automatically renewable.

2.11.4 Future renewal may be cancelled through the account or by contacting billing@myrqelon.com before the next charge date. Cancellation stops future charges but does not normally cancel the already supplied paid period, subject to mandatory rights.

2.11.5 On termination, the Customer is given a reasonable opportunity to export Customer data where technically feasible and consistent with security, third-party rights and law.

2.12 Intellectual property

2.12.1 Until full payment, rights in created deliverables remain with the Provider to the extent permitted by law.

2.12.2 After full payment, the Customer receives the rights expressly stated in the Order or Specification. If none are stated, the Customer receives a non-exclusive, worldwide and, for a one-off deliverable, perpetual licence to use the delivered result for the Customer's lawful internal or business purposes, without reselling it as a standalone template or competing product.

2.12.3 Exclusive economic rights transfer only under an express written/electronic term identifying the work, territory, term and permitted uses, and only after full payment.

2.12.4 The Provider always retains rights in pre-existing materials, frameworks, libraries, know-how, general methods, general-purpose tools, open-source/third-party components under their licences, and anonymised skills and knowledge that do not reveal Customer confidential information.

2.12.5 Source code is delivered only if expressly listed as a deliverable. Repository access does not itself transfer exclusive rights.

2.12.6 The Customer warrants that it has the necessary rights in all trademarks, texts, images, databases, personal data and other content it supplies.

2.13 Third-party services and open source

2.13.1 Deliverables may depend on third-party APIs, banks, hosting, app stores, AI providers or open-source components.

2.13.2 Third parties operate under their own terms and may change availability, APIs, prices or policies. The Provider is not responsible for their independent conduct but discloses known critical dependencies.

2.13.3 Open-source notices and licence obligations remain applicable. No contract term grants rights broader than a relevant third-party licence.

2.14 Support, security and corrections

2.14.1 Support scope is stated in the Order. If no separate warranty correction period is stated, for 30 calendar days after acceptance the Provider will correct reproducible defects that cause the deliverable not to meet agreed criteria, without additional service fees.

2.14.2 Free correction excludes issues caused by Customer/third-party changes, misuse, an incompatible environment, third-party services, failure to install a recommended update or new requirements.

2.14.3 Passwords and secrets must not be sent through insecure channels. Access should be temporary, least-privilege and revoked after completion.

2.14.4 The Provider applies reasonable technical and organisational safeguards but cannot guarantee absolute absence of vulnerabilities. Critical security issues should be privately reported to support@myrqelon.com.

2.15 Cancellation, withdrawal and refunds

2.15.1 The Cancellation, Withdrawal and Refund Policy forms part of the contract.

2.15.2 Before custom work starts, cancellation may be requested. The amount received is refunded less actually incurred, legally non-refundable bank or specifically authorised third-party costs, only where such deduction is lawful.

2.15.3 After custom work starts, the refund is based on the unperformed portion, taking account of completed milestones, documented work, agreed non-refundable costs and mandatory consumer rights.

2.15.4 Special rights concerning conformity, updates, correction, price reduction and termination apply to digital content and digital services and are not excluded.

2.15.5 Refunds are normally made to the original payer and original method after required verification.

2.16 Customer obligations and prohibited use

The Customer shall provide truthful contact/payment information, possess authority to act, use the deliverable lawfully, hold rights in supplied content, avoid malware, unauthorised access, evasion, unlawful surveillance or rights infringement, and comply with sanctions, export controls, payment-provider and platform rules. The Acceptable Use Policy provides further detail.

2.17 Sanctions, export and territorial restrictions

2.17.1 Services are not supplied to persons, entities, banks, territories or transactions subject to applicable Ukrainian sanctions, mandatory UN sanctions, payment-provider restrictions or other binding prohibitions.

2.17.2 The Customer represents that the Customer, beneficial owners, payer and end users are not prohibited persons and are not acting for them.

2.17.3 The Provider may request KYC/compliance documents, suspend the Order, reject or return a payment where screening is not completed or a reasonable breach risk exists.

2.17.4 Concealing location, payer or end user to evade restrictions is prohibited.

2.18 Confidentiality

Each party protects the other's non-public technical, commercial and organisational information and uses it only for the contract. Information lawfully known, independently developed, publicly available without breach, lawfully obtained from a third party or required to be disclosed is excluded. Unless a separate NDA applies, confidentiality lasts during the contract and for three years after, and trade secrets remain protected while they qualify as such.

2.19 Personal data

The Provider processes personal data as described in the Privacy Policy for contracting, performance, support, payment, accounting, security, compliance and, separately, consented marketing. Where the Provider processes personal data on behalf of a B2B Customer, the Data Processing Addendum or separately agreed processing terms apply.

2.20 Liability

2.20.1 Each party is responsible for breach under applicable law and this Offer.

2.20.2 To the extent permitted by law, the Provider is not liable for indirect loss, lost profit, lost opportunity or data loss not caused by wilful misconduct or gross negligence.

2.20.3 For a B2B Customer, aggregate liability for an Order is limited to the amount paid for that Order during the preceding 12 months, except for wilful misconduct, confidentiality, intellectual-property infringement, data-protection obligations or liability that cannot lawfully be limited.

2.20.4 These limitations do not restrict mandatory consumer rights, personal injury, fraud or any non-excludable liability.

2.20.5 The Customer is responsible for the legality of supplied instructions, materials and use of the deliverable.

2.21 Force majeure

A party is not liable for delay caused by circumstances beyond reasonable control, including war, hostilities, air alerts, evacuation, utility or communications failure, cyberattack, fire, natural disaster, government action, sanctions, strike, critical-infrastructure or provider failure. The affected party gives notice where practical and mitigates impact. Deadlines extend for the impact period. If substantial impossibility continues for more than 60 calendar days, either party may terminate the unperformed portion, with payment for work already performed.

2.22 Suspension and termination

The Provider may suspend for overdue payment, missing materials, a security risk, unlawful use, sanctions issue or material breach, ordinarily after notice and a reasonable cure period where safe and lawful. Either party may terminate for a material breach not cured within 10 Business Days after written notice, unless the nature of the breach requires otherwise. Accrued payment, confidentiality, intellectual property, data protection, liability and dispute terms survive.

2.23 Governing law and disputes

The contract is governed by Ukrainian law, without depriving a Consumer of non-waivable protections of the law of habitual residence. Before litigation, a written complaint should be sent and answered, where possible, within 15 Business Days. Competent Ukrainian courts have jurisdiction unless mandatory law or a separate B2B agreement provides otherwise. Mediation or arbitration may be separately agreed for an international B2B project.

2.24 Notices

Customer notices go to hello@myrqelon.com, billing@myrqelon.com, privacy@myrqelon.com or the relevant listed address. Provider notices go to the Customer's email, account or agreed channel. A notice is received when accessible to the recipient unless a delivery failure is returned.

2.25 Changes and versions

The current version and date are published on the Website. The version accepted when an Order is placed governs that Order, unless a legal change is mandatory or a later amendment is agreed. Material changes to an active subscription are notified in advance and a right to end the future period is provided where required.

2.26 Provider details

PE ROHOVYI VALERII

Ukrainian taxpayer number 3545205238

Office and correspondence address of MYRQELON Interactive Technologies: Office 4, Section 1, 13 Hlybochytska Street, Kyiv, 04052, Ukraine. The Provider is registered in Ukraine; official correspondence is also handled by email.

hello@myrqelon.com

+380 93 292 03 80

https://myrqelon.com/

---