Definitions

1. Agreement is the agreement between the Customer and the Provider regarding the provision of the Services by the Provider and use of the Services by the Customer.

2. Availability is that the Customer can execute and use the essential functions of the Services at the Handover Point as defined in the Agreement.

3. Downtime is the total number of hours (h) in which the essential functions of the Service as defined in the Agreement are not available for use by the Customer during the System Runtime.

4. Handover Point are the internet hubs of the data center.

5. Incident is any impairment on the Service, such as Downtimes, errors or a reduction of quality.

6. Incident Management is the processing of Incidents.

7. Incident Priority is the severity of the Incident.

8. Response Time is the period of time to start working on an Incident reported by the Customer.

9. Maintenance Work is all maintenance activities required to keep the Service running, to eliminate errors in the Service, to backup data and/or activities required to enhance, enlarge or renew functionalities to ensure that the Service can be used in accordance with the Agreement.

10. Service Provision Period is the time in which the system must be ready for operation.

11. SLA is this Service Level Agreement.

General Provisions

1. This SLA sets forth the Availability of the Service and supporting service levels. The Provider shall provide the services as described below in accordance with the price list valid at the time of conclusion of the Agreement.

2. This SLA applies solely to the Service made available for productive use by the Customer and not apply to any non-productive, free and/or try-out versions of the Service, integration or test systems having unreleased functions or functionality.

3. This SLA is only valid in conjunction with the Agreement and shall not take effect until Customer and Provider have executed the Agreement. 1 IAMPOP.COM

4. All obligations of the Provider in this SLA only apply to the Service as made available to the Customer at the Handover Point. Provider is not responsible for data transmission from the Handover Point to the Customer and/or in the area of Customer’s IT system.

5. Any malicious misuse of the Provider's extra privileges with regard to the Provider's access to the Customer's platform/Services will be treated as a breach of the SLA and void the Agreement.

Support

Operating times of support

• Business days

• Monday - Friday

Operating Times

• 10:00 - 18:00

Language

• English

The support comprises a service desk for receiving Incidents from Customer by means of tickets or e-Mails via hello@iampop.com, prioritising Incident reports according to the urgency of the Incident, analysing and isolating the Incident.

All times are based on the Central European Time (CET) or Central European Summer Time (CEST) valid in The Netherlands.

Incident Management

Incident Management shall comprise all the activities between the Customer and the Provider associated with the notification and management of Incidents until resolution.

Incident Priority

All Incidents within the Service shall be assigned an Incident Priority which shall determine the target Response Time

• Critical

  • There is an Incident Priority 1 if the use of the Service or major parts of the Service is completely unavailable or severely restricted for instance due to malfunctions, false work results or response times.

    • <3h during operating times

• Major

  • There is an Incident Priority 2 if, although the use of the Service is not unavailable or severely restricted, for instance due to malfunctions, false work results or response times, the use is subject to restriction(s) which is (are) material

    • <6h during operating times

• Minor

  • There is an Incident Priority 3 if the use of the Service is not directly and/or significantly/ considerably impaired. e.g. basic settings are unfavourably defined or ‘niceto-have’ functions are missing.

    • <12h during operating times

• None

  • There is an Incident Priority 4 if there is no limitation of the use of the Service functionalities; e.g. minor flaws, questions or requests for improvement by the Customer.

    • <24h during operating times

Process

• Customer shall immediately notify the Provider of all Incidents.

• All Incidents must be communicated to the Provider via ticket system or e-Mail.

• The Customer shall ensure that when the Incident is reported, the Incident reporting must include the following required information:

  • Customer Account name

  • Detailed description of the Incident in order to reproduce the incident;

  • Service name and functionality of the Service affected;

  • Cloud infrastructure and region affected;

  • Date and time when the Incident occurred;

Incident Priority;

• The action(s) which the Customer has already taken to remedy the Incident and any results from the action to remedy the Incident taken by the Customer.

• Once the Customer provides all required information, the resolution process shall start and the first feedback after receipt of the Incident report shall be given according to the Response Time in relation to the Incident Priority according to Section 5.2.

• The Provider shall notify the Customer upon Incident closure.

• Incident processing shall be performed during the business days and operating times as defined in Section 4.1.

• The Provider may provide the Customer with an interface for creating Incident tickets in Provider’s ticketing system (JIRA). The Provider reserves the right to amend the ticketing system in its sole discretion due to a change in requirements. Any use of the ticketing system by third parties, in particular by end customers or suppliers of the Customer, is prohibited. The ticket language for all tickets is English.

Maintenance Work

1. The Provider has the right to interrupt the provision of the Service for Maintenance Work.

2. The Provider shall plan Maintenance Work to minimise the interruption of the use of the Service, so that the use of the Service by the Customer is affected as little as possible.

3. Planned Maintenance Work will be announced 30 calendar days in advance on the IAMPOP.com Dashboard or via email.

4. The Provider is also permitted to conduct unscheduled Maintenance Work on the Service for important reasons, e. g. if the Service operation is jeopardised. This includes but is not limited to emergency changes, e. g. the implementation of security patches, which are necessary for securing and maintaining operations and require immediate implementation. The Customer must be notified hereof without undue delay and the unscheduled Maintenance Work must be carried out in such a way as to minimise malfunctions in operational processes as far as possible.

Security

1. The Provider shall have repeatable and periodic processes in place for scanning, identifying and remediating newly discovered security vulnerabilities on servers, workstations, network and equipment and applications.

2. The Provider shall ensure that regular penetration testing exists and is conducted by a reputable external third-party organisation and shall provide copies of the testing results upon request.

3. The Provider will indemnify against all costs, expenses (including legal expenses), damages, loss (including loss of business or loss of profits) liabilities, demands, claims, actions or proceedings which the client may incur arising out of any breach of this SLA by the Provider up to a cap of 2x the agreed client revenue for the preceding 12 months of service.

Miscellaneous

The provisions of the Agreement shall remain in full force and effect.