Terms of Use
RAFT, LLC
These Terms of Use (the “Terms”) govern access to and use of Provider’s cloud-hosted software made available by Provider at the URL through which these Terms are presented, as further described in Schedule B (the “Service”). The Service is a shared, multi-tenant environment made available at no charge to customers, prospective customers, and early-access users, both government and non-government.
By clicking “I AGREE,” or by accessing or using the Service, the individual accepting these Terms agrees to be bound by them on behalf of both themselves and, where they are accepting for an organization, that organization (in either case, “Subscriber”), and represents that they have authority to bind any organization on whose behalf they accept.
If the individual does not agree, they must not access or use the Service. Subscriber’s use of the Service is also subject to Provider’s Privacy Policy and Acceptable Use Policy, each incorporated by reference and available at the URL(s) identified on the landing page (and, for the AUP, in Section 2.8).
WHEREAS, Provider has developed, exclusively at private expense, certain proprietary and copyrighted software-as-a-service solutions (the “Service,” as further defined below);
WHEREAS, Provider makes the Service available at no charge to customers, prospective customers, and early-access users, both government and non-government;
WHEREAS, Subscriber desires to access the Service for its internal evaluation, testing, and familiarization use subject to the terms and conditions hereof;
WHEREAS, Provider desires to grant such access upon the terms and conditions set forth herein.
NOW THEREFORE, in consideration of the mutual covenants and conditions contained herein, and for other good and valuable consideration, the receipt and sufficiency of which are hereby acknowledged, the parties agree as follows:
1. Definitions
1.1. “Authorized Use” means Subscriber’s access to and use of the Service solely for Subscriber’s internal evaluation, testing, and familiarization purposes, and strictly in accordance with the terms and conditions set forth herein. Authorized Use does not include: (a) use of the Service by, or on behalf of, any entity that is not Subscriber or a Permitted Affiliate; (b) the right to resell, sublicense, or make the Service available to any third party; or (c) the right to modify, reverse engineer, reproduce, create derivative works from, or disclose any component of the Service to any third party.
1.2. “Authorized Users” means any employee, contractor, or authorized representative of Subscriber or a Permitted Affiliate who accesses or uses the Service on Subscriber’s behalf. Subscriber is responsible for all acts and omissions of its Authorized Users in connection with the Service. There is no limit on the number of Authorized Users, provided that access remains within the scope of Authorized Use.
1.3. “Data” means any information, content, or materials submitted by Subscriber or its Authorized Users to the Service in connection with Authorized Use.
1.4. “Documentation” means the user manuals and supporting materials (if any) provided by Provider in connection with the Service, whether in printed or electronic form.
1.5. “Effective Date” means the date Subscriber first accepts these Terms.
1.6. “Feedback” means any suggestion, enhancement request, recommendation, correction, or other input provided by Subscriber or its Authorized Users to Provider regarding the Service or SDK.
1.7. “Hosting Environment” means the cloud infrastructure or data center environment through which Provider makes the Service available to Subscriber.
1.8. “Incident” means any actual or reasonably suspected unauthorized access to, use of, disclosure of, modification of, or destruction of Subscriber Data, or any event that materially disrupts or threatens to disrupt the availability, integrity, or confidentiality of the Service or Subscriber Data.
1.9. “Intellectual Property Rights” means all inventions, patents and patent applications, works of authorship, copyrights, trademarks, know-how, show how, trade secrets, and other similar proprietary rights throughout the world, whether arising under federal, state, common, foreign law, or otherwise.
1.10. “Permitted Affiliates” means Subscriber’s wholly-owned subsidiaries and affiliates. Access by Permitted Affiliates is part of Subscriber’s access and does not require separate agreements, provided that Subscriber remains liable for each Permitted Affiliate’s compliance with these Terms.
1.11. “Provider” means Raft, LLC.
1.12. “Service” means the hosted software solutions set forth in Schedule B, made available by Provider at no charge via the Hosting Environment. The Service does not include installation of software on Subscriber-controlled systems. The Service constitutes “commercial computer software” as that term is defined in FAR 2.101 and DFARS 252.227-7014(a)(1) as applicable, and is developed exclusively at private expense.
1.13. “Software Development Kit” or “SDK” means any software development kit, including libraries, sample code, application programming interfaces (“APIs”), tools, plug-ins, documentation, and related materials, provided by Provider to Subscriber in connection with the Service, as identified in Schedule B. The SDK is an optional feature of the Service and is made available as described in Schedule B.
1.14. “Subscriber Integration” means any software application, module, or interface created by Subscriber using the SDK that interfaces with the Service, but does not include any portion of the Service itself or any modification or derivative thereof.
2. Access Rights and Restrictions
2.1 Grant of Access. Subject to and conditioned upon Subscriber’s compliance with these Terms, Provider grants Subscriber a limited, non-exclusive, non-assignable, non-sublicensable, non-transferable right to access and use the Service during the Term solely for Authorized Use. This grant includes:
a) The right to permit any number of Authorized Users to access the Service via Provider-designated interfaces;
b) The right to extend access to Permitted Affiliates, provided that Subscriber remains liable for each Permitted Affiliate’s compliance with these Terms;
c) The right to use any APIs provided with the Service solely to create interfaces between the Service and Subscriber’s internal systems; and
d) The right to access and use the Documentation solely to support Authorized Use.
2.2. Restrictions. The rights granted in Section 2.1 are subject to the following restrictions. Subscriber may not:
a) attempt to access, copy, modify, or derive source code or underlying algorithms of the Service;
b) use the Service for commercial time-sharing, service bureau, or rental purposes without prior written consent of Provider;
c) use the Service in violation of applicable law or regulation, or in conjunction with third-party software in violation of that software’s terms;
d) make the Service available to any entity other than Subscriber and its Permitted Affiliates, or permit access by any person acting outside the scope of Authorized Use;
e) attempt to circumvent or disable any security or access control mechanism of the Service;
f) remove or obscure any proprietary notices contained in or on the Service or Documentation; or
g) use the Service, Documentation, or SDK to develop, directly or indirectly, any product or service intended to compete with or serve as a substitute for the Service, or perform or publish any benchmark or performance test of the Service or SDK without Provider’s prior written consent.
2.3 No Source Code. The Service is made available as a hosted solution. Nothing in these Terms grants any license to underlying source code of the Service.
2.4 No Implied License. All rights not expressly granted herein are reserved. Nothing in these Terms shall be construed to grant any license by implication, estoppel, or otherwise. For the avoidance of doubt, nothing in these Terms grants Subscriber any rights in or to any Provider technology, platform, or intellectual property outside the scope of the Service and Documentation as expressly identified in Schedule B.
2.5 Assignment. Neither these Terms nor any rights hereunder may be assigned or transferred by Subscriber, in whole or in part, by operation of law or otherwise, without Provider’s prior written consent, except that Subscriber may assign these Terms without consent to a successor entity in connection with a merger, acquisition, or sale of all or substantially all of Subscriber’s assets, provided that: (i) Subscriber provides Provider with written notice promptly following such assignment; and (ii) the successor entity agrees in writing to be bound by these Terms. Provider may assign these Terms in connection with a merger, acquisition, or sale of all or substantially all of its assets upon written notice to Subscriber. Any attempted assignment not permitted by this Section shall be void and of no effect.
2.6 Compliance Verification. Subscriber shall maintain reasonable records sufficient to demonstrate compliance with the use restrictions in these Terms and shall, upon written request no more than once annually, certify in writing its compliance with those restrictions. Provider’s right to verify compliance is limited to Subscriber’s adherence to the use restrictions in Section 2.
2.7 Not a Sale. The parties agree that these Terms grant a right of access only and do not constitute a sale of the Service or any component thereof. All Intellectual Property Rights in the Service and Documentation remain Provider’s sole and exclusive property.
2.8 Acceptable Use. Subscriber’s and Authorized Users’ use of the Service is subject to Provider’s Acceptable Use Policy (“AUP”), as published by Provider at [INSERT URL] and updated from time to time on reasonable notice to Subscriber. In the event of conflict between the AUP and these Terms, these Terms control. The AUP governs prohibited uses including without limitation: spam and unsolicited communications, illegal content, automated scraping, intentional interference with the Service, and use in violation of applicable law. Subscriber is responsible for ensuring that its Authorized Users comply with the AUP.
2.9 SDK Terms.
a) License Grant. Subject to and conditioned upon Subscriber’s compliance with these Terms, Provider grants Subscriber a limited, non-exclusive, non-assignable, non-sublicensable, non-transferable license during the Term to: (i) access and use the SDK via Provider-designated delivery mechanisms, including any developer portal or package registry identified in Schedule B, solely for developing Subscriber Integrations; (ii) use the SDK documentation solely to support development of Subscriber Integrations; and (iii) reproduce SDK sample code solely as incorporated into Subscriber Integrations for use with the Service.
b) Restrictions. Subscriber shall not: (i) distribute, sublicense, or make the SDK available to any third party, including contractors or systems integrators, without Provider’s prior written consent; (ii) use the SDK to develop any application or interface other than Subscriber Integrations as defined herein; (iii) use the SDK in any manner that circumvents the access or use restrictions applicable to the Service under Section 2.2; (iv) combine or distribute any portion of the SDK with open-source software in a manner that would require the SDK or any portion thereof to be disclosed, licensed, or distributed under open-source terms; or (v) remove or alter any proprietary markings or license notices in the SDK.
c) Subscriber Integrations. As between the parties, Subscriber retains ownership of the original elements of Subscriber Integrations, subject to Provider’s underlying rights in the Service and SDK. Subscriber acknowledges that Subscriber Integrations that incorporate SDK components are subject to, and may only be used in accordance with, these Terms. Subscriber Integrations do not constitute the Service and are not entitled to support or maintenance from Provider unless separately agreed in writing.
d) Feedback. Subscriber hereby grants Provider a perpetual, irrevocable, worldwide, royalty-free, fully paid-up license to use, incorporate, and exploit any Feedback in any manner, including in future versions of the Service or SDK, without obligation of compensation, attribution, or confidentiality to Subscriber. Subscriber represents that it has the right to provide such Feedback free of third-party claims.
e) No Warranty on SDK. THE SDK IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND. PROVIDER DISCLAIMS ALL WARRANTIES WITH RESPECT TO THE SDK, EXPRESS OR IMPLIED, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. PROVIDER SHALL HAVE NO OBLIGATION TO PROVIDE SUPPORT, UPDATES, OR MAINTENANCE FOR THE SDK UNLESS SEPARATELY AGREED IN WRITING.
f) SDK Audit. Provider’s compliance verification right under Section 2.6 extends to Subscriber’s use of the SDK and the development and deployment of Subscriber Integrations.
g) API and SDK Usage Monitoring. Provider may monitor API calls and SDK usage patterns for purposes of security monitoring, abuse detection, service integrity, and compliance with these Terms. Provider shall not use such monitoring data for any commercial purpose unrelated to providing the Service, and shall not disclose such data to any third party except as required by law or as necessary to investigate a suspected security incident or breach of these Terms.
h) Effect of Termination. Upon expiration or termination of these Terms, all SDK license rights shall immediately terminate. Subscriber shall promptly cease all use of the SDK, delete all copies from its systems, and cease operation of all Subscriber Integrations. The certification obligation in Section 7.4 extends to the SDK and all copies thereof.
3. Provider Hosting Obligations
3.1 Hosting; No Availability Commitment. Provider will use commercially reasonable efforts to make the Service available but provides the Service on an “as-is” and “as-available” basis, with no service-level agreement, uptime or availability commitment, service credit, or availability remedy of any kind. Provider may suspend, limit, interrupt, or discontinue the Service, in whole or in part, at any time, for any reason, with or without notice. Provider’s hosting obligations are limited to the Hosting Environment and do not extend to Subscriber-controlled infrastructure.
3.2 Scheduled Maintenance. Provider may perform maintenance on the Service at any time and is not required to provide advance notice.
3.3 Updates and Modifications. Provider may modify or update the Service from time to time, including to address security vulnerabilities, improve functionality, or comply with applicable law. Provider may modify, update, or discontinue the Service, in whole or in part, at any time without advance notice.
3.4 Subprocessors. Provider may engage subprocessors, including cloud infrastructure providers, to support delivery of the Service. Provider shall ensure that any subprocessor is bound by data protection and confidentiality obligations no less protective than those imposed on Provider under these Terms. Provider remains responsible for the acts and omissions of its subprocessors with respect to the Service and Subscriber Data. Provider shall notify Subscriber of any material change to its subprocessor arrangements that may affect the security or availability of the Service. If Subscriber reasonably objects in writing to a proposed material subprocessor change within ten (10) days of Provider’s notice, the parties shall discuss the objection in good faith. Provider may nonetheless proceed with the subprocessor change following such discussion, in which case Subscriber’s sole remedy shall be to terminate these Terms for convenience pursuant to Section 7.3.
4. Third-Party Software and Infrastructure
4.1 The Service may incorporate third-party software, including open-source components. Subscriber’s right to use such components is limited to use within the Service as permitted by these Terms. Schedule B or the Documentation will identify material third-party software components and applicable license terms. In the event of conflict between these Terms and applicable third-party license terms, the third-party terms shall control with respect to those components.
4.2 Provider is responsible for maintaining the Hosting Environment. Subscriber is responsible for obtaining, at its own expense, any third-party equipment, software, or connectivity necessary to access the Service from Subscriber’s systems.
5. Subscriber Data
5.1 Subscriber Data Ownership. As between the parties, Subscriber retains all right, title, and interest in and to the Data. Provider acquires no rights in the Data except as necessary to provide the Service under these Terms.
5.2 Provider Data Obligations. Provider shall implement and maintain reasonable technical and organizational security measures appropriate to the nature of the Data to protect it against unauthorized access, disclosure, modification, or loss, as further described in Section 12. Provider’s security obligations are defined exclusively by Section 12 and this Section 5.2; no additional obligations shall be implied from the nature of the Data or Subscriber’s industry.
5.3 Permitted Uses of Data.
(a) Provider may use Data as follows: (i) to provide, operate, maintain, and improve the Service for Subscriber; (ii) to monitor and ensure the security, integrity, and availability of the Service; (iii) to comply with applicable law or respond to lawful governmental requests; and (iv) in aggregated, anonymized, or de-identified form that cannot reasonably be used to identify Subscriber or any individual, for purposes of product development, service analytics, benchmarking, and improvement of Provider’s offerings.
(b) Provider shall not sell Subscriber’s Data to any third party. For the avoidance of doubt, Section 5.3(a)(iv) does not permit Provider to disclose identifiable Subscriber Data to third parties or to use identifiable Subscriber Data for Provider’s independent commercial benefit.
(c) Data transmitted to or through the Service via any Subscriber Integration is Data for purposes of these Terms and are subject to this Section 5.3 and the restrictions set forth in Section 5.4. Provider’s rights with respect to such data are neither expanded nor reduced by the manner of its transmission.
5.4 Restrictions on Data Disclosure. Provider shall not disclose Data to any third party except: (a) as necessary to provide the Service using subprocessors in accordance with Section 3.4; (b) as required by applicable law, regulation, or valid legal process; or (c) as expressly permitted by Subscriber in writing. In the event Provider is required by law or legal process to disclose Data, Provider shall, to the extent permitted by law, provide Subscriber with prompt written notice and cooperate with Subscriber’s reasonable efforts to limit the scope of such disclosure.
5.5 Data Return and Deletion. Upon expiration or termination of these Terms, Provider shall, at Subscriber’s written request made within thirty (30) days of the effective date of termination or expiration, provide Subscriber with a reasonable export of its Data in a commonly usable format. Provider shall have no obligation to maintain Data beyond ninety (90) days following the effective date of termination or expiration, after which Provider may delete or destroy Data in the ordinary course of its data management practices. Provider shall certify such deletion in writing upon Subscriber’s written request.
5.6 Regulated Data; Data Processing Addendum. The Service is a general commercial offering not specifically designed or certified for any particular regulated data category. Subscriber is solely responsible for determining whether the Service is appropriate for its intended use and for ensuring compliance with all laws and regulations applicable to the Data Subscriber submits to the Service, including without limitation HIPAA, GLBA, FERPA, CCPA, GDPR, and any other privacy, data protection, or sector-specific regulatory frameworks. Subscribers whose use of the Service involves regulated personal data or data subject to heightened legal requirements should request Provider’s Data Processing Addendum prior to submitting such data to the Service. Provider makes no representation that the Service satisfies any particular regulatory framework applicable to Subscriber’s business absent a separately executed addendum.
6. Term
6.1 Term. These Terms take effect on the Effective Date and continue in effect until terminated in accordance with Section 7 or until Provider discontinues the Service in accordance with Section 3.1 (the “Term”). There is no fixed or minimum term, and no fees are due for any period.
7. Termination
7.1 Termination for Cause. Either party may terminate these Terms upon thirty (30) days’ written notice if the other party materially breaches these Terms and fails to cure such breach within the notice period. Notwithstanding the foregoing, if Subscriber materially breaches the same obligation more than once in any twelve (12)-month period, Provider may terminate these Terms immediately upon written notice without a cure period on the second or any subsequent breach of that obligation.
7.2 Termination for Insolvency. Either party may terminate these Terms immediately upon written notice if the other party: (a) admits in writing its inability to pay its debts generally as they become due; (b) makes a general assignment for the benefit of creditors; (c) institutes proceedings to be adjudicated as voluntary bankrupt or consents to the filing of a petition of bankruptcy against it; (d) is adjudicated by a court of competent jurisdiction as being bankrupt or insolvent; or (e) has a decree entered against it by a court of competent jurisdiction appointing a receiver, liquidator, trustee, or assignee in bankruptcy or in insolvency covering all or substantially all of its property.
7.3 Termination for Convenience.
a) By Subscriber. Subscriber may terminate these Terms for convenience upon thirty (30) days’ written notice to Provider.
b) By Provider. Provider may terminate these Terms for convenience upon ninety (90) days’ written notice to Subscriber.
7.4 Effect of Termination. Upon termination or expiration of these Terms: (a) all access rights granted hereunder shall immediately terminate; (b) Subscriber shall cease all use of the Service; and (c) the Data return and deletion procedures in Section 5.5 shall apply.
7.5 Injunctive Relief. The parties acknowledge that breach of the use restrictions or confidentiality obligations in these Terms may cause irreparable harm not compensable by money damages alone, and that the non-breaching party shall be entitled to seek injunctive or other equitable relief without posting bond. Equitable remedies are in addition to, and not in lieu of, all other remedies available at law or equity.
8. Fees
8.1 No Fees. The Service is provided to Subscriber at no charge. Provider does not charge, and Subscriber has no obligation to pay, any subscription, license, usage, maintenance, or other fees for access to or use of the Service (including the SDK) under these Terms. Any paid or on-premises deployment of Provider’s software will be governed by a separate end-user license agreement (EULA).
9. Proprietary Information
9.1 Definition. “Proprietary Information” means nonpublic, confidential, and proprietary information disclosed by one party (the “Disclosing Party”) to the other (the “Receiving Party”), including without limitation technical information, software, algorithms, business plans, financial information, client information, and any other information that the Receiving Party knows or reasonably should know is proprietary to the Disclosing Party. Proprietary Information includes the Service, Documentation, and these Terms. Subscriber Data is Subscriber’s Proprietary Information and is additionally governed by Sections 5 and 12.
Proprietary Information does not include information that: (i) is or becomes publicly available through no fault of the Receiving Party; (ii) was already known to the Receiving Party without restriction prior to disclosure; (iii) is lawfully disclosed by a third party not under a confidentiality obligation to the Disclosing Party; or (iv) is independently developed by the Receiving Party without reference to the Disclosing Party’s Proprietary Information.
9.2 Obligations. The Receiving Party shall: (a) hold Proprietary Information in strict confidence using measures no less protective than those it uses for its own most sensitive confidential information; (b) use Proprietary Information solely in connection with these Terms – meaning, in the case of Subscriber, for Authorized Use of the Service, and in the case of Provider, for performance of its obligations under these Terms (the “Permitted Purpose”); (c) limit access to those employees and authorized representatives who need to know and who are bound by confidentiality obligations no less restrictive than those set forth herein; and (d) not disclose Proprietary Information to any third party without the Disclosing Party’s prior written consent.
9.3 Compelled Disclosure. A party may disclose Proprietary Information pursuant to a valid court order, governmental requirement, or applicable law. The Receiving Party shall use best efforts to provide the Disclosing Party with prompt written notice to the extent permitted by applicable law, seek confidential treatment of any Proprietary Information so disclosed, and limit the scope of disclosure to the minimum required. The Receiving Party’s obligation to provide notice shall not apply where prohibited by law or where the Receiving Party reasonably determines that compliance with applicable law or a valid legal order requires immediate disclosure.
9.4 Unauthorized Disclosure. The Receiving Party shall notify the Disclosing Party immediately upon discovery of any unauthorized use or disclosure of Proprietary Information and shall cooperate fully in minimizing harm from such disclosure, including taking steps to recover such Proprietary Information and prevent further unauthorized use or disclosure. Such remedy shall be in addition to and not in lieu of any other rights and remedies the Disclosing Party may have at law or in equity.
10. Warranties and Limitations
10.1 Provider Warranty. Provider warrants that, during the Term:
a) the Service will perform materially in accordance with the Documentation; and
b) Provider has the right to grant the access rights set forth in these Terms free of any third-party claims.
Provider’s sole obligation for breach of the warranty in Section 10.1(a) shall be to use commercially reasonable efforts to correct the non-conforming functionality. If correction is not commercially feasible within a reasonable time, Provider shall notify Subscriber and, at Subscriber’s election, terminate access to the affected Service (no refund being available, as the Service is provided at no charge). For the avoidance of doubt, Provider’s sole obligation with respect to any claim that the Service infringes a third-party Intellectual Property Right is the warranty remedy set forth in this Section 10.1. No additional IP indemnification obligation shall be implied from the warranty in Section 10.1(b) or any other provision of these Terms.
10.2 Disclaimer. EXCEPT AS EXPRESSLY SET FORTH IN SECTION 10.1, PROVIDER DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, WITH RESPECT TO THE SERVICE, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. PROVIDER DOES NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED OR ERROR-FREE, OR THAT ALL DEFECTS WILL BE CORRECTED.
10.3 Consequential Damages Waiver. IN NO EVENT SHALL EITHER PARTY BE LIABLE FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL, OR PUNITIVE DAMAGES ARISING OUT OF OR IN CONNECTION WITH these Terms, REGARDLESS OF THE FORM OF ACTION AND WHETHER IN CONTRACT, TORT, STRICT LIABILITY, OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING WAIVER SHALL NOT APPLY TO EITHER PARTY’S INDEMNIFICATION OBLIGATIONS UNDER SECTION 11 WITH RESPECT TO THIRD-PARTY CLAIMS.
10.4 Liability Cap. PROVIDER’S AGGREGATE LIABILITY ARISING OUT OF OR RELATED TO THESE TERMS SHALL NOT EXCEED ONE U.S. DOLLARS (US$1) IN THE AGGREGATE. THE LIABILITY CAP IN THIS SECTION 10.4 SHALL NOT APPLY TO EITHER PARTY’S INDEMNIFICATION OBLIGATIONS UNDER SECTION 11 WITH RESPECT TO THIRD-PARTY CLAIMS.
11. Indemnification
11.1 Subscriber agrees to indemnify, defend, and hold harmless Provider from and against any third-party claims, damages, losses, costs, and expenses (including reasonable attorneys’ fees) arising from: (a) Subscriber’s use and/or misuse of the Service and/or Materials; (b) Subscriber’s breach of these Terms; or (c) any Data submitted by Subscriber that infringes the intellectual property or privacy rights of any third party.
12. Data Protection and Security
12.1 Security Measures. Provider acknowledges that the Service may process sensitive information and agrees to implement and maintain appropriate technical and organizational security measures to protect Subscriber Data against unauthorized access, disclosure, modification, or loss. Such measures may include, by way of example and without commitment to any specific control or standard: (a) encryption of Data in transit using TLS 1.2 or higher; (b) encryption of Data at rest using AES-256 or equivalent; (c) multi-factor authentication for all administrative and Authorized User access; and (d) access controls limiting Data access to personnel who require it to perform their obligations under these Terms.
12.2 Incident Response. Provider will use commercially reasonable efforts to notify Subscriber without undue delay after Provider confirms an Incident affecting Subscriber Data. Such notification shall include, to the extent then known: (a) the nature and scope of the Incident; (b) the Data affected; (c) Provider’s immediate response actions; and (d) Provider’s proposed remediation plan. Provider shall keep Subscriber reasonably informed of material developments in Provider’s investigation and remediation of the Incident and shall notify Subscriber in writing when the Incident has been remediated and the affected systems restored to normal operation. Provider shall cooperate with Subscriber’s reasonable requests for information directly related to the Incident, subject to: (i) Provider’s legal obligations and the advice of counsel; (ii) Provider’s confidentiality obligations to third parties; and (iii) Provider’s reasonable operational constraints. Such cooperation shall not require Provider to disclose information about other customers, provide access to Provider’s internal systems, or waive any applicable privilege.
12.3 Subscriber Security Obligations. Subscriber shall: (a) ensure that Authorized Users comply with all applicable security protocols in their use of the Service; (b) promptly notify Provider of any suspected compromise of Authorized User credentials; (c) promptly notify Provider of any suspected compromise of any API keys or integration credentials used in connection with any Subscriber Integration; (d) implement reasonable security controls over any Subscriber Integration that accesses the Service, including access controls, credential rotation, and transport security using commercially reasonable, industry-standard measures; (e) implement reasonable access controls governing its Authorized Users’ use of the Service; and (f) assess its own data protection and regulatory compliance obligations arising from its industry or jurisdiction and ensure that is use of the Service and any Subscriber Integration is consistent with those obligations. Provider makes no representation that the Service or SDK satisfies any particular regulatory framework applicable to Subscriber’s business.
13. U.S. Government End Users
13.1 The Service is “commercial computer software” as that term is defined in FAR 2.101 or DFARS 252.227-7014(a)(1), as applicable, and was developed exclusively at private expense. U.S. Government subscribers acquire rights in the Service subject to these Terms as specified in FAR 12.212 or DFARS 227.7202, as applicable, except as follows:
a) Section 7.1 (Termination for Cause) shall not apply;
b) Section 6.2 (Auto-Renewal) shall not apply and renewal shall require an affirmative order or contract modification;
c) Section 11 (Indemnification) shall not apply; and
d) Section 15.8 (Governing Law) shall not apply and disputes shall be resolved under the applicable government contract vehicle in accordance with federal procurement law.
13.2 Any provision of these Terms deemed inconsistent with applicable Federal procurement law shall be severed and replaced by the applicable FAR or DFARS clause incorporated into the relevant government contract.
14. Export Controls
14.1 Subscriber agrees to comply fully with all relevant export laws and regulations of the United States, including, but not limited to, the U.S. Export Administration Regulations (“U.S. Export Controls”). Without limiting the generality of the foregoing, Subscriber expressly agrees that it shall not, and shall cause its Authorized Users and representatives to agree not to, export, directly or indirectly, re-export, divert, or transfer the Service or any direct product thereof to any destination, company, or person restricted or prohibited by any U.S. Export Controls.
15. Miscellaneous
15.1 Headings. Headings are for convenience only and shall not affect interpretation.
15.2 Force Majeure. Neither party shall be liable for delays caused by events beyond its reasonable control, including acts of nature, acts of governmental authority, or third-party infrastructure failures. Provider shall notify Subscriber promptly of any force majeure event and shall use commercially reasonable efforts to restore the Service.
15.3 Waiver. No delay or failure of either party in exercising any right hereunder, nor any partial exercise thereof, shall be deemed a waiver unless evidenced by a signed writing expressly waiving such right.
15.4 Trademarks. Each party retains all rights in its own trademarks and service marks. No party shall use the other party’s marks without prior written consent, except that Provider may identify Subscriber as a customer on its standard customer lists and in public filings required by law.
15.5 Independent Contractors. The parties are independent contractors. Nothing in these Terms creates a partnership, joint venture, agency, or employment relationship.
15.6 Notices. Notices shall be in writing and effective when delivered in person, by registered or certified mail (return receipt requested), or by personal courier to an appropriate officer of the receiving party at the address of record, or by email with written confirmation of receipt.
15.7 Governing Law and Venue. These Terms shall be governed by and interpreted in accordance with the laws of the Commonwealth of Virginia (without regard to its principles of conflicts of law). The parties consent to the exclusive personal jurisdiction and venue in the state courts located in Fairfax County, Virginia and the United States District Court for the Eastern District of Virginia. Section 13 governs disputes arising under U.S. Government contracts.
15.8 Entire Agreement. These Terms, together with all Schedules (which are hereby incorporated by reference), constitutes the entire agreement of the parties with respect to its subject matter and supersedes all prior and contemporaneous understandings, negotiations, and agreements, written or oral. No amendment shall be binding unless in writing and signed by authorized representatives of both parties. The invalidity of any provision shall not affect the remaining provisions. Notwithstanding the foregoing, Provider may update Schedule B to reflect additions or modifications to the Service upon thirty (30) days’ written notice to Subscriber, provided that such updates do not materially reduce the functionality of the Service as described in Schedule B at the time of execution of these Terms. Provider may update its Acceptable Use Policy upon thirty (30) days’ written notice to Subscriber; continued use of the Service following the effective date of any AUP update constitutes Subscriber’s acceptance of the revised AUP.
15.9 Order of Precedence. In the event of conflict among the documents comprising these Terms, the order of precedence shall be: (1) any separate written agreement for the Service signed by both parties; (2) applicable government contract vehicle terms; (3) these Terms; (4) the remaining Schedules. For the avoidance of doubt, where Subscriber has a separate signed agreement with Provider covering the Service, that agreement governs and these Terms do not apply to use under that agreement.
15.10 Survival. Sections 2.2, 2.3, 2.4, 2.9(d), 2.9(h), 5.1, 5.3, 5.4, 7.4, 7.5, 9, 10.2, 10.3, 10.4, 11, 12, 14, and 15 shall survive expiration or termination of these Terms.
ACCEPTANCE
To
CLOUD HOSTED SOFTWARE TERMS OF USE
By clicking “I AGREE” (or by accessing or using the Service), Subscriber accepts these Terms as of the Effective Date. Acceptance is effected electronically and no handwritten signature is required. The individual accepting represents that they are authorized to bind any organization on whose behalf they accept; where they accept only for themselves, these Terms bind that individual as Subscriber.
SCHEDULE B
SERVICE DESCRIPTION
B.1 Service Modules
| Module | Description | Delivery | Instances |
|---|---|---|---|
[R]DP |
Data Platform module |
Hosted - Provider-managed cloud |
One (1) |
[R]AIMS |
AI Management Suite |
Hosted - Provider-managed cloud |
One (1) |
[R] SDK |
SDK libraries, APIs, sample code, and documentation as delivered by Provider |
Developer portal at https://developer.teamraft.com, WDM buf registry at https://buf.build/raft/wdm, and SDKs at https://github.com/raft-tech/rdp-sdk-go, https://github.com/raft-tech/rdp-sdk-java, https://github.com/raft-tech/rdp-sdk-python, and https://github.com/raft-tech/rdp-sdk-typescript. |
As delivered |
B.2 Third-Party Software Components
Open-source components are incorporated in the Service. Subscriber’s use of such components is limited to use within the Service as permitted by these Terms . Applicable license terms are available upon request.
A complete list of open-source components is available upon written request to Provider.
B.3 Excluded Features and Services
The following are expressly excluded from the Service as described in Schedule B and are not covered by the Subscription Fee unless separately agreed in writing:
| Excluded Item | Notes |
|---|---|
On-premises installation or deployment |
Covered under separate on-premises EULA if applicable |
Custom development or professional services |
Available under separate Statement of Work |
Training and onboarding services |
Available under separate services agreement |
SDK support and maintenance |
SDK provided as-is per Section 2.9(e); support available under separate agreement |