Back to Legal Overview

Service Level Agreement (SLA)

Last updated: January 9, 2025

This Service Level Agreement (“SLA”) forms part of the SaaS Subscription Agreement between Markular and Customer (the “Agreement”) under which Markular provides its Software-as-a-Service for Crew Management Solution of Customer’s Content.

1. DEFINITIONS

“Incident” means (i) any single event, or (ii) any set of events, that result in Downtime.

“Service Credits” means the calendar days of prepaid Service Fees that will be applied in the form of monetary credit for future use of the Service upon Markular’s approval of request according to Section 2.5.

“Downtime” means, except for scheduled system maintenance, the period that the Service is either (a) not available to Customer or (b) substantially not functioning. Downtime does not include unavailability of the Service due to limitations described in Section 2.6.

“Service Level” means the level of service availability that Markular has undertaken to meet towards Customer.

“Scheduled Downtime” means periods of scheduled Downtime related to maintenance or upgrades of the Service in certain maintenance windows as communicated by Markular to Customer.

2. SERVICE LEVEL

  1. Service Level. Customer is entitled to a Service Level corresponding to 24 hours per day, 7 days per week at 99.5% of the time in each calendar month during Customer’s Subscription Period. An exception is made for Scheduled Downtime.

  2. Service Credits in case of deviance from Service Level. If Markular does not meet the promised Service Level, Customer is eligible to receive the Service Credits as described below. The availability of Service Credits is Customer’s sole and exclusive remedy for any failure by Markular to meet the terms of this SLA.

    a) For availability between 99.0% and 99.5% the Customer will receive 3 calendar days of Service Credit.

    b) For availability between 95.0% and 99.0% the Customer will receive 7 calendar days of Service Credit.

    c) For availability below 95% the Customer will receive 15 calendar days of Service Credit.

  3. Maximum Service Credit. The aggregate amount of Service Credits to be issued to Customer for all Downtime that occurs in a single calendar month shall not exceed 15 calendar days of Service.

  4. Request for Service Credit. Customer must request the Service Credit by notifying Markular within 30 days from the Incident occurred by contacting support@base12.no. The request shall include all information necessary for Markular to validate the request, including but not limited to: (i) a detailed description of the Incident, (ii) information regarding the time and duration of the Downtime, (iii) the number of affected users and location(s), and (iv) description of Customer’s attempt to resolve the Incident at the time of occurrence. Failure to comply with these requirements will forfeit the Customer’s right to receive the Service Credit.

  5. Evaluation of and response to request. Markular shall evaluate all information reasonably available and make a good faith determination of whether a Service Credit is owed. Markular shall use reasonable efforts to process and respond to the request within 30 calendar days from received request. Customer must comply with the SLA to be eligible for a Service Credit. Markular will issue Service Credits that it deems to be owed by Customer in the form of monetary credit applied to future use of the Service. Customer may request reimbursement of prepaid Service Fees instead if Customer is unable to utilize the monetary credit due to termination of the Agreement.

  6. Limitations. This SLA and any applicable Service Credits do not apply to any performance or availability issues:

    1. Due to factors outside Markular’s reasonable control (such as, but not limited to natural disaster, war, acts of terrorism, riots, government action, or a network or device failure external to Markular’s data centers, including Customer’s site or between Customer’s site and Markular’s data center)

    2. Due to Customer’s use of the Service inconsistent with the Documentation or in violation of the Agreement

    3. Due to Customer’s use of the Service in combination with any other product or service not provided or recommended by Markular

    4. Due to Customer’s use of the Service in a way that substantially exceeds its assigned, monthly network quota (inbound and outbound) based on purchased storage

    5. With respect to preview, prerelease or beta versions of the Service or any features not covered by the Documentation