Appmixer “Software as a Service” Terms and Conditions

For Cloud-Based Appmixer Solution

Version 1.0 · 16 November 2026

1. Nature and Scope of the Terms

1.1 These Appmixer “Software as a Service” Terms and Conditions (“Terms”) apply to the agreement entered into between the Customer (as defined below) and the Provider (as defined below) (the “Agreement”), and set out the terms and conditions under which the Provider will grant the Customer access to the Software (as defined below) and provide other services.

1.2 The Customer’s and Provider’s acceptance of the Order (as defined below) shall constitute a binding Agreement between the Customer and the Provider.

1.3 These Terms, the Schedules hereto and any other documents, provisions and policies referred to in these Terms form an integral part of the Agreement.

2. Scope of the Agreement

2.1 The Provider undertakes, under the conditions specified in these Terms and for the duration of the Subscription Term (as defined below) to, in particular:

  • 2.1.1 provide the Customer with SaaS Services (as defined below);
  • 2.1.2 ensure a guaranteed level of availability of the SaaS Services to the Customer under the conditions specified in SLA (as defined below);
  • 2.1.3 provide the Customer with Support and Maintenance Services (as defined below); and

2.2 The Customer undertakes in particular to:

  • 2.2.1 use the SaaS Services and the Software strictly in compliance with this Agreement and the Documentation (as defined below); and
  • 2.2.2 pay the Subscription Fee (as defined below) to the Provider.

3. Definitions

3.1 “Appmixer” shall mean a software and technology for building automation workflows and integrations.

3.2 “Authorised User” means any Customer’s employee, subcontractor or other person designated by Customer who has been granted access to and the right to use the SaaS Services through necessary access credentials provided by the Provider.

3.3 “Customer” means the entity identified as a customer in the Order.

3.4 “Customer Application” means the software application or SaaS product developed and operated by Customer into which the Software is integrated (utilizing Redistributables and Integration Components) to provide automation functionality to End Users.

3.5 “Data Message” means an individual unit of information or a data packet transmitted between two components (such as connector triggers, actions or utilities) during the execution of a workflow within the Software or Customer Application. Each such individual transmission constitutes one Data Message for the purpose of calculating Usage-based Fees (see Article 11.4).

3.6 “Documentation” means user guides, online help, release notes, training materials, and any other documentation related to the use or operation of the Software or SaaS Services.

3.7 “Effective Date” means the date on which the Order was accepted by both Parties.

3.8 “End Users” means Customer’s customers or authorized users who access integration or automation functionality within the Customer Application.

3.9 “Host” means the computer equipment on which the Software is installed which is owned and operated by the Provider or its subcontractors (e.g. Amazon Web Services).

3.10 “Order” means the completed order form for provision of the SaaS Services and Support and Maintenance Services accepted by both Parties.

3.11 “Party” shall mean the Customer or the Provider respectively.

3.12 “Parties” shall mean collectively Customer and the Provider.

3.13 “Provider” means Appmixer s.r.o., with its registered seat: Pernerova 697/35, Karlín, 186 00 Praha 8, Czech Republic, company ID: 23916664, or (as the case may be) other entity identified as the provider of services in the Order.

3.14 “Price List” means the list of generally applicable Subscription Fee(s) made available on the Provider’s website or otherwise made available to the public, which can be amended by the Provider from time to time.

3.15 “Redistributables” means (a) the object code form of portions of the Software, which portions are described as such in the Documentation and are usually provided as obfuscated JavaScript files, and (b) also the source code or object code form of the Sample Code as originally supplied to, or as modified by, the Customer. For the avoidance of doubt, obfuscated JavaScript files are considered to be object code and not source code.

3.16 “Services” means collectively SaaS Services and Support and Maintenance Services.

3.17 “SaaS Services” means services described in Article 4 hereof.

3.18 “Sample Code” means the source code examples, snippets, and demonstration projects provided by the Provider in the Documentation or via the Software, intended to illustrate the use or integration of the Software and meant to be copied or modified by the Customer for use within the Customer Application.

3.19 “Service Level Agreement” or “SLA” means the agreement that outlines guaranteed service levels of the SaaS Services, as specified in Schedule No. 1.

3.20 “Software” means the Appmixer integration and workflow automation platform, including all Redistributables, operated by Provider and made available to Customer as a cloud-based service.

3.21 “Subscription Fee” means a fee that the Customer shall pay to the Provider for provision of the Services.

3.22 “Subscription Term” means the period during which Customer is authorized to access and use the Services under this Agreement, as specified in the applicable Order, including any renewal periods unless terminated in accordance with this Agreement.

3.23 “Support and Maintenance Services” means the support and maintenance services provided by the Provider to Customer as outlined in separate Support and Maintenance Services Terms.

3.24 “User” means collectively the Virtual User and the Authorised User.

3.25 “Virtual User” means a unique account or digital identity created by the Customer within the Software (typically via API) that represents an End User or an internal team member. A Virtual User profile serves to isolate and manage that specific individual’s third-party credentials, configuration settings, and automated workflows within the Customer Application.

4. Rules of Interpretation

4.1 Gender and Number: References to any gender include all genders, and references to the singular include the plural and vice versa.

4.2 Inclusive Language: Any phrase introduced by the terms “including”, “include”, “in particular”, “for example”, or any similar expression shall be construed as illustrative and shall not limit the generality of the preceding words.

4.3 Legislative References: Except where expressly stated otherwise, references to any law, regulation, statute, code, or other legislative or regulatory enactment shall be deemed to include any amendments, modifications, re-enactments, or extensions thereof, as well as any subordinate legislation made thereunder, whether enacted before or after the date of this Agreement.

4.4 Headings: Headings are inserted for convenience only and shall not affect the interpretation or construction of this Agreement.

4.5 Days, Business Days, Months and Time Calculation:

  • 4.5.1 References to “days” shall mean calendar days, unless specifically stated as “business days”, in which case business days refer to days on which banks are generally open for business in the Czech Republic. In such case, if the time for performing an obligation falls on a non-business day, the time for performance shall be extended to the next business day.
  • 4.5.2 Unless specifically stated as “calendar month”, any reference to “month” shall mean the period starting on the day of the month the Subscription Term commences (the “anniversary date”) and ending on the day immediately preceding the same date in the following calendar month. If an anniversary date does not exist in a given month (e.g., the 31st), the month shall end on the last day of that calendar month.
  • 4.5.3 References to “calendar month” shall mean January, February, etc.

4.6 Precedence of Terms: In the event of any conflict or inconsistency between the Order, provisions of the main body of these Terms and those contained in any Appendix or referenced document, the precedence of the documents shall be:

  • 4.6.1 The Order;
  • 4.6.2 Body of these Terms;
  • 4.6.3 Schedules to these Terms;
  • 4.6.4 Any referenced document (e.g. Provider’s General Terms listed in Article 21.3).

4.7 References to Parties: References to a Party include that Party’s permitted assigns, successors, and authorized representatives.

5. SaaS Services and License

5.1 SaaS Services License Grant. During the Subscription Term, the Provider grants the Customer a non-exclusive, non-assignable, worldwide license to access and use the Software, including for the purpose of integrating and embedding its functionality into the Customer Application (“SaaS Services”).

5.2 Scope of Use. This license specifically authorizes the Customer to:

  • 5.2.1 Develop and Integrate: Utilize the Software (including APIs, SDKs and Redistributables) to build, manage, and execute automated workflows and data transmissions within the Customer Application.
  • 5.2.2 Embed UI Components: Display and operate the Software’s embedded user interface components (including automation builder, integration marketplace, and configuration dashboards) directly within the Customer Application, optionally under the Customer’s own branding (White-Label).
  • 5.2.3 Enable End Users: Permit End Users to access the integrated functionality within the Customer Application to configure, authorize, and manage their own integrations and automation workflows.

5.3 Distribution Rights. The Customer is authorized to distribute the Redistributables as part of the Customer Application to its End Users solely in compliance with this Agreement and in the manner described in the Documentation.

6. Delivery and Use of Redistributables

6.1 Means of Access. The Provider shall make the Redistributables available to the Customer through one or more of the following methods, at the Provider’s discretion:

  • 6.1.1 Secure Download: Via a dedicated developer portal or the administrative interface of the Software;
  • 6.1.2 Package Managers: Via public or private repositories (e.g., NPM, GitHub, or similar package management systems); or
  • 6.1.3 Content Delivery Network (CDN): Via direct links to hosted JavaScript files maintained by the Provider.

6.2 Updates and Maintenance. The Provider may, from time to time, release updates, bug fixes, or new versions of the Redistributables. The Customer is responsible for:

  • 6.2.1 Integrating the latest stable version of the Redistributables into the Customer Application within a reasonable timeframe, especially if the update is marked as critical for security or API compatibility;
  • 6.2.2 Ensuring that any modified Sample Code remains compatible with the current version of the SaaS Services.

6.3 Responsibility for Integration. The Customer acknowledges that the successful integration and deployment of the Redistributables within the Customer Application is the sole responsibility of the Customer. The Provider’s obligation is limited to providing the Redistributables and the Documentation.

6.4 Source Code: Notwithstanding Article 7.1, where the Provider delivers Redistributables or Sample Code in source code form, then during the Subscription Term:

  • 6.4.1 Authorized Use: The Customer is authorized to use, modify, and incorporate such source code solely for internal development purposes and for the purpose of integrating the Software into the Customer Application.
  • 6.4.2 Non-Compete: The Customer is strictly prohibited from using the source code (or any knowledge gained from it) to create, develop, or assist any third party in creating a product or service that is the same as, or substantially similar to, the Software or any of its Integration Components.
  • 6.4.3 Confidentiality: The Customer shall not provide, disclose, or make available the Source Code to any third party other than its Authorised Users who require access for the integration of the Customer Application.

6.5 Modifications to Source Code: Any modifications made by the Customer to the Source Code of Redistributables or Sample Code are made at the Customer’s own risk. While the Customer may own the specific modifications it creates, the underlying rights to the original Source Code remain with the Provider at all times.

7. SaaS Services General Terms

7.1 No Delivery of Software. The Customer acknowledges that, with the exception of the Redistributables, the Provider will not provide copies (in a form of object code, source code or intermediate code or otherwise) of the Software to Customer as a part of the SaaS Services. Access to the SaaS Services and the Software is exclusively through the API, UI or similar interface.

7.2 Access Grant. The Customer shall be deemed to have received the right to access and use the Software once the Provider has provided the Customer with access credentials for the agreed number of Authorised Users.

7.3 Additional User Access. Access credentials for initial number of Authorised Users shall be provided by the Provider to the Customer on the Effective Date. Access credentials for any additional Authorised Users can be created by the Customer at its discretion. The number of Authorised Users is not limited for the Customer. However, adding new Authorized Users may increase the Subscription Fee in accordance with the Price List.

7.4 Customer’s Responsibility. Customer shall be solely responsible for:

  • 7.4.1 the acts and omissions of its Authorised Users or any other personnel utilising the SaaS Services. The Provider shall not be liable for any loss or damage (incl. loss of data or functionality) caused directly or indirectly by such Authorised Users or any other personnel utilising the SaaS Services.
  • 7.4.2 the Customer Application and for ensuring that all End Users comply with the terms of this Agreement and the Documentation.

7.5 Software. The Customer has familiarised itself with the Software, its functionalities, parameters, and limitations. The Provider provides the Customer with only limited warranties concerning the Software as set forth in Article 13 of these Terms.

7.6 Documentation. During the Subscription Term, the Customer will have access to the Documentation made available to the public online, currently at docs.appmixer.com (which can be amended from time to time). The Provider reserves the right, at its sole discretion, to add, change, or otherwise modify the Documentation from time to time to reflect ongoing development or changes to the SaaS Services or the Software. The Provider will not provide the Customer with any Documentation (whether in written or electronic form) other than as set out in this Clause.

8. Service Level Agreement

8.1 The Service Level Agreement for the SaaS Services is set forth in Schedule No. 1 hereto. The SLA sets forth Customer’s sole remedies for availability or quality of the SaaS Services, including any failure to meet any guarantee set forth in the SLA.

9. Support and Maintenance Services

9.1 During the Subscription Term, the Provider shall provide to the Customer Support and Maintenance Services as set forth in separate Support and Maintenance Services Terms (see Article 21.3).

9.2 Fees for Support and Maintenance Services are included in the Subscription Fees and unless specifically agreed otherwise, the Provider will not charge the Customer any additional fees for the provision of Support and Maintenance Services.

10. Customer’s Obligations and Responsibilities

10.1 Customer shall not, and shall not permit anyone to:

  • 10.1.1 unless specifically authorised herein, copy or republish the SaaS Services or Software,
  • 10.1.2 make the SaaS Services available to any person other than Authorised Users,
  • 10.1.3 use or access the SaaS Services to provide service bureau, time-sharing or other similar services to third parties,
  • 10.1.4 remove, modify or obscure any copyright, trademark or other proprietary notices contained in the Software or in the Documentation,
  • 10.1.5 provide false identity information to gain access to or use the SaaS Services,
  • 10.1.6 access the SaaS Services or use the Software or Documentation in order to build a similar product or competitive product,
  • 10.1.7 use the SaaS Services, Software or Documentation in any way that causes, or may cause, damage to the SaaS Services, Software or the Host, or impairs the availability or accessibility of the SaaS Services,
  • 10.1.8 use the SaaS Services in any way that is unlawful, illegal, fraudulent or harmful.

10.2 Customer shall, in particular:

  • 10.2.1 notify the Provider immediately of any unauthorized use of any access credentials or any other known or suspected breach of security,
  • 10.2.2 report to the Provider immediately and use reasonable efforts to stop any unauthorized use of the SaaS Services that is known or suspected by the Customer,
  • 10.2.3 comply with requirements relating to intellectual property rights as set forth in Article 14 hereof.

11. Subscription Fee and Payment

11.1 Subscription Fee. As consideration for the SaaS Services and Support and Maintenance Services, the Customer shall pay the Provider the Subscription Fee. The Subscription Fee is either based on the Price List or specifically agreed by the Parties, as it is indicated in the Order.

11.2 Subscription Fee Structure. The Subscription Fee consists of two components:

  • 11.2.1 a Platform Fee (fixed fee for the selected tier of SaaS Services, e.g. Starter, Professional, Enterprise); and
  • 11.2.2 Usage-based Fees, being overage charges for (i) unique Users and/or (ii) Data Messages, both exceeding the included volume; Usage-based Fees are applicable to selected tiers of SaaS Services only (see Price List) and their amounts are set forth in the Price List or the Order.

11.3 The specific volume of Users and Data Messages included in the Platform Fee is set forth in the Price List and the Order. Usage exceeding these limits will be charged at the rates specified in the Price List or Order.

11.4 Payment and Invoicing.

  • 11.4.1 Platform Fees are payable by the Customer annually, semi-annually, quarterly or monthly in advance, before the commencement of each Subscription Term.
  • 11.4.2 Usage-based Fees are calculated at the end of each month of the Subscription Term based on the Provider’s monitoring and records of the Customer’s actual usage.
  • 11.4.3 Payment: The Customer hereby authorizes the Provider to automatically charge the Subscription Fee and any other fees due under this Agreement using the payment method provided by the Customer (e.g., credit card or direct debit). Such charges will be processed on or after the date of the relevant invoice. In the event that the Provider does not collect the payment automatically for any reason, the relevant invoice shall be payable by the Customer within fourteen (14) days from the date of its issuance via bank transfer or another method agreed upon by the Parties.
  • 11.4.4 Invoicing: The Provider shall issue invoices electronically.

All payments shall be made in the currency set forth in the Price List or the Order (typically USD or EUR) via credit card, bank transfer, or other payment methods supported by the Provider.

11.5 No Refund. Except as expressly provided otherwise, all fees are non-refundable.

11.6 VAT: All Subscription Fees are exclusive of VAT or applicable taxes.

11.7 Changes to the Price List. The Provider is entitled to unilaterally change the Price List. For existing Customers, any increase in the Platform Fee or to Usage-based Fee shall only take effect upon the commencement of the next (renewal) Subscription Term, provided the Provider notifies the Customer at least sixty (60) days in advance.

11.8 Suspension for Non-Payment. The Provider reserves the right to suspend the SaaS Services and/or Support and Maintenance Services if the Customer fails to pay any undisputed amounts due. However, the Provider may only exercise this right if:

  • 11.8.1 the payment is more than fifteen (15) days overdue; and
  • 11.8.2 the Provider has provided the Customer with at least ten (10) days’ prior written notice of its intent to suspend services.

Suspension shall not release the Customer from its obligation to pay all fees due for the Subscription Term. The Provider shall restore the SaaS Services promptly after the Customer has paid all overdue amounts, including any late interest. The Customer agrees that the Provider shall not be liable to the Customer or to any third party (including End Users) for any damages or losses arising from a suspension carried out in accordance with this Agreement.

12. Subscription Term and Termination

12.1 Term of Agreement. The term of the Agreement shall begin on the Effective Date and shall continue until (i) the expiry of the Subscription Term due to its non-renewal or (ii) until terminated by either party as outlined in this Section.

12.2 Subscription Term and its Renewal. Unless specifically agreed otherwise between the Parties, the Subscription Term shall automatically renew on a rolling basis unless either Party delivers written notice of non-renewal to the other party at least 30 calendar days prior to the expiration of the then-current Subscription Term.

12.3 Termination by Both Parties. Either party may terminate the Agreement immediately upon a material breach by the other party that has not been cured within ten (10) days after receipt of notice of such breach or if otherwise agreed in these Terms.

12.4 Termination by Customer. Provided that the Customer disagrees with the updated Terms pursuant to Article 21.1, it may terminate the Agreement prior to the effective date of the new Terms and such termination shall be effective as the effective date of the new Terms. If the Customer does not agree to the updated Terms, the Customer may terminate this Agreement by giving notice to the Provider at any time prior to the effective date of such updated Terms. The termination shall take effect on the date the updated Terms would otherwise have become effective.

12.5 Effect of Termination or Expiry of Subscription Term.

  • 12.5.1 Upon termination of the Agreement or expiration of the Subscription Term:
    • (a) the Provider shall immediately cease providing the SaaS Services and Support and Maintenance Services and all usage rights granted under these Terms and the Agreement shall terminate,
    • (b) except in the case of termination by the Provider for the Customer’s material breach (including non-payment), the Customer shall have a period of thirty (30) days (the “transition period”) to migrate End Users away from the Software. During this period, the license remains active solely for the purpose of maintaining existing End User workflows, but no new integrations or workflows may be created,
    • (c) after such transition period, the Customer shall immediately cease all use of the Software, including the removal of all Redistributables and Integration Components from the Customer Application.
  • 12.5.2 If the Provider terminates the Agreement due to a breach by the Customer, then the Customer shall pay to the Provider the Subscription Fee for the whole current Subscription Term (unless already paid) and all other amounts then due under these Terms and the Agreement.
  • 12.5.3 If the Customer terminates the Agreement due to a breach by the Provider, then the Provider shall repay to Customer on a pro-rated basis the already paid Subscription Fee for the current Subscription Term.

12.6 Surviving Provisions. Termination or expiration of the Agreement shall not affect claims for compensation for damage, late payment interest, contractual penalty and other provisions which (according to the expressed will of the parties or due to their nature) are to continue even after the termination of the Agreement. Provisions of Sections 14, 15, 16, and 18 shall also survive the expiration or termination of the Agreement for any reason.

13. Warranties and Limitations

13.1 Provider’s Warranties. The Provider represents and warrants that it will provide the SaaS Services in a professional manner consistent with general industry standards and that the SaaS Services will perform substantially in accordance with the Documentation.

13.2 Malicious Code Warranty. The Provider warrants that the SaaS Services and Redistributables, as delivered, do not contain any “back doors,” “viruses,” or other malicious code designed to disrupt or provide unauthorized access to the Customer Application or data.

13.3 Customer Security Responsibility. The Customer acknowledges that security is a shared responsibility. The Customer is responsible for:

  • 13.3.1 ensuring that its Authorised Users follow industry-standard security practices for web applications;
  • 13.3.2 implementing reasonable system-level measures to mitigate security risks (e.g., secure handling of API keys and tokens); and
  • 13.3.3 ensuring that any Customer modifications to Redistributables do not introduce security vulnerabilities.

13.4 Customer Responsibility for Workflow. Customer acknowledges that workflows are configured by Customer or End Users and executed automatically. Provider shall not be liable for any consequences arising from workflow configuration, including erroneous, unintended, or automated actions.

13.5 SaaS Services Performance. The Provider does not guarantee that the SaaS Services will be performed error-free, uninterrupted or completely secure, or that the Provider will correct all SaaS Services errors. The Customer acknowledges that the Provider does not control the transfer of data over communications facilities, including the internet, and that the SaaS Service may be subject to limitations, delays, and other problems inherent in the use of such communications facilities.

13.6 Disclaimer of Warranties. Except as expressly provided in this Agreement, the SaaS Services, the Software (incl. any Redistributables), and the Documentation are provided “as is” and “as available.” To the maximum extent permitted by law, the Provider and its suppliers disclaim all other warranties, whether express or implied, including the implied warranties of merchantability, fitness for a particular purpose, title, and non-infringement.

13.7 Responsibility for Customer Application or Customer’s Data. The Provider shall implement and maintain industry-standard technical and organizational measures designed to protect the Customer Application and Customer’s data against unauthorized access, loss, or destruction. Except to the extent directly caused by the Provider’s gross negligence, willful misconduct, or a material breach of its security obligations expressly set forth in this Agreement, the Provider and its service providers shall not be liable for the unauthorized alteration, theft, loss, or destruction of any Customer Application or Customer data. Notwithstanding the foregoing, the Provider shall have no liability for data loss or security breaches resulting from:

  • 13.7.1 the Customer’s (or its Users’) failure to maintain the confidentiality of login credentials;
  • 13.7.2 the Customer’s own configuration errors within the Software and Customer Application; or
  • 13.7.3 vulnerabilities in third-party software or hardware not provided by the Provider.

13.8 The Provider’s total liability for any data-related claim shall be subject to the limitation of liability set forth in this Agreement.

13.9 No Responsibility for Third Party Components. The Customer acknowledges that the availability and functionality of the SaaS Services are dependent on third-party APIs or other components. The Provider is not responsible for any changes, outages, or deprecations of features by third-party service providers or such third-party components. Provider does not warrant that any specific third-party component will remain available, compatible, or functional, and reserves the right to modify, suspend, or discontinue any Integration Component based thereupon.

13.10 Exclusive Remedy. For any breach of any warranty, Customer’s exclusive remedy shall be termination under Section 12 hereof and, where applicable, the receipt of a pro-rata refund of any pre-paid fees.

14. Intellectual Property Rights

14.1 Provider’s Rights. The Provider shall own all right, title and interest in and to the Software incl. Redistributables and Integration Components (but excluding any Customer modifications therein within the Customer Applications), SaaS Services, Documentation, including all modifications, improvements, upgrades, and derivative works thereto. For the avoidance of doubt, the Provider’s ownership includes the underlying code of any Redistributables, even if modified by the Customer as permitted herein.

14.2 White-Label. For avoidance of doubts, the Customer’s use of its own branding in the Customer Application (White-Labeling) shall not create any ownership interest for the Customer in the underlying Software.

14.3 Customer’s Rights. The Customer shall own all right, title and interest in and to the Customer Applications, however excluding any underlying Provider’s Software.

14.4 Custom Components and Workflows.

  • 14.4.1 Workflows: Any automation workflows or “flows” created by the Customer using the Software’s builder are the property of the Customer. However, the Customer’s right to execute these workflows is dependent on an active Subscription Term.
  • 14.4.2 Custom Connectors: If the Customer develops a custom connector using the Software’s features (e.g. SDK/CLI):
    • (a) the Customer owns the specific logic and code of that connector;
    • (b) the Provider retains ownership of the underlying feature (SDK/APIs etc.) used to build it.
  • 14.4.3 License to Provider: The Customer grants the Provider a non-exclusive, royalty-free, worldwide license to host, transmit, and execute the workflows and custom connectors solely as necessary to provide the SaaS Services during the Subscription Term.

14.5 Exchange Program (Public Contributions). If the Customer elects to submit, publish, or otherwise make available a workflow, connector, or any other feature or component to the Provider’s public library (the “Exchange Program”), the following terms apply:

  • 14.5.1 License Grant: The Customer grants the Provider a perpetual, irrevocable, worldwide, royalty-free, and sub-licensable license to use, host, store, reproduce, amend, modify, distribute, and make available such components to any third-party users of the SaaS Services.
  • 14.5.2 Customer Warranty: The Customer represents and warrants that it owns or has secured all necessary intellectual property rights and authorizations to contribute the component to the Exchange Program and that such contribution does not infringe the rights of any third party.
  • 14.5.3 No Obligation to Maintain: The Provider acts as a mere host for the Exchange Program. The Provider is under no obligation to maintain, support, or guarantee the functional performance of any component contributed by the Customer, and the Provider may remove any contributed component at its sole discretion without notice.
  • 14.5.4 Indemnity: The Customer shall indemnify and hold the Provider harmless against any third-party claims arising from a breach of the warranties set forth in this sub-clause.

15. Indemnification

15.1 Indemnification by the Provider. If a third party makes a claim against Customer that the SaaS Services or the Software infringe any patent, copyright or trademark, or misappropriate any trade secret, or infringe any other intellectual property right, the Provider shall defend the Customer against the claim at Provider’s expense and the Provider shall pay all losses, damages and expenses (including reasonable attorneys’ fees) finally awarded against the Customer or agreed to in a written settlement agreement signed by both parties, to the extent arising from the claim.

15.2 Exclusions. The Provider shall have no liability for any claim based on (a) the Customer’s Application or any components created or modified by the Customer, or (b) use of the SaaS Services or Software other than in accordance with the Documentation, these Terms and the Agreement.

15.3 Additional Remedies. In case of a third party’s claim, the Provider may also, at its sole option and expense,

  • 15.3.1 procure for Customer the right to continue use of the Software and SaaS Services, modify the Software or SaaS Services in a manner that does not materially impair the functionality, or
  • 15.3.2 terminate the Subscription Term and repay to Customer any amount paid by Customer with respect to the Subscription Term following the termination date.

15.4 Indemnification by the Customer. If a third party makes a claim against the Provider that the Customer’s Application or any components created or modified by the Customer infringe any patent, copyright or trademark, or misappropriates any trade secret, or infringes any other intellectual property right, Customer shall defend the Provider against such claim at Customer’s expense and Customer shall pay all losses, damages and expenses (including reasonable attorneys’ fees) finally awarded against the Provider or agreed to in a written settlement agreement signed by both parties, to the extent arising from the claim.

15.5 Conditions for Indemnification. A party seeking indemnification under this Section shall (a) promptly notify the other party of the claim, (b) give the other party sole control of the defense and settlement of the claim, and (c) provide, at the other party’s expense for out-of-pocket expenses, the assistance, information and authority reasonably requested by the other party in the defense and settlement of the claim.

16. Limitations of Liability

16.1 Limitations of Liability. To the maximum extent permitted by applicable law, the total aggregate liability of either Party to the other for all claims arising out of or related to this Agreement (whether in contract, tort, or otherwise) shall not exceed the total amount of Subscription Fees paid by the Customer to the Provider during the twelve (12) months immediately preceding the event giving rise to the claim.

16.2 Exclusion of Liability. To the fullest extent permitted by law, neither Party shall be liable to the other for any lost profits, loss of revenue, loss of data, loss of goodwill, business interruption, or for any consequential, incidental, special, punitive, or indirect damages, even if such damages were foreseeable, known, or the Party was advised of the possibility of such damages.

16.3 Exceptions. The foregoing limitations and exclusions of liability shall not apply (i) to any damages caused intentionally or due to gross negligence by either party and (ii) to any obligations (or any breach thereof) under Section 15 (Indemnification).

17. Personal Data

17.1 Personal data are subject to separate Privacy Policy (see Article 21.3).

18. Confidentiality

18.1 Definition of Confidential Information. “Confidential Information” means all non-public information disclosed by one Party (“Disclosing Party”) to the other Party (“Receiving Party”), whether orally or in writing, that is designated as confidential or that reasonably should be understood to be confidential given the nature of the information and the circumstances of disclosure.

  • 18.1.1 Provider Confidential Information includes the Software, Source Code, pricing, and security reports.
  • 18.1.2 Customer Confidential Information includes the Customer Application (non-public parts), Customer data, and the specific logic of Custom Connectors and Workflows.

Notwithstanding the foregoing, Confidential Information shall not include any workflows, connectors, or other components that the Customer voluntarily elects to share or publish via the Exchange Program.

18.2 Protection of Confidential Information. The Receiving Party shall:

  • 18.2.1 use the same degree of care that it uses to protect the confidentiality of its own confidential information of like kind (but in no event less than reasonable care);
  • 18.2.2 not use any Confidential Information of the Disclosing Party for any purpose outside the scope of this Agreement; and
  • 18.2.3 limit access to Confidential Information to those of its employees, contractors, and advisors who need such access for purposes consistent with this Agreement and who have signed confidentiality agreements with the Receiving Party containing protections no less stringent than those herein.

18.3 Exceptions. Confidential Information shall not include any information that:

  • 18.3.1 is or becomes generally known to the public without breach of any obligation owed to the Disclosing Party;
  • 18.3.2 was known to the Receiving Party prior to its disclosure by the Disclosing Party without breach of any obligation owed to the Disclosing Party;
  • 18.3.3 is received from a third party without breach of any obligation owed to the Disclosing Party;
  • 18.3.4 is expressly designated by the Customer as non-confidential or is voluntarily contributed by the Customer to the Exchange Program or any similar public repository within the Software; or
  • 18.3.5 was independently developed by the Receiving Party without use of or reference to the Disclosing Party’s Confidential Information.

18.4 Compelled Disclosure. The Receiving Party may disclose Confidential Information of the Disclosing Party if it is compelled by law to do so, provided the Receiving Party gives the Disclosing Party prior notice of such compelled disclosure (to the extent legally permitted) and reasonable assistance, at the Disclosing Party’s cost, if the Disclosing Party wishes to contest the disclosure.

18.5 Provider’s PR: Notwithstanding the confidentiality obligations set forth in this Agreement, the Provider shall be entitled to reference the cooperation with the Customer for public relations (PR) and marketing purposes, provided that no confidential terms or content of this Agreement are disclosed. In connection with such references, the Provider may:

  • 18.5.1 use the Customer’s name, the name of the project, the Customer’s logos, and trademarks, solely in a factual and non-disparaging manner; and
  • 18.5.2 provide a basic description of the cooperation under this Agreement in marketing materials, case studies, presentations, or websites.

19. Assignment

19.1 Customer’s Assignment. The Customer may not assign this Agreement, in whole or in part, without the prior written consent of the Provider. Notwithstanding the foregoing, the Customer may assign this Agreement without consent to a successor in connection with a merger, acquisition, or sale of all or substantially all of its assets, provided that:

  • 19.1.1 the successor agrees in writing to be bound by all terms of this Agreement; and
  • 19.1.2 the Customer provides the Provider with written notice within thirty (30) days of the assignment.

19.2 Provider’s Assignment. The Provider may freely assign this Agreement or any of its rights and obligations hereunder to any third party.

19.3 Binding Effect. This Agreement shall be binding upon and inure to the benefit of the Parties and their respective permitted successors and assigns.

20. Governing Law and Venue of Dispute Resolution

20.1 These Terms and the Agreement shall be governed by the laws of the Czech Republic, including the Czech Civil Code. The Parties hereby submit to the exclusive jurisdiction of the Czech courts and the Municipality Court of Prague shall have the jurisdiction to hear all disputes arising therefrom.

21. Final Provisions

21.1 Modifications. The Provider reserves the right to revise or modify these Terms periodically. In such instances, the Provider will provide notice to the Customer regarding the availability of new versions of the Terms at least 30 days prior to their effective date. It is the Customer’s responsibility to review and become familiar with these updated Terms. Once timely notified, the new versions of the Terms will become binding and effective for the Customer on its effective date. Provided that the Customer disagrees with the updated Terms, it shall have the right to terminate the Agreement pursuant to Article 12.4.

21.2 No Prevailing Customer’s General Terms. No Customer’s terms and conditions shall apply to the mutual relationship between Customer and the Provider under this Agreement.

21.3 Provider’s General Terms. The following Provider’s general terms and conditions shall apply to mutual relationship between Customer and the Provider under this Agreement:

  • 21.3.1 Privacy Policy. Available at the internet address (URL): [_________________]
  • 21.3.2 Support and Maintenance Services Terms. Available at the internet address (URL): [_________________]

21.4 No Custom Usage. The Parties do not wish that any rights and obligations be inferred beyond the scope of the explicit provisions of these Terms from any customs used in general or in the sector relating to the subject thereof, unless these Terms explicitly stipulate otherwise.

21.5 Set-off. Set-off of claims arising from these Terms and the Agreement shall not be permitted unless agreed in writing.

21.6 Force Majeure. Each party will be excused from performance for any period during which, and to the extent that, such party or any subcontractor is prevented from performing any obligation or SaaS Service, in whole or in part, as a result of causes beyond its reasonable control, and without its fault or negligence, including without limitation, acts of God, strikes, lockouts, riots, acts of terrorism or war, epidemics, communication line failures, and power failures and extraordinary, unforeseeable and insurmountable obstacles arising independently of the party’s will (as stipulated in sec. 2913 of the Czech Civil Code). In the event of any such cause, the affected Party’s time for delivery or other performance will be extended for a period equal to the duration of the delay caused thereby plus 5 (in words: five) business days.

21.7 Complete Agreement and Applicable Documents. These Terms (along with all Schedules hereto and any other documents, provisions, and policies referenced herein) constitute the entire agreement between the parties regarding its subject matter and supersede any prior agreements, understandings, or arrangements, whether oral or written. The Customer represents that it has had the opportunity to consult with its legal counsel regarding these Terms and shall not consider itself to be the weaker party.

21.8 Effectiveness of the Terms and the Agreement. These Terms and the Agreement become binding and effective to the Parties on the Effective Date.

21.9 Severability. If any provision of these Terms or the Agreement is held to be invalid or unenforceable, that provision shall be reformed to achieve as nearly as possible the same effect as the original one, and the remainder of these Terms and the Agreement shall remain in full force.

Schedule No. 1 — Service Level Agreement

1. Uptime. The Customer acknowledges that the SaaS Services are provided on an “as is” and “as available” basis and that the Provider does not guarantee that access will be entirely uninterrupted or error-free. However, the Provider shall use commercially reasonable efforts to ensure the SaaS Services achieve System Availability (as defined below) of at least 99.9% during each month of the Subscription Term.

2. “System Availability” means the number of minutes in a particular month of the Subscription Term that the key components of the SaaS Services are operational, as a percentage of the total number of minutes in such month. System Availability calculations shall exclude downtime (excused downtime) resulting from:

  • 2.1 Scheduled maintenance for which notice was provided;
  • 2.2 Any suspension of Service the Provider deems necessary to prevent an imminent security threat or to protect the integrity of the Software, Customer Application or Customer’s data;
  • 2.3 Any computer, communications, internet service, or hosting facility failures (including outages of the provider of the Host);
  • 2.4 Events of Force Majeure;
  • 2.5 Malicious attacks on the system (e.g., DDoS attacks);
  • 2.6 Issues associated with the Customer’s computing devices, local area networks, or internet service provider connections;
  • 2.7 Inability to deliver services because of acts or omissions of the Customer, End User or any Authorised User; or
  • 2.8 Third-party API or other components outages or deprecations.

3. Scheduled Maintenance. The Provider reserves the right to take the SaaS Services offline for scheduled maintenance. The Provider shall provide the Customer with reasonable prior notice (typically via email or the Provider’s status page).

4. Remedies. If the Provider fails to meet System Availability in a particular month, the Customer may, as its sole and exclusive remedy, request a service credit:

  • 4.1 Request Process: The Customer must submit a written request within fifteen (15) days after the end of the affected month.
  • 4.2 Credit Amount: The Provider will issue a credit against the Customer’s next invoice equal to 1% of the monthly Platform Fee for each full 1% of System Availability loss below the agreed uptime threshold.
  • 4.3 Maximum Cap: Total credits in any single month shall not exceed the Platform Fee paid for that month.