General Terms & Conditions

Version 1.0 – 26th January 2026.

TABLE OF CONTENTS:

  1. Scope

  2. MedCube Platform

  3. Definitions

  4. Access Rights and Obligations

  5. Service Scope and Availability

  6. Fees and Billing

  7. Platform Conduct and Restrictions

  8. Data Protection and Security

  9. Sub-processors and Hosting

  10. Intellectual Property, Use Restrictions, and Infringement

  11. Warranties and Disclaimer

  12. Limitation of Liability

  13. Indemnity

  14. Force Majeure

  15. Term and Suspension

  16. Dispute Resolution and Governing Law

  17. Entire Agreement

  18. Changes to Terms

  1. Scope

    These General Terms & Conditions ("GTC") govern the access to and use of the MedCube Platform by legal entities entering a MedCube Service Agreement with MedCube AS ('MedCube'). This GTC applies to all types of use, including but not limited to case coordination, resource scheduling, service provision, and data communication.

  2. MedCube Platform

    The MedCube Platform is a cloud-based system for the coordination and execution of medical transport activities, mission management, and marketplace-based service engagement.


    The MedCube Platform allows Platform Customers to manage, coordinate, and deploy their internal resources for medical missions and any subsequent communication relating to the missions. It also provides access to a curated marketplace of external services offered by Network Providers, streamlining the booking and coordination process for complex, multi-party Cases.


    The MedCube Platform allows Network Providers to showcase their services, respond to mission requests, and manage availability, pricing, and communication through a single interface. It provides a clear overview of active and upcoming service demands from Platform Customers, along with tools for documentation, coordination, and participation in co-transport missions that increase efficiency and revenue potential.


    The MedCube Platform also supports organisations that operate in both roles. An organisation may act as a Platform Customer in some contexts - managing their own missions - and as a Network Provider in others, offering their own services to third parties. MedCube enables this dual-role participation while keeping operational, commercial, and data responsibilities clearly separated through role-based interfaces and Annexed terms.


    All Cases are supported by role-based communication and data exchange between stakeholders, optionally including patients and their relatives.

    1. Key capabilities include:

      • A unified Case and mission management dashboard

      • Access to a marketplace of curated service providers (Network Providers - including but not limited to air and ground ambulances, hospitals, medical escorts)

      • Role-based access control and messaging channels

      • Native mobile apps for all stakeholders including but not limited to escorts, patients, and next of kin

      • Automated Case reporting, vitals logging, and standardised checklists

      • Integrated quoting, invoicing, and reporting tools

      • Real-time transport tracking, mapping, and delay notifications

      • Support for Co-transportation of patients (e.g. multi-patient missions, backhauls)

      • Use of anonymised Case data to power a machine-learning based decision-support engine and cost/sustainability benchmarking tools for all Partners.

      MedCube may enhance, modify, or retire specific features at its discretion, provided such changes do not materially reduce the core functionality unless otherwise agreed in writing.


      The Platform is designed to comply with European health data protection regulations and offers APIs and structured data exchange compatible with HL7/FHIR standards for integration with clinical systems and public health records.

  3. Definitions

    1. Access Fee

      Recurring charges for general access to the Platform by a Partner organisation.

    2. Agreement

      The MedCube Service Agreement incorporating the General Terms & Conditions (GTC), Data Processing Agreement (DPA), Service Level Agreement (SLA), and applicable Commercial Annexes.

    3. Billing Cycle

      The agreed time interval for MedCube to issue invoices (e.g. monthly, quarterly).

    4. Case

      An individual medical mission or task managed via the Platform, including all associated service elements.

    5. Case Fee

      A per activity or per Case fee based on the complexity or type of medical mission. These currently include, but are not limited to:

      • Case Type A: Medical Escort Case

      • Case Type B: Ground Transportation Case

      • Case Type C: Commercial Flight - Sitting with MEDIF

      • Case Type D: Commercial Flight - Stretcher

      • Case Type E: Air Ambulance Single Patient Transport

      • Case Type F: Air Ambulance Co-Transport Mission.

    6. Co-Transportation

      A mission in which multiple patients are served through a shared air ambulance itinerary. This may include transporting multiple patients simultaneously, transporting one patient each way on a round

      trip that would otherwise include an empty leg, or picking up a patient enroute to another destination, provided the routing reduces the total number of flights that would otherwise be required to complete the Cases separately.

    7. Commission Fee

      A variable, percentage-based fee payable to MedCube on the net amount finally invoiced by one Partner to another Partner for completed missions or services requested and arranged through the MedCube Platform, as further specified in the applicable Service Agreement or Commercial Annex.

    8. Customisation Fee

      Charges for Partner-requested integrations, configuration, or non-standard workflows.

    9. Due Date

      The deadline for payment of an invoice issued by MedCube.

    10. Effective Date

      The date on which the Agreement comes into force.

    11. Force Majeure

      An event beyond the control of either party that prevents fulfilment of obligations under this Agreement.

    12. Marketplace

      The Platform module where Network Providers offer services for quoting and booking by Platform Customers.

    13. Material Breach

      A significant violation of the Agreement that allows the other party to terminate the contract for cause.

    14. MedCube Platform or Platform

      The cloud-based platform, as updated from time to time, used for coordinating medical missions, managing internal resources, and accessing services from Network Providers, including associated apps and tools.

    15. Partner

      Any legal entity registered with MedCube under an Agreement, including Platform Customers, Network Providers, and Dual-Use Partners.

    16. Partner Types

      1. Network Provider

        A Partner that offers services such as air ambulance, ground transport, medical escort, or hospital care via the MedCube marketplace. Subject to the terms of both Commercial Annex B.

      2. Platform Customer

        A Partner that uses the MedCube Platform to coordinate, manage, and initiate medical transport missions, with or without internal resources. Subject to the terms of both Commercial Annex A.

      3. Dual-Use Partner

        A Partner that performs both Platform Customer and Network Provider roles. Subject to the terms of both Commercial Annex A and B.

    17. Service Fee

      Charges for additional service modules or infrastructure add-ons.

    18. Termination Date

      The date upon which the Agreement ends.

    19. Trusted Partner Validation Fee

      Applicable to Network Providers for validation, audit, and listing of services.

    20. User:

      An authorised natural person acting on behalf of a Partner through the MedCube Platform, including employees, contractors, and subcontractors engaged or appointed by the Partner for activities related to their Platform use.

    21. User Fee:

      Charges based on the number of active named Users under a Partner account.

  4. Access Rights and Obligations

    1. Licence Grant

      Partners are granted a limited, non-exclusive, non-transferable licence to access and use the Platform as set out in the Agreement.

    2. Access Control and Security

      Partners must ensure authorised use of the Platform, protect login credentials, and take reasonable steps to prevent unauthorised access. The Partner is liable for any misuse or unauthorised activity resulting from their failure to maintain access controls.

    3. Acceptance by Individual Users

      • Access to and use of the MedCube Platform requires each User to explicitly accept these GTCs through the Platform’s interface

      • By registering, logging in, or using any functionality of the Platform, Users acknowledge that they are bound by this GTCs and agree to comply with all applicable obligations and restrictions

      • The Partner is responsible for ensuring that all its Users understand and comply with these GTCs and any related data protection or confidentiality obligations

      • Where individual acceptance is not feasible due to Partner policies, acceptance by an authorised Partner representative on behalf of Users shall suffice.

    4. Suspension of Access

      MedCube may suspend access for a User or Partner in the event of:

      1. breach of the Agreement

      2. use that threatens Platform security or integrity

      3. overdue payments

      4. failure to meet data protection obligations.

      Suspension of one or more Users does not affect the legal validity of the Agreement unless otherwise stated.

  5. Service Scope and Availability

    MedCube will provide access to the Platform with reasonable availability, excluding scheduled maintenance, emergency updates, and events beyond its control. Availability and support commitments are detailed in the Service Level Agreement (SLA).

  6. Fees and Billing

    1. Reference to Definitions

      All Fees listed below are defined in Article 3 (Definitions) and further detailed in the applicable Commercial Annexes A and/or B, including but not limited to Access Fees, Service Fees, User Fees, Case Fees, Certification Fees, Commission Fees, and Customisation Fees.

    2. Invoicing and Billing Cycles

      • Access, Service, User, and Validation Fees shall be invoiced monthly or annually in advance as specified in the relevant Annex

      • Case Fees and Commission Fees shall be invoiced monthly in arrears, based on completed missions and accepted service segments.

    3. Payment Terms

      • All invoices are payable in EUR within fifteen (15) business days of invoice date

      • If a Partner elects to pay in a currency other than EUR, the exchange rate shall be the published mid-market interbank rate on the invoice date as listed by the ECB, plus a 3% currency conversion margin

      • All payments must be made via bank transfer to the account specified on the invoice

      • MedCube does not accept payment by cheque, cash, or third-party payment platforms unless explicitly agreed in writing.

    4. Taxes and Duties

      Fees are exclusive of VAT, duties, and other government charges; such amounts are payable by the Partner where applicable.

    5. Annual Fee Adjustments

      1. Platform Access fees, Case Fees, and other standard charges listed in the Partner’s Commercial Annex may be adjusted effective 1 January each year based on the change in the Eurostat Producer Price Index for Services.

      2. Annual adjustments are capped at 5% per calendar year, except under extraordinary economic circumstances subject to prior written notice.

      3. Commission rates are excluded from annual indexation. These are fixed as defined in the applicable Commercial Annex and may only be changed through written agreement between the parties.

    6. Late Payments

      1. Late payments incur interest at 1.5% per month (or highest lawful rate) plus a fixed reminder fee of €50 per overdue invoice

      2. MedCube may suspend access after fourteen (14) days’ notice following a second unpaid reminder.

    7. Mutual Audit Rights

      • Each Party may request a financial and usage audit once per twelve (12) month period. Audits must be conducted by an independent third party with at least twenty (20) business days’ notice

      • If an audit shows a discrepancy of 5% or more, the audited Party shall reimburse reasonable audit costs; otherwise, the requesting Party bears the cost.

  7. Platform Conduct and Restrictions

    Partners may not:

    1. Copy, modify, or reverse engineer the MedCube Platform.

    2. Use it for unlawful, misleading, or abusive activities.

    3. Permit access to unauthorised third parties.

    4. Introduce malware or interfere with system security.

    5. Connect or deploy AI agents, bots, or automated decision-making systems to the MedCube Platform unless explicitly authorised by MedCube. MedCube may provide or authorise AI agents for specific use cases (e.g., triage, quoting).

    6. Unauthorised automated traffic may be rate-limited or blocked without notice.

    7. Any unauthorised automated activity may result in immediate suspension of access.

  8. Data Protection and Security

    1. MedCube acts as a data processor with respect to any personal data exchanged or uploaded via the Platform, including health and identity data related to medical transport activities.

    2. The roles, responsibilities, and obligations related to personal data processing are defined in the MedCube Data Processing Agreement (DPA), which forms an integral and binding part of this Agreement.

    3. Partners are responsible for ensuring that all personal data uploaded to the MedCube Platform is lawfully obtained, and that valid consent from data subjects is in place.

    4. The Partner represents and warrants that all uploaded data has a lawful basis, and MedCube is entitled to process it as a data processor.

    5. Anonymised data may be processed by MedCube to develop and train decision support tools and to benchmark platform performance, sustainability, and cost efficiency.

    6. The anonymisation process shall ensure that no personal data can be re-identified.

    7. To the extent permitted by applicable law, MedCube shall own all anonymised and aggregated data sets, statistical information, and derived data generated from the use of the MedCube Platform or the provision of the Services, provided that such data does not identify any individual, customer, or mission. Nothing in this Agreement restricts MedCube’s right to use such anonymised and derived data for product development, analytics, benchmarking, or system training.

  9. Sub-processors and Hosting

    MedCube may use sub-processors and hosting providers for performance of the service. Details are listed in the DPA. Sub-processors are subject to GDPR-compliant agreements and safeguards.

  10. Intellectual Property, Use Restrictions, and Infringement

    1. Ownership of Intellectual Property

      All rights, title, and interest in and to the MedCube Platform, including its software, architecture, algorithms, User interfaces, workflows, documentation, AI models, and all related tools or content, are and shall remain the sole and exclusive property of MedCube AS.


      Unless otherwise agreed in writing, any configuration, integration, or customisation developed by MedCube for a Partner shall be considered part of the MedCube Platform and owned by MedCube. This includes improvements or new features suggested or co-designed by a Partner, provided they are implemented within the MedCube Platform.

    2. Third-Party Rights and Indemnity

      MedCube warrants that the MedCube Platform does not, to the best of its knowledge, infringe upon any third-party intellectual property rights. If a third-party claim arises alleging such infringement, MedCube shall defend and indemnify the Partner against reasonable legal fees and settlements.


      MedCube shall not be liable for claims resulting from (a) Partner modifications, (b) third-party components not supplied by MedCube, or (c) use of the MedCube Platform outside the scope of the Agreement.

    3. Restrictions on Use and Confidentiality

      All MedCube services are licensed for internal use by the Partner only. The Partner may not, without prior written consent:

      • sell, sublicense, disclose, or share MedCube Platform access with any third party

      • decompile, reverse engineer, or otherwise attempt to extract source code or architecture

      • modify, translate, or create derivative works of the Platform

      • use MedCube Platform content or data for competitive development purposes.

      The Partner shall take reasonable technical and organisational steps to protect the MedCube Platform and all associated data, content, and configurations from unauthorised access or use.


      These restrictions shall survive the termination of this Agreement indefinitely.

    4. Infringement and Misuse

      Any breach of this Section 10, or other material misuse of the MedCube Platform constitutes a material breach of the Agreement. MedCube may, without liability, suspend or terminate access to the Platform immediately in the event of such breach. If suspension results in operational or financial loss to the Partner, MedCube shall bear no responsibility whatsoever.


      Suspension shall be limited to what is strictly necessary and proportionate to address the underlying risk and, where feasible, restricted to the affected users/modules. Access shall be restored without undue delay once the grounds for suspension cease.

    5. Marketing and Reference Rights

      Unless otherwise agreed in writing, MedCube may list the Partner’s name and logo as a reference customer in presentations, pitch materials, websites, and press releases, provided such reference is factual and not misleading. No confidential or operational data will be disclosed.


      The Partner may revoke this right at any time by written notice to MedCube.

  11. Warranties and Disclaimer

    The Platform is provided 'as is' without warranties of fitness, availability, or suitability for any specific purpose. MedCube does not guarantee uninterrupted service. All implied warranties are disclaimed to the maximum extent permitted by law.

  12. Limitation of Liability

    Except in Cases of gross negligence or wilful misconduct, MedCube’s liability is limited to the total fees paid by the Partner in the six (6) months preceding the event giving rise to the claim.

    MedCube is not liable for indirect losses, loss of revenue, or consequential damages. This limitation applies in aggregate under the Agreement, not per claim.

  13. Indemnity

    Each Party shall be liable to compensate the other Party for direct losses that arise as a direct consequence of a material breach of this Agreement. The Parties shall not be liable for any indirect or consequential losses.


    Notwithstanding the above, MedCube’s liability under this clause shall be limited to losses that could reasonably have been foreseen at the time of entering into the Agreement and shall in no event exceed the liability cap set out in Clause 12 above.


    For the avoidance of doubt, MedCube shall not be liable for any losses, claims, or consequences arising from the Partner’s clinical assessments, medical decisions, operational choices, routing, resource allocation, or any other professional judgment exercised by the Partner or its personnel. MedCube provides a coordination and information platform only and does not assume any responsibility for the Partner’s operational or medical outcomes.


    MedCube shall not be liable for any delay, outage, degradation, data loss, or failure caused by third-party hosting providers, cloud infrastructure, or internet service providers, provided such providers were industry-standard and reasonably selected. The Partner acknowledges that the Platform relies on third-party hosting environments, and interruptions in such environments do not constitute MedCube breach.


    Direct losses shall not include any losses resulting from reduced availability, service degradation, or downtime, except where such losses arise from the MedCube’s failure to meet the availability commitments expressly defined in the applicable Service Level Agreement (SLA). Any compensation for downtime shall be limited to the service credits set out in the SLA, which constitute the Partner’s sole and exclusive remedy for such events.


    No representations, statements, platform descriptions, or documentation shall be interpreted as creating any indemnity, warranty, or liability obligation beyond those expressly set out in the Agreement.


    Nothing in the Agreement shall limit either Party’s liability for losses caused by its gross negligence or intentional misconduct, to the extent such limitation would be invalid under applicable law.


    This clause constitutes an exclusive and exhaustive allocation of risk between the Parties, and no additional indemnity obligations shall apply unless expressly agreed in writing.

  14. Force Majeure

    Neither Party shall be liable for any delay or failure to perform its obligations under this Agreement if and to the extent such delay or failure is caused by an event beyond its reasonable control, including but not limited to:

    • acts of God, flood, fire, earthquake, or explosion

    • war, terrorism, civil unrest, or cyberattack

    • epidemic, pandemic, or public health emergency

    • government restrictions or regulatory intervention

    • failure of third-party hosting, cloud infrastructure, or internet services not under the direct control of the affected Party.

    • promptly notify the other Party of the event and its expected impact; and

    • use reasonable efforts to mitigate the effects of the delay or failure.

    If a Force Majeure event prevents either Party from fulfilling its material obligations under this Agreement for a period exceeding thirty (30) consecutive days, either Party may terminate the Agreement upon written notice.


    The affected Party shall:

    • promptly notify the other Party of the event and its expected impact; and

    • use reasonable efforts to mitigate the effects of the delay or failure.

    Obligations delayed due to a Force Majeure event shall be suspended for the duration of the event and resumed as soon as reasonably practicable thereafter.

  15. Term and Suspension

    1. Term and Suspension

      This GTC remains in force for the duration of the Agreement.


      MedCube may suspend or terminate access with immediate effect in the event of:

      1. a material breach of the Agreement.

      2. non-payment of fees.

      3. a credible threat to Platform integrity or data security.

      Obligations regarding data return or deletion upon termination are governed by the Data Processing Agreement (DPA).


      Upon termination or expiry, Partner is entitled to receive a machine-readable export (e.g., FHIR/CSV or other agreed format) of its data. MedCube will delete or return personal data in accordance with the DPA and retain only anonymised datasets as permitted. Migration assistance is available on a time-and-materials basis.

    2. Retention of Anonymised Data

      Termination of the Agreement does not affect MedCube’s right to retain and use anonymised datasets derived from transport activity and Platform usage. Such data may be used to support benchmarking, co-transport optimisation, system training, or performance analytics. No personally identifiable information shall be retained beyond the period specified in the Data Processing Agreement (DPA), unless otherwise required by law.

  16. Dispute Resolution and Governing Law

    The Agreement is governed by and shall be interpreted in accordance with Norwegian law. Any dispute arising out of or in connection with this Agreement shall be finally settled by arbitration administered by the Oslo Chamber of Commerce Arbitration Institute (OCC). The seat of arbitration shall be Oslo, Norway and the arbitration shall be conducted in English. The arbitral tribunal shall consist of one arbitrator if the disputed amount does not exceed NOK 1million. If the disputed amount exceeds NOK 1million, the tribunal shall consist of three arbitrators.

  17. Entire Agreement

    These GTCs, together with the SLA, DPA and applicable Commercial Annexes are an integral part of the Service Agreement between the Parties.

  18. Changes to Terms

MedCube reserves the right to update or modify the GTC, SLA, DPA and/or related policies at any time to reflect changes in functionality, legal requirements, or business operations. Only non-material changes to these documents are allowed by MedCube.


Partners will be notified of changes via email or Platform notification at least thirty (30) days before the updated terms take effect. Continued use of the Platform after the effective date constitutes acceptance of the new terms.


If a Partner does not accept the updated terms, they may terminate the Agreement by providing written notice before the effective date of the changes. In such Cases, the Partner remains liable for all fees and obligations incurred up to the termination date.