Domternal Pro Commercial License Agreement

This Commercial License Agreement governs published packages under the @domternal-pro npm scope, except @domternal-pro/extension-export-fonts, which is licensed under the SIL Open Font License 1.1. Each covered package includes the Agreement version applicable to that release in its LICENSE.md file. This page reproduces the current Agreement.

For a paid Order, the Agreement version identified in and recorded with the Order governs. For keyless Evaluation, the LICENSE.md file included with the installed package release governs that release's Evaluation use, subject to Section 13(c). Free packages under the @domternal scope remain MIT licensed and are not affected by this Agreement.

The Version 1.0 archive is available at /legal/domternal-pro-license-v1.0.md, SHA-256 5feb7905101de0cc900cb0ad041a73b92f6a9c48c0822126dc144b80a5ff5384. No earlier version of this Agreement has been published.

Full Agreement

Version 1.0, September 2026

This Commercial License Agreement (the "Agreement") is between M Pro Solution, obrt za administrativne i pomoćne uslužne djelatnosti, Croatia (the "Licensor"; the Licensor's full legal details are published on the imprint page at domternal.dev) and the legal entity or natural person acting in the course of a trade, business, craft or profession identified in the Order or, for an Evaluation, evaluating the Software (the "Customer"). It governs the packages published under the @domternal-pro npm scope (the "Software"). The Customer represents that it acquires the Software for business purposes.

For a paid purchase, the Customer accepts this Agreement by affirmatively accepting it at checkout, accepting the Order in writing, or paying an invoice for an Order that made this Agreement available before payment. A receipt or confirmation sent only after payment does not add or replace a term unless the Customer expressly accepts that change. For an Evaluation without a paid Order, the Customer accepts this Agreement by activating an Evaluation Key or using the Software under Section 5.

For a paid Order, the Agreement version identified in that Order governs. The Licensor records that version with the Order and makes it available in a form the Customer can store and reproduce. For an Evaluation Key, the version the Licensor identifies when issuing that key governs its use.

For a keyless Evaluation without an Order, the Agreement included as LICENSE.md in the installed package release governs use of that release. Installing and continuing to use a later release containing a later Agreement constitutes acceptance of that later Agreement for Evaluation use of that release. The Licensor preserves published Agreement versions but does not maintain a per-Customer acceptance record for an anonymous keyless Evaluation.

1. Definitions

• "Software": the packages published under the @domternal-pro npm scope, as distributed on the npm registry (compiled JavaScript, TypeScript type declarations and stylesheets), including all Updates delivered during the Subscription. The packages are publicly downloadable from the npm registry; downloading them grants no rights beyond those in this Agreement.

• "License Key": the signed, current-format activation key the Licensor issues for an Order or, for an Evaluation Key, under Section 5. Every current key contains its key type, an individual random serial and its applicable technical time and release boundaries. A Commercial Key also contains an opaque random entitlement identifier, its exact Product Line, signed not-before day, Section 6(b) grace-period end, ordinary release cutoff, signed post-grace eligibility and any exact later Release Dates required by Section 10. An ordinary Subscription key's release cutoff is the last paid day. A replacement under Section 6(g), 6(h), 7 or 10 preserves or narrows that cutoff as the applicable provision requires and never widens ordinary release rights. An Evaluation Key contains its own expiry day.

  The payload is signed but not encrypted and may be readable where Section 3(b) permits it to be embedded. Readability does not permit sharing or use outside the Customer's licensed scope. The key contains no Customer or contact name, email address, Order reference, plan, price, separate payment field or Developer limit. Its technical dates may correspond to facts in the Order or private records. The Licensor keeps the minimum durable entitlement state needed to recognize a continuing right, while supporting commercial, calculation and evidence records follow their separate retention periods. The opaque identifier links Commercial Keys for the same entitlement, and each renewal or replacement has a new random serial.

  Local validation under Section 6(k) uses registered package Release Dates, Product Line metadata and the current UTC day reported by the runtime. A Commercial Key activates ordinary production only if every commercial package in that context identifies the Product Line signed into the key; missing, conflicting or mismatched metadata remains uncovered. A Commercial Key cannot activate before its signed not-before day. That is the Subscription start for an ordinary Subscription or renewal key and is ordinarily preserved by a replacement. A Section 7 or 10 replacement may instead use a later required decision or issuance day, never retroactively.

  Sections 6(a) through 6(c) govern the ordinary lifecycle, subject to Sections 6(g), 6(h), 7, 8 and 10. Section 8 exclusively governs later Security Updates through a Security Release Certificate; Section 10 exclusively governs exact later replacement Release Dates. An Evaluation Key stops removing notices after its signed expiry day. Technical activation does not establish a Qualified Build, authorize build work or grant or extend a right. A genuine legacy DMP1 key may be recognized for migration diagnostics, but has no signed key type and cannot activate current Software or satisfy a production assertion; a current DMP2 key is required.

• "Commercial Key": a License Key issued for a paid Order. Every Commercial Key is limited to the Product Line signed into it. Only a Commercial Key may activate the Software's production mode. An Evaluation Key does not become a Commercial Key merely because it technically activates the installed package versions.

• "Evaluation Key": a License Key issued under Section 5 for a notice-free internal evaluation when used in evaluation mode. It does not activate production mode or grant any Subscription rights.

• "License Mode": the local configuration by which a headless or non-visual JavaScript execution context identifies its intended use as evaluation or production. Selecting a License Mode is a technical safeguard and does not itself grant or extend any license rights.

• "Release Date": the UTC publication day the Licensor records in each version of the Software. Whether a License Key activates a version is determined under its signed boundaries and the applicable provisions of this Agreement.

• "Order": the Domternal order form or invoice offer the Customer accepts, or, for an approved checkout, the checkout record together with the exact Domternal-authored entitlement terms, Agreement version, ordering terms and refund policy displayed and affirmatively accepted before payment. A reseller's or merchant of record's standard terms govern its payment, invoicing, tax and refund role, but do not replace the Software rights and limits the Customer accepted from the Licensor. A later confirmation may record or correct the parties' agreed facts, but changes the accepted Order only if the Customer expressly accepts the change.

• "Subscription": the period for which the fees stated in the Order have been paid, starting as stated in Section 6(a).

• "Update": any new version of the Software within the Product Line identified in the applicable Order, published by the Licensor during the paid Subscription and otherwise included in that Order. A release in another Product Line is not an Update for that Order, even if it is published while the Subscription is active, unless the Order expressly adds that Product Line.

• "Product Line": a compatible series of Software releases identified in the Order by a common major version or another published line identifier.

• "Security Support End Date": the end of the UTC calendar day that the Licensor publishes for a Product Line before accepting the first Order for that Product Line and states in each applicable Order. The date is fixed for the Product Line. A purchase, renewal, add-on, Update, Security Update, replacement key or republication does not restart or extend it, except to the extent applicable mandatory law requires otherwise.

• "Security Support Period": the period beginning when the Product Line is first made commercially available and ending on its Security Support End Date.

• "Security Update": a release or patch that the Licensor identifies as security-only and that is principally intended to remediate a vulnerability in the unmodified Software, or that applicable mandatory law requires the Licensor to provide as a security update. It may contain changes reasonably necessary to implement, test and deliver that remediation, but does not include new commercial functionality merely because it is published later.

• "Security Release Certificate": the separate signed DMS1 certificate embedded in a Security Update. It identifies that release, its Product Line, its feature baseline, its Release Date, its Security Support End Date and the commercial package set to which it applies. It is not a License Key and does not alter a DMP2 Commercial Key or grant a license right.

• "Application": a software product of the Customer or an authorized, Order-named Affiliate that includes the Software together with material additional functionality, so that the Software is a component of the product rather than its substance. A product whose intended users are End Users rather than developers is an Application even if rich-text editing is its principal user-facing feature. Server-side components the Customer deploys to support an Application, including reference backend code published by the Licensor, are part of that Application.

• "Qualified Build": a complete, immutable and deployable production artifact of an Application that the Customer created while its paid Subscription was active, using only Software versions then licensed to it, and placed before the Subscription ended in the Customer's controlled, versioned release, package, image or artifact storage with records reasonably sufficient to identify the artifact and its exact bytes. Qualification applies separately to each retained artifact. A byte-for-byte copy remains the same Qualified Build. External Customer data, content, secrets, runtime configuration and infrastructure are not part of the artifact unless embedded in it, so changing only those external items does not create a new build. Recompiling, rebundling, relinking, regenerating or otherwise changing any part of the retained artifact creates a different build and requires an active Subscription unless Section 7, 8 or 10 expressly permits that specific build work, or Section 6(g) or 6(h) permits the narrow replacement of an embedded License Key. A Qualified Build does not include or create a perpetual right in the Application's source code or build system.

• "Permitted Remedial Build": an exact artifact created through the limited post-Subscription work expressly authorized and governed by Section 6(j).

• "Source Period": the Subscription period for which an original Commercial Key was issued. A renewal creates its own Source Period. A replacement, paid Developer-limit amendment or Section 10 remedy successor remains associated with the Source Period of its source key.

• "Developer": as defined in Section 4.

• "End User": a person who uses an Application without developing it.

• "Affiliate": an entity that controls, is controlled by, or is under common control with the Customer, where "control" means direct or indirect ownership of more than half of the voting interests.

2. License grant

While the Subscription is active and subject to this Agreement, the Licensor grants the Customer a non-exclusive, worldwide license, non-transferable except as provided in Section 13(b), to:

1. receive a License Key for the Order and use it to activate the Software for the Order's Product Line and no more than the permitted number of Developers;

2. use the Software to develop Applications and modify it as reasonably needed for that development, without support for modified code;

3. build, deploy and operate Applications on unlimited servers, domains and environments, including as commercial software-as-a-service, for unlimited End Users;

4. distribute the Software to End Users only as an integrated part of an Application through ordinary bundling; and

5. permit End Users to use it only as part of those Applications.

   An Affiliate may exercise the rights in this Section on the Customer's behalf only while satisfying the Affiliate definition and being expressly named in the Order. Naming one does not authorize another; group-wide scope exists only where an Enterprise Order expressly grants it. The Customer is responsible for each authorized Affiliate, their personnel are aggregated for the Developer limit, and their products count as Applications. If an Affiliate ceases to qualify or be named, its rights end immediately without its own grace period or Section 6(c) right. The Customer's rights do not transfer to it.

   Before distributing an Application to End Users, the Customer must use end-user terms, acceptable-use rules or another enforceable arrangement appropriate to the Application that grants no right to extract or separately redistribute the Software, use it as a developer tool, SDK, component library or editor toolkit, sublicense it, circumvent its license controls or exercise any right broader than this Agreement permits. The Customer must use reasonable measures to preserve copyright, license and attribution notices that remain visible in the distributed Application. End Users need not accept this Agreement, and the Customer is not responsible for an End User's independent conduct it did not authorize or facilitate. Applicable mandatory rights remain.

   The Customer controls its Applications, data and content, End User relationships, hosting, infrastructure, dependencies, configuration and access controls. It is responsible for necessary rights, notices, consents and lawful grounds; the legality and accuracy of its data, content and instructions; appropriate security, testing, monitoring, backups and recovery; and compliance with laws and industry requirements applicable to it or its Applications. The Software is a developer component, not professional advice, and may not be the sole control in a system whose failure could reasonably cause death, personal injury or catastrophic physical damage unless an Order expressly permits that use. Mandatory Licensor obligations for the unmodified Software remain.

   The Software is licensed, not sold. The Licensor and its licensors retain all intellectual-property rights. Modifications the Customer makes under Section 2(b) are derivative works of the Software and may be used only as part of the Software under this Agreement and distributed only within Applications under subsection (d).

   No Software rights are granted by implication or estoppel or outside this Section and Sections 5, 6(b), 6(c), 6(g), 6(h), 7, 8 and 10. Section 13(n)'s limited trademark-reference license grants no Software right.

3. Restrictions

The Customer must not:

1. redistribute the Software separately; include it in a product primarily providing its functionality to developers, including a development tool, SDK, component library or editor toolkit; or include it in a product primarily enabling users to place the Software's editing functionality in software or sites those users provide to third parties. Such use requires a separate written OEM agreement with the Licensor. This does not restrict internal sharing among the Customer's and authorized, Order-named Affiliates' Developers, including through internal component libraries not distributed to third parties, or content editing by End Users within an Application;

2. share a License Key outside its Developers; embed it outside the Customer's Applications and their development and build systems; publish the License Key or Software to a public or third-party registry or repository; or intentionally circumvent, remove or disable license validation or an evaluation notice, or assist anyone in doing so. An unavoidably readable key embedded as permitted, or Software bundled in an Application under Section 2(d), is not prohibited publication. Neither is a mirror in an access-controlled private registry, repository or artifact cache operated by the Customer or a service provider bound to the Customer by a contract with confidentiality obligations covering the Software and License Key, if access is limited to the Customer's and authorized Affiliates' Developers and build systems, and to provider personnel solely as needed to operate the service. Documented headless, standalone, custom-UI or UI-disabled use is not by itself circumvention, but production still requires contractual rights and technical activation. Applicable mandatory rights remain unaffected;

3. remove or alter copyright, license or attribution notices in the Software;

4. develop an Application for a third party unless that party has its own active Subscription covering the Developers working on it or the Order expressly permits otherwise;

5. exceed an Order limit;

6. use, modify, combine or distribute the Software in a way purporting to impose source-disclosure terms or rights broader than this Agreement on any part of it;

7. use the Software as machine-learning training data or include it in a training dataset. This does not restrict analysis to integrate it with an Application or rights guaranteed by Directive 2009/24/EC notwithstanding contrary agreement; or

8. reverse engineer, decompile, disassemble or otherwise attempt to derive the Software's non-public source code, algorithms, internal structure or non-public interfaces, except where applicable mandatory law permits the act notwithstanding agreement. Ordinary inspection, debugging and analysis solely to exercise documented Section 2 rights, and non-excludable Directive 2009/24/EC rights, remain permitted.

4. Developers and how they are counted

"Developer" means every natural person, whether an employee, contractor or staff of an authorized, Order-named Affiliate, who, during an active Subscription, the limited Section 7 wind-down, or build work expressly permitted after expiry by Section 6(g), 6(h), 8 or 10, develops or modifies any user interface or server-side part of an Application that includes or interacts with the Software. The person counts whether or not they write directly against the Software's APIs. Merely operating, copying, distributing, scaling, moving or redeploying a byte-for-byte identical Qualified Build does not make a person a Developer.

The Customer is responsible for compliance by every Developer, employee, contractor, agent, authorized Affiliate and service provider given access to the Software or a License Key or authority within the licensed scope. Their acts and omissions within that access or authority are the Customer's. The Customer is not responsible for an independent third party's conduct that it did not authorize or facilitate and could not reasonably control, but must use reasonable access controls and comply with Section 6(g)'s compromised-key duties.

1. The Developer count may not exceed the Order limit and aggregates the Customer and every authorized, Order-named Affiliate. A Section 7 wind-down uses the last active limit. Section 6(b) grace-period work under Section 8 or 10 uses the last paid limit. Post-grace work under Section 6(g), 6(h), 8 or 10 uses the applicable Perpetual Developer Limit under Section 6(c)(3) or 7.

2. A License Key is issued per Order, not per person. People may join and leave, but the concurrent count at any time is the number of distinct people who acted as Developers at any point in the preceding 30 days.

3. Automated build systems (CI/CD) may use the License Key at no charge and without counting as Developers.

4. A person is not a Developer merely for running, deploying or operating the finished Application; manually testing it without a scripting or build environment; using it as an End User; or executing pre-existing automated tests without changing test or Application code. The same applies to a person who writes or changes only black-box tests that interact solely through the finished, built Application's interface, without changing source code, Software integration or build configuration or importing or calling Software APIs in test code. A person who writes or changes code that imports or calls those APIs, changes the integration, or works on an interacting server-side component is a Developer even when the work is called testing. A person who uses only the Application UI to configure, customize or assemble content or interfaces without source access is an End User, not a Developer.

5. Evaluation

The Licensor grants the Customer a non-exclusive, non-transferable license to use the Software without a License Key solely for internal evaluation. Evaluation does not permit production use.

In a DOM-connected editor with a supported Pro UI surface, the Software displays an evaluation notice unless an activating Commercial Key is active or an activating Evaluation Key is used in evaluation mode. Word, PDF and browser print output from the Pro Export package follows the same rule. Other output, including HTML, JSON, text, Markdown and data returned by a standalone API, may carry no notice. Absence of a notice does not grant or evidence a production right.

The same evaluation and production boundaries apply to server-side, worker, command-line, standalone-API, custom-UI, headless and other non-visual use. A headless context performing an operation guarded by the Software must explicitly select evaluation mode to use that operation without a Commercial Key. The Software may then warn locally without changing the Customer's data or output. Reading, deleting, recovering, migrating or cleaning up the Customer's data does not require production mode merely because the operation uses a documented data-exit or maintenance API.

For each JavaScript execution context performing a guarded headless operation in production, the Customer must run the Software in production mode and initialize it with a Commercial Key that activates the package versions used in that context. This technical requirement neither replaces nor enlarges the Customer's rights and does not restrict a right continuing under Section 6(c), 6(d) or 7.

The Licensor may issue an Evaluation Key that removes notices in evaluation mode. Unless stated otherwise in writing, such an evaluation lasts 14 days and its Evaluation Key stops removing notices after the signed UTC expiry day. It does not activate production. The Licensor may revoke it at any time, ending only the notice-free evaluation and allowing later releases to reject it.

Keyless Evaluation is not time-limited, but the Licensor may end a specific Customer's evaluation license by 30 days' written notice or change or end keyless Evaluation generally on at least 30 days' public notice on its license or pricing page. A general change applies prospectively and does not shorten a paid Subscription, alter an accepted Order, reduce an accrued Section 6(c) right or convert an Evaluation into production use.

"Production use" means making an Application available to End Users or using it to process live business data. Internal development, testing and proof-of-concept builds are Evaluation. Other provisions apply only where their subject matter can apply to an Evaluation. Evaluation is provided "as is", at the Customer's sole risk, and creates no Subscription, Section 6(c) right, paid Section 10 warranty or intellectual-property remedy or defense, or Section 8 support, service-level, Update or Security Update obligation. Section 11's EUR 100 aggregate cap applies. Nothing excludes a right, remedy or liability that applicable mandatory law does not permit the parties to exclude.

6. Term, renewal, and what happens at the end

1. Subscription period. The Subscription starts on the later of: (i) the UTC calendar day the Licensor receives its fees or, where a reseller or merchant of record collects them, the day the Customer's payment completes; and (ii) any start date in the Order. It then runs for the full ordered length. Section 8 support, the last paid day and the Commercial Key's signed activation boundaries follow that start. The Order or renewal record states the last paid day, which need not appear in the key.

   The Subscription renews as stated in the Order. A renewal continues from the end of the period renewed; Section 6(b) governs late payment. A new Subscription that is not a renewal may start no more than 90 days after payment. A renewal and paid Additional-Developer add-on remain in the original Product Line, which every renewed or amended Commercial Key preserves. Another Product Line requires a separate Order expressly identifying it. Every day in this subsection is a UTC calendar day.

   The Licensor issues a new Commercial Key promptly on or after the Subscription starts. It may issue a renewal key after receiving payment but before the renewal starts; the key's signed not-before day remains that renewal's first day and it does not activate earlier. Before a later new-Subscription start, the Customer may use keyless Evaluation or a separate Evaluation Key under Section 5 if the Licensor issues one.

2. Grace period. If renewal payment is not received by Subscription end, a 14-day grace period begins on the next UTC calendar day. An end under Section 6(d) or 6(f) creates no grace period. During grace, the Customer may continue operating, distributing, scaling, moving and redeploying production deployments existing at the paid Subscription end and any byte-for-byte identical Qualified Build. It may use only ordinary Software releases dated no later than the last paid day, which is the Commercial Key's ordinary release cutoff.

   Grace adds no feature release day or ordinary support and permits no new Application, Application modification, recompile, rebundle, relink, regeneration or other artifact change. Sections 8 and 10 exclusively govern eligibility for, and Section 6(j) governs the narrow work needed to apply, a Security Update or exact replacement during grace.

   Renewal payment received during grace makes the Subscription uninterrupted, restores all rights under the renewed Subscription without a contractual gap and requires the Licensor to issue the renewal key. Without payment, expiry takes effect when grace ends and the key enters the Section 6(c)(2) post-grace state.

3. Expiry.

   Fallback eligibility. The rights in this subsection accrue at no additional charge only if the expiring Subscription and the unbroken series immediately preceding it cover at least 12 consecutive elapsed months whose fees were paid and not refunded. Renewal within Section 6(b) grace preserves the series; any other gap breaks it and restarts the count. A 12-month period beginning on a calendar day ends at the end of the day immediately before the corresponding day in the twelfth following month, or that month's last day if it has no corresponding day.

   If these rights do not accrue, all Section 2 rights from the ended Subscription end when grace ends. The Customer must stop its Production use, including making available or operating Applications for End Users, and stop developing, building, distributing and deploying with the Software. This does not restrict Section 5 Evaluation, Section 7's limited rights or rights accrued at an earlier expiry. A nonqualifying series does not extend those earlier Covered Versions or Qualified Builds.

   "Covered Versions" are Software versions in the applicable Order's Product Line, dated no later than the expiring Subscription end and that the Customer was otherwise entitled to receive under that Subscription. A release in another Product Line is not a Covered Version for that Order.

   1. Perpetual operation of Qualified Builds. The Licensor grants the Customer a perpetual, non-exclusive, worldwide license, subject to this Agreement and non-transferable except as provided in Section 13(b), to operate, distribute, scale, move and redeploy each byte-for-byte identical Qualified Build created and retained during the expiring Subscription or the unbroken paid Subscription series counted for this expiry. Those rights include moving the same Qualified Build between the Customer's permitted infrastructure, servers, domains and deployment environments, and changing external Customer data, content, secrets, runtime configuration and infrastructure as the Qualified Build definition permits.

      These rights authorize no new Application, development, build, modification or change to an artifact. That work requires an active Subscription except for a Permitted Remedial Build expressly authorized by Section 6(g), 6(h), 8 or 10 and governed by Section 6(j). The Customer must retain each Qualified Build and records reasonably sufficient to identify its exact bytes. Possessing a Covered Version does not authorize another build, and a version published after the Subscription ends is not Covered. A later Security Update is governed solely by Section 8 and does not become a Covered Version through technical activation.

   2. Key validity. After unrenewed grace, an applicable Commercial Key continues to activate ordinary releases through its signed cutoff only if its signed post-grace state confirms that subsection (c) rights accrued. The cutoff is the last paid day, not the grace end, and ordinary expiry eligibility is negative if those rights did not accrue. Section 7 may require a separate positive replacement key solely for its own rights.

      The applicable Perpetual Developer Limit under paragraph 3 remains, while relevant, as a final derived value in the minimum durable entitlement state. It is neither technically counted nor included in the License Key, which does not enlarge it. Supporting Order, payment and calculation history need not be retained solely because the final value continues.

      Rights from different expiries remain separate. The Customer must retain each Commercial Key needed for an earlier right, and a later nonqualifying series does not widen it.

      Section 8 exclusively governs later Security Update activation through a Security Release Certificate; Section 10 exclusively governs an exact later replacement Release Date for its remedy. Section 6(k) governs both paths, including their inability to change Product Line, ordinary cutoff, post-grace eligibility, Covered Versions, Developer limits or other rights, establish a Qualified Build, or authorize development or build work.

      The Software remains downloadable from the public npm registry. The Licensor does not control that registry and has no obligation to keep any particular version available there or to replace a Qualified Build or Customer record that the Customer did not retain.

   3. Continuing limits. Sections 3, 4 and 12 govern subsection (c) rights. Operating, copying, distributing, scaling, moving or redeploying an identical Qualified Build consumes no Developer seat merely for that work. Every person performing post-grace work expressly permitted by Section 6(g), 6(h), 8 or 10 is a Developer, and their total number may not exceed the "Perpetual Developer Limit". That limit is the lower of: (i) the number permitted immediately before the expiry when the relevant rights first accrued; and (ii) the lowest number permitted, with all corresponding fees paid and not refunded, during the 12-month period ending on that expiry under the calendar rule above.

      An Additional-Developer add-on increases that limit only at an expiry after the higher number actually applied, with corresponding fees paid and not refunded, throughout the full 12-month period; its actual effective day controls. Rights accruing at separate expiries retain separate Covered Versions, Qualified Builds and Perpetual Developer Limits; a later expiry neither retroactively reduces nor enlarges them. Ordinary Updates and email support end with the paid Subscription. Security Update duties and rights continue only as Section 8 and applicable mandatory law expressly provide.

4. Termination for breach or insolvency. The Licensor may terminate this Agreement for a material breach not cured within 30 days after written notice. No cure period applies to an incurable breach, including publication of the Software or a License Key or intentional Section 3(b) circumvention. To the extent applicable law permits, the Licensor may also terminate for insolvency, liquidation, bankruptcy or an equivalent proceeding.

   Except as Section 7 expressly provides, termination of this Agreement or of any license under it is not an expiry under Section 6(b) or 6(c), starts or continues no grace period and creates, accelerates or expands no fallback, perpetual or other subsection (c) right. All license rights end except subsection (c) rights actually accrued at an expiry before termination, on their existing terms and subject to the next paragraph.

   Those accrued rights do not survive an uncured material breach consisting of: (i) fraud or a knowingly false or incomplete verification used to obtain, measure or maintain them; (ii) deliberate concealment or intentional obstruction of a material license shortfall; (iii) intentional circumvention or unauthorized acquisition, transfer, publication, sharing or material misuse of the Software or a License Key; or (iv) a material breach of Section 2, 3 or 4 or an Order license-scope limit that directly concerns those rights. An immaterial discrepancy or unrelated breach does not extinguish accrued rights merely because termination occurs, without limiting another remedy.

   After termination, Section 8 creates no contractual duty to issue or right to apply a later Security Update unless applicable mandatory law requires it. An exact artifact containing a Security Update lawfully applied before termination continues only to the extent its underlying right in that artifact survives. That continued use arises from the underlying right, not separate survival of Section 8. No Security Update, replacement, notice or other action creates, restores, accelerates or expands an ended or unaccrued right. When all rights end, the Customer will delete its Software copies except those needed for a surviving right or required by law.

5. Survival. On expiry, Sections 1, 3, 4, 6(c), 6(d), 6(f), 6(g), 6(h), 6(i), 6(j), 6(k), 7, 8, 9, 10, 11, 12 and 13 survive and continue to apply to rights that survive under Section 6(c), Section 6(d) or Section 7. Section 8 survives expiry only on its terms to govern an existing or surviving right, including its Security Support Period and the limits on later use of an in-period Security Update.

   On termination, Sections 1, 3, 4, 6(c), 6(d), 6(f), 6(g), 6(h), 6(i), 6(j), 6(k), 7, 9, 10, 11, 12 and 13 survive only to the extent needed to govern rights that expressly survive under Section 6(d), accrued obligations and enforcement of this Agreement. Section 8 survives termination only to the extent applicable mandatory law requires.

   On expiry or termination, only the non-grant obligations and limitations in Section 2 concerning responsibility for authorized Affiliates, end-user arrangements and notices, Customer-controlled Applications, data, content, infrastructure and safeguards, the professional-advice disclaimer and the limitation on using the Software as the sole control in specified high-risk systems, ownership of the Software, and Customer modifications continue, and only to the extent their subject matter applies to a right that expressly continues under Section 6(b), 6(c), 6(d), 6(g), 6(h), 7, 8 or 10. No license grant in Section 2 survives or is recreated by this paragraph. Every continuing right in the Software that would otherwise arise from Section 2 exists only where one of those Sections expressly provides it. Neither expiry, termination, continued use of a Security Update nor survival of any Section creates, restores, accelerates or expands a production, fallback, perpetual or other license right.

6. Refunds and chargebacks. A refunded Subscription period, every Section 6(b) grace period arising from it and its Section 2 rights end on the day the Licensor or merchant of record instructs the payment provider to return the fees, the "Refund Date". If a chargeback leaves the Licensor or merchant without payment, they end on the day the provider records that reversal, the "Chargeback Date". Neither event starts a new grace period.

   The affected period does not count under Section 6(c). If refunded or reversed fees contributed to fallback eligibility, an ordinary cutoff or a Perpetual Developer Limit, eligibility, Covered Versions, Qualified Builds and that limit are recalculated as if the period were unpaid, and excess rights lapse. A Section 7 refund of only unused prepaid fees does not reverse completed paid days or remove them from the subsection (c) count.

   For a voluntary refund, a request is complete only if the Licensor receives, within the applicable policy's request period, all required information and cessation and deletion confirmations. A later confirmation does not preserve or revive eligibility unless the Licensor agrees in writing. This does not limit a mandatory right that applicable law does not permit it to exclude.

7. Compromised keys and retired signers. If a License Key becomes available outside the Developers, build systems, private repositories and Application delivery permitted by Section 3(b), or the Licensor reasonably determines that an unauthorized person may use or alter it, the key is compromised. The Licensor will issue a same-scope replacement for the same signed Product Line, subject to the fee rules below, and send it or secure retrieval instructions to the Customer's notices address. The Licensor may reject the compromised key only in versions published more than 30 days after the later of replacement issuance and receipt under Section 13(e); released versions keep working with it. Readability caused solely by permitted embedding under Section 3(b) is expected and is not itself compromise or prohibited disclosure. An automated delivery failure postpones receipt until the Licensor uses reasonable follow-up measures based on current Order records and provides reasonable secure retrieval. Receipt, or those measures and availability, starts the 30-day period even if the Customer does not acknowledge or retrieve the key.

   The Customer must notify the Licensor promptly after discovering a compromise, provide information reasonably needed to identify the entitlement, cooperate with replacement, and take reasonable steps to remove unauthorized access and prevent recurrence. The first replacement for a compromise, and any replacement for a compromise not materially caused by breach of those duties, is free. If repeated compromise is materially caused by failure to follow reasonable security measures after written guidance or by intentional or reckless disclosure or misuse, the Licensor may charge a reasonable administrative fee disclosed before the work and suspend ordinary future keys, Updates or support under Section 6(i) until the cause is remedied and the fee paid. Those measures do not by themselves end an accrued substantive right. A same-scope replacement technically necessary solely for a continuing right remains available after reasonable proof of that right and cooperation, subject to any fee due.

   For planned retirement of a signing key or signer, the Licensor will issue at no charge a replacement preserving the signed Product Line and other surviving scope of every affected entitlement it can reasonably identify, and send each affected Customer its replacement or secure retrieval instructions at that Customer's notices address. It may reject the signer only in versions published at least 60 UTC calendar days after the later of the last required replacement's issuance and the sending of the last required notice or retrieval instructions. If no affected entitlement has active, grace-period or surviving scope that requires a replacement or notice on the date of the written retirement determination, the 60 days run from that date and no delivery is required. Notice is received under Section 13(e). An automated failure does not postpone retirement if the Licensor uses reasonable follow-up based on current Order records and keeps a reasonable post-retirement replacement process for a Customer that proves the affected Order. The Customer must keep its address current and retrieve an available replacement; one Customer's failure does not postpone retirement for others. Released versions keep the retired signer.

   If an applicable retention rule lawfully removed a Customer's notices address before the planned-retirement determination, lack of direct notice does not postpone retirement. The Licensor must still issue a same-scope replacement for every affected surviving entitlement it can reasonably identify, publish reasonable retirement and secure-retrieval instructions on its license or support page throughout the transition, and keep a reasonable post-retirement recovery process for a Customer that proves the entitlement, Order or old key. No notices address need be retained beyond its lawful retention period.

   If the Licensor reasonably determines that a signing key has been compromised, can be used to create unauthorized keys, or must be retired promptly to address a material security or legal risk, it may reject that signer in a later release without the planned transition or 60-day wait. Before doing so, it will issue at no charge a replacement for each affected surviving entitlement it can identify, each preserving the original signed Product Line, and send the key or secure retrieval instructions to each affected Customer's notices address. If delivery fails, it will keep a reasonable replacement process available after the Customer proves the affected Order. If an address was lawfully removed before emergency retirement, the Licensor will publish reasonable secure-retrieval instructions and keep a reasonable proof-based recovery process to the extent reasonably possible without delaying action needed to address the material security or legal risk. Emergency retirement does not end a surviving substantive right, and released versions keep their existing offline signer set.

8. Technical narrowing and revocation. If, because of a refund, chargeback, termination, a remedy under this Agreement or Permanent Discontinuation under Section 7, some key-backed rights remain or arise while a Commercial Key for the same Source Period can activate broader release coverage or is linked to a higher Perpetual Developer Limit, the Licensor may reject that broader key in later versions only after issuing one replacement Commercial Key for that Source Period. The replacement must preserve the entitlement and original signed Product Line, use the narrowest ordinary-release cutoff and exact remedial Release-Date set reasonably necessary for the remaining rights, and be linked to no higher durable Developer limit than those rights allow. If the Licensor elects to reject the broader key, it must make the replacement reasonably available through the last notices address available from current records or reasonable secure retrieval.

   If a later refund, chargeback, termination decision or other event permitted by this Agreement further reduces the rights remaining for the same Source Period, the Licensor may repeat that narrowing only from the current terminal replacement. Each successor must preserve the entitlement and Product Line, remain separate from every other Source Period, and only reduce, never restore or expand, its ordinary cutoff, exact remedial-date set or durable Perpetual Developer Limit. A superseded or parallel key cannot create another narrowing branch. Narrowing does not reissue a Section 7 final retained build.

   Association follows the Source Period definition in Section 1. One replacement may replace every affected broader serial for that Source Period. If those keys contain multiple exact remedial Release Dates, only dates whose attached remedy rights remain may be included. Rights from another Source Period or expiry may not be aggregated, merged or transferred; that period requires its own decision and, if rights remain or arise, its own replacement.

   Customer acknowledgement, receipt or retrieval is not required. After issuance and one reasonable availability method above, delivery failure, no current address or failure to retrieve does not postpone narrowing. An affected serial governed by Section 6(g) may be rejected only when Section 6(g)'s stricter issuance, delivery and timing requirements are satisfied. If no key-backed right remains or arises for one Source Period, later versions may reject every key for that period without affecting another period under the entitlement. They may reject every key for the entitlement only if no such right remains or arises anywhere under it.

   A later release may implement either decision offline through privacy-minimized opaque technical revocation identifiers. The Licensor keeps the detailed decision, reason and supporting records privately; only the privacy-minimized technical identifier and minimum status needed to apply it may be distributed. Narrowing changes no contractual right, contacts no licensing service and alters no installed version. Minimum technical decision and status data may remain while needed to apply the decision; reasons, notices, delivery material and evidence follow their separate retention periods and are not kept solely because an identifier remains effective.

   If a License Key replaced under Section 6(g) or this subsection was embedded in a Qualified Build, the Customer may create a Permitted Remedial Build under Section 6(j) solely to substitute that key. Section 6(j) governs the required build identity, permitted changes, evidence, Developer limits, treatment of the resulting artifact and prohibition on any other build or modification.

9. Suspension of future performance. The Licensor may proportionately suspend future performance if: (i) a due amount remains overdue and is not subject to a timely, bona fide dispute stated in reasonable detail; (ii) the Customer materially breaches Section 2, 3, 4, 12, 13(l), 13(n), 13(o) or a material Order limit; (iii) the Licensor reasonably identifies fraud, abuse, a compromised credential or material security risk connected with the Customer's use; or (iv) applicable law or a binding order requires suspension.

   Future performance may include new or renewed keys, entitlement increases, ordinary Updates and support, later-release access, optional private distribution or support channels and optional hosted services. The Licensor will give written notice describing the material basis and, where curable, a reasonable opportunity to cure before suspension. It may suspend immediately where delay creates material security, legal or fraud risk, with notice as soon as reasonably practicable.

   Suspension does not remotely alter or disable an installed copy, revoke an accrued right, extend Subscription or grace, or excuse fees already due. The Licensor will not withhold a Security Update or same-scope replacement key where mandatory law requires it or the replacement is technically necessary only to preserve a continuing right and the Customer reasonably cooperates with verification of that right. After cure to the Licensor's reasonable satisfaction, affected future performance resumes prospectively within a reasonable time. Unless mandatory law requires otherwise, Customer-caused suspension creates no refund, credit, extension or right to performance that otherwise fell due while suspended.

10. Permitted Remedial Builds. Where Section 6(g), 6(h), 8 or 10 expressly authorizes post-Subscription build work, the Customer may create only the exact artifact or artifacts that provision permits, solely to preserve or implement the underlying right.

    It must keep the same Application scope and make only integration, configuration and build changes technically necessary for the permitted key substitution, Security Update or non-infringing replacement. It may not start a new Application, add a feature, update an unrelated dependency or make an unrelated code, content or configuration change. For a key substitution under Section 6(g) or 6(h), it must use the same Application source, Software and dependency versions, build settings and output process and change only the embedded key. An authorizing provision may be narrower.

    The Customer must retain every exact resulting artifact and records reasonably identifying its bytes. For a build under Section 8 or 10, the records must also identify the applied Security Update or non-infringing replacement. Section 12 governs UTC creation and retention date records where its schedule applies. Every person doing the work is a Developer. During Section 6(b) grace, the last paid Developer limit applies; afterward, the applicable Perpetual Developer Limit under Section 6(c)(3) or 7 applies.

    Notwithstanding ordinary Qualified Build timing, the result is the same Qualified Build only within the scope and duration of the production right making the work eligible. Section 7 work and artifacts remain subject to Section 7's Application scope, final-artifact limit and wind-down. The artifact does not survive its underlying right. This subsection does not make an update or replacement a Covered Version, permit continuing development or another build, create a source-code or build-system right, or create, restore, renew, accelerate or expand any license right.

11. Local validation and technical boundaries. Every distributed copy validates and activates License Keys locally. It does not automatically contact a Domternal-controlled licensing service, send Customer or End User content or usage data to the Licensor for licensing, meter Developers online, or provide a remote licensing kill switch capable of changing or disabling an installed copy.

    Local validation may enforce signed key type, time, cutoff, post-grace state, Product Line, exact remedial Release Date and other local boundaries. A later release may apply locally distributed signer and privacy-minimized revocation data, and installing it subjects that copy to its local validation. Technical activation does not establish a Qualified Build or grant, restore, renew or expand a contractual right.

    An exact remedial Release Date may technically activate Software released on that recorded UTC day within the signed Product Line, but grants rights only to the replacement to which the remedy attaches and not to an unrelated same-day release. It does not change Product Line or cutoff or create post-grace eligibility.

    As this Agreement and applicable law permit, the Licensor may refuse or stop future keys, renewals, Updates, support or later-release access and promises no indefinite registry, download, optional service or future release. None of those measures remotely changes an installed copy or ends a substantive right expressly preserved here.

7. Continuity

"Permanent Discontinuation" occurs only if the Licensor or its successor definitively stops offering the applicable Product Line as a commercial product and generally stops accepting its renewals, without offering a materially equivalent successor product and a commercially reasonable migration path.

It does not include: a rename or rebrand; a new version, edition or Product Line; a change in price, plan, billing cadence, licensing model, package layout or distribution channel; withdrawal of one plan, package, feature or integration while the Product Line or a materially equivalent successor continues; a sale, assignment, merger, reorganization or other change of control where a successor continues the Software or a materially equivalent successor; a temporary interruption; or ordinary end-of-life of a version or Product Line where a materially equivalent successor and commercially reasonable migration path remain available.

That migration path may consist of generally available documentation, tooling or transition information selected by the Licensor. It need not include bespoke services, backward compatibility, migration of Customer data or an Application, adaptation to the Customer's environment, or the same price, plan, billing cadence, licensing model or commercial terms. A successor may be a new generation or Product Line offered under its then-current terms and a separate Order.

The "Discontinuation Notice Date" is the UTC calendar day of the Licensor's formal written notice of Permanent Discontinuation or, if none was given, the day Permanent Discontinuation occurs. This Section protects only a Customer that on that date: (i) has an active Subscription or is within Section 6(b) grace; (ii) is not suspended or terminated for breach; and (iii) is current on all due and undisputed fees.

An eligible Customer that already satisfies Section 6(c)'s fallback eligibility condition receives only its Section 6(c) rights. Permanent Discontinuation does not expand them.

Every other eligible Customer receives a limited 90-day final-build wind-down from the Discontinuation Notice Date at no additional license fee. An active paid Subscription and the Licensor's paid performance may continue beyond that period on their ordinary terms; the wind-down neither shortens nor expands those rights. If paid performance ends before day 90, the wind-down continues through that day.

During the wind-down, the Customer may use only ordinary Software releases with a Release Date on or before the last day for which the Licensor provided paid Subscription performance. It may finish and retain no more than one final production artifact for each Application already in production or documented active development before the Discontinuation Notice Date. Only work reasonably necessary to complete, package and deploy that Application as then scoped is permitted. The Customer may not begin another Application, add a materially new feature, perform unrelated development, or use the Software for a third party not already authorized by the Order. All Developers remain aggregated, and their total number may not exceed the limit on the Subscription's last active day.

Notwithstanding the ordinary Qualified Build timing requirement, each exact final artifact completed, retained and documented during the wind-down is a Qualified Build solely for Section 6(c)(1)'s perpetual operational rights. After the wind-down, the Customer may operate, distribute, scale, move and redeploy that byte-for-byte identical artifact, but may not continue development or create or modify another build except through a Permitted Remedial Build expressly authorized by Section 6(g), 6(h), 8 or 10 and governed by Section 6(j). No broader perpetual right arises in the Software, Covered Versions, source code, an Application's source code or its build system.

For rights created by this Section, the "Perpetual Developer Limit" for later build work expressly permitted by Section 6(g), 6(h), 8 or 10 is the Developer limit on the last active paid day. Customer and authorized Affiliate Developers remain aggregated. This limit does not independently authorize build work.

If the Licensor ends paid Subscription performance before the last paid day, it will refund the affected unused prepaid fees pro rata. The refund does not remove the wind-down or resulting operational right or refund completed paid days, and is the Customer's sole monetary remedy for that early end, except where applicable mandatory law does not permit that limitation.

Permanent Discontinuation does not restart or extend the Security Support Period or Security Support End Date except where applicable mandatory law requires otherwise. If the current Commercial Key cannot activate rights created by this Section, the Licensor will issue at no charge a replacement that preserves the original signed Product Line, has an ordinary release cutoff no later than the last day of paid performance applicable to those rights, and contains only their required post-grace eligibility. It will be sent to the Customer's notices address or made available through a secure retrieval method. Section 6(k) governs its local validation and technical boundaries. If the Licensor stops accepting broader keys in that conversion, Section 6(h) applies separately to every affected Source Period.

Where the Order provides for it, the Licensor deposits the Software's source code with an independent escrow agent under a separate agreement among the Licensor, Customer and agent. Release events are limited to the Licensor ceasing to trade, entering insolvency proceedings, or Permanent Discontinuation without the protections above taking effect. The Customer pays the agent's fees unless the Order says otherwise. Released source remains subject to Section 3 and may be used only during an active Subscription, during the wind-down above, or for post-expiry build work expressly permitted by Section 8 or 10. Escrow release creates no general right to maintain, modify or develop the Software or an Application after expiry.

8. Updates and support

1. Ordinary Updates and support. An active paid Subscription includes every Update published during its paid period for the Product Line identified in its Order, and ordinary support by email. A release in another Product Line requires a separate Order. The pricing page states the response target for a self-serve plan, which is recorded in the Order; an Enterprise response target is stated in its Order. A target measures the first substantive response, not resolution, workaround or completion, and is not a guarantee unless a written service level agreement says otherwise. The Section 6(b) grace period includes no ordinary Update, feature release, ordinary support or service level unless renewal payment restores the Subscription. An Evaluation includes none of those benefits.

   Ordinary support covers reasonable guidance on installing and configuring the unmodified Software in a documented supported environment, using its documented API, understanding its documentation and triaging a specific, reproducible issue in the unmodified Software. It is subject to reasonable fair use proportionate to the plan and does not replace the Customer's own engineering, operations or professional advisers. Unless the Order expressly includes them, it excludes Customer-code development or review, custom features, architecture or security review, migration, training, data recovery, legal or compliance advice, adaptation to a modified or unsupported environment, and investigation of a third-party provider, dependency, network or infrastructure outside the Licensor's control. The Licensor may decline an out-of-scope request or offer separate paid services.

   To administer fair use, the Licensor may combine duplicate or materially related requests, prioritize by severity, Customer impact and order received, require reasonably sufficient reproduction details, and pause a request while necessary Customer information or access is missing. It may limit or decline abusive, repetitive, excessive or out-of-scope volume disproportionate to the plan. These measures do not reduce an express service level in the Order or an obligation that applicable mandatory law does not permit the parties to limit.

2. Security Support Period. Security Updates are separate from ordinary Updates and ordinary support. Only to the extent applicable mandatory law applies to the Software and requires the Licensor to do so, the Licensor will make necessary Security Updates for the unmodified Software available without an additional license fee during the applicable Security Support Period. The Order states the Product Line and its Security Support End Date. Nothing in this Section requires the Licensor to provide a Security Update after that date, except to the extent applicable mandatory law expressly requires otherwise.

   Subject to applicable mandatory law, the Licensor determines the technically reasonable form, scope and compatibility of a Security Update. It may provide a security-only patch, a later compatible security-only release or an interim mitigation while preparing an update. It need not backport a fix to every earlier release, support a Customer modification, adapt an Application or environment, remediate a third-party component not exploitable through the unmodified Software, or include new functionality, except where applicable mandatory law requires otherwise.

3. Eligibility after ordinary Update rights end. After ordinary Update rights end, the Customer may use a later Security Update only to secure: (i) an affected production deployment or Qualified Build covered by rights continuing during the Section 6(b) grace period; (ii) an affected Qualified Build within rights surviving under Section 6(c) or 7; (iii) an Application being completed under Section 7; or (iv) a right that applicable mandatory law requires to continue after termination. Rights surviving under Section 6(d) do not by themselves include a contractual right to receive or apply a later Security Update.

   The Commercial Key, every ordinary release registered in the same production context, and the Security Update and its Security Release Certificate must identify exactly the same Product Line. Missing, conflicting or mismatched Product Line metadata remains uncovered and does not activate production.

   During the Section 6(b) grace period, a later Security Update requires a valid Security Release Certificate whose signed feature-baseline Release Date is no later than the Commercial Key's ordinary release cutoff; signed post-grace eligibility is not then required. After grace, the same path also requires positive signed post-grace eligibility and a surviving production right under Section 6(c) or 7. A key without that eligibility cannot activate the Security Update after grace. The certificate does not modify or renew the Commercial Key, change its signed Product Line, ordinary release cutoff or post-grace eligibility, or grant another Product Line. An exact Section 10 replacement Release Date is not an ordinary release cutoff and creates no eligibility for this Security Update path. Section 6(k) otherwise governs local validation and technical boundaries.

4. Permitted work. After the paid Subscription ends, the Customer may create a Permitted Remedial Build under Section 6(j) solely to substitute an eligible Security Update in an existing production deployment it may continue operating under Section 6(b), an affected Qualified Build, or an Application being completed under Section 7. During grace, the resulting exact artifact may be operated as the updated form of the same deployment or Application only for the remainder of grace. An artifact derived from a Qualified Build, or from an Application being completed under Section 7, is treated as that same Qualified Build only within the scope and for the duration of the right that made the Security Update eligible. Section 6(j) governs all other build, evidence, Developer-limit and no-expansion rules.

5. No expansion and end of support. A Security Update does not become a new Covered Version, move an ordinary release cutoff, renew a Subscription, create or restore an ended production right, add a Developer, provide ordinary support or a service level, unlock a feature, or grant rights to another Product Line, except where applicable mandatory law requires otherwise.

   The Security Support End Date ends the Licensor's obligation to issue further Security Updates, subject to applicable mandatory law. A Security Update carrying a valid Security Release Certificate that the Licensor signed and released during the Security Support Period may remain usable afterward only within the same existing or surviving production right, Developer limit and other restrictions that made it eligible. Continued use does not make the Product Line supported or create a warranty, feature entitlement, support obligation or service level, or create, restore, renew or expand any license right.

   The Licensor will keep a released Security Update available for any minimum period required by applicable mandatory law. Continued availability does not extend the Security Support Period or require another update. A voluntary update, mitigation, notice or extension creates no renewal, ongoing obligation or course of dealing.

6. Customer responsibilities. The Customer is responsible for keeping its notices address current, monitoring the published security policy and notices, maintaining supported dependencies and environments, testing changes and backups for its Application, and applying an available Security Update or mitigation without undue delay after reasonable validation. These responsibilities do not reduce an obligation that applicable law does not permit the parties to exclude.

9. Third-party components

The Software includes or depends on third-party components governed by their own terms. Components bundled in a package are listed in its THIRD-PARTY-LICENSES.md; separately installed dependencies, including peer dependencies, are identified in its package.json and licensed by their authors. Those terms govern those components. This Agreement governs the Licensor's code and, except below, each package as a whole regardless of a contrary file.

@domternal-pro/extension-export-fonts is governed by the SIL Open Font License 1.1 stated in its LICENSE.md; every other Software package is governed by this Agreement, subject to the third-party terms above.

The reference collaboration server and AI proxy published separately in the public domternal/self-hosting repository are governed by its MIT license and are not Software under this Agreement. Running or modifying them does not itself require a License Key. Use of the Software in an Application with those services remains governed by this Agreement.

10. Warranty

1. Scope of intellectual-property warranty. The warranty and remedies in subsections (a) through (d) apply only to a Customer with a paid Order and only to use within the rights granted by that Order and this Agreement. They do not apply to an Evaluation. The Licensor warrants that it holds the rights necessary to grant this license. Unless an Enterprise Order expressly includes broader intellectual-property defense or indemnity, the Licensor need not defend, indemnify or hold the Customer harmless against a third-party claim. Any broader Enterprise protection is limited to the scope, procedure, exclusions and liability cap expressly stated in that Order.

2. Claim and remedies. If a third party makes a credible written claim that the unmodified Software infringes its intellectual-property rights, the Licensor will, at its option, procure continued-use rights, replace or modify the Software to avoid infringement, or terminate the affected license and refund fees paid for the current Subscription period. This is the Customer's exclusive remedy for breach of the warranty in subsection (a).

   Such termination does not affect rights accrued under Section 6(c), unless continued use of an affected Covered Version in a Qualified Build would infringe. The Licensor may then end those accrued rights for the affected use and, at its option, either: (i) provide a non-infringing replacement within the original Product Line, together with any required same-Product-Line License Key, to which the affected Qualified Build rights attach; or (ii) refund the fees paid for the 12 months of Subscription preceding the expiry at which those rights accrued. That refund compensates for the ended rights and is not a refund of Subscription fees under Section 6(f).

   The Customer will promptly notify the Licensor of a third-party claim against it that the Software infringes intellectual-property rights; late notice matters only to the extent it materially prejudices an available response. A claim is credible when the Licensor reasonably considers it so. If the Licensor elects to control the defense, or an Enterprise Order requires it, the Customer will give the Licensor sole control of the defense and settlement to the extent concerning the Software, cooperate reasonably at the Licensor's expense, and make no admission or settlement concerning that part without the Licensor's written consent. The Licensor may not settle a controlled defense in a way that admits Customer fault or imposes an obligation beyond ceasing use of the affected version without the Customer's written consent. The Customer will adopt an available non-infringing replacement or modification provided under this Section without undue delay.

3. Replacement activation and build work. The Customer will use a replacement key provided for this remedy. If a replacement version has a Release Date after the ordinary release cutoff, the key may include that exact Release Date under Section 6(k). During Section 6(b) grace, the exact exception may activate without positive signed post-grace eligibility only while the underlying grace-period right continues. After grace, it requires positive signed post-grace eligibility and an underlying surviving production right under Section 6(c) or 7. A later Section 6(h) replacement may retain only exact remedial Release Dates whose attached remedy rights remain for the same Source Period and may not combine rights from another period or expiry.

   After the paid Subscription ends, the Customer may create a Permitted Remedial Build under Section 6(j) solely to substitute the replacement in an affected production deployment it may continue operating under Section 6(b), each affected Qualified Build, or an Application being completed under Section 7. During grace, the exact artifact may be operated as the replacement form of the same deployment or Application only for the remainder of grace. An artifact derived from a Qualified Build, or from an Application being completed under Section 7, is treated as that same Qualified Build solely within the surviving scope of this remedy. Section 6(j) governs all other build, evidence, Developer-limit and no-expansion rules.

4. Exclusions. The warranty and remedies do not apply to the extent a claim arises from: (i) a Customer modification, specification or instruction; (ii) combination with an item not supplied by the Licensor; (iii) a third-party component standing alone under its own terms, except a claim that the Licensor lacked the right to distribute it as included in the unmodified Software; (iv) use in breach of this Agreement; (v) use after the Licensor gave reasonable notice that continued affected use could infringe, where stopping that use could avoid the claim; or (vi) failure to adopt without undue delay an available replacement, modification or Update that would have avoided the claim without materially reducing the documented functionality of the affected Software. Subject to applicable mandatory law, this Section provides the Customer's exclusive remedies for a third-party intellectual-property claim concerning the Software.

5. Network-capable features. Section 6(k) governs local License Key validation. AI and collaboration features may contact endpoints configured by the Customer's host Application. Optional Domternal-hosted services, if offered, may communicate over a network and are governed by their separate Order, service terms and privacy disclosures. Future Product Lines may use a different licensing or service architecture under separate Orders. None of those paths is License Key validation for an installed copy governed by Section 6(k), and none expands this Agreement's rights.

6. Third-party AI. The Software provides integration tools and does not itself supply, operate or control a third-party artificial-intelligence model or provider selected by the Customer. The Customer controls and is responsible for its endpoint, provider, model, prompts, inputs, outputs and provider account, and for the rights, legal basis, notices, consents and safeguards required for data it sends. It will review AI output and apply human or other oversight appropriate to the context and foreseeable impact before relying on or distributing it.

   The Licensor does not warrant a third-party model, provider or output, including its accuracy, completeness, lawfulness, non-infringement, security, availability or suitability; the provider's terms govern it. This does not exclude liability for a defect in the unmodified Software or an obligation that applicable mandatory law places on the Licensor.

7. Disclaimer. Except for the warranties above, and to the maximum extent permitted by applicable law, the Software is provided "as is", without express or implied warranties, including merchantability, fitness for a particular purpose and non-infringement beyond subsection (a). The Licensor does not warrant that the Software is error-free, vulnerability-free or immune from attack. A Security Update or interim mitigation does not warrant that every vulnerability has been identified, every attack will be prevented, or the update will be compatible with a modified or unsupported Application or environment.

   Nothing in this Section excludes or limits a warranty, liability or remedy that applicable law does not permit the parties to exclude or limit, including an applicable rule concerning a defect the Licensor knew of and did not disclose to the Customer.

8. Defect and security information. The Licensor may document confirmed non-security defects or resolved issues in a changelog, public issue tracker, release notes or another appropriate channel when it considers that useful. Public channels are not a complete record of internal reports, investigations, duplicates, unconfirmed or immaterial issues, or confidential matters.

   Security vulnerabilities are handled through coordinated private disclosure, subject to any earlier reporting, notice or disclosure required by law. After a fix or mitigation is available, the Licensor may publish an advisory or changelog entry with timing and detail reasonably chosen to protect Customers and End Users.

   The Licensor provides reports, notices and disclosures required by applicable law. Where mandatory law requires individual notice, it may use the last notices address the Customer provided. The Licensor may also publish or send an advisory when it reasonably considers additional notice useful, but a voluntary advisory or notice does not create a duty to identify or contact every affected user or a continuing notification obligation.

11. Liability

1. Cap and excluded loss. To the maximum extent permitted by law, the Licensor's total aggregate liability arising from or relating to a paid Order is limited to the greater of: (i) EUR 100; and (ii) the fees the Customer actually paid and that were not refunded under the affected Order during the 12 months immediately preceding the first event giving rise to the claim. Claims arising from the same or related events, acts, omissions, Software defect or series of transactions are aggregated and use the date of the first such event. For use under Section 5 without a paid Order, the Licensor's total aggregate liability is limited to EUR 100. Neither party is liable for indirect, incidental, special or consequential damages, or for lost profits, revenue or data.

   To the maximum extent permitted by applicable law, the Licensor is not liable to the extent a loss was caused or increased by the Customer's failure to apply an available Security Update or interim mitigation without undue delay after reasonable validation, by a modification or combination not supplied by the Licensor, by an unsupported dependency or environment, or by continued use after the applicable Security Support End Date.

2. Carve-outs. The limitations and exclusions in subsection (a) do not apply to damage caused intentionally or by gross negligence, or to liability that applicable law does not permit the parties to exclude or limit. They also do not apply to: (i) the Customer's breach of Section 2, 3 or 4 or a limit stated in the Order; (ii) fees due under an Order; (iii) the indemnification in subsection (d); (iv) the Customer's fraud, knowingly false verification statement, deliberate concealment or intentional obstruction under Section 12; (v) intentional or materially misleading misuse of a Domternal Mark under Section 13(n); or (vi) an intentional or grossly negligent breach of Section 13(o).

3. Non-monetary relief. Nothing in this Section limits a party's right to seek an injunction, specific performance, correction, removal, technical narrowing, revocation or another non-monetary remedy available under this Agreement or applicable law. Such a remedy does not expand a substantive right or permit remote alteration of an installed copy contrary to Section 6(k).

4. Indemnification by the Customer. The Customer will defend and indemnify the Licensor against third-party claims, and resulting damages and reasonable costs, arising from an Application, the Customer's data or content, the Customer Marks or the Licensor's permitted use of them under Section 13(k), the Customer's modifications or combinations of the Software, or use of the Software in breach of this Agreement. This indemnity does not apply to the extent the claim arises from the unmodified Software itself, or from the Licensor altering a Customer Mark or using it beyond Section 13(k) or an applicable Order limitation.

   The Licensor will promptly notify the Customer of a covered claim; late notice matters only to the extent it prejudices the defense. The Customer may control the defense and settlement. The Licensor may participate with its own counsel at its own expense and will reasonably cooperate at the Customer's expense. No settlement may admit fault of, or impose an obligation on, the Licensor without its written consent.

12. Verification

1. Annual statement. No more than once in any 12-month period, the Licensor may request, and the Customer will provide within 30 days, a written statement of the maximum concurrent number of all Developers counted together under Section 4(a), including the Customer's Developers and the Developers of every authorized, Order-named Affiliate, during the preceding 12 months, signed by an authorized representative of the Customer. The Customer keeps records reasonably sufficient to support that statement for the Subscription and any period during which it exercises post-expiry rights, and provides those records on the Licensor's reasonable request. Records may be provided in pseudonymized or aggregated form where sufficient to support the statement.

2. Qualified Build schedule. If the Customer exercises post-expiry rights under Section 6(c) or 7, the same request may also require a signed schedule of the Qualified Builds on which it relies. The schedule must give: (i) a neutral identifier for each Application; (ii) a SHA-256 or equivalently reliable cryptographic hash of each retained Qualified Build, including a final artifact under Section 7 or a Permitted Remedial Build under Section 6(j); (iii) the UTC creation and retention date of each artifact; and (iv) confirmation that the Customer has not made or used a later build except as this Agreement expressly permits. The Licensor will not require Application source code, Customer content, secrets or personal data merely to satisfy this schedule requirement.

3. Independent audit. The Licensor may require verification by an independent auditor bound by confidentiality if the Licensor has a documented reasonable basis to suspect a material discrepancy, a requested discrepancy remains unresolved, the Customer does not provide reasonably sufficient records after two written requests, or a previous verification identified a material discrepancy. Except where new reasonable grounds arise after an earlier verification, an independent audit may occur no more than once in any 12-month period. The Licensor will give at least 30 days' written notice, use a suitably qualified independent auditor, conduct the audit remotely where reasonably sufficient and limit it to records reasonably necessary to verify compliance with this Agreement. Any on-site work must occur during normal business hours and avoid unreasonable disruption. The Licensor and auditor will not require Application source code, Customer content, secrets or unrelated personal data. The auditor may report the compliance result, calculation and supporting basis to the Licensor without disclosing unrelated Customer information.

4. Use, cost and shortfall. The Licensor uses verification materials only to verify and enforce this Agreement, treats them as Confidential Information under Section 13(o) and limits access to people who need them for that purpose. The Licensor bears the reasonable external cost of an independent audit unless it identifies an underpayment or Developer shortfall greater than 5 percent for the period examined, in which case the Customer will reimburse the Licensor's reasonable, documented external audit cost in addition to correcting the shortfall. The Customer will promptly purchase any Developer shortfall for the excess period at the Licensor's then-current list price and pay any other resulting underpayment.

   For the first shortfall that was non-willful, arose despite good-faith compliance and is fully corrected within 30 days after identification, that correction is the Licensor's exclusive monetary remedy for the shortfall itself, apart from audit costs payable under the preceding paragraph. It does not retroactively license excess use, waive a record or verification duty, prevent proportionate non-monetary relief, or apply to fraud, deliberate concealment, intentional obstruction, a knowingly false or incomplete statement, gross negligence or a repeated shortfall. A materially inaccurate or knowingly incomplete statement or schedule, fraud, deliberate concealment or intentional obstruction of verification is a material breach.

5. Incomplete verification. The Licensor may suspend future performance under Section 6(i) while requested verification remains materially incomplete after the applicable response period. That suspension does not suspend, terminate or otherwise reduce a right that already accrued under Section 6(c) or 7, delete or block Customer data, or prevent lawful access to, export, recovery or deletion of Customer data. A requested statement, schedule or audit access remaining outstanding after the applicable response period does not waive the verification obligation or limit the Licensor's right to require compliance, recover fees, audit costs or other amounts due, seek proportionate non-monetary relief, terminate this Agreement where Section 6(d) permits, or use another remedy available under this Agreement or applicable law. Any suspension and any restoration operate prospectively under Section 6(i); neither authorizes use that this Agreement did not permit.

13. General

1. Entire agreement. This Agreement and the Order are the entire agreement about the Software. The Licensor's ordering terms and refund policy referenced in the Order form part of the Order. A conflict is resolved only for its subject, in this order: (i) a negotiated Order term that expressly identifies the provision it changes; (ii) this Agreement for Software license rights, restrictions, warranties, remedies and liability; (iii) the Licensor's ordering terms for ordering, payment, renewal and account administration; (iv) the refund policy solely for refund eligibility and procedure; and (v) a reseller's or merchant of record's standard terms solely for its payment, invoicing, tax and provider-administered refund role. Preprinted or standard terms on a Customer purchase order, and terms on a reseller or merchant-of-record receipt not authored by the Licensor, do not otherwise modify this Agreement.

2. Assignment. The Customer may assign this Agreement to a successor in connection with a merger or acquisition of substantially all its business, with written notice to the Licensor, provided the successor assumes this Agreement in writing and is not a direct competitor of the Licensor; any other assignment requires the Licensor's consent, not to be unreasonably withheld. The Licensor may assign this Agreement, in whole or in the relevant part, to an Affiliate, a legal successor, a successor created by a change of legal or business form, or an entity that acquires the Software, its Product Line, or all or substantially all of the business or assets to which this Agreement relates, including through a merger, reorganization, sale or other transfer. A transferee of the entire Agreement assumes the Licensor's unperformed obligations arising after the transfer, and the transfer does not reduce rights that the Customer already accrued. The Licensor may also assign a receivable, payment right or related security interest without the Customer's consent. No assignment releases either party from an obligation that accrued before the assignment unless the other party agrees in writing or applicable law provides otherwise.

3. Changes. The Licensor may publish revised versions of this Agreement. A "Material Revision" is a revision that materially changes a Customer's license rights, restrictions, payment obligations, remedies, warranty, liability, renewal terms or obligations concerning its data. An editorial, formatting, contact, URL, cross-reference or administrative correction, or a clarification that does not materially change those matters, is not a Material Revision.

   For a Customer with an active paid Subscription or in its Section 6(b) grace period, the Licensor will notify the Customer of a Material Revision, with the revised text or a link to it, at least 30 days before it first applies at renewal and, where the Order requires notice of non-renewal, before the last day that notice can be given. The Licensor may publish a revision that is not material in its version archive or on its website without direct notice. For any other Customer, including one whose Subscription has ended or whose notices address is known only because a License Key was issued, the Licensor has no contractual duty to give direct notice unless notice is reasonably necessary to administer an existing right or applicable law requires it. A voluntary notice does not create a continuing notification obligation.

   For a Customer with an active paid Subscription or in its Section 6(b) grace period, a revised version applies only from the first renewal that starts after the revised version takes effect, not retroactively, and no revision reduces rights that already accrued under Section 6(c) for Qualified Builds created and retained during periods already paid for. If the Customer does not accept a revised version, it may let the Subscription expire at the end of the current period, and the version it accepted governs until then.

   For an anonymous keyless Evaluation, a revised version does not apply retroactively to an installed package release. The Licensor gives notice by including the revised Agreement as LICENSE.md in a later package release and making that version available at domternal.dev. Installing and continuing to use that later release constitutes acceptance of the revised Agreement for Evaluation use of that release. A Customer that does not accept the revision must not use the later release and may continue keyless Evaluation of an earlier release under the Agreement version included with it, subject to Section 5.

4. Governing law. This Agreement is governed by Croatian law, excluding its conflict-of-law rules and the UN Convention on Contracts for the International Sale of Goods. The courts at the Licensor's seat have jurisdiction, and that jurisdiction is exclusive for proceedings brought by the Customer. The Licensor may also bring proceedings in the courts of the European Union Member State or Lugano Convention State in which the Customer is domiciled or, where the Customer is domiciled in neither, in the courts of the place where the Customer has its seat or principal place of business. Either party may seek injunctive relief in any competent court. This Agreement is drafted in English; translations are for convenience only and the English text governs.

5. Notices. Notices under this Agreement may be given by email to the Customer at the address in the Order or the address to which the License Key was issued, and to the Licensor at [email protected]. The Customer will keep that address current and may designate another notices address in writing, which then prevails. Email is deemed received on the next business day at the recipient's seat, absent an automated delivery failure. For an anonymous keyless Evaluation for which the Licensor has no notices address, public notice on the Licensor's license or pricing page is sufficient for a general change or end under Section 5. That public-notice rule does not replace direct notice required for a paid Order or by applicable mandatory law.

6. Severability. If a provision of this Agreement is held unenforceable, it is enforced to the maximum extent permitted and the remainder stays in force.

7. No waiver. A failure or delay in exercising a right under this Agreement is not a waiver. A waiver is effective only in writing and only for the instance given.

8. Force majeure. Neither party is liable for delay or failure to perform, other than payment obligations, caused by events beyond its reasonable control, provided it resumes performance as soon as reasonably possible. If such an event prevents a material future obligation for 90 consecutive days, either party may terminate the affected unperformed Subscription or service by written notice. The termination does not affect fees or obligations accrued before it, an already accrued Section 6(c) right, or any unaffected Order. If the Licensor cannot provide a prepaid affected service after that termination, the Customer's sole monetary remedy for the force-majeure period is a pro rata refund of the unused prepaid fee for that service, except to the extent applicable mandatory law requires otherwise.

9. Independent contractors. The parties are independent contractors. This Agreement creates no partnership, agency or employment relationship.

10. Feedback. If the Customer provides suggestions, ideas or other feedback about the Software, it grants the Licensor a perpetual, irrevocable, worldwide, royalty-free license to use that feedback without restriction or obligation. Feedback does not include the Customer's Applications or confidential information.

11. Publicity. During an active Subscription and its Section 6(b) grace period, the Customer grants the Licensor a non-exclusive, worldwide, royalty-free license to use, reproduce and display any company or business name, trade name, primary corporate trademark or word mark, and current, unmodified official corporate logo that the Customer owns or controls and uses to identify itself or expressly provides for this purpose (collectively, "Customer Marks"). The Licensor may use Customer Marks solely to identify the Customer accurately as a Domternal customer or customer reference on its websites, customer and reference lists, and sales and marketing materials. The Customer represents that it has the rights and authority to grant this license. The Licensor may proportionately resize a logo for placement but not otherwise alter its design, colors, proportions or content; will follow reasonable written brand guidelines the Customer provides; and may permit service providers acting solely on its behalf to make the same limited use. All resulting goodwill inures solely to the Customer.

    For a natural-person Customer, or any Customer Mark identifying a natural person, the license applies only if the Order or later separate written permission expressly identifies and authorizes that Mark for this use. Permission is optional and withdrawable at any time.

    An Order may exclude this license or limit its Customer Marks, channels or uses, and that term controls. The Customer may also opt out or impose limits by written notice at any time. An opt-out or limitation continues through renewals and add-ons absent the Customer's express written agreement to change it, and is effective when received under Section 13(e), unless it states a later date. The license ends on the earliest of the Refund Date or Chargeback Date under Section 6(f), termination of this Agreement, and the end of the Section 6(b) grace period. After an opt-out, limitation or end, the Licensor will promptly stop new affected uses and remove affected Customer Marks from controlled websites and digital marketing materials within 30 days. If a Mark identifies a natural person who withdraws permission or objects, the Licensor will stop that use and remove the Mark from controlled digital materials without undue delay. It need not recall physical materials lawfully distributed before the use ended. Non-public archival or legal-record copies not used for current marketing, and third-party caches outside its control, may remain.

    This subsection permits only factual identification of the customer relationship. Testimonials, attributed quotations or other attributed statements, detailed case studies, press releases, and statements or presentations claiming or implying sponsorship, endorsement, partnership or approval of Domternal each require separate, express written permission identifying the specific content and use. This subsection permits neither disclosure of Customer contact details, usage metrics, non-public information or confidential information, nor use of a natural person's image, likeness or personal endorsement, and does not oblige the Customer to participate in a reference call.

12. Trade compliance. The Customer represents that it is not subject to a prohibition that makes the Order or its performance unlawful under sanctions or export-control law applicable to the Licensor, the Customer or the transaction. Applicable law includes Croatian and European Union law; UN measures to the extent implemented by or otherwise applicable to a party; and United States or other foreign law only where it lawfully applies to a party, the Software, the payment route, a provider or the transaction and is consistent with directly applicable European Union law.

    The Customer will not export, re-export, transfer, provide or use the Software in violation of such law and will provide information reasonably necessary for a lawful compliance check. The Licensor may delay or withhold a License Key, suspend performance under Section 6(i), reject or cancel an Order, or terminate this Agreement to the extent reasonably necessary to comply with such law or a binding order. It may also do so if a bank, payment provider or distribution provider lawfully refuses the transaction on those grounds and no commercially reasonable compliant alternative is available.

13. Taxes. Fees are exclusive of taxes, duties and withholdings. For Orders the Licensor invoices directly, the Customer bears all transaction taxes except taxes on the Licensor's income, and amounts payable are grossed up so the Licensor receives the full fee.

14. Trademarks. Each party retains all rights in its names, trade names, logos and trademarks. The Licensor has no right in Customer Marks except under subsection (k).

    During an active Subscription, its Section 6(b) grace period, and any later lawful exercise of Section 6(c) surviving rights, the Licensor grants the Customer a non-exclusive, worldwide, royalty-free license, transferable only as part of an assignment permitted by Section 13(b), to use, reproduce and display the Domternal name in plain text and the current, unmodified official Domternal logo publicly offered for customer-reference use (collectively, "Domternal Marks"). The Customer may use them solely to state accurately that it or an Application uses or incorporates the Software, on its websites and in Application documentation, technology-stack and integration pages, Application user interfaces, about, credits and attribution surfaces, and sales and marketing materials. Permitted factual statements include "Uses Domternal", "Built with Domternal" and "Powered by Domternal". It may not sublicense, but may authorize service providers acting solely on its behalf to make the same limited use. Affiliates lawfully exercising its Section 2 rights may do likewise; the Customer remains responsible for their use.

    The Domternal Marks exclude the Licensor's legal business name; the owner's name, image, likeness, signature and personal endorsement; and every other name, logo or mark. Using any requires separate, express written permission unless applicable law permits it without a license.

    The Customer may resize the Domternal logo proportionately solely for placement but not otherwise alter its design, colors, proportions or content. It will follow reasonable written brand guidelines the Licensor publishes or provides and use the current official logo within a reasonable period when the Licensor requests an update. It must not use a Domternal Mark as part of a company, product or service name, domain name, social-media account name, application icon or trademark; make it more prominent than its primary brand; use it unlawfully, misleadingly, deceptively or disparagingly; or state or imply the Licensor's sponsorship, endorsement, partnership, certification or approval. All resulting goodwill inures solely to the Licensor, which may require prompt correction or removal of a violating use.

    The Licensor may withdraw or limit logo permission on 30 days' written notice, or suspend or end it immediately by written notice if the Customer violates this subsection, uses a Domternal Mark unlawfully or misleadingly, infringes a third party's rights, or uses it in a way reasonably likely to materially harm the Licensor's reputation or goodwill. Logo permission also ends immediately if the Licensor terminates this Agreement for the Customer's breach under Section 6(d), even if Section 6(c) rights survive. When permission ends or is limited, the Customer must stop new affected uses by the effective date and remove the affected logo from controlled digital materials within 30 days, or promptly after immediate termination for a prohibited use. It need not recall physical materials lawfully distributed before permission ended, but may not reprint or reuse them.

    Ending or limiting logo permission does not prevent plain-text use of the Domternal name for permitted factual identification while the Customer lawfully uses the Software; all other limits continue. Nothing here restricts use of that name permitted without a license by applicable law, including a truthful nominative reference, but such use must not imply the Licensor's endorsement or approval. Retaining notices as Section 3(c) requires is not restricted.

15. Confidentiality. "Confidential Information" means non-public information that a party discloses in connection with this Agreement and marks as confidential, or that a reasonable recipient would understand to be confidential from its nature and the circumstances. The Licensor's Confidential Information includes non-public source code, roadmap and commercial information, security reports, signing material, License Key incident information and verification methods. The Customer's Confidential Information includes non-public Application, business, security and verification information.

    Confidential Information does not include information the recipient can document: (i) is or becomes public without breach of an obligation; (ii) it lawfully knew without restriction before disclosure; (iii) it receives lawfully and without a confidentiality duty from a third party; or (iv) it develops independently without using the discloser's Confidential Information. Software and information intentionally published in a public package, repository, website, documentation, pricing or other public channel is not Confidential Information merely because it concerns a party or the Software.

    The recipient will use Confidential Information only to perform, receive or enforce rights and obligations under this Agreement. It will protect the information with at least reasonable care and disclose it only to its personnel, professional advisers, auditors, financing sources and service providers who need it for that purpose and are bound by confidentiality obligations at least as protective as this subsection. The recipient remains responsible for their compliance. If law, regulation, court order or a competent authority requires disclosure, the recipient may disclose only what is required and, where legally permitted, will give prompt notice and reasonable assistance so the discloser may seek protection at its own expense.

    These obligations continue for five years after each disclosure, and for a trade secret as long as it remains one under applicable law through no breach by the recipient. On written request or when this Agreement ends, the recipient will delete or return Confidential Information no longer needed for a surviving right or obligation. Subject to applicable data-protection law, this excludes copies retained under law or professional recordkeeping rules and isolated routine backups that cannot reasonably be removed individually.

    A backup may remain only until its normal overwrite or deletion cycle, must remain protected, and must not be accessed or used except for backup integrity, security, recovery or legal compliance. If restored, the applicable deletion or return duty must be reapplied before ordinary use unless another lawful retention ground remains. No party must alter an immutable backup solely to remove particular information before its normal cycle, but this does not authorize indefinite retention. This subsection grants no intellectual-property license and does not prevent a disclosure or use that another provision expressly permits.

16. Current product and no roadmap reliance. The Customer enters an Order based on the Software, documentation and express commitments available when the Order is accepted. A roadmap, preview, prototype, planned feature, estimated date, forecast or other statement about future functionality is informational, may change or be withdrawn, and is not a binding delivery commitment, warranty or condition of purchase unless the Order expressly identifies it as one. Nothing in this subsection limits liability for fraud, an express written warranty or a right that applicable mandatory law does not permit the parties to exclude.

17. Cumulative remedies. Except where this Agreement expressly states that a remedy is exclusive, rights and remedies under this Agreement and applicable law are cumulative. Exercising one does not prevent another, but no party may recover twice for the same loss.

    ---

    Copyright (c) 2026 M Pro Solution, obrt za administrativne i pomoćne uslužne djelatnosti, Croatia. All rights reserved.