SaaS Release & Upgrade Policy

Last Update: August 2022

Overview

As a SaaS company, Zoomin is committed to continuously and frequently upgrading its customers and their end-users’ experience. New features and functionalities to the Services are added from time to time through these updates and upgrades, provided by Zoomin in accordance with this policy.

One impact of new releases in a SaaS environment is that older versions are not supported and will no longer be available. To ensure that our customers obtain the maximum value of the offering, the Customer should review any custom configurations implemented for Zoomin's Services for usability and effectiveness when new releases occur, as outlined below.

Release Types, Notification, and Customer Obligations

Certain releases may include a “Breaking Change”, meaning a material modification which impacts the Customer’s end users in one of the following aspects: (i) significant changes to the look and feel or functionality, or (ii) breaking change to Zoomin official API behaviors. 

To protect our customers, any release that causes a Breaking Change will be preceded by 2 months’ prior notice to our Customers (unless otherwise communicated by the parties directly) and be accompanied with release notes detailing the changes included. Each Customer shall have the opportunity to access a non-production site preview of the Breaking Change as set forth in our notification policy below, where the Customer may verify the functionality and customizations and alert Zoomin if issues are found. Any release that does not include a Breaking Change will not be subject to prior notification, and the Customer does not have any obligation to verify the functionality and customizations for any such non-Breaking Change. 

In addition, Zoomin may need to address urgent issues such as a security vulnerability, system or application stability, or other functional issue, i.e. a patch or a "hot-fix". Hot-fixes will be applied as required, though Zoomin endeavors to perform such hot-fixes outside of typical business hours (US time).

Customer Notification Policies

In the event any release includes a Breaking Change, Zoomin will provide each Customer the opportunity to observe and/or test the new release on its non-production environment prior to such release moving into production. Zoomin generally provides the ability to observe and/or test on the nonproduction site for a period of thirty (30) days (unless otherwise agreed by the parties) for customers to ascertain what, if any, impact there may be on its user groups. Additionally, if the nature of the changes requires the Customer to work with Zoomin on any customization for any of the newly introduced elements, a reasonable period of time to complete such work will be agreed upon between Zoomin and Customer. 

Advanced notice provided by Zoomin to a Customer will reference applicable release notes as well as the location of the non-production site noted above. Release notes will include a brief overview of the update, the purpose, end-user impact, and any additional notes relevant to the release.

Software Version Requirements

Zoomin strives to run all SaaS offerings on the most current generally available version of the underlying Zoomin Software. Zoomin will not be required to support any versions other than for the most current generally available version and the immediately prior major version. At its discretion, Zoomin may either upgrade any non-compliant instance or suspend the service until Customer has completed any actions required to move to the supported version without rebate or credit for any such period of suspension.

Customizations

In cases where the Customer has obtained or desires to obtain a New Customization (if any, as defined in the agreement between Zoomin and the Customer), and such New Customization is affected by a new release, the Customer shall be responsible for identifying any specific requirements of such New Customization during the non-production preview site, and shall inform Zoomin of such requirements in order to ensure that the New Customization is applied to the new elements in the respective release.