SaaS Agreement - SMB (Arizona)

SOFTWARE AS A SERVICE AGREEMENT (SMB)

STATE OF ARIZONA

TABLE OF CONTENTS

1. Parties and Recitals
2. Definitions
3. Access Rights and Restrictions
4. Service Levels and Support
5. Customer Obligations
6. Fees and Payment
7. Data Protection and Security
8. Intellectual Property and Feedback
9. Confidentiality
10. Warranties and Disclaimers
11. Indemnification
12. Limitations of Liability
13. Term, Renewal, and Termination
14. Beta and Free Trials
15. Compliance
16. Governing Law and Dispute Resolution
17. Miscellaneous
18. Signature Blocks
19. Attachments

1. PARTIES AND RECITALS

This Software as a Service Agreement ("Agreement") is entered into as of [__/__/____] ("Effective Date") by and between:

Provider:
Name: [________________________________]
State of Organization: [________________________________]
Principal Address: [________________________________]
Email for Notices: [________________________________]

("Provider")

AND

Customer:
Name: [________________________________]
State of Organization: [________________________________]
Principal Address: [________________________________]
Email for Notices: [________________________________]

("Customer")

Provider and Customer are each a "Party" and collectively the "Parties."

RECITALS

WHEREAS, Provider has developed and operates a cloud-based software application that it makes available to customers on a subscription basis as a service;

WHEREAS, Customer desires to subscribe to and access Provider's software application for use in Customer's internal business operations;

WHEREAS, Provider is willing to grant Customer access to the SaaS Platform subject to the terms and conditions of this Agreement and the applicable Order Form(s);

WHEREAS, the Parties intend that this Agreement, together with any Order Forms, the Data Processing Addendum, the Service Level Agreement, the Support Policy, and the Acceptable Use Policy, shall constitute the entire agreement between the Parties regarding the subject matter hereof;

WHEREAS, this Agreement shall be governed by the laws of the State of Arizona;

NOW, THEREFORE, in consideration of the mutual covenants, terms, and conditions set forth herein, and for other good and valuable consideration, the receipt and sufficiency of which are hereby acknowledged, the Parties agree as follows:

2. DEFINITIONS

As used in this Agreement, the following capitalized terms have the meanings set forth below:

2.1 "Affiliate" means any entity that directly or indirectly controls, is controlled by, or is under common control with a Party, where "control" means ownership of more than fifty percent (50%) of the voting securities or equivalent ownership interest.

2.2 "Acceptable Use Policy" or "AUP" means Provider's policy governing acceptable use of the SaaS Platform, as set forth in Attachment E and as may be updated by Provider from time to time with reasonable prior notice to Customer.

2.3 "Authorized Users" means Customer's employees, contractors, and agents who are authorized by Customer to access and use the SaaS Platform under Customer's account, subject to the Usage Limits.

2.4 "Business Day" means any day other than a Saturday, Sunday, or public holiday in the State of Arizona.

2.5 "Confidential Information" means all non-public information disclosed by or on behalf of one Party ("Disclosing Party") to the other Party ("Receiving Party") that is designated as confidential or that, given the nature of the information or the circumstances of disclosure, reasonably should be understood to be confidential. Confidential Information includes, without limitation, trade secrets, business plans, financial data, customer lists, technical data, product roadmaps, source code, algorithms, and the terms and pricing of this Agreement.

2.6 "Customer Data" means all electronic data, content, and information submitted, uploaded, or transmitted by or on behalf of Customer or its Authorized Users to the SaaS Platform, including Personal Data.

2.7 "Data Processing Addendum" or "DPA" means the data processing terms attached hereto as Attachment D, governing Provider's processing of Personal Data on behalf of Customer.

2.8 "Documentation" means Provider's standard user guides, online help resources, technical specifications, and other materials describing the features, functionality, and use of the SaaS Platform, as updated from time to time.

2.9 "Downtime" means any period during which the SaaS Platform is unavailable to Customer, excluding Scheduled Maintenance, emergency maintenance communicated to Customer, and outages caused by factors outside Provider's reasonable control (including Customer's internet connectivity, Customer's equipment, or Force Majeure Events).

2.10 "Effective Date" means the date set forth in the preamble of this Agreement.

2.11 "Fees" means the subscription fees, usage-based fees, professional services fees, and any other amounts payable by Customer to Provider under this Agreement and any Order Form.

2.12 "Force Majeure Event" means any event beyond the reasonable control of the affected Party, including acts of God, fire, flood, earthquake, hurricane, epidemic, pandemic, war, terrorism, riot, civil commotion, government action or regulation, labor dispute (not involving the affected Party's employees), internet service provider failure, power outage, or third-party telecommunications failure.

2.13 "Intellectual Property" or "IP" means all patents, copyrights, trademarks, service marks, trade secrets, know-how, inventions, moral rights, and all other intellectual property rights, whether registered or unregistered, and all applications and registrations therefor.

2.14 "Malware" means any virus, worm, Trojan horse, ransomware, spyware, adware, or other malicious code designed to disrupt, disable, or harm computer systems or data.

2.15 "Order Form" means each ordering document entered into between the Parties that references this Agreement and specifies the SaaS Platform subscriptions, Usage Limits, Fees, Subscription Term, and other commercial terms.

2.16 "Personal Data" means any information relating to an identified or identifiable natural person, as defined under applicable data protection laws, including the definitions of "personal information" under A.R.S. § 18-551.

2.17 "SaaS Platform" or "Service" means the cloud-based software application(s) and related services provided by Provider to Customer as identified in the applicable Order Form.

2.18 "Scheduled Maintenance" means routine maintenance of the SaaS Platform performed by Provider during the designated maintenance window as described in the SLA (Attachment B), of which Provider has given Customer reasonable prior notice.

2.19 "Service Level Agreement" or "SLA" means the service level commitments and remedies set forth in Attachment B.

2.20 "Subscription Term" means the initial subscription period and any renewal periods as specified in the applicable Order Form.

2.21 "Support" means the technical support and maintenance services provided by Provider in accordance with the Support Policy (Attachment C).

2.22 "Updates" means bug fixes, patches, minor enhancements, and new releases of the SaaS Platform that Provider makes generally available to subscribing customers at no additional charge.

2.23 "Usage Limits" means the quantitative limits on Customer's use of the SaaS Platform as specified in the applicable Order Form, including limits on the number of Authorized Users, storage, API calls, or transaction volumes.

3. ACCESS RIGHTS AND RESTRICTIONS

3.1 License Grant

Subject to Customer's compliance with this Agreement and payment of all applicable Fees, Provider hereby grants Customer a non-exclusive, non-transferable (except as provided in Section 17.1), non-sublicensable right to access and use the SaaS Platform during the Subscription Term, solely for Customer's internal business purposes and in accordance with the Documentation and Usage Limits specified in the applicable Order Form.

3.2 Authorized Users

(a) Customer may permit its Authorized Users to access and use the SaaS Platform. Customer shall ensure that each Authorized User maintains unique login credentials and does not share credentials with any other person.

(b) Customer is responsible for all actions taken through Authorized Users' accounts and shall ensure that each Authorized User complies with this Agreement and the AUP.

(c) Customer shall promptly deactivate the credentials of any Authorized User who is no longer authorized to access the SaaS Platform.

3.3 Usage Limits

Customer shall not exceed the Usage Limits. If Customer exceeds the Usage Limits, Provider may: (a) charge Customer for the excess usage at Provider's then-current rates; or (b) require Customer to execute an amended Order Form reflecting the additional usage.

3.4 Restrictions

Customer shall not, and shall not permit any third party to:

(a) Copy, modify, adapt, translate, or create derivative works based on the SaaS Platform;

(b) Reverse engineer, disassemble, decompile, or otherwise attempt to derive the source code, algorithms, or underlying structure of the SaaS Platform, except to the extent expressly permitted by applicable Arizona or federal law;

(c) Sublicense, lease, rent, loan, distribute, sell, resell, or otherwise transfer access to the SaaS Platform to any third party;

(d) Use the SaaS Platform for the benefit of any third party, including operating a service bureau, outsourcing arrangement, or time-sharing service;

(e) Remove, alter, or obscure any proprietary notices, labels, or markings on the SaaS Platform or Documentation;

(f) Interfere with or disrupt the integrity or performance of the SaaS Platform or any third-party systems connected thereto;

(g) Attempt to gain unauthorized access to the SaaS Platform, other customers' accounts, or Provider's systems or networks;

(h) Use the SaaS Platform to transmit any Malware or engage in any activity that violates the AUP;

(i) Use the SaaS Platform to store or transmit content that is infringing, defamatory, obscene, or otherwise unlawful;

(j) Publish or distribute any benchmarking or performance testing results without Provider's prior written consent;

(k) Allow any competitor of Provider to access the SaaS Platform, where legally permissible to restrict.

3.5 API Access

If the SaaS Platform includes APIs, Customer may use such APIs solely in accordance with the Documentation and any API-specific terms. Provider reserves the right to impose rate limits, authentication requirements, and other technical restrictions on API usage.

3.6 Third-Party Integrations

Customer may integrate the SaaS Platform with third-party applications, provided that: (a) Customer assumes all risk; (b) Provider shall have no liability for issues arising from such integrations; and (c) Customer shall not hold Provider responsible for the performance, security, or availability of third-party applications.

4. SERVICE LEVELS AND SUPPORT

4.1 Uptime Commitment

Provider shall use commercially reasonable efforts to maintain a monthly uptime percentage of at least [____]% (the "Uptime Target") for the SaaS Platform, measured and calculated as set forth in the SLA (Attachment B). The Uptime Target excludes Scheduled Maintenance and Downtime caused by Force Majeure Events.

4.2 Uptime Measurement

(a) Monthly uptime percentage is calculated as: ((Total Minutes in Month - Downtime Minutes) / Total Minutes in Month) x 100.

(b) Provider shall maintain monitoring systems to track availability and make uptime reports available to Customer upon reasonable request.

4.3 SLA Credits

(a) If Provider fails to meet the Uptime Target in any calendar month, Customer shall be entitled to SLA credits:

(b) Customer must request SLA credits in writing within thirty (30) days after the end of the affected month.

(c) SLA credits shall be applied against future Fees and shall not exceed the total Fees for the affected month. SLA credits are Customer's sole and exclusive remedy for SLA failures, unless chronic failure triggers termination rights under Section 13.

4.4 Support Services

Provider shall provide Support in accordance with the Support Policy (Attachment C):

(a) Support Hours: [________________________________]

(b) Support Channels: [________________________________]

(c) Response Times:

4.5 Scheduled Maintenance

Provider shall perform Scheduled Maintenance during [________________________________] (e.g., Sundays 2:00 AM - 6:00 AM MST) and shall provide at least [____] hours' prior notice. Emergency maintenance may be performed outside the maintenance window with as much advance notice as reasonably practicable.

5. CUSTOMER OBLIGATIONS

5.1 Account Security

(a) Customer shall maintain the confidentiality and security of all login credentials and account information.

(b) Customer shall implement reasonable security measures, including multi-factor authentication where available.

(c) Customer shall promptly notify Provider of any unauthorized access or security breach.

5.2 Acceptable Use

Customer shall comply with the AUP and ensure all Authorized Users comply. Customer shall not use the SaaS Platform in any manner that violates applicable law, including the Arizona Consumer Fraud Act (A.R.S. § 44-1521 et seq.).

5.3 Data Accuracy

Customer shall ensure that all Customer Data is accurate, complete, and lawfully obtained, and that Customer has all necessary rights, consents, and permissions to submit such data.

5.4 Cooperation

Customer shall provide reasonable cooperation and assistance, including timely responses to support requests, access to necessary systems, and designation of a primary point of contact.

5.5 System Requirements

Customer shall maintain the hardware, software, internet connectivity, and system configurations necessary to access and use the SaaS Platform as set forth in the Documentation.

5.6 Compliance with Laws

Customer shall use the SaaS Platform in compliance with all applicable laws, including data protection, export control, and anti-corruption laws.

6. FEES AND PAYMENT

6.1 Subscription Fees

Customer shall pay the subscription Fees as specified in the Order Form. Unless otherwise stated, subscription Fees are invoiced:

☐ Annually in advance
☐ Quarterly in advance
☐ Monthly in advance

6.2 Usage-Based Fees

If applicable, Customer shall pay usage-based Fees for usage exceeding the Usage Limits at rates specified in the Order Form. Provider shall provide usage reports and invoice usage-based Fees [________________________________] (e.g., monthly in arrears).

6.3 Professional Services Fees

Fees for professional services shall be set forth in a separate statement of work or the Order Form.

6.4 Invoicing and Payment Terms

(a) Provider shall invoice Customer per the billing frequency in the Order Form.

(b) All invoices are due within [____] days of the invoice date, unless otherwise specified.

(c) All payments shall be in United States dollars.

(d) Except as expressly set forth herein, all Fees are non-refundable.

6.5 Late Payment

(a) Overdue amounts shall bear interest at the rate of [____]% per month (or [____]% per annum).

(b) Arizona Interest Rate Note: Under A.R.S. § 44-1201, the default interest rate is ten percent (10%) per annum unless a different rate is contracted for in writing, in which event the parties may agree to any rate. Arizona does not impose a statutory ceiling on contracted interest rates in written commercial agreements. However, the Parties agree that the late payment rate specified herein constitutes the agreed rate and shall not be deemed usurious.

(c) Customer shall also reimburse Provider for reasonable costs of collection, including attorneys' fees.

6.6 Taxes

(a) All Fees are exclusive of taxes. Customer shall be responsible for all applicable taxes, excluding taxes based on Provider's net income.

(b) Arizona SaaS Tax Note: Arizona treats SaaS as taxable under the Transaction Privilege Tax (TPT). The Arizona Department of Revenue considers SaaS a rental of personal property subject to TPT at a state rate of approximately 5.6%, with additional local taxes that may bring the combined rate to approximately 8-9% depending on the municipality. Custom software developed to a specific client's specifications is generally not subject to TPT. Customer acknowledges that applicable TPT and local taxes will be added to invoices. If Customer provides a valid Arizona TPT exemption certificate, Provider shall not charge TPT on the exempt portion.

(c) If Provider is required by law to collect taxes, Provider shall include such taxes on the invoice, and Customer shall pay such taxes in addition to the Fees.

6.7 Price Increases

(a) Provider may increase Fees upon renewal by providing at least [____] days' written notice.

(b) Any price increase shall not exceed [____]% unless otherwise agreed in writing.

6.8 Disputed Invoices

(a) Customer may dispute any invoice in good faith by providing written notice within [____] days of the invoice date, specifying the disputed amount and basis.

(b) Customer shall pay all undisputed amounts by the due date. The Parties shall resolve disputes within thirty (30) days.

(c) Provider shall not suspend access solely due to a good-faith dispute, provided undisputed amounts are paid.

7. DATA PROTECTION AND SECURITY

7.1 Security Safeguards

Provider shall implement and maintain administrative, technical, and physical security safeguards designed to protect Customer Data against unauthorized access, disclosure, alteration, destruction, or loss, including:

(a) Encryption of Customer Data in transit (TLS 1.2 or higher) and at rest (AES-256 or equivalent);

(b) Access controls, including role-based access, least-privilege principles, and multi-factor authentication for Provider personnel;

(c) Regular vulnerability assessments and penetration testing;

(d) Intrusion detection and prevention systems;

(e) Audit logging and monitoring of access to Customer Data;

(f) Employee background checks and security awareness training;

(g) Physical security controls for data centers;

(h) Incident response and business continuity / disaster recovery plans.

7.2 Compliance Certifications

Provider shall maintain, at a minimum:

☐ SOC 2 Type II certification
☐ ISO 27001 certification
☐ Other: [________________________________]

Provider shall make compliance reports available to Customer upon reasonable request, subject to confidentiality requirements.

7.3 Data Breach Notification - Arizona Requirements

(a) Provider shall notify Customer of any confirmed Security Breach affecting Customer Data without unreasonable delay and in no event later than [____] hours after Provider's determination that a Security Breach has occurred.

(b) Arizona Data Breach Notification Law (A.R.S. § 18-552): Arizona law requires notification to affected Arizona residents within forty-five (45) days after determining that a breach has occurred. If notification is required for more than one thousand (1,000) individuals, the entity must also notify the three largest nationwide consumer reporting agencies, the Arizona Attorney General, and the Director of the Arizona Department of Homeland Security, in writing.

(c) Civil Penalties: The Arizona Attorney General may impose civil penalties not to exceed the lesser of $10,000 per affected individual or the total amount of economic loss sustained by affected individuals, with a maximum of $500,000 for a breach or series of related breaches.

(d) Confidentiality: Notifications to the Attorney General and the Director of Homeland Security are confidential and exempt from public disclosure under Arizona law.

(e) Provider shall cooperate with Customer in: (i) investigating the Security Breach; (ii) identifying affected individuals; (iii) preparing and delivering notifications; (iv) mitigating effects; and (v) complying with all Arizona breach notification requirements.

(f) Provider's notification to Customer shall include, to the extent known: (i) a description of the Security Breach; (ii) the type of Personal Data affected; (iii) the estimated number of individuals affected; (iv) measures taken to address the breach; and (v) Provider's security contact information.

7.4 Data Processing

(a) Provider shall process Customer Data only in accordance with Customer's documented instructions and this Agreement.

(b) Provider shall not access, use, or disclose Customer Data except as necessary to provide the SaaS Platform or as required by applicable law.

7.5 Sub-Processors

(a) Customer provides general authorization for Provider to engage sub-processors, subject to Provider: (i) maintaining a current sub-processor list; (ii) providing at least [____] days' prior notice before engaging a new sub-processor; and (iii) binding sub-processors to data protection obligations no less protective than those herein.

(b) Customer may object to a new sub-processor within [____] days. If the objection cannot be resolved, Customer may terminate the affected Order Form without penalty.

7.6 Data Location

Provider shall store and process Customer Data in the United States unless otherwise agreed in writing.

7.7 Incident Response

Provider shall maintain and test an incident response plan at least annually and share post-incident remediation findings with Customer upon request.

8. INTELLECTUAL PROPERTY AND FEEDBACK

8.1 Provider Intellectual Property

As between the Parties, Provider retains all right, title, and interest in and to the SaaS Platform, Documentation, and all related Intellectual Property, including all Updates, modifications, and derivative works thereof. Nothing herein transfers any ownership interest in Provider's IP to Customer.

8.2 Customer Intellectual Property

As between the Parties, Customer retains all right, title, and interest in and to Customer Data and Customer IP. Provider acquires no rights in Customer Data except as expressly granted herein.

8.3 Usage Data

Provider may collect, use, and disclose aggregated and anonymized Usage Data, provided that such data: (a) does not identify Customer, Authorized Users, or any individual; (b) does not include identifiable Customer Data; and (c) is used solely for legitimate business purposes.

8.4 Feedback

If Customer provides Feedback, Customer hereby grants Provider a non-exclusive, royalty-free, perpetual, irrevocable, worldwide license to use, reproduce, modify, create derivative works from, distribute, and exploit such Feedback without restriction or obligation to Customer.

8.5 No Implied Rights

Except as expressly granted herein, neither Party grants the other any rights or licenses, express or implied, to any Intellectual Property.

9. CONFIDENTIALITY

9.1 Confidentiality Obligations

Each Party agrees that during the term and for [____] years after expiration or termination, the Receiving Party shall: (a) hold the Disclosing Party's Confidential Information in strict confidence; (b) not disclose it without prior written consent except as permitted herein; (c) use it solely for exercising rights and performing obligations under this Agreement; and (d) protect it with at least the same degree of care used for its own confidential information, but not less than reasonable care.

9.2 Permitted Disclosures

The Receiving Party may disclose Confidential Information to employees, contractors, advisors, and agents who: (a) have a need to know; and (b) are bound by comparable confidentiality obligations.

9.3 Exclusions

Confidential Information does not include information that: (a) is or becomes publicly available through no fault of the Receiving Party; (b) was already in the Receiving Party's possession; (c) is independently developed without reference to Confidential Information; or (d) is lawfully received from a third party without restriction.

9.4 Compelled Disclosure

If compelled by law to disclose Confidential Information, the Receiving Party shall: (a) provide prompt notice (to the extent legally permitted); (b) cooperate to obtain protective orders; and (c) disclose only the legally required portion.

9.5 Trade Secrets - Arizona Law

(a) To the extent any Confidential Information constitutes a trade secret under the Arizona Uniform Trade Secrets Act (A.R.S. § 44-401 et seq.), the confidentiality obligations shall continue for as long as such information remains a trade secret, regardless of the time-limited confidentiality period in Section 9.1.

(b) The Arizona UTSA provides for injunctive relief and damages for misappropriation, and such remedies shall be in addition to any other remedies under this Agreement. Under A.R.S. § 44-403, a court may award damages for actual loss caused by misappropriation and for unjust enrichment, including exemplary damages not to exceed twice any award of damages if willful and malicious misappropriation exists.

9.6 Return or Destruction

Upon termination or expiration, or upon written request, the Receiving Party shall promptly return or destroy all Confidential Information and certify such in writing, except that one archival copy may be retained for legal compliance purposes, subject to continuing confidentiality obligations.

10. WARRANTIES AND DISCLAIMERS

10.1 Provider Warranties

Provider represents and warrants that:

(a) Conformance: The SaaS Platform shall materially conform to the Documentation during the Subscription Term;

(b) Professional Services: Any professional services shall be performed in a professional and workmanlike manner;

(c) No Malware: Provider shall use commercially reasonable efforts to ensure the SaaS Platform does not contain Malware;

(d) Authority: Provider has full power and authority to enter into this Agreement and grant the rights herein;

(e) Non-Infringement: To Provider's knowledge, the SaaS Platform does not infringe any third party's Intellectual Property rights when used in accordance with this Agreement;

(f) Compliance with Laws: Provider shall comply with all applicable laws, including A.R.S. § 18-551 et seq. (data breach notification).

10.2 Customer Warranties

Customer represents and warrants that:

(a) Customer has full power and authority to enter into this Agreement;

(b) Customer's use of the SaaS Platform shall comply with all applicable laws and shall not infringe third-party rights;

(c) Customer has obtained all necessary consents for processing Personal Data.

10.3 Warranty Remedies

If the SaaS Platform fails to conform to Section 10.1(a), Provider shall, at its option: (a) correct the non-conformity; or (b) provide a workaround. If neither is achieved within [____] days, Customer may terminate the affected Order Form and receive a pro-rata refund.

10.4 Disclaimer of Implied Warranties

EXCEPT FOR THE EXPRESS WARRANTIES IN THIS SECTION 10, AND TO THE MAXIMUM EXTENT PERMITTED BY ARIZONA LAW, INCLUDING THE ARIZONA UCC (A.R.S. § 47-2101 ET SEQ.), THE SAAS PLATFORM AND ALL RELATED SERVICES ARE PROVIDED "AS IS" AND "AS AVAILABLE." PROVIDER DISCLAIMS ALL IMPLIED WARRANTIES, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, AND ANY WARRANTIES ARISING FROM COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

10.5 Consumer Protection Carve-Out

Nothing in this Agreement shall be construed to waive or limit any rights under the Arizona Consumer Fraud Act (A.R.S. § 44-1521 et seq.) to the extent such rights cannot be waived by contract. The Arizona Consumer Fraud Act prohibits any deception, deceptive or unfair act or practice, fraud, false pretense, false promise, misrepresentation, or concealment of material fact in connection with the sale or advertisement of any merchandise, which includes intangibles and services such as SaaS.

11. INDEMNIFICATION

11.1 Provider Indemnification (IP Indemnity)

Provider shall indemnify, defend, and hold harmless Customer Indemnitees from and against any third-party Claim alleging that Customer's use of the SaaS Platform in accordance with this Agreement infringes or misappropriates such third party's Intellectual Property rights, and shall pay all damages, costs, and expenses (including reasonable attorneys' fees) finally awarded or agreed to in settlement.

11.2 IP Indemnity Exclusions

Provider has no obligation under Section 11.1 for Claims arising from: (a) Customer Data; (b) unauthorized modifications; (c) combination with non-Provider products; (d) use of a superseded version; or (e) use in violation of this Agreement.

11.3 IP Indemnity Remedies

If the SaaS Platform becomes subject to an infringement Claim, Provider may: (a) procure the right for Customer to continue using it; (b) replace or modify it to become non-infringing; or (c) terminate the affected Order Form and refund prepaid Fees.

11.4 Customer Indemnification

Customer shall indemnify, defend, and hold harmless Provider Indemnitees from third-party Claims arising from: (a) Customer Data; (b) AUP violations; (c) breach of this Agreement; or (d) violation of applicable law.

11.5 Indemnification Procedure

(a) Prompt written notice to the indemnifying Party (failure to provide prompt notice shall not relieve obligations except to the extent materially prejudiced).

(b) Sole control of defense by indemnifying Party, with no settlement that imposes obligations on or admits fault of the indemnified Party without consent.

(c) Reasonable cooperation by the indemnified Party at the indemnifying Party's expense.

11.6 Sole Remedy

This Section 11 states each Party's sole liability and exclusive remedy for third-party Claims described herein.

12. LIMITATIONS OF LIABILITY

12.1 Liability Cap

EXCEPT FOR THE CARVE-OUTS IN SECTION 12.3, EACH PARTY'S TOTAL AGGREGATE LIABILITY SHALL NOT EXCEED THE TOTAL FEES PAID OR PAYABLE BY CUSTOMER DURING THE [____]-MONTH PERIOD IMMEDIATELY PRECEDING THE EVENT GIVING RISE TO THE LIABILITY (THE "LIABILITY CAP").

12.2 Exclusion of Consequential Damages

EXCEPT FOR THE CARVE-OUTS IN SECTION 12.3, IN NO EVENT SHALL EITHER PARTY BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, INCLUDING DAMAGES FOR LOSS OF PROFITS, REVENUE, GOODWILL, USE, DATA, OR BUSINESS OPPORTUNITIES, REGARDLESS OF THE THEORY OF LIABILITY AND EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

12.3 Carve-Outs

The limitations in Sections 12.1 and 12.2 shall not apply to:

(a) Indemnification obligations under Section 11;

(b) Breach of confidentiality obligations under Section 9;

(c) Willful misconduct or gross negligence;

(d) Customer's payment obligations under Section 6;

(e) Provider's data security and breach notification obligations;

(f) Any liability that cannot be limited or excluded under Arizona law.

12.4 Essential Purpose

THE LIMITATIONS SHALL APPLY EVEN IF A LIMITED REMEDY FAILS OF ITS ESSENTIAL PURPOSE. THE PARTIES ACKNOWLEDGE THAT THESE LIMITATIONS REFLECT A FAIR ALLOCATION OF RISK AND FORM AN ESSENTIAL BASIS OF THE BARGAIN.

12.5 Arizona Law Compliance

The limitations shall apply to the fullest extent permitted by the laws of the State of Arizona.

13. TERM, RENEWAL, AND TERMINATION

13.1 Agreement Term

This Agreement commences on the Effective Date and continues until all Order Forms have expired or been terminated.

13.2 Subscription Term and Renewal

The initial Subscription Term shall be as specified in the Order Form. Each Subscription Term shall automatically renew for successive periods of equal length unless either Party provides written notice of non-renewal at least [____] days prior to the end of the then-current Subscription Term.

13.3 Termination for Convenience

Either Party may terminate an Order Form for convenience with [____] days' prior written notice. If Customer terminates for convenience, Customer shall pay all Fees accrued through termination but shall not receive a refund unless specified in the Order Form.

13.4 Termination for Cause

Either Party may terminate immediately upon written notice if:

(a) The other Party commits a material breach and fails to cure within [____] days (or [____] days for payment defaults);

(b) The other Party becomes the subject of a bankruptcy petition not dismissed within sixty (60) days;

(c) The other Party ceases business or makes a general assignment for the benefit of creditors.

13.5 Suspension Rights

(a) Provider may suspend access upon [____] days' notice if: (i) Customer fails to pay undisputed Fees; (ii) Customer's use violates the AUP or poses a security risk; or (iii) suspension is required by law.

(b) Provider shall limit suspension scope and duration and restore access upon cure.

13.6 Effect of Termination

Upon termination:

(a) Customer's access rights cease immediately;

(b) Customer shall pay all Fees accrued through the termination date;

(c) Each Party shall return or destroy Confidential Information per Section 9.6;

(d) Provider shall make Customer Data available for export for [____] days, then delete per the DPA.

13.7 Survival

Sections 2, 6 (accrued obligations), 7.3, 8, 9, 10.4, 11, 12, 13.6, 13.7, 16, and 17 shall survive termination.

14. BETA AND FREE TRIALS

14.1 Trial Access

Provider may make available beta features, pilot programs, or free trial access ("Trial Services") for evaluation purposes.

14.2 Trial Terms

(a) Trial Services are provided "AS IS" without warranty, SLA, indemnity, or support obligation.

(b) Provider may modify, suspend, or discontinue Trial Services at any time without notice.

(c) The trial period terminates as specified by Provider unless converted to a paid subscription.

14.3 Data Handling

Provider may delete trial Customer Data upon trial termination unless Customer converts to a paid subscription.

14.4 Feedback

Trial Feedback is subject to Section 8.4.

15. COMPLIANCE

15.1 Acceptable Use Policy

Customer shall comply with the AUP (Attachment E). Material changes shall be subject to notice requirements.

15.2 Export Controls and Sanctions

(a) Each Party shall comply with all applicable export control laws, including EAR (15 CFR Parts 730-774) and ITAR (22 CFR Parts 120-130).

(b) Customer shall not access the SaaS Platform from sanctioned countries or provide access to restricted parties.

15.3 Anti-Corruption

(a) Each Party shall comply with all applicable anti-corruption laws, including the FCPA.

(b) No facilitation payments or improper payments.

(c) Accurate books and records.

15.4 Accessibility

Provider shall use commercially reasonable efforts to conform to Section 508 and WCAG 2.1 Level AA.

15.5 Arizona Regulatory Requirements

Customer is solely responsible for compliance with any industry-specific or regulatory requirements under Arizona law applicable to Customer's business.

16. GOVERNING LAW AND DISPUTE RESOLUTION

16.1 Governing Law

This Agreement shall be governed by and construed in accordance with the laws of the State of Arizona, without regard to conflicts of law principles.

16.2 Venue

Any legal action shall be brought exclusively in the Superior Court of Maricopa County, Arizona, or the United States District Court for the District of Arizona (Phoenix Division). Each Party irrevocably consents to jurisdiction and venue and waives objections based on inconvenient forum.

16.3 Escalation Procedure

Before formal legal action (other than actions for injunctive or equitable relief):

(a) Step 1 - Operational Contacts: Meet within ten (10) Business Days of written notice to attempt resolution.

(b) Step 2 - Executive Escalation: If not resolved within twenty (20) Business Days, escalate to senior executives who shall meet within ten (10) Business Days.

(c) Step 3 - Mediation (Optional): If not resolved within twenty (20) Business Days of Step 2, either Party may propose non-binding mediation in Phoenix, Arizona, with costs shared equally.

16.4 Jury Waiver

Arizona law recognizes the enforceability of contractual jury trial waivers where they are entered into knowingly, voluntarily, and intelligently, the waiver language is clear and unequivocal, and there is mutuality and fairness in the agreement.

TO THE FULLEST EXTENT PERMITTED BY ARIZONA LAW, EACH PARTY HEREBY KNOWINGLY, VOLUNTARILY, AND IRREVOCABLY WAIVES ANY RIGHT TO A TRIAL BY JURY IN ANY ACTION ARISING OUT OF OR RELATING TO THIS AGREEMENT. EACH PARTY CERTIFIES THAT: (A) NO REPRESENTATIVE OF THE OTHER PARTY HAS REPRESENTED THAT THE OTHER PARTY WOULD NOT ENFORCE THIS WAIVER; (B) EACH PARTY UNDERSTANDS AND HAS CONSIDERED THE IMPLICATIONS; (C) EACH PARTY MAKES THIS WAIVER VOLUNTARILY; AND (D) EACH PARTY HAS BEEN INDUCED TO ENTER INTO THIS AGREEMENT BY THE MUTUAL WAIVERS HEREIN.

16.5 Attorneys' Fees

The prevailing Party shall be entitled to recover reasonable attorneys' fees, court costs, and litigation expenses.

16.6 Injunctive Relief

Either Party may seek injunctive or equitable relief from any court of competent jurisdiction to prevent irreparable harm or enforce its rights under Sections 3, 8, or 9, without posting a bond or proving actual damages.

17. MISCELLANEOUS

17.1 Assignment

Neither Party may assign this Agreement without the other Party's prior written consent (not unreasonably withheld); provided that either Party may assign without consent to an Affiliate or successor in connection with a merger, acquisition, or sale of substantially all assets. Any purported assignment in violation shall be void.

17.2 Subcontracting

Provider may subcontract obligations, remaining fully responsible for subcontractor performance and compliance.

17.3 Notices

All notices shall be in writing and deemed given: (a) upon personal delivery; (b) one (1) Business Day after overnight courier deposit; (c) three (3) Business Days after certified U.S. mail deposit; or (d) upon confirmed email receipt to addresses in the preamble or Order Form.

17.4 Force Majeure

(a) No liability for failure or delay caused by Force Majeure Events (except payment obligations).

(b) The affected Party shall promptly notify the other, mitigate effects, and resume performance.

(c) If a Force Majeure Event persists for [____] consecutive days, either Party may terminate the affected Order Form.

17.5 Order of Precedence

In the event of conflict (highest to lowest): (a) DPA / Security Addendum; (b) Main Agreement; (c) Order Form; (d) SLA; (e) Support Policy; (f) AUP.

17.6 Severability

Invalid provisions shall be modified to the minimum extent necessary. Remaining provisions continue in full force.

17.7 Amendments

Amendments require a written instrument signed by both Parties.

17.8 Waiver

Failure to enforce a provision is not a waiver. Waivers must be in writing.

17.9 Entire Agreement

This Agreement and all attachments constitute the entire agreement, superseding all prior agreements and understandings.

17.10 Counterparts

May be executed in counterparts, each deemed an original.

17.11 Electronic Signatures

Electronic signatures are valid and enforceable under the Arizona Uniform Electronic Transactions Act (A.R.S. § 44-7001 et seq.) and the federal E-SIGN Act (15 U.S.C. § 7001 et seq.).

17.12 Headings

Headings are for convenience only.

17.13 Third-Party Beneficiaries

No third-party beneficiaries.

17.14 Relationship of the Parties

The Parties are independent contractors. No partnership, joint venture, agency, or employment relationship is created.

17.15 Publicity

Neither Party shall use the other's name, logo, or trademarks without consent, except Provider may include Customer in its customer list.

17.16 Construction

Construed fairly, not against the drafter. "Including" means "including, without limitation."

18. SIGNATURE BLOCKS

IN WITNESS WHEREOF, the Parties have executed this Agreement as of the Effective Date.

PROVIDER:

CUSTOMER:

19. ATTACHMENTS

• Attachment A: Order Form - Subscriptions, Usage Limits, Fees, Subscription Term, commercial terms.

• Attachment B: Service Level Agreement (SLA) - Uptime commitments, measurement, SLA credits, remedies.

• Attachment C: Support Policy - Support hours, channels, severity levels, response times, escalation, maintenance.

• Attachment D: Data Processing Addendum (DPA) / Security Addendum - Personal Data processing, security, breach notification, sub-processors, data subject rights.

• Attachment E: Acceptable Use Policy (AUP) - Prohibited uses, content standards, enforcement.

ATTACHMENT A: ORDER FORM (TEMPLATE)

ATTACHMENT B: SERVICE LEVEL AGREEMENT (TEMPLATE)

1. Uptime Target: [____]% monthly uptime

2. Measurement Period: Calendar month

3. Exclusions: Scheduled Maintenance, Force Majeure Events, Customer-caused outages, third-party failures

4. SLA Credit Table:

5. Credit Request Procedure: Written request within 30 days

6. Maximum Credit: Not to exceed 100% of monthly Fees

7. Chronic Failure: If uptime falls below [____]% for [____] consecutive months, Customer may terminate

ATTACHMENT C: SUPPORT POLICY (OUTLINE)

1. Support Hours: [________________________________]

2. Support Channels: [________________________________]

3. Severity Definitions and Response Times: (See Section 4.4)

4. Escalation Procedures:

• Level 1: Support engineer
• Level 2: Senior engineer / team lead
• Level 3: Engineering management
• Level 4: Executive escalation

5. Maintenance Windows: [________________________________]

6. Release Management: [________________________________]

ATTACHMENT D: DATA PROCESSING ADDENDUM (SUMMARY)

1. Scope: Processing of Personal Data by Provider on behalf of Customer

2. Roles: Customer as data controller; Provider as data processor

3. Processing Instructions: Per this Agreement and Customer's written instructions

4. Security Measures: As described in Section 7.1

5. Sub-Processors: As described in Section 7.5

6. Breach Notification: As described in Section 7.3

7. Data Subject Rights: Provider shall assist Customer in responding to requests

8. Data Deletion/Return: As described in Section 13.6

9. Arizona Compliance: Provider shall comply with A.R.S. § 18-551 et seq.

ATTACHMENT E: ACCEPTABLE USE POLICY (OUTLINE)

1. Prohibited Activities:

• Unauthorized access or interference
• Distribution of Malware
• Unsolicited commercial communications
• Activities violating applicable law
• Activities infringing third-party rights

2. Content Standards:

• No unlawful, defamatory, obscene, or harmful content
• No IP-infringing content
• No privacy-violating content

3. Resource Usage:

• No excessive consumption of resources
• No unauthorized scraping or data extraction

4. Enforcement:

• Suspension for violations with notice and opportunity to cure
• Repeated violations may result in termination

This template is provided for informational purposes only and does not constitute legal advice. Legal counsel licensed in the State of Arizona should review and customize this Agreement before execution. Laws and regulations change frequently; verify all statutory citations are current before use.