Redis Cloud Agreement

This Redis Cloud Agreement (“Agreement”) is entered into by and between Redis and the Customer identified in the applicable Transaction and is effective upon the completion of a Transaction, which may be through an Order Form, completing an online order, or agreeing to a Marketplace Transaction (“Effective Date”). Redis and Customer are each a “Party” and collectively the “Parties.” This Agreement forms a legally binding contract and describes the Parties’ rights and responsibilities. When you purchase Cloud Services, on behalf of an organization in acceptance of the terms of this Agreement, you represent and warrant that you have the authority to bind that organization.

Appendix 1 – Bring Your Own Cloud Deployment

If Customer elects to deploy the Cloud Services under Customer’s private cloud account, the additional provisions in Appendix 1 apply.

The Parties hereby agree as follows:

1. Definitions.

Capitalized terms not defined elsewhere in this Agreement have the following meanings

Acceptable Use Policy or AUP means the acceptable use policy found at https://redis.io/legal/acceptable-use-policy, as updated by Redis from time to time.

Administrator(s) means a person designated by the Customer to have access to and administer the Cloud Services.

Affiliate(s) means any company controlling, controlled by, or under common control with a Party, where control means ownership, directly or indirectly, of the shares of a company representing fifty percent (50%) or more of the voting rights in the company.

Cloud Services mean the Redis Cloud service or other cloud service provided by Redis, as specified in a Transaction. Cloud Services do not include Previews or Evaluation Services.

Commercial Subscription means a paid or paying subscription to Cloud Services during the Subscription Term pursuant to a Transaction.

Committed Expenditure means the total expenditure committed by Customer for all Commercial Subscriptions of the Cloud Services during the Subscription Term, as specified in the applicable Transaction.

Customer Data means all data submitted by or on behalf of Customer to the Cloud Services.

Customer Property means Customer Confidential Information and Customer Marks.

Documentation means the published technical or user documentation made available by Redis in connection with the Cloud Services at https://redis.io/docs/latest/.

Evaluation Services means a trial access to the Cloud Services.

Maintenance means the incorporation of new features, upgrades, updates, cluster optimization, patches, and/or bug fixes performed on the Cloud Services.

Marketplace means a third-party online marketplace such as Google Cloud Platform, Amazon Web Services, Microsoft Azure Cloud, or other authorized platforms through which Customer completes a Transaction.

Marks means a Party’s trademarks, logos, and service marks.

Network Charges mean variable network charges associated with Customer’s usage of the Cloud Services.

Order Form means an ordering document for the provision of Cloud Services and Services.

Partner means an authorized third-party reseller or distributor of the Cloud Services and Services.

Previews means pre-release previews of Cloud Services features, modules, or new offerings not generally available.

Redis Materials means Documentation, templates, training materials, videos, and other items Redis may provide to Customer through the Cloud Services or as part of Professional Services.

Redis Tools means proprietary tools, libraries, know-how, techniques, and expertise used by Redis to develop Redis Materials.

Services means Support Services and Professional Services.

Service Level Agreement or SLA has the meaning specified in Section 2.5 (Service Level Agreement).

SOW means a statement of work for Professional Services.

Subscription Term means the period of the Commercial Subscription specified in a Transaction and includes the initial term and any renewal terms.

Support Services has the meaning specified in Section 2.7 (Support Services).

Transaction means the offer and acceptance by Customer of Cloud Services and/or Services through: (a) the execution of an Order Form or SOW; (b) completing an online order; (c) a purchase from a Partner; or (d) a Marketplace that includes the applicable pricing and access rights specifics of the Cloud Services.

2. Access and Use of the Cloud Services.

2.1 Access and Use. Subject to the terms and conditions of this Agreement and the applicable Transaction, Redis shall, during the applicable Subscription Term: (a) make the Cloud Services available to Customer up to the number of Cloud Services units specified in a Transaction; (b) allow Administrators to access Customer’s account in the Cloud Services; and (c) allow Customer to use any Redis Materials. Customer may allow Affiliates to: (i) use the Cloud Services used by Customer under a Transaction; or (ii) execute a separate Transaction with Redis subject to the terms of this Agreement, provided that in both cases Customer is responsible for such Affiliate’s compliance with this Agreement. The Cloud Services may contain portions that are separately available from Redis under open source or source available licenses. The rights granted by Redis to Customer under this Agreement supersede the terms of such licenses for those portions of the Cloud Services. Cloud Services are not sold, even if Redis refers to words such as “sale” or “purchase” for convenience.

2.2 Acceptable Use. Customer and its Administrators must comply with the Acceptable Use Policy. Customer shall not (and shall not permit others to) do the following with the Cloud Services: (a) use them in a manner that intentionally circumvents contractual usage restrictions; (b) license, sub-license, sell, re-sell, rent, lease, transfer, distribute, timeshare, or otherwise make any of it available for access by third parties except as otherwise expressly provided in a Transaction; (c) access it for the purpose of developing or operating competing products or services offered to third parties; (d) use it for benchmark testing, performance testing, or comparison to competitive products; or disclose the results of any benchmark test of it to any third party without Redis’ prior written approval, (e) disassemble, reverse engineer or decompile it; (f) copy, create derivative works based on, or otherwise modify it except as permitted in this Agreement; (g) remove or modify a copyright or other proprietary rights notice in it; (h) use it to create, use, send, store or run viruses or other harmful computer code, files, scripts, agents or other programs or otherwise engage in a malicious act or disrupt its security, integrity or operation; (i) use it to access without authorization, or disable, any Redis or third-party data, software or network; or (j) use it to process any unencrypted sensitive personally identifiable information or sensitive personal data, as defined in the European General Data Protection Regulation (EU 2016/679) (“GDPR”) or other applicable privacy laws.

2.3 Customer Data. Customer grants to Redis, its Affiliates, and applicable contractors a worldwide, limited-term license to host, copy, transmit, and display Customer Data, as necessary for Redis to provide the Cloud Services. Customer will: (a) be solely responsible for the nature, quality, and accuracy of the Customer Data; (b) ensure that the Customer Data complies with the terms of this Agreement and all applicable laws; (c) promptly handle and resolve any notices and claims relating to the Customer Data; and (d) ensure that it has the rights to the Customer Data in order to grant Redis the rights specified by this Agreement. Redis has no liability to Customer or any third party as a result of: (i) any unauthorized disclosure or access to an Administrator’s account or Customer Data as a result of Customer’s or an Administrator’s misuse of the Cloud Services or loss or theft of any Administrator password or username, except to the extent resulting from Redis’ gross negligence or willful misconduct; (ii) any deletion, destruction, damage or loss of Customer Data caused by or at the direction of Customer or an Administrator; or (iii) Customer’s failure to maintain adequate security or virus controls in any devices used to access the Cloud Services. Upon termination of this Agreement, Customer can retrieve and/or delete Customer Data from the Cloud Services in accordance with the Documentation. Unless otherwise agreed in writing by the Parties, Redis may delete Customer’s entire usage history and data files after the termination of this Agreement.

2.4 Professional Services. Redis may provide Professional Services subject to the Redis Professional Services Policy available at https://redis.io/legal/redis-professional-services-policy/ ("PS Policy"). Each applicable Transaction will include a description of the Professional Services. All rights and title in and to the Professional Services, Redis Tools, and Redis Materials belong exclusively to Redis, subject to the PS Policy. Redis grants Customer a limited, non-exclusive, non-sublicensable, non-transferable, revocable license during the Subscription Term to use Redis Materials and Redis Tools solely for Customer's internal operations in connection with its authorized use of the Cloud Services.

2.5 Service Level Agreement. Subject to payment of the applicable fees, Redis will provide the Cloud Services and Maintenance pursuant to the Service Level Agreement described at https://redis.io/legal/redis-enterprise-cloud-service-level-agreement.

2.6 Suspension. Customer is responsible for all activities conducted under its and its Administrators' accounts on the Cloud Services. Redis may suspend Customer's or any Administrator's access to the Cloud Services if Redis reasonably believes that (a) Customer has violated this Agreement (including non-payment of applicable fees), (b) Customer’s use of the Cloud Services poses a security risk to the Cloud Services, Redis' infrastructure, or the data of other Redis customers, or (c) suspension is necessary to comply with applicable law, regulation, or court order. Redis will provide Customer with reasonable prior notice of any such suspension unless immediate action is necessary under clauses (b) or (c), in which case Redis will notify Customer to the extent permitted by applicable law. Customer remains responsible for all fees accrued through the date of suspension and will not be entitled to any credit or refund for any period of suspension. During any suspension, Redis will continue to store Customer Data in accordance with this Agreement.

2.7 Support Services. Subject to payment of the applicable fees and in accordance with the Support Policy, during the Subscription Term Redis will provide one of the Support Service levels found at https://redis.io/legal/cloud-support-policy/ (the “Support Policy”) as specified in the corresponding Transaction. The Support Policy is: (a) automatically included with the access and use rights and fees for the Cloud Services; and (b) not separable from the access and use rights provided under this Agreement. Evaluation Services and Previews are not eligible for Support Services.

2.8 Evaluation Services and Previews. Redis may offer Evaluation Services and Previews subject to usage limits designated by Redis or set out in the Redis online price list at https://redis.io/redis-enterprise-cloud/pricing/, and may modify, limit, or discontinue them at any time without prior notice. Customer's use is subject to Section 2.2 (Acceptable Use), and Customer will treat all Preview and Evaluation Services features and related information as Redis' Confidential Information. Evaluation Services and Previews are provided "as-is," "with all faults," and "as-available," may not be used in production environments, and may not operate at the level of generally available offerings. Redis may change or discontinue Previews without releasing them into general availability. Unless otherwise stated in a Transaction, Evaluation Services and Previews are each provided for a term of 30 days. Redis may delete inactive Evaluation Services instances and associated Customer Data after 14 days of inactivity (as determined by the absence of account activity). If Customer does not convert an Evaluation Service or Preview into a Commercial Subscription before expiration of the applicable term, Redis will terminate access and delete associated Customer Data. If Customer exceeds applicable usage limits or continues use beyond the stated term, Redis may, at its option, (a) terminate access and delete associated Customer Data, or (b) convert such usage to a Commercial Subscription at then-current list rates by issuing a Transaction to Customer. Customer's continued use of the Cloud Services after receipt of such Transaction constitutes acceptance of its terms, with fees accruing from the date of Redis' notice of conversion. If Customer elects to convert an Evaluation Service or Preview into a Commercial Subscription, such conversion will be documented in a Transaction. For any conversion, whether at Redis' or Customer’s election, Customer Data and configurations will carry over to the Commercial Subscription. The indemnities, warranties, and SLA do not apply to Evaluation Services or Previews.

3. Fees and Cloud Service Charges.

3.1 Fees. Customer agrees to pay all fees specified in the applicable Transaction. Unless otherwise specified in a Transaction (a) all fees are payable in United States Dollars, and (b) the first invoice is issued upon execution of the applicable Transaction. All payment obligations are non-cancelable and all payments are non-refundable, except as expressly stated in this Agreement. All fees are exclusive of taxes, and Customer shall pay all applicable sales, usage, excise, value-added, and similar taxes imposed in connection with this Agreement, excluding taxes based on Redis’ net income. If applicable law requires Customer to withhold any amount, Customer will provide Redis with related documentation and cooperate in seeking a waiver or reduction. Overdue payments are subject to a late charge at the lesser of 1.5% per month or the maximum rate permitted by applicable law. Any third-party payment processing fees selected by Customer will be included on applicable invoices.

3.2 Marketplace and Partner Purchases. If Customer's Transaction is through a Marketplace or Partner, Customer will pay the applicable Marketplace or Partner directly and is responsible for full payment of fees for the Subscription Term, regardless of usage or billing terms between Customer and the Marketplace or Partner. Customer's acceptance of Marketplace or Partner terms binds Customer to the obligations of this Agreement. If for any reason Redis does not receive the full Transaction fees from the applicable Marketplace or Partner, Redis may invoice Customer directly for any outstanding amounts and Customer shall pay such amounts in accordance with this Agreement.

3.3 Cloud Services Charges. Redis charges for the Cloud Services based on Customer's Committed Expenditure and actual usage. Customer shall pay the Committed Expenditure regardless of its level of use of the Cloud Services. Network Charges are passed through to Customer as described in the applicable Transaction.

3.5 Authorizing Payment. By providing a credit card or other payment method accepted by Redis (“Payment Method”) in connection with the Transaction, Customer is authorizing Redis to charge the applicable fees to the Payment Method. If applicable to a Transaction, Customer authorizes Redis to charge a recurring monthly charge based on the then-current Redis online price list.

4. Confidential Information.

4.1 Definition. A Party may disclose Confidential Information to the other Party under this Agreement in furtherance of the business relationship (the “Purpose”). “Confidential Information” means non-public information disclosed by one Party (“Discloser”) to the other Party (“Recipient”) that is shared, whether orally or in writing, that is designated as confidential, or that reasonably should be understood to be confidential given the nature of the information and the circumstances of disclosure, including copies and derivatives. Confidential information includes the Cloud Services, Customer Property, Redis Materials, Redis Tools, the Agreement terms, the Transaction terms, and Redis security or other sensitive documentation (such as a SOC 2 Type II report). Confidential Information does not include information that: (a) is or becomes publicly available through no fault of Recipient; (b) was known to Recipient, free of any confidentiality obligations, before receipt; (c) becomes known to Recipient, free of any confidentiality obligations, from a source other than Discloser; or (d) is independently developed by Recipient without the use of Confidential Information.

4.2 Obligations. Recipient will not reproduce, use, disseminate, or disclose Confidential Information to any person or entity, except to its authorized employees, Affiliates, consultants, or advisors (collectively, “Representatives”), who need to know the Confidential Information to further the Purpose and are bound by obligations at least as restrictive as this Agreement before having access to Confidential Information. Recipient is responsible for the acts and omissions of its Representatives under this Agreement. Recipient will not modify, reverse engineer, create other works from, or disassemble any software programs contained in the Confidential Information without Discloser’s written approval. Recipient will treat all Confidential Information with at least the same degree of care as it treats its own information of similar sensitivity, but never less than reasonable care. Recipient may disclose Confidential Information: (a) upon Discloser’s written approval; and (b) as necessary to respond to a valid order by a court or governmental body, as required by law, or as necessary to establish the rights of either Party, provided that Recipient promptly notifies Discloser upon receipt of a disclosure order and requests confidential treatment of any affected Confidential Information. Subject to applicable law, Recipient shall comply with its confidentiality and nondisclosure obligations under this Agreement for 5 years after termination of the Agreement (except for trade secrets, which must be kept in confidence in perpetuity). Upon written request of the Discloser or at the termination of this Agreement, Recipient will promptly return to Discloser or destroy (or in the case of electronic data, use commercially reasonable efforts to delete or render practicably inaccessible by Recipient) Confidential Information of Discloser, except as otherwise required by law or pursuant to a bona fide archival or document retention policy.

4.3 Rights. All Confidential Information remains the property of Discloser. Recipient does not receive any license or intellectual property rights to Discloser’s Confidential Information. The Parties agree that the Recipient’s disclosure of Confidential Information, except as provided herein, may result in irreparable injury for which monetary damages may be inadequate. The Parties further agree that in the event of such disclosure or threatened disclosure, the Discloser may be entitled to seek an injunction to prevent the breach or threatened breach, in addition to remedies otherwise available to the Discloser at law or in equity. If the Parties have executed a separate non-disclosure or confidentiality agreement (an “NDA”) related to the purpose of this Agreement, this Section will supersede and replace such NDA.

5. Intellectual Property and Data Security.

5.1 Ownership. All rights, title, and interest in and to all intellectual property rights in the Cloud Services, Services, Evaluation Services, Previews, Redis Materials (except to the extent of Customer Property incorporated therein), and Redis Tools are owned exclusively by Redis notwithstanding any other provision in this Agreement. Except as expressly provided in this Agreement, Redis reserves all rights in the Cloud Services, Previews, Redis Tools, and Redis Materials and does not grant Customer any rights, express, implied, or by estoppel. Redis may inspect Customer's records relating to its use of the Cloud Services to verify compliance with this Agreement for up to 1 year following termination. All rights, title, and interest in and to all intellectual property rights in Customer Data and Customer Property are owned exclusively by Customer notwithstanding any other provision in this Agreement.

5.2 Usage Data and Feedback. Except as expressly provided in this Agreement, Customer reserves all rights in the Customer Data and does not grant Redis any rights, express or implied, or by estoppel. Redis owns the statistical usage data derived from the operation of the Cloud Services (“Usage Data”). Nothing herein will be construed as prohibiting Redis from utilizing the Usage Data to optimize and improve the Cloud Services or otherwise operate Redis’ business. If Redis provides Usage Data to third parties, such Usage Data shall be de-identified and presented in the aggregate so that it will not disclose the identity of Customer to any third party. Redis encourages Customer to provide suggestions, proposals, ideas, recommendations, or other feedback regarding improvements to Redis’ products and services. If Customer provides such feedback, Customer grants to Redis a royalty-free, fully paid, sub-licensable, transferable, non-exclusive, irrevocable, perpetual, worldwide right and license to make, use, sell, offer for sale, import, and otherwise exploit feedback (including by incorporation of such feedback into the Cloud Services, or Redis Materials) without restriction.

5.3 Data Security and Data Privacy. Redis shall: (a) maintain appropriate administrative, physical, and technical safeguards to protect the security and integrity of the Cloud Services and the Customer Data; (b) protect the confidentiality of the Customer Data in accordance with the Agreement; and (c) access and use the Customer Data solely to perform its obligations under the Agreement or as otherwise permitted by Customer. These measures will conform with the Redis Technical and Organizational Security Measures (“TOMs”) available at https://redis.io/legal/redis-technical-and-organizational-security-measures/. Redis will not materially diminish the protections in the TOMs during the Subscription Term. To the extent the EU Data Act (Regulation (EU) 2023/2854) applies to Customer and the Cloud Services, the Redis EU Data Act Addendum available here https://redis.io/legal/redis-eu-data-act-addendum/ will apply. The Redis Data Processing Addendum available at https://redis.io/legal/data-processing-addendum-dpa/ (“DPA”) applies to Personal Data (as defined in the DPA) contained in Customer Data, to the extent: (i) the GDPR, or (ii) other data protection laws and regulations identified in the DPA, apply. Redis, its Affiliates, and applicable contractors may process business contact information (including, but not limited to, name, address, business telephone, email, and applicable user ID) of Customer, its personnel, Administrators, and other authorized users. Where consent by the individuals (or other notice) is required for such processing, Customer will notify and/or obtain such consent. The Redis Privacy Policy available at https://redis.io/legal/privacy-policy/ governs how Redis processes such data.

6. Warranty and Disclaimer.

6.1 Cloud Services Warranty. Redis warrants that during the applicable Subscription Term: (a) the Cloud Services will perform materially in accordance with the applicable Documentation; (b) Redis shall make commercially reasonable efforts to make the Cloud Services available in accordance with the SLA (except for any unavailability caused by a Force Majeure Event or Maintenance); (c) Redis will employ industry-standard measures to test the Cloud Services to detect and remediate viruses, Trojan horses, worms, logic bombs, or other harmful code or programs designed to negatively impact the operation or performance of the Cloud Services; and (d) it owns or otherwise has sufficient rights in the Cloud Services to grant to Customer the right to use the Cloud Services. If Customer believes there has been a breach of this warranty, Customer must promptly notify Redis in writing, stating in reasonable detail the nature of the alleged breach. If there has been a breach of this warranty, then the exclusive remedies will be for Redis to: (i) correct or replace the non-performing components of the Cloud Services at no additional charge to Customer; or (ii) if Redis fails to successfully correct the Cloud Services within a reasonable time of receipt of written notice from Customer detailing the breach, allow Customer to terminate the applicable Transaction and provide a pro-rated refund of the fees prepaid by Customer for the remainder of the Subscription.

6.2 Services Warranty. Redis warrants that the Services will be: (a) performed by Redis personnel with the necessary knowledge, skills, experience, qualifications, and resources to provide; and (b) performed in a work person-like manner consistent with industry standards. If Customer believes there has been a breach of this warranty, Customer must promptly notify Redis in writing following delivery of the Services stating in reasonable detail the nature of the alleged breach. If there has been a breach of this warranty through no fault of Customer, then the exclusive remedy will be for Redis to re-perform the affected Services at no additional charge.

6.3 Mutual Warranty. Each Party represents and warrants that this Agreement has been duly authorized, executed, and delivered and constitutes a valid and binding agreement enforceable against the other Party in accordance with its terms.

6.4 Disclaimer. Except as provided in this warranty Section and to the extent not prohibited by applicable law, the Cloud Services (including Previews and Evaluation Services), Services, and Redis Materials are provided to Customer "as-is" without any warranties of any kind, express or implied, including, but not limited to, any implied warranties of merchantability, fitness for a particular purpose, integration, non-infringement, title, performance, security, and accuracy and any implied warranties arising from statute, course of dealing, course of performance, or usage of trade. All Redis products and services under this Agreement are not designed, manufactured, or intended for use in the planning, construction, maintenance, control, or direct operation of nuclear facilities, aircraft navigation, control or communication systems, weapons systems, direct life support systems, or other mission critical systems. The warranties outlined in this Section apply only if the Cloud Services have been utilized in accordance with the Documentation, this Agreement (including any Transaction), and applicable law. Each Party acknowledges that the disclaimers and limitations in this Agreement are a fundamental part of the basis of the bargain between the Parties and have been taken into account in determining the consideration to be given by each Party under this Agreement.

7. Limitation of Liability.

7.1 Limit on Direct Damages. To the extent not prohibited by law, in no event will either Party’s (or their Affiliates’) total and cumulative liability, for all claims of any nature arising out of or related to this Agreement exceed the total fees paid by Customer to Redis for Commercial Subscriptions in the 12 months preceding the date of the first event which gives rise to liability under this Agreement. This Section does not apply to Section 8 (Indemnification).

7.2 Indirect Damages Disclaimer. To the extent not prohibited by law, in no event will either Party be liable for any indirect, incidental, special, punitive, cover, loss of profits or revenue, loss of goodwill, loss of data, or any consequential damages however caused, whether based in contract, tort, warranty, negligence, or any other theory of liability, even if such Party has been advised as to the possibility of such damages.

7.3 Exceptions to the Limitation of Liability. The limitations of liability and disclaimer of damages do not apply to: (a) any obligation as described in Section 3 (Fees and Cloud Service Charges); or Section 5.1 (Ownership), including payments to a third party; or any liability for: (i) death or bodily injury caused by negligence; (ii) gross negligence; (iii) willful misconduct; or (iv) anything else that cannot be limited by law. Neither Party’s third-party licensors nor suppliers have any liability under this Agreement. The Parties agree that limitations of liability in this Agreement are intended to survive if a Party’s remedy fails of its essential purpose and that the fees for Cloud Services and Services would have been greater without them.

8. Indemnification.

8.1 Indemnification by Redis. Redis will defend Customer against any third-party claim that the Cloud Services infringe a registered patent, registered Mark, or copyright of a third party, or misappropriates a trade secret (“IP Claim”) and will pay Customer for the resulting amounts finally awarded against Customer to such third party by a court of competent jurisdiction or agreed to in settlement. Redis will have no liability to Customer under this Section for any IP Claim that arises out of: (a) any unauthorized use, reproduction, or distribution of the Cloud Services by Customer; (b) use of the Cloud Services in combination with any other services, software, content, data, business process, or equipment not supported in the Documentation if such IP Claim would have been avoided without such combination; (c) any modification or alteration of the Cloud Services by anyone other than Redis; (d) use of any older release of the Cloud Services when a newer version would have avoided the infringement; (e) Redis’ compliance with any materials, designs, specifications or instructions provided by Customer; and/or (f) any infringement of Evaluation Services, Previews, or third-party open source software included within the Cloud Services. In the event of an IP Claim pursuant to this Section, Redis will (at Redis’ option and expense): (i) obtain for Customer the right to continue using the Cloud Services; (ii) modify the Cloud Services to make them non-infringing; or (iii) if subsections (i) and (ii) are not commercially viable (as determined by Redis in its sole discretion), terminate this Agreement, in which case Customer will be entitled to a pro-rated refund of any fees pre-paid by Customer for the remainder of the applicable Subscription Term.

8.2 Indemnification by Customer. Customer will defend Redis against: (a) any third-party claim that any Customer Data, or Customer’s use of the Cloud Services in breach of this Agreement, infringes a registered patent, registered Mark, or copyright, or misappropriates a trade secret (to the extent that such infringement or misappropriation is not the result of Redis’ actions); or (b) any claim relating to Customer’s use of the Cloud Services in violation of Section 2.1 (Access and Use) or Section 2.2 (Acceptable Use) of this Agreement. Customer will, with respect to any claim against Redis that is subject to this Section, indemnify Redis for the resulting costs and damages finally awarded by a court of competent jurisdiction or agreed to in settlement.

8.3 Indemnification Process. As a condition of receiving an indemnification under this Agreement, the Party seeking indemnification (the “Indemnified Party”) will provide the other Party (the “Indemnifying Party”) with: (a) prompt written notice of the claim, provided, however, that the failure to give such notice does not relieve the Indemnifying Party’s obligations except if the Indemnifying Party is prejudiced by such failure; (b) complete control over the defense and settlement of the claim (provided, that the Indemnifying Party will not settle any claim without the Indemnified Party’s prior written consent if the settlement fails to unconditionally release the Indemnified Party from all liability pertaining to such claim, such consent will not be unreasonably withheld, delayed or conditioned); and (c) assistance requested by the Indemnifying Party in connection with the defense and settlement of the claim, at the Indemnifying Party’s expense. The indemnification obligations under this Section state the Indemnifying Party’s entire liability and the Indemnified Party’s exclusive remedy for third-party claims and actions.

9. Term and Termination.

9.1 Agreement Term. This Agreement commences on the Effective Date, and continues for the duration of the Subscription Term, Preview term, or Evaluation Services term unless either Party terminates this Agreement in accordance with this Section. If all Transactions under this Agreement have expired or been terminated, either Party may terminate this Agreement for convenience by providing 30 days’ written notice. Either Party may terminate this Agreement and any applicable Transaction if the other Party materially breaches this Agreement and does not cure such breach within 30 days of written notice. If Customer terminates this Agreement or a Transaction due to Redis' uncured material breach, Redis will provide a pro-rata refund of any fees prepaid by Customer for the unused portion of the applicable Subscription Term. Termination of a Transaction will have no effect on the Agreement, which must be terminated in accordance with its terms. Upon termination of this Agreement, all rights under Section 2.1 (Access and Use) and if applicable, Appendix 1 (Bring Your Own Cloud Deployment), terminate. Upon termination, Customer Data will be available for retrieval and subsequently deleted in accordance with Section 2.3 (Customer Data). Any provisions intended by their nature to survive termination of this Agreement will survive. The Transaction specifies the start and end date of the Commercial Subscription.

10. General.

10.1 Ambiguities. Each Party has participated in the review of this Agreement. Any rule of construction to the effect that ambiguities are to be resolved against the drafting Party does not apply in interpreting this Agreement. The language in this Agreement will be interpreted as to its fair meaning and not strictly for or against any Party.

10.2 Assignment. Customer will not, directly, indirectly, by operation of law or otherwise, assign all or any part of this Agreement or its rights hereunder or delegate performance of any of its duties hereunder without the prior written consent of Redis and such attempt to do so will be null and void. Notwithstanding the foregoing and any non-transferable rights herein, either Party may assign this Agreement to an Affiliate or in connection with a successor in interest in a merger, reorganization, or a sale of all or substantially all the assets of the Party so long as the assigning Party requires the acquirer or successor to agree in writing to be bound by this Agreement as of the effective date of the transfer. Subject to the foregoing restrictions, this Agreement will be fully binding upon, inure to the benefit of and be enforceable by the Parties and their respective successors and assigns.

10.3 Collaboration. Each Party acknowledges that the Marks of the other Party are the property of Redis or Customer, as applicable. Subject to Customer’s ability to revoke consent for use at any time, Redis may reference Customer, or Customer’s Marks (subject to Customer’s applicable brand guidelines), and Customer’s use of the Cloud Services in customer and prospect communications and on Redis’ website. Redis agrees to stop distributing, publicly referencing, and displaying the materials at any time upon written request from Customer.

10.4 Compliance with Laws. The Parties will comply with all laws, statutes, and regulations applicable to them respectively under this Agreement. Each Party agrees that it has not received or been offered any illegal or improper bribe, kickback, payment, gift, or thing of value from any of the other Parties’ Representatives in connection with this Agreement. If a Party becomes aware of any violation of this Section, it will notify the other in accordance with Section 10.10 (Notices).

10.5 Contractual Relationship. The Parties are entering into this Agreement as independent contracting Parties. Neither Party will have, or hold itself out as having, any right or authority to incur any obligation on behalf of the other Party. This Agreement will not be construed to create an association, joint venture, principal-to-agent relationship, or partnership between the Parties or to impose any partnership liability upon any Party.

10.6 Force Majeure. A Party will not be liable for failures or delays in performance due to causes beyond its reasonable control, including, an act of God, fire, earthquake, flood, storm, natural disaster, computer-related attacks, hacking, internet service provider failures, or delays, accident, pandemic, labor unrest, civil disobedience, act of terrorism or act of government (each, a “Force Majeure Event”). The Parties agree to use their best efforts to minimize the effects of any Force Majeure Event. The inability to meet financial obligations or compliance with existing applicable law will not be considered Force Majeure Events.

10.7 Government Users. If Customer is a U.S. government entity or if this Agreement otherwise becomes subject to the Federal Acquisition Regulations (“FAR”), Customer acknowledges that: (a) elements provided herein constitute software, services, and Documentation and are provided as “Commercial Products” and “Commercial Services” as defined at 48 C.F.R. 2.101; and (b) are being licensed as commercial computer software and services, subject to the restricted rights of 48 C.F.R. 2.101 and 12.212.

10.8 Integration; Order of Precedence. This Agreement, any Transaction, Appendix, and SOWs constitute the entire agreement between the Parties and supersede all prior agreements, or communications regarding the subject matter hereof. The terms of this Agreement control over any conflicting or additional terms and conditions of any purchase order, acknowledgement, confirmation, or other document or statement issued by Customer. Notwithstanding the foregoing, in the event of a conflict between this Agreement and any Transaction, the terms of such Transaction prevail solely for purposes of such Transaction.

10.9 Nonwaiver. The failure of either Party to insist upon or enforce strict performance of any of the provisions of this Agreement or to exercise any rights or remedies under this Agreement will not be construed as a waiver or relinquishment to any extent of such Party’s right to assert or rely upon any such provision, right or remedy in that or any other instance; rather, the same will remain in full force and effect.

10.10 Notices. Redis may provide any notice to Customer by sending an email to Customer’s email contact, as provided by Customer, or as designated in this Section. Customer may provide notice to Redis by sending an email to [email protected]. Notices will be: (a) in writing; (b) in English; and (c) treated as received when the email is sent, whether the other Party has received the email or not. Customer is responsible for keeping its designated email contact current throughout the Subscription Term. Customer agrees to send a courtesy copy of any notice sent to: Redis Inc., Attention: General Counsel, 303 2nd St., North Tower, Suite 525, San Francisco, California 94107, U.S.A. Billing notices by Redis will be addressed to the billing contact designated by Customer.

10.11 Redis Entity; Governing Law. The laws governing this Agreement, regardless of conflict of laws principles, and the Redis entity entering into this Agreement with Customer (as applicable, “Redis”), are determined by Customer’s domicile. The following does not limit or restrict either Party from seeking injunctive or other equitable relief from a court of competent jurisdiction.

(a) [AS APPLICABLE] If Customer is domiciled in Asia, Pacific, Americas, or other jurisdictions not listed in (b) or (c) below: (i) the Redis entity that is party to this Agreement is Redis Inc., a Delaware corporation with principal offices located at 303 2nd St., North Tower, Suite 525, San Francisco, California 94107, U.S.A.; and (ii) this Agreement will be construed and enforced in all respects in accordance with the laws of the State of California, U.S.A., without reference to its choice of law rules. The courts located in the County of Santa Clara, California have exclusive jurisdiction for all purposes regarding this Agreement.

(b) [AS APPLICABLE] If Customer is domiciled in Israel: (i) the Redis entity that is party to this Agreement is Redis Ltd., a limited company with registered office at Alon 2 Tower 32nd Floor, 94 Yigal Alon St., Tel-Aviv 6789140, Israel; and (ii) this Agreement will be construed and enforced in all respects in accordance with the laws of the State of Israel without reference to its choice of law rules. The courts located in the Central District of the State of Israel have exclusive jurisdiction for all purposes regarding this Agreement.

(c) [AS APPLICABLE] If Customer is domiciled in Europe, United Kingdom, Middle East, or Africa: (i) the Redis entity that is party to this Agreement is Redis EMEA Ltd., a limited company with registered office at Bridge House, 4 Borough High Street, London, SE1 9QQ, United Kingdom; and (ii) this Agreement will be construed and enforced in all respects in accordance with the laws of England and Wales without reference to their choice of law rules. The competent courts located in London, England have exclusive jurisdiction for all purposes regarding this Agreement.

10.12 Third-party Beneficiaries. Nothing in this Agreement confers, or is intended to confer, to any third party any benefit or the right to enforce any term of this Agreement. Notwithstanding the foregoing, Customer agrees that Redis may enforce its rights for violations of the access rights terms or other use terms of this Agreement, even if such violations are related to, or arising out of an agreement between Customer and a Partner.

10.13 Updates to This Agreement. Redis reserves the right to amend the terms of this Agreement at any time by posting a revised version on Redis’s website for the applicable Cloud Services or by notifying Customer via email. Any amended terms become effective upon posting on the Redis website for the applicable Cloud Services or as stated in an email notice message. By continuing to use the Cloud Services after the effective date of any amendment to the terms of this Agreement, Customer agrees to be bound by the amended terms. Please check our website for the applicable terms regularly. These terms were last amended on the date indicated above.

APPENDIX 1

Bring Your Own Cloud Deployment (“BYOC”)

The following provisions apply when Cloud Services run on virtual machines (“Instances”) and persistent storage devices (“Persistent Storage”) (Instances and Persistent Storage are jointly referred to as “Resources”) under Customer’s BYOC account.

1. Access and Use.

Subject to the Agreement and an applicable Transaction, Redis shall make the Cloud Services available to Customer from within Customer’s BYOC during the applicable Subscription Term.

2. Additional Services.

In addition to the Cloud Services, Redis may: (a) launch Resources in the Customer’s BYOC; (b) shutdown provisioned Resources; (c) operate the Cloud Services on the Resources to support Customer's database needs; and (d) monitor performance and health of the Resources and Cloud Services (collectively, “Additional Services”).

3. BYOC Obligations.

Customer shall: (a) set its account with the applicable cloud provider, so that Redis can self-provision Resources in the Customer’s BYOC; (b) configure its account with the applicable cloud provider, such that Redis shall receive immediate response to any reasonable provisioning request in the Customer’s BYOC; (c) grant Redis predefined access permission defined by Redis (“Permission”) to the Customer’s BYOC, which shall remain continuously enabled at the highest level of user permissions available in Customer's BYOC, to enable Redis to provide the Cloud Services and Additional Services; (d) not terminate or cease the Permission, or prevent Redis access in any other way to any Resources provisioned by Redis in the Customer’s BYOC; (e) not access, connect to, modify, interfere with, or maintain any SSH access or any other administrative access (including via AWS Systems Manager (SSM) or equivalent services) to the Resources provisioned and managed by Redis in the Customer’s BYOC; and (f) upon Redis' written request, submit a reasonably detailed report of the used Resources and/or Cloud Services used during the Subscription Term. If the used Cloud Services under (f) exceed the Cloud Services outlined in the Transaction, Redis will invoice Customer a prorated charge for additional Cloud Services added by Customer during the then-current term at the agreed-upon unit price or, if there is no specified pricing, the fee will be based on the then-current list price (the “True-up Fee”). Customer shall pay the True-up Fee in accordance with the applicable Transaction. Redis will use the Permissions solely to provide the Cloud Services and Additional Services and will not intentionally access, modify, or delete any Customer resources outside the scope of the Cloud Services.

4. Termination.

If Customer: (a) terminates some or all the Resources on the Customer’s BYOC applicable to the Cloud Services and Additional Services; or (b) performs any Identity and Access Management (IAM) changes which affect Redis’ Permission, Redis may, in its sole discretion, notify Customer that Redis will suspend or terminate a Transaction within 3 days of (a) and/or (b) (“Notice Period”). If Customer does not initiate a Support Ticket, and/or is unresponsive to Redis requests during the Notice Period, then Redis will complete the suspension or termination of the Transaction.

5. Miscellaneous.

Customer agrees that Redis will launch in the Customer’s BYOC as many Resources as Redis sees fit to provide the Cloud Services and Additional Services. Redis is not responsible for any damage, loss of data or information, or any other loss that may occur as a result of or in relation to Customer terminating Resources provisioned by Redis in the Customer’s BYOC. Redis is not liable or responsible for any Cloud Services failure resulting from: (a) Customer's failure to fulfill its obligations under this Appendix; (b) Customer’s BYOC technical failures; and/or (c) terms or policy changes effected by the applicable cloud provider to Customer’s BYOC.