These terms govern how MergeLabs GmbH provides the Cothena platform to its clients. A client signs a short order form that names the event or subscription, the fees and any special terms, and refers to these terms and the Data Processing Addendum by version.
1. Scope and contract structure
1.1 This Master Services Agreement (“MSA”) governs the provision of the Cothena event operations platform and related services by MergeLabs GmbH (“MergeLabs”), whose address and register details are on the imprint, to the client named in an order form (the “Client”). MergeLabs and the Client are each a “Party”.
1.2 A contract is formed when both Parties sign an order form that refers to this MSA. Each order form, together with this MSA and the documents listed in section 1.3, forms a separate contract (an “Agreement”).
1.3 The following documents form part of each Agreement. If they conflict, they apply in this order:
- (a) the order form, but only where it expressly identifies a term as deviating from this MSA or the DPA (“Special Terms”);
- (b) the Cothena Data Processing Addendum (“DPA”), for everything concerning the processing of personal data, together with its annexes, Cothena Security Measures and Cothena Subprocessors;
- (c) Schedule 1 (Service levels) of this MSA;
- (d) this MSA;
- (e) the Documentation.
1.4 Cothena is offered only to clients acting in the course of their trade, business, profession or organisational activities, including non-profit organisations and public bodies. It is not offered to consumers within the meaning of section 13 of the German Civil Code (Bürgerliches Gesetzbuch, “BGB”).
1.5 The Client’s own general terms and conditions, including terms printed on purchase orders, do not apply, even if MergeLabs does not object to them or performs without reservation. A purchase order number may be shown on invoices for administrative purposes only.
1.6 MergeLabs publishes this MSA and the DPA as dated, versioned documents. Each order form names the version that applies to it. A later version applies to an existing Agreement only if both Parties sign a new order form or agree to it in text form.
2. Definitions
Access Period: for a Single Event Order Form, the period during which the Client may use the Platform, as stated in the order form, including any grace period.
Assist: Cothena Assist, the optional AI assistant in the Platform.
Authorised Users: the employees, volunteers, contractors, agencies and other individuals whom the Client allows to use the Services on its behalf.
Business Day: Monday to Friday, except public holidays in the German state of Baden-Württemberg.
Client Data: all data, content and materials, including personal data, that the Client or its Authorised Users upload to, enter into or generate through the Services, including inputs to and outputs from Assist.
Documentation: the API documentation, the MCP server’s tool descriptions and any user guides MergeLabs provides in the Platform, in their current version. Marketing materials and the website are not Documentation.
Effective Date: the date of the last signature on an order form, unless the order form states otherwise.
Event Days: the days of a live event stated in an order form.
Fees: the fees stated in an order form and any additional fees agreed under this MSA.
Platform: the Cothena event operations platform provided as software as a service, consisting of the Management Panel, Cothena Management (the staff app), the documented REST API, the MCP server (Model Context Protocol) and Assist, together with the modules selected under section 3.3.
Professional Services: onboarding beyond the scope stated in an order form, customisation, configuration, data migration, integration work, bespoke development, enhanced support and on-site support.
Services: the Platform, standard support, the onboarding stated in the order form, and any Professional Services agreed under section 9.
Single Event Order Form: an order form for the use of the Platform for one or more named events against a one-time Fee.
Subscription Order Form: an order form for the use of the Platform for a fixed term against recurring or periodic Fees.
Term: the Access Period or the term of a Subscription Order Form, as applicable.
3. The Platform
3.1 Provision. MergeLabs makes the Platform available to the Client over the internet for the Term, with the functionality described in the Documentation and the order form. MergeLabs’ obligation ends at the point where its hosting environment connects to the public internet. The Client is responsible for its own internet connection, devices, and supported browsers and operating systems.
3.2 Right of use. MergeLabs grants the Client, for the Term, a non-exclusive, non-transferable and non-sublicensable right to use the Platform and the Documentation for its own organisational purposes and, under a Single Event Order Form, for the events named in it. The Client may authorise the number of Authorised Users stated in the order form, or unlimited Authorised Users where it says so. The Client is responsible for the acts and omissions of its Authorised Users as for its own.
3.3 Modules. The Management Panel, Cothena Management, the REST API, the MCP server and Assist are included in every Agreement. The following modules are included only where the order form selects them:
- (a) Bookings and payments (the Registration add-on on the price list): booking pages, booking management and checkout. Payments are processed by the Client’s own payment provider under the Client’s contract with that provider.
- (b) Cothena App: the guest app for event participants.
3.4 Allowances. The order form may set allowances, for example for events, venues, spaces, schedules, users, Assist usage or API usage. MergeLabs may set technical limits that are reasonable for the agreed use.
3.5 Restrictions. The Client will not, and will not allow others to:
- (a) sell, resell, rent or otherwise make the Services available to anyone other than Authorised Users;
- (b) decompile, disassemble or reverse engineer the software, except as mandatory law allows (in particular sections 69d and 69e of the German Copyright Act);
- (c) remove proprietary notices;
- (d) circumvent security measures or usage limits;
- (e) carry out load or penetration tests without MergeLabs’ prior consent in text form;
- (f) upload malicious code or unlawful content; or
- (g) use the Services in breach of applicable law, including sanctions and export control law.
3.6 Changes to the Platform. MergeLabs may develop and change the Platform, including its user interface and technical environment, provided that the functionality agreed in the order form is not materially reduced and the change is reasonable for the Client. If a change materially and adversely affects the Client’s agreed use, MergeLabs notifies the Client by email under section 21.1 at least 30 days in advance, or as soon as possible where the change is needed for security or legal reasons. The Client may then terminate the affected order form with effect from the date the change takes effect, and MergeLabs refunds prepaid Fees for the period after termination pro rata.
3.7 Third-party components. The Platform includes open-source and other third-party components. Their licence terms apply where they are mandatory. They do not restrict the Client’s rights under this MSA.
3.8 Temporary suspension. MergeLabs may temporarily suspend access to the Services, in whole or in part, where this is necessary because:
- (a) MergeLabs reasonably suspects that an account or credentials have been compromised;
- (b) the Client’s use poses a material security risk to the Platform or to other clients;
- (c) the Client’s use materially breaches section 3.5 or section 6.7; or
- (d) the Client is in default of payment under section 10.5.
MergeLabs notifies the Client promptly, limits the suspension to what is necessary and restores access once the cause has been resolved. The Client’s payment obligations continue during any suspension caused by circumstances for which the Client is responsible.
4. Availability
The availability MergeLabs aims for, and how it is measured, are set out in Schedule 1 (Service levels).
5. Support
5.1 Standard support. Standard support is included for the Term. MergeLabs handles support requests sent by email to [email protected] from 09:00 to 21:00 German time (CET/CEST) on Business Days, according to their urgency.
5.2 Other channels. An order form may add other support channels or hours. Where it adds channels such as WhatsApp, they are for logistics only, such as scheduling, quick questions and status updates. The Client will not send personal data of third parties, credentials or confidential event content through them, and will use email instead.
5.3 Enhanced and on-site support. The Parties may agree in text form on extended support before or during an event. Enhanced support and on-site support are Professional Services under section 9.
6. Cothena Assist and AI
6.1 Optional feature. Assist is optional. The Platform’s core workflows can be used without it. Which Authorised Users may use Assist, and who may approve its changes, is set by their roles.
6.2 AI models. Assist uses AI models from the provider named in Cothena Subprocessors. MergeLabs may change the models or provider under the subprocessor procedure in the DPA. How Assist data is handled, including that it is not used to train AI models, is set out in the DPA.
6.3 Usage allowance. The order form may include an Assist usage allowance. Once it is used up, MergeLabs may pause Assist until the Parties agree on further usage in text form, at a rate MergeLabs states before use. Discounts in the order form do not apply to further usage unless the order form says so.
6.4 Nature of AI output. Assist generates outputs automatically using probabilistic models. Outputs may be inaccurate, incomplete or unsuitable for the Client’s purpose. The agreed quality of Assist is that it works as described in the Documentation; it does not extend to the factual correctness, completeness or fitness of any individual output. The Client reviews outputs before relying on them, in particular before decisions that affect safety, legal compliance, finances or individuals, and before sharing them with event participants or other third parties.
6.5 Rights in outputs. As between the Parties, the Client holds whatever rights exist in the Assist outputs generated for it. MergeLabs does not promise that outputs are protected by intellectual property rights or unique to the Client.
6.6 Client-selected models. The Client may connect an external AI model or agent of its choice to the Platform through the MCP server or the REST API. The Client then chooses the provider, grants the access permissions and is responsible for that provider’s terms, charges and processing of Client Data. Such a provider is neither a subcontractor nor a subprocessor of MergeLabs, and MergeLabs is not responsible for its availability, performance or outputs.
6.7 Acceptable use of AI. The Client will not use Assist or the Platform’s AI features:
- (a) for practices prohibited under Regulation (EU) 2024/1689 (the “AI Act”);
- (b) to make or materially inform decisions on the recruitment, promotion, termination, performance evaluation or monitoring of workers, or to allocate tasks based on individual behaviour, personal traits or characteristics; or
- (c) for any other purpose that would make Assist a high-risk AI system under the AI Act.
The Client remains responsible for ensuring that its Authorised Users who use AI features have a sufficient level of AI literacy.
7. API and MCP access
7.1 Access to the documented REST API and the MCP server is included, subject to the Documentation and any rate limits stated in it or in the order form.
7.2 The Client keeps API keys and access tokens confidential and is responsible for all use made of them.
7.3 MergeLabs announces changes to the REST API or the MCP server that are not backward-compatible by email under section 21.1 at least 30 days in advance, except where an earlier change is needed for security or legal reasons.
7.4 Integration planning or implementation beyond the onboarding stated in the order form is a Professional Service.
8. Client responsibilities
8.1 The Client:
- (a) manages its Authorised Users, their roles and their credentials;
- (b) keeps credentials confidential and promptly reports suspected unauthorised access;
- (c) enters, checks and maintains its event content and schedules in the Platform;
- (d) provides the information and cooperation MergeLabs reasonably needs to perform the Services; and
- (e) reports material faults under section 12.2.
8.2 The Client confirms that it has the rights and permissions needed to upload Client Data and to authorise MergeLabs to process it for the Services, and that Client Data does not infringe third-party rights or applicable law.
8.3 Special categories of personal data (Art. 9 GDPR) may be entered only as the DPA allows.
8.4 Services the Client connects under its own contract, such as its email provider, its payment provider, its Google Cloud account for push notifications or an AI provider connected through MCP, are provided by those third parties. The Client is responsible for its contracts with them, and MergeLabs is not responsible for their availability or performance.
9. Onboarding and Professional Services
9.1 Onboarding. MergeLabs provides the onboarding and training stated in the order form.
9.2 Separate scope required. Professional Services require a separate written statement of work or order form that sets out scope, assumptions, timeline and fees before work begins.
9.3 Nature of the services. Unless the statement of work expressly defines a work result subject to acceptance, Professional Services are services (Dienstleistungen, section 611 BGB). MergeLabs owes performance with reasonable skill and care, not a particular result.
9.4 Fees and expenses. Unless the statement of work states a fixed fee, Professional Services are charged on a time-and-materials basis at the rates stated in it. Reasonable travel and accommodation costs for on-site work are charged at cost, subject to the Client’s prior approval in text form.
9.5 Results. Generic developments, improvements and features that MergeLabs creates, including those suggested by or made for the Client, become part of the Platform. MergeLabs holds all rights in them, and the Client may use them under section 3.2. Rights in Client-specific deliverables are governed by the statement of work.
9.6 Changes. Either Party may request a change to a statement of work. A change is binding only when agreed in text form, including its effect on fees and timeline.
10. Fees and payment
10.1 Fees. The Client pays the Fees stated in the order form. Fees are in the currency stated in the order form and exclude value added tax and other applicable taxes.
10.2 Invoicing. Unless the order form states otherwise:
- (a) one-time Fees under a Single Event Order Form are invoiced on the Effective Date;
- (b) Fees under a Subscription Order Form are invoiced in advance at the start of the Term; and
- (c) additional Assist usage, Professional Services and expenses are invoiced monthly in arrears.
10.3 Payment. Invoices are payable by bank transfer within 14 calendar days of the invoice date, without deduction.
10.4 Taxes. The Client pays value added tax or similar tax at the statutory rate. Where the reverse-charge procedure applies, the Client provides its VAT identification number or equivalent proof of business status.
10.5 Default. If the Client is in default of payment, MergeLabs may claim statutory default interest and the statutory lump sum under section 288 BGB. If an undisputed amount remains unpaid more than 14 days after a reminder in text form that announces the suspension, MergeLabs may suspend access to the Services under section 3.8(d) until payment is received.
10.6 Set-off and retention. The Client may set off only claims that are undisputed, have been finally determined by a court, are ready for decision, or arise from the same contractual relationship. The same applies to rights of retention.
11. Term and termination
11.1 This MSA. This MSA applies to each Agreement for as long as the order form remains in force.
11.2 Single Event Order Forms. A Single Event Order Form runs for the Access Period stated in it and ends automatically when the Access Period expires. Ordinary termination (ordentliche Kündigung) during the Access Period is excluded, without affecting sections 11.4 and 11.5.
11.3 Subscription Order Forms. A Subscription Order Form runs for the Term stated in it, or 12 months from the Effective Date if it states none, and ends when the Term expires. It does not renew automatically. The Parties continue by signing a new order form.
11.4 Switching providers (EU Data Act).
- (a) The Client may at any time give notice that it wishes to switch to another provider of data processing services, to move its data to its own infrastructure, or to have its exportable data erased. The notice period is two months.
- (b) After the notice period, a transition period of up to 30 calendar days begins. During it, MergeLabs provides reasonable assistance, acts with due care to maintain business continuity, informs the Client of known risks to continuity and maintains a high level of security. If the switch is technically unfeasible within that period, MergeLabs informs the Client within 14 Business Days of the notice and may extend the transition period to no more than seven months. The Client may extend the transition period once, by a period it considers more appropriate.
- (c) Exportable data is the Client Data and the other input and output data, including metadata, generated through the Client’s use of the Services, excluding MergeLabs’ intellectual property and trade secrets and data relating only to the internal functioning of the Platform. MergeLabs makes exportable data available in structured, commonly used and machine-readable formats through the Platform’s export features, the REST API and the MCP server, as described in the Documentation. Data that these do not cover is provided by MergeLabs on request in a machine-readable format.
- (d) The retrieval period under section 11.7 runs for at least 30 calendar days after the end of the transition period. MergeLabs then erases the exportable data under the DPA.
- (e) MergeLabs charges no switching or data egress fees.
- (f) The Agreement ends when the switch is completed or, where the Client only asks for erasure, at the end of the notice period. Fees accrued up to that date remain payable. Fees paid in advance for the Term are not refunded.
11.5 Termination for cause. Either Party may terminate an order form for cause (aus wichtigem Grund), in particular if the other Party materially breaches the Agreement and does not remedy the breach within 30 days of notice in text form. Cause for MergeLabs includes the Client’s default in paying an amount equal to at least two months’ Fees, or a one-time Fee, for more than 30 days after a reminder in text form. Statutory rights to terminate for cause remain unaffected.
11.6 Form. Notices of termination must be given in text form (Textform, section 126b BGB) to the contact named in the order form.
11.7 After the end. When an Agreement ends, the Client’s right of use ends. For 30 days afterwards the Client may still use the export features, the REST API and the MCP server to retrieve its data, as set out in the DPA; MergeLabs then deletes the data under the DPA. MergeLabs may keep the Client’s organisation and its settings, which contain no personal data, so that the Client can return later, unless the Client asks for them to be deleted as well. Accrued payment obligations and sections 8.2, 10, 12, 13, 14, 15, 16, 21, 22 and 23 survive, as do other provisions which by their nature are meant to survive.
12. Performance and defects
12.1 Agreed quality. MergeLabs provides the Platform with the functionality described in the Documentation and the order form, and performs its services with reasonable skill and care. Minor deviations that do not materially affect the agreed use are not defects.
12.2 Fault reports. The Client reports material faults in text form without undue delay, with a description that allows the fault to be reproduced, and provides the information reasonably needed to diagnose it.
12.3 Remedy. MergeLabs investigates and remedies reproducible material faults within a reasonable time, taking account of their urgency. MergeLabs may remedy a fault with a workaround where this does not unreasonably impair the Client’s use.
12.4 No liability without fault for initial defects. MergeLabs’ strict liability for defects that already existed when the Agreement was concluded (section 536a(1), first alternative, BGB) is excluded. Liability for fault is governed by section 13.
12.5 No deductions. The Client may not reduce Fees by deducting amounts from invoices. Its right to reclaim Fees paid in excess, under the rules on unjust enrichment, remains unaffected.
12.6 Termination for failure to provide use. The Client may terminate for failure to provide use (section 543(2), sentence 1, no. 1 BGB) only after MergeLabs has had a reasonable opportunity to remedy the fault and the remedy has failed.
12.7 Limitation period. Claims for defects become time-barred 12 months after the statutory limitation period begins. This does not apply to claims under section 13.1.
12.8 Third-party intellectual property rights.
- (a) If a third party claims that the Client’s contractual use of the Platform infringes its intellectual property rights, MergeLabs defends the Client against the claim at its own expense and holds the Client harmless from damages and costs finally awarded or agreed in a settlement MergeLabs has approved.
- (b) This applies only if the Client tells MergeLabs about the claim without undue delay, does not acknowledge it, and leaves the defence and any settlement negotiations to MergeLabs, with the Client’s reasonable cooperation at MergeLabs’ cost.
- (c) If an infringement is established or likely, MergeLabs may, at its option and cost, obtain the necessary rights, or modify or replace the affected part of the Platform without materially reducing the agreed functionality. If neither is possible on reasonable terms, either Party may terminate the affected order form, and MergeLabs refunds prepaid Fees for the period after termination.
- (d) This section 12.8 does not apply where the claim results from Client Data (other than unmodified Assist outputs), from use in breach of the Agreement, or from combination with products MergeLabs did not provide.
- (e) The Client holds MergeLabs harmless, on the same conditions, against third-party claims arising from Client Data (other than unmodified Assist outputs) or from use of the Services in breach of the Agreement.
- (f) Claims for damages under this section 12.8 are subject to section 13.
13. Liability
13.1 Unlimited liability. Each Party is liable without limitation:
- (a) for intent and gross negligence (Vorsatz und grobe Fahrlässigkeit);
- (b) for injury to life, body or health;
- (c) under a guarantee expressly given in writing;
- (d) for fraudulently concealing a defect;
- (e) under the German Product Liability Act (Produkthaftungsgesetz); and
- (f) where liability is otherwise mandatory by law.
13.2 Ordinary negligence. For ordinary negligence (leichte Fahrlässigkeit), each Party is liable only for breach of a material contractual obligation: an obligation whose fulfilment is essential for the proper performance of the Agreement and on which the other Party regularly relies and may rely (Kardinalpflicht). In that case, liability is limited to the damage that is foreseeable and typical for this kind of contract. Otherwise, liability for ordinary negligence is excluded.
13.3 Amount. Where an order form states an individually agreed maximum amount for liability under section 13.2, that amount applies to all claims under that order form together.
13.4 Fees. Sections 13.2 and 13.3 do not limit the Client’s obligation to pay the Fees.
13.5 Persons. The limitations in this section 13 also apply to the personal liability of each Party’s legal representatives, employees and agents (Erfüllungsgehilfen).
13.6 Burden of proof. This section 13 does not change the statutory burden of proof.
14. Ownership and usage data
14.1 The Client keeps all rights in Client Data. It grants MergeLabs the non-exclusive right, limited to the Term and the retrieval and deletion periods, to use Client Data as far as needed to provide the Services.
14.2 MergeLabs and its licensors keep all rights in the Platform, the Documentation and any improvements to them. No rights are granted except as this MSA expressly states.
14.3 MergeLabs may record technical data about the use of the Services (“Usage Data”), for example Assist usage, and use it only to operate, secure and bill the Services. Usage Data that relates to identifiable individuals is used only in line with the DPA and the privacy policy. MergeLabs does not share Usage Data with third parties other than its subprocessors in a form that identifies the Client or any individual.
14.4 If the Client gives suggestions or feedback about the Services, MergeLabs may use them without restriction or payment, and will not name the Client as their source without consent.
15. Confidentiality
15.1 “Confidential Information” means all information a Party discloses that is marked as confidential or should reasonably be understood to be confidential, including Client Data, the terms of the Agreement, pricing, and technical and business information.
15.2 The receiving Party uses Confidential Information only for the Agreement and protects it with at least reasonable care. It shares it only with its personnel, subprocessors, subcontractors and professional advisers who need to know it and are bound by confidentiality obligations at least as protective as this section 15.
15.3 These obligations do not apply to information that is or becomes public without a breach of the Agreement, was already lawfully known to the receiving Party, is independently developed, or is lawfully received from a third party without a confidentiality obligation.
15.4 If the law, a court or an authority requires disclosure, the receiving Party gives prior notice where lawful and discloses only what is required.
15.5 These obligations continue for three years after the end of the last Agreement, and for trade secrets for as long as they remain trade secrets under the German Trade Secrets Act (Geschäftsgeheimnisgesetz). After the end of the Agreement, the receiving Party returns or deletes Confidential Information on request, except where the law requires it to be kept. Client Data is deleted under the DPA.
16. Data protection
16.1 Where MergeLabs processes personal data on the Client’s behalf, the DPA applies.
16.2 Where each Party processes personal data as a controller, in particular contact details of the other Party’s staff for contract administration and billing, each Party is responsible for its own compliance with data protection law. MergeLabs’ privacy policy describes its own processing.
17. Publicity
17.1 Neither Party may use the other Party’s name, logo or trademarks publicly without prior consent in text form, unless the order form provides otherwise.
17.2 Any reference an order form permits must be factually accurate, respect confidentiality and not imply endorsement beyond the client relationship.
18. Force majeure
18.1 Neither Party is liable for failure or delay in performance caused by circumstances beyond its reasonable control, such as natural disasters, epidemics, war, terrorism, government action, strikes at third parties, or failures of public networks or energy supply. This does not apply to payment obligations.
18.2 The affected Party informs the other Party promptly and takes reasonable steps to limit the disruption. Affected obligations are suspended only for as long as the impediment lasts. If it lasts longer than 60 days, either Party may terminate the affected order form. Changes to an event, such as postponement, substitution or cancellation, are governed by the order form.
19. Subcontractors
MergeLabs may use subcontractors to perform the Services and remains responsible for them as for its own performance. The use of subprocessors is governed by the DPA.
20. Assignment
20.1 Neither Party may assign or transfer the Agreement or rights under it without the other Party’s prior consent in text form, which may not be unreasonably withheld. Section 354a of the German Commercial Code (Handelsgesetzbuch) remains unaffected.
20.2 MergeLabs may transfer the Agreement as a whole, without consent, to an affiliated company or to a successor in a merger, reorganisation or sale of all or substantially all of the business or assets relating to Cothena. MergeLabs notifies the Client in text form. If the transfer is unreasonable for the Client, the Client may terminate the affected order form within 30 days of the notice.
21. Notices
21.1 Notices under the Agreement may be given by email to the contacts named in the order form, or to a replacement contact notified in text form.
21.2 The Parties may agree or give notice of routine matters by email, such as training dates, event substitution within the Term, publicity approvals and notices about subprocessor changes.
22. Governing law and jurisdiction
22.1 The Agreement is governed by the laws of the Federal Republic of Germany. The United Nations Convention on Contracts for the International Sale of Goods (CISG) and the conflict-of-law rules of private international law do not apply.
22.2 To the extent the law allows, the courts competent for MergeLabs’ registered office have exclusive jurisdiction over all disputes arising out of or in connection with the Agreement. MergeLabs may also bring proceedings where the Client has its general place of jurisdiction.
23. Final provisions
23.1 Entire agreement. The Agreement records the Parties’ entire agreement on its subject and supersedes earlier proposals and quotes, unless the order form refers to them.
23.2 Amendments. Amendments to an order form, including changes to scope, Fees or Term, require a written amendment or a new order form signed by authorised representatives of both Parties, except where this MSA allows agreement in text form. Electronic signatures are sufficient. Individually agreed terms take precedence (section 305b BGB).
23.3 Language. The Agreement is made in English. Where a German legal term is given in brackets, it determines the meaning of the English term.
23.4 Severability. If a provision of the Agreement is or becomes invalid or unenforceable, the remaining provisions remain unaffected. The Parties will replace the invalid provision with a valid one that comes as close as possible to their economic intention.
23.5 Signatures. Order forms may be signed in counterparts and by electronic signature.
Schedule 1: Service levels
S1.1 Availability target. MergeLabs aims for 99.5% monthly availability of the production Platform: the Management Panel, the booking pages where the module is selected, the REST API and the MCP server. Availability is measured at the point where MergeLabs’ hosting environment connects to the public internet.
S1.2 Exclusions. Unavailability does not count against the target where it results from:
- (a) planned or emergency maintenance;
- (b) the Client, its Authorised Users or services the Client connects under its own contract;
- (c) third-party networks and services, including outages of MergeLabs’ network and security provider (Cloudflare), the AI provider behind Assist, and push notification and email services; or
- (d) force majeure under section 18.
S1.3 Measurement. MergeLabs monitors availability and gives the Client its figures for a month on request.
S1.4 Missed target. Missing the target does not give rise to service credits. The Client’s other rights under sections 12 and 13 remain unaffected.