ICE CREAM SOCIAL SERVICE LEVEL AGREEMENT

Dated: March 2022

This is the Service Level Agreement referred to in the Ice Cream Social User Agreement (“User Agreement”). All capitalized terms used herein shall have the same meaning as they do in the User Agreement which links to this document.

  1. From and after the date on which User’s application is first made commercially available (“Launch Date”), Ice Cream Social shall use commercially reasonable efforts to ensure that System Uptime (as hereafter defined) shall be available and responsive 99% of the time, and that User reports are available 99% of the time, measured on a monthly basis calculated to include twenty-four (24) hours per day over each month (“Minimum Uptime Commitment” or “Uptime”). Uptime means the System is operational and is available to communicate with the internet in Ice Cream Social’s server location (which may be at a co-location facility).
  2. It shall not be considered a Service Level failure to the extent that the failure to achieve the Uptime is due or relates to: (a) scheduled maintenance or downtime; (b) any modifications or alterations of the Software made by any individual or entity other than Ice Cream Social or its authorized agents; (c) any violation of the User Agreement by User, its employees, contractors, or agents; (d) any unavailability due to a User action that cannot be reasonably recreated by Ice Cream Social; (e) User’s negligence, abuse or misapplication, or unauthorized use of Software other than as specified in the Documentation or as approved by Ice Cream Social, or any failure to comply with the documentation published for the Software; (f) any third party software not provided by Ice Cream Social; (g) outages or latency in the Public Circuit (as defined below); (h) failures due to Force Majeure events; (i) any inability to access or operate the Software due to problems with software, hardware, telecommunications, or networking equipment not owned or operated by Ice Cream Social, including without limitation, any such equipment owned, controlled or operated by User, any payment processors, or any other third party; (j) denial of service attacks, virus attacks, hacking attempts, internet service interruptions, or any other circumstances or events that are not within Ice Cream Social’s reasonable control.
  3. Maintenance outages, if necessary, will be conducted between the hours of 10:00 PM and 4:00 AM Pacific Standard Time (the “Maintenance Window”) or other off-business hours as may be mutually agreed on by the parties to the User Agreement. Maintenance outages may result from, but are not limited to, the installation of upgrades, service packs, and routine server or application configuration changes. All active Maintenance Windows will be according to a scheduled time set by Ice Cream Social and announced via e-mail to User.
  4. To the extent practicable, Ice Cream Social shall notify User in advance of any outages that may occur outside of a Maintenance Window, and temporary Workarounds will be put in place if possible.
  5. Ice Cream Social will provide User reasonable written notification to a pre-defined User email address of any system freeze and possible related processing impact, regardless of cause.
  6. Support Response Time and Credits.

Ice Cream Social will respond to support requests made via ticket, e-mail or telephone within the following time frames. All cases created by Ice Cream Social will be assigned a priority level by Ice Cream Social. Priority guidelines and the corresponding response times specify how quickly Ice Cream Social will diagnose and resolve the issue and respond to User.

  1. Priority Level 1 – P1 (Emergency) System Down
  2. Example – Entire System is down; no service possible; severe impacts.
  3. Initial Response < 30 minutes
  4. Immediate Management Escalation and a Status Update within two (2) hours
  5. Priority Level 2 – P2 (High) Severe System Disruption
    1. Example – Significant number of User’s customers are unable to retrieve rewards, or User reports are unavailable.
    2. Initial Response – < 2 hours
    3. Management Escalation and a Status Update within four (4) hours
  6. Priority Level 3 – P3 (Medium) Single Function Failure
    1. Example – User systems generally functioning, but incorrectly or very slowly, limited to certain or isolated aspects of the System.
    2. Initial Response – < 4 hours
    3. Management Escalation and a Status Update within two Business Days
  7. Priority Level – P4 (Routine) Minor Issue or Procedural Question
    1. Examples – Programming questions / Operational or Procedural questions / Research of intermittent issues
    2. E-mail support and/or phone support
    3. Initial Response – < 48 hours
    4. Minor issues may be resolved in future releases or versions of the Software

Failure to meet the response time guaranties stated in this Section, discovery that the Ice Cream Social System is not functioning within the Service Level Agreement shall entitle User to a service credit as set out below:

 

Unscheduled Downtime (minutes) Service Credit Percentage (%)
To 438 0%
439 to 877 2.5%
878 to 1316 5.0%
1317 to 1755 7.5%
1756 to 2193 10%
Each additional 438 min. additional 5%

 

User must request a credit in writing either via a support ticket or by notice as specified in the User Agreement, no later than seven (7) days following the occurrence of the event giving rise to the credit. Ice Cream Social will contact User within 30 days to approve or reject the claim or to request more information. If the claim is approved, the credit will appear on User’s monthly invoice following approval. Notwithstanding anything in this Agreement to the contrary, the maximum total credit for any calendar month for failure to meet Service Levels under this Agreement for that month, shall not exceed 100% of Service fees for the affected Service. Credits that would be available but for this limitation will not be carried forward to future months.

Time is based on a 730-hour month. For the purpose of determining whether a credit is due, time periods will be measured from the time stamp generated by the Ice Cream Social support ticket system.  User may open a support ticket to document the start time for a support request or other incident, or if User contacts Ice Cream Social by telephone to request support, Ice Cream Social will open a ticket. If User contacts Ice Cream Social by phone or regular e-mail service, there may be a delay between the time of the call and the time Ice Cream Social opens a ticket.

There is no entitlement to a credit for downtime or outages resulting from System maintenance where such maintenance is (1) within the Maintenance Window or there are other modification or repairs to shared infrastructure that Ice Cream Social scheduled at least 72 hours in advance; or (2) scheduled User maintenance – maintenance that User requests and that Ice Cream Social schedules with User in advance (either on a case by case basis, or based on standing instructions), such as hardware or software upgrades implemented by User.  User is not entitled to any credit if User is in breach of the User Agreement (including User’s payment obligations to Ice Cream Social) at the time of the occurrence of the event giving rise to the credit, until User has cured the breach.  User is not entitled to a credit if the event giving rise to the credit would not have occurred but for User’s breach of the User Agreement or any other agreement between User and Ice Cream Social.

All support services are contingent on Ice Cream Social having full access to User’s configuration. No credit will be due if the credit would not have accrued but for User’s restriction of Ice Cream Social’s access to User’s configuration.

Disabling or Removal of Monitoring or Security Services, Interference with Services: User must notify Ice Cream Social in advance if User plans to disable, block, or remove any monitoring or security element of User’s website or hosting service for more than ten (10) minutes. Ice Cream Social will not issue User any credit for events that might have been avoided or mitigated if User had not disabled, blocked or removed Ice Cream Social’s monitoring or security elements, or otherwise interfered with Ice Cream Social’s ability to provide the Services.

7. Failure to Reproduce Issue

If Ice Cream Social believes that a problem or issue reported by User is not reproducible, affects only User, and is unlikely to be due to an error existing in the Software or System, Ice Cream Social will so notify User. At that time, User may (1) instruct Ice Cream Social to proceed with problem determination at User’s expense as set forth below, or (2) instruct Ice Cream Social that User does not wish the problem pursued at its expense. If User requests that Ice Cream Social proceed with problem determination at its expense and Ice Cream Social determines that the error was not due to an issue with the Software, User shall pay Ice Cream Social, at Ice Cream Social’s then-current and standard consulting rates for all work performed in connection with such determination, plus reasonable, out-of-pocket related expenses actually and directly incurred therewith. User shall not be liable for (i) problem determination or repair to the extent problems are due to errors in the Software; or (ii) work performed after User has notified Ice Cream Social that it no longer wishes work on the problem determination to be continued at its possible expense (such notice shall be deemed given when actually received by Ice Cream Social). If User instructs Ice Cream Social that it does not wish the problem pursued at its possible expense or if such determination requires effort in excess of User’s instructions, Ice Cream Social may, at its sole discretion, elect not to investigate the error with no liability therefor.

8. New Features

User may submit requests for new features, and if acceptable, Ice Cream Social shall be engaged and performed pursuant to a Statement of Work under the Agreement. All new features shall be considered within the definition of Software under the Agreement, and licensed pursuant to the terms of the Agreement. Ice Cream Social will inform User, using commercially reasonable efforts, of the status of the development of the requested feature. If Ice Cream Social does not plan to build the requested feature, or if it plans to build the feature but on a timeline that is not acceptable to User, Ice Cream Social may, at its discretion, offer User the option to accelerate the development of the feature for a cost. Costs for accelerated feature development will depend on the feature being developed, and may include time, materials, and licensing fees and shall be previously approved by User.

9. Additional Definitions

“Business Days” means Monday through Friday, excluding U.S. holidays and any other holidays in the State of California.

“E-mail support” means requests for technical support assistance by e-mail concerning the use of the then current release of the Software.

“Initial Response” means the first contact by a support engineer after the incident has been logged and a ticket generated.

“Management Escalation” means, if the initial Workaround or fix does not resolve the Error, notification of Ice Cream Social management that such Errors have been reported and of steps being taken to correct such Error(s).

“Public Circuit” means the third party provided circuits, overland and/or submarine cabling, and other connectivity infrastructure from a point of demarcation starting immediately after the ingress/egress router or similar appliance at  User’s or Patrons’ site to the point immediately before the ingress/egress router or similar appliance at the facility used by Ice Cream Social to host the Software.

“Status Update” means if the initial Workaround or fix cannot resolve the Error, notification of the User regarding the progress of the Workaround or fix.

“Upgrades” means, other than routine bug fixes and updates, additional software added to the Software that provides new functionality or modules to the Software.

“Workaround” means a change in the procedures followed or data supplied by User to avoid an Error without substantially impairing User’s use of the Software or that of Patrons.