# SCC Hosting SLA **URL:** \ **Category:** Membership & Services\ **Tags:** Members-only\ **Created:** [May 26, 2026, 5:55pm UTC](https://speciforum.org/t/scc-hosting-sla/3661 "2026-05-26T17:55:23Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Grant](https://yyz1.discourse-cdn.com/flex029/user_avatar/speciforum.org/grant/32/4255_2.png) [@Grant](https://speciforum.org/u/Grant)\ **Post date:** [May 26, 2026, 5:55pm UTC](https://speciforum.org/t/scc-hosting-sla/3661/1 "2026-05-26T17:55:23Z")
# **SCC Database and Asset Hosting** # **Service Level Agreement** SPECIFY COLLECTIONS CONSORTIUM This Agreement represents a Service Level Agreement (“SLA” or “Agreement”) for Specify Collections Consortium (“SCC”) technical (system and application) support services, and for Specify Cloud Hosting (“Specify Cloud” or “Service”) on the provider and location/Zone indicated in Exhibit A for the Research Organization (“RO”) collection databases and their associated digital assets using Specify software. The Agreement is effective as of Effective Date between the University of Kansas Center for Research, Inc., (“KUCR”), a not-for-profit corporation organized and existing under the laws of the State of Kansas, USA, affiliated with the University of Kansas (“KU”), a state institution of higher education, on behalf of the SCC, having an address at 2385 Irving Hill Rd, Lawrence, KS 66045-7568, USA and the Research Organization identified in Exhibit A. KUCR and RO are collectively referred to herein as the “Parties”. 1. ## **Purpose** The purpose of this SLA is to: - Describe how the SCC enables RO to remotely access and use the Specify software and all its customer data in “Software as a service” mode. - Explicitly identify the Specify Cloud Service hosting technical support services, software maintenance and updates, price, online availability, backup protocols, access restrictions, data ownership, and stakeholder responsibilities. 1. ## **Duration** This SLA is valid from the Effective Date, as defined in Exhibit A, and remains valid until superseded by a revised agreement. It is renewed from year to year unless terminated by either party in accordance with this section. The SLA may be terminated by RO at any time. SCC may terminate the SLA with 30 days written notice, or if RO becomes a Member not in good standing. Either party may terminate for material breach after 30 days’ notice and opportunity to cure. Upon termination or expiration, SCC will make the most recent backups available for secure download for 30 days; after that, data will be deleted per §5.10. 1. ## **Price** Basic database and asset hosting are included in the SCC Membership. Storage is allocated for databases and assets per the [SCC Membership Rights and Responsibilities (SCC MRR)](https://speciforum.org/t/scc-membership-rights-and-responsibilities-mrr/3372) based on RO’s membership level as defined in Exhibit A. The SCC reserves the right to assess storage overage and other usage-based fees during the hosting year if the database or assets grow to exceed the basic storage allocation for RO’s membership level, as defined in Exhibit A, contracted for during that year. Storage usage is evaluated quarterly and charged at the rates described in the [SCC Membership and Technical Support Services Prices](https://speciforum.org/t/scc-membership-and-technical-support-services-prices/2601). 1. ## **Contractors and Subcontractors** SCC’s cloud hosting provider is defined in Exhibit A. SCC may not add subcontractors without the customer’s prior written consent. Consent will not be unreasonably withheld, conditioned, or delayed. 1. ## **Service Agreement** 1. ### **Service Scope** The following services are covered by this SLA: - Technical support in accordance with the conditions described in [SCC’s Support Services Guide](https://speciforum.org/t/support-services-guide/2765) for technical issues related to Specify Cloud database hosting that arise. - Online availability of Specify Cloud virtual server, collection database, and Specify software application. - Continuous server, database, and application status monitoring. - SCC management of Specify software and security updates, updates by the cloud hosting provider to Hosting Services, and other integral software as required. - Backup and recovery of hosted data as described in §5.10. 1. ## **Data Ownership** All data created by RO hosted in the Specify Cloud service are RO’s property and KUCR and SCC make no claim of ownership to RO’s data. RO will not store regulated data (e.g., PHI, PCI, sensitive PII) unless separately agreed in a data protection addendum. KUCR and SCC will not access, inspect, use, or distribute RO data for testing, technical support, problem solving or for any other purpose without the express, written permission of RO. A limited administrative account in MariaDB will be required to create and restore backup files using scripts, all within the cloud servers. The SCC uses Member Specify databases for internal testing, technical support, or problem solving purposes only with express permission granted in the Membership Service Level Agreement, Exhibit A. 1. ## **Security Incident/Data Breach Notification** SCC will notify the RO without undue delay upon confirming an incident involving RO data. Notifications may be updated as additional information becomes available. The RO retains authority over external notifications, except where law requires SCC to notify. 1. ## **Warranty; Disclaimer; Limitation of Liability** SERVICES ARE PROVIDED “AS IS”; SCC DISCLAIMS ALL IMPLIED WARRANTIES TO THE FULLEST EXTENT PERMITTED BY LAW. SCC’S AGGREGATE LIABILITY FOR DIRECT DAMAGES UNDER THIS SLA IS CAPPED AT THE TOTAL FEES PAID FOR HOSTING SERVICES IN THE 12 MONTHS PRECEDING THE CLAIM; NO LIABILITY FOR INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL, EXEMPLARY, OR LOST PROFITS DAMAGES. IMMUNITY CARVE-OUT APPLIES AS IN MEMBERSHIP SLA. 1. ## **Force Majeure** Neither party is liable for delays or failures due to events beyond reasonable control, including outages of third-party networks or cloud providers, acts of God, or changes in law. 1. ## **Responsibilities** 1. ### **RO Responsibilities** RO responsibilities in support of the SLA include: - Payment for support costs at the agreed interval and period of service. - Providing reasonable availability of a RO representative when resolving a service-related incident or request. - Providing and maintaining the Hosting Contact List. - Meeting response times associated with service-related incidents. - Providing RO with an annual report of the service’s uptime - Notification to designated RO representatives of all planned and emergency maintenance. - Notification to the RO of a data breach within 24hrs of SCC becoming aware of the data breach. - SCC will implement reasonable administrative, technical, and physical safeguards aligned with recognized frameworks appropriate for the scale of the Services. **For KUCR / administrative:** University of Kansas Center for Research, Inc. 2385 Irving Hill Road Lawrence, KS 66045, USA [kucrbussvs@ku.edu](mailto:kucrbussvs@ku.edu) **For Specify Collections Consortium:** Aimee M. Stewart, Consortium Executive Director Biodiversity Institute, University of Kansas 1345 Jayhawk Boulevard Lawrence, KS 66045, USA Office: +1 785-864-2233 Email: [director@specifysoftware.org](mailto:director@specifysoftware.org) Theresa M. Miller, Membership and Fulfillment Officer Biodiversity Institute, University of Kansas 1345 Jayhawk Boulevard Lawrence, KS 66045, USA Office: +1 785-864-4652 Email: [membership@specifysoftware.org](mailto:membership@specifysoftware.org) **IN WITNESS WHEREOF** , the parties have accepted and executed this Agreement through their duly authorized representatives as of the date entered below. | Member Institution (RO) | | The University of Kansas Center for Research, Inc., on behalf of the Specify Collections Consortium | | --- | --- | --- | | | | | | Signature | | Signature | | | | | | Name | | Name | | | | | | Title | | Title | | | | | | Email | | Email | | | | | | Date | | Date | # **Exhibit A:** **Research Organization (RO):** \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ **RO Business Office:** \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ **RO Legal Jurisdiction:** \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ **Effective Date:** \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ **Hosting Service:** \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ **Hosting Location/Zone:** \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ **Number Databases Hosted:** \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ **Size Limit for Hosted Databases:** \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ **Assets are Hosted by SCC (Yes/No):** \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ **Size Limit for Hosted Assets:** \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ ---
**Author:** ![Grant](https://yyz1.discourse-cdn.com/flex029/user_avatar/speciforum.org/grant/32/4255_2.png) [@Grant](https://speciforum.org/u/Grant)\ **Post date:** [May 26, 2026, 5:55pm UTC](https://speciforum.org/t/scc-hosting-sla/3661/2 "2026-05-26T17:55:30Z")