Scope of Work Agreement for App Development

1.1 Governing SOW. The specific deliverables, features, technology stack, platforms, integrations, and milestones for this engagement are set forth in the Statement of Work attached hereto as Exhibit A (the "SOW"), which is incorporated by reference and made a part of this Agreement. In the event of a conflict between the body of this Agreement and any SOW, the SOW shall control solely with respect to the subject matter addressed therein. 1.2 Completeness of Deliverables. Provider shall deliver only those features, pages, screens, integrations, and functionalities expressly described in the SOW. Any feature, function, content element, third-party integration, platform, or deliverable not listed in the SOW is out of scope and shall not be provided under this Agreement without a fully executed Change Order as provided in Section 2. 1.3 Explicit Exclusions. Without limiting Section 1.2, the following are expressly excluded from the scope of this Agreement unless separately specified in the SOW or a Change Order: (a) SEO optimization, copywriting, or content creation beyond placeholder or seed content identified in the SOW; (b) third-party service fees, API subscription costs, domain registration, SSL certificates, or hosting fees; (c) training, documentation, or post-launch support beyond any maintenance period defined in the SOW; (d) data migration from legacy systems unless expressly itemized; (e) accessibility remediation beyond the WCAG compliance level specified in the SOW; and (f) compatibility with browsers, operating systems, or devices not identified in the SOW. 1.4 Technology Stack. Provider shall use the technology stack identified in the SOW. Material deviations from the specified stack require Client's prior written consent, which shall not be unreasonably withheld. 1.5 SOW Amendments. The SOW may only be amended through a signed Change Order executed by both parties. No verbal instruction, email direction, or other informal communication shall expand, modify, or supersede the SOW. 1.6 Client Responsibilities. Client shall furnish all materials, assets, credentials, and approvals identified as Client-supplied in the SOW by the dates specified therein. Provider's timeline obligations are tolled day-for-day for each day Client is in default of any material supply or approval obligation.

2.1 Scope Lock. The SOW constitutes the complete and exclusive description of the work to be performed under this Agreement. No addition, deletion, or modification of scope takes effect unless documented in a Change Order signed by authorized representatives of both parties. 2.2 Change Order Process. Either party may propose a scope change by delivering a written change request to the other party's project contact. Within 3 business days of receipt, Provider shall deliver a written Change Order proposal specifying: (a) a description of the requested change; (b) any additions to or deletions from the deliverable list; (c) the additional or reduced fee, calculated at the rates set forth in the SOW or, if not specified, at Hourly rate for out-of-scope / additional work (e.g., "$175") per hour; (d) the revised milestone or delivery schedule; and (e) any impacts on dependencies, third-party integrations, or previously accepted work. The Change Order is not binding until signed by both parties. 2.3 No Work Until Signed. Provider shall not commence out-of-scope work until a Change Order is signed by both parties. Client shall not direct Provider to perform out-of-scope work orally or by informal communication, and any such direction does not create an obligation for Provider to perform or Client to pay. This Section constitutes a no-oral-modification clause within the meaning of applicable contract law. 2.4 Revision vs. New Work. A "Revision" is a modification to content or design within the scope of an already-approved deliverable that does not add functionality, pages, screens, integrations, or platform targets. "New Work" is any addition, substitution, or expansion that falls outside the approved deliverable list or requires material additional development effort. The SOW specifies the number of Revision rounds included at no additional charge for each deliverable. Additional Revision rounds beyond the included number are billed at the rate in Section 2.2(c) above. 2.5 Effect on Timeline. Each executed Change Order may extend affected milestone dates by the number of days necessary to accommodate the change, as specified in the Change Order. Changes that are additive to scope do not accelerate remaining milestone dates. 2.6 Pending Change Orders. While a Change Order is pending and unsigned, Provider may, at its election: (a) continue in-scope work unaffected by the proposed change; or (b) pause work on deliverables that depend on resolution of the pending change, without being deemed in breach, provided Provider notifies Client of the pause in writing within one business day.

3.1 Fee. Client shall pay Provider the total fee set forth in the SOW (the "Project Fee") in accordance with the milestone schedule in Section 3.2. All amounts are in Invoice Currency (e.g., USD, CAD, GBP) and are exclusive of applicable taxes. 3.2 Milestone Payment Schedule. Unless the SOW specifies a different schedule, the Project Fee is due as follows: (a) Deposit: Deposit Percentage (%)% of the Project Fee is due upon execution of this Agreement. The deposit is non-refundable once Provider commences work and represents compensation for reserving Provider's capacity. (b) [Remaining milestones as specified in SOW.] 3.3 Late Payment. Invoices not paid within 30 days of invoice date will accrue interest at 1.5% per month (or the maximum rate permitted by applicable law, whichever is less) from the due date until paid in full. Provider may also suspend Services upon 5 business days' written notice if any invoice remains unpaid for more than 10 days after the due date. 3.4 Price Changes During Contract Term. Provider may not unilaterally increase fees for work covered by a signed SOW. For any renewal, extension, or new SOW entered into after the initial SOW term, Provider shall provide written notice of any fee change at least 30 days before the proposed effective date. If Client does not accept the new fees in writing and the parties do not agree on pricing within 15 days of notice, either party may decline to enter into a new SOW without penalty. 3.5 Price Cap for Maintenance and Retainer Engagements. For ongoing maintenance or retainer engagements that auto-renew under Section Auto-Renewal Section Reference: (a) the monthly fee for any Renewal Term shall not exceed the current-term fee by more than Annual Price Escalation Cap (%)% without Client's prior written consent; (b) if Provider's proposed renewal fee exceeds this cap, Client may terminate the maintenance engagement with 30 days' written notice without a kill fee, effective at the end of the current term; and (c) the CPI-based adjustment index used, if any, shall be the US CPI-U as published for the most recent 12-month period ending June of the renewal year. 3.6 Disputed Invoices. Client may withhold payment of a genuinely disputed invoice item by providing Provider with written notice of the dispute within 10 days of the invoice date, identifying the disputed amount and the basis for the dispute. Undisputed amounts must be paid by the original due date. The parties shall attempt to resolve the dispute within 14 days of the dispute notice.

INTELLECTUAL PROPERTY OWNERSHIP (a) Background IP. Each party retains all right, title, and interest in its Background IP. "Background IP" means all intellectual property owned or licensed by a party prior to the Effective Date or developed independently of this Agreement. Each party grants the other a limited, non-exclusive, royalty-free license to use its Background IP solely to the extent necessary to perform or receive the Services during the term of this Agreement. (b) Deliverables — Work-for-Hire Designation. To the extent that any Deliverable constitutes a "work made for hire" as defined in 17 U.S.C. § 101 (including as a contribution to a collective work, as a part of a motion picture or other audiovisual work, as a translation, as a supplementary work, as a compilation, as an instructional text, as a test, as answer material for a test, or as an atlas), such Deliverable is a work made for hire for Client name / business name, and Client name / business name will be the author and owner of the copyright therein from the moment of creation. (c) Assignment. To the extent that any Deliverable does not qualify as a work made for hire, Your name / business name hereby irrevocably assigns to Client name / business name, effective upon receipt of full payment for such Deliverable, all right, title, and interest in and to such Deliverable, including all copyrights, patents, trademarks, trade secrets, and other intellectual property rights worldwide, in perpetuity. (d) License for Partially-Paid Deliverables. If this Agreement terminates before Client name / business name has paid in full for a Deliverable, Your name / business name grants Client name / business name a non-exclusive, non-transferable, revocable license to use that Deliverable solely for Client name / business name's internal purposes until the outstanding balance is paid, at which point the assignment in Section (c) becomes effective. (e) Agency Portfolio License. Client name / business name grants Your name / business name a non-exclusive, royalty-free, perpetual license to display the Deliverables (excluding any Confidential Information) in Your name / business name's portfolio, case studies, and marketing materials, unless Client name / business name notifies Your name / business name in writing that a specific Deliverable is subject to confidentiality restrictions. (f) Third-Party Content. Your name / business name will obtain all necessary licenses for third-party content (stock images, fonts, music, software) incorporated into Deliverables, and will disclose to Client name / business name any third-party license restrictions that limit Client name / business name's use of the Deliverables. (g) Moral Rights. To the extent permitted by applicable law, Your name / business name waives all moral rights in the Deliverables in favor of Client name / business name. (h) Agency Tools & Methodologies. Notwithstanding the foregoing, Your name / business name retains all right, title, and interest in its proprietary tools, templates, methodologies, know-how, and general processes used to create the Deliverables. Client name / business name's rights are limited to the Deliverables themselves.

Pre-Existing / Background IP Retention and License-Back 1. Reservation of Background IP. Each party retains sole and exclusive ownership of all Intellectual Property Rights in works, inventions, methodologies, tools, frameworks, libraries, components, code bases, templates, and know-how that: (a) were created, developed, or acquired prior to the Effective Date; (b) are developed independently of this Agreement and the applicable SOW; or (c) are general-purpose tools or methodologies not created specifically for Client name / business name (collectively, "Background IP"). No assignment, transfer, or other conveyance of Background IP is intended or shall be implied by this Agreement. 2. Developer Background IP Schedule. Your name / business name's Background IP incorporated into or required to operate the Deliverables is described in Schedule A – Background IP attached to the applicable SOW ("Developer Background IP"). Your name / business name shall update Schedule A prior to delivery of each Deliverable to reflect any additional Background IP incorporated during the engagement. 3. License Grant to Client. Your name / business name hereby grants Client name / business name a non-exclusive, royalty-free, irrevocable, worldwide, perpetual license to use, execute, and reproduce the Developer Background IP solely to the extent incorporated in, or reasonably necessary to operate, the Deliverables for Client name / business name's internal business purposes (the "Background IP License"). The Background IP License does not include the right to: (a) sublicense, transfer, or assign the license except in connection with a permitted assignment of this Agreement; (b) use Developer Background IP in any product or service other than the Deliverables; (c) decompile, disassemble, or reverse-engineer any proprietary Developer Background IP beyond what is permitted by applicable law; or (d) use Developer Background IP to develop, train, or improve any competing product or service. 4. No Implied License. Except as expressly set out in Section 3, no license, right, or interest in Your name / business name's Background IP is granted to Client name / business name, whether by implication, estoppel, or otherwise. 5. Foreground IP. All Intellectual Property Rights in works specifically created for Client name / business name under an SOW that are not Background IP ("Foreground IP" or "Deliverables IP") are governed by the IP Ownership / Work-for-Hire & Assignment clause of this Agreement.

CONFIDENTIALITY (a) Definition. "Confidential Information" means all non-public information disclosed by one party ("Discloser") to the other ("Recipient") in connection with this Agreement that is designated as confidential at the time of disclosure, or that a reasonable person would understand to be confidential given the nature of the information and circumstances of disclosure. Without limiting the foregoing, Confidential Information includes: business plans, financial data, pricing, fee structures, customer and prospect lists, proprietary methodologies, software, technical specifications, and personnel information. (b) Exclusions. Confidential Information does not include information that: (i) is or becomes publicly available through no fault of Recipient; (ii) Recipient already knew before receiving it from Discloser, as shown by written records; (iii) Recipient independently develops without use of or reference to the Confidential Information; or (iv) Recipient rightfully receives from a third party without restriction. (c) Obligations. Recipient will: (i) use Discloser's Confidential Information solely to perform or receive the Services under this Agreement; (ii) disclose it only to its employees, contractors, and advisors who have a need to know and who are bound by confidentiality obligations no less protective than this clause; and (iii) protect it with at least the same degree of care it uses for its own confidential information of similar sensitivity, but in no event less than reasonable care. (d) Compelled Disclosure. Recipient may disclose Confidential Information if required by law, court order, or regulatory authority, provided that Recipient: (i) gives Discloser prompt prior written notice to the extent legally permitted; (ii) cooperates with Discloser in seeking a protective order or other appropriate relief; and (iii) discloses only what is legally required. (e) Trade Secrets. Obligations with respect to information that constitutes a trade secret under applicable law (including the Defend Trade Secrets Act, 18 U.S.C. § 1836) will continue for as long as such information remains a trade secret, notwithstanding any shorter survival period stated below. (f) Subcontractors. Your name / business name may share Client name / business name's Confidential Information with approved subcontractors solely to the extent necessary for them to perform work under this Agreement, provided each subcontractor is bound by written confidentiality obligations at least as protective as this clause. (g) Return or Destruction. Upon termination or expiration of this Agreement, or upon Discloser's written request, Recipient will promptly return or securely destroy all of Discloser's Confidential Information (including copies) and certify such return or destruction in writing, except as required by law or for legal-hold purposes. (h) Survival. This Section survives termination or expiration of this Agreement for a period of 3 years, except as provided in Section (e).

Acceptance Testing, Deemed Acceptance & Cure 1. Acceptance Gates. The parties agree that the Deliverables will be reviewed and accepted in up to three (3) sequential stages (each, an "Acceptance Gate"), as identified in the applicable Statement of Work ("SOW") or project schedule: - Gate 1 – Design Comps: Static design mockups, wireframes, or visual prototypes submitted for approval prior to build. - Gate 2 – Staging Build: A fully functional version of the Deliverable deployed to a staging or test environment. - Gate 3 – Production Launch: The final Deliverable deployed to the production environment and ready for end-user access. Each Acceptance Gate corresponds to the payment milestone identified in the SOW. 2. Review Window. Upon Your name / business name's written notification that a Deliverable is ready for review at an Acceptance Gate, Client name / business name shall have 5 business days (the "Review Window") to review the Deliverable and either (a) provide written acceptance, or (b) deliver a written deficiency report as described in Section 3. 3. Deficiency Reports. To reject a Deliverable, Client name / business name must deliver a written deficiency report within the Review Window that: (i) identifies each defect with sufficient specificity to allow Your name / business name to reproduce it; (ii) classifies each defect by severity tier in accordance with Section 5; and (iii) identifies the specific specification, SOW requirement, or Acceptance Criteria the Deliverable fails to meet. Subjective design preferences not documented in the SOW, Acceptance Criteria, or a signed change order do not constitute grounds for rejection. 4. Cure Period. Upon receipt of a conforming deficiency report, Your name / business name shall have 10 business days (the "Cure Period") to correct all identified Critical and Major defects and re-submit the Deliverable. The Review Window restarts in full upon re-submission. If Your name / business name fails to cure all Critical and Major defects within a second Cure Period, Client name / business name's sole and exclusive remedy is, at Client name / business name's election: (a) a pro-rata reduction in the fees attributable to the non-conforming Acceptance Gate only; or (b) termination of the SOW with respect to the uncompleted phase and a pro-rata refund of fees paid for that phase, net of the reasonable value of work delivered to date. 5. Defect Severity Tiers. | Tier | Definition | Cure Target | |------|-----------|-------------| | Critical | Defect that completely blocks a core function described in the SOW and has no reasonable workaround. | 5 business days | | Major | Defect that materially impairs a function described in the SOW but a reasonable workaround exists. | 10 business days | | Minor | Cosmetic defect, typographic error, or non-material deviation; does not block or materially impair function. | Addressed in next scheduled release or maintenance cycle. | A Deliverable shall be deemed accepted once all Critical and Major defects have been resolved. Minor defects do not block acceptance or withhold payment. 6. Deemed Acceptance. If Client name / business name does not deliver a conforming written deficiency report before the expiry of the Review Window, the Deliverable shall be deemed accepted as of the last day of the Review Window, and the associated payment milestone shall become immediately due and payable. Production use of any Deliverable by Client name / business name or its end users prior to formal acceptance shall also constitute deemed acceptance of that Deliverable. 7. Acceptance Criteria. The parties shall agree on objective Acceptance Criteria for each Acceptance Gate no later than Deadline to agree on Acceptance Criteria (e.g. '10 business days') after the Effective Date. Where Acceptance Criteria are not specified, the applicable standard is conformity with the functional and technical specifications set out in the SOW.

Third-Party Components; License Allocation; Dependency Risk 1. Identification of Third-Party Components. Prior to or concurrent with execution of the Statement of Work ("SOW"), Developer shall provide Client with a written schedule (the "Dependency Schedule") identifying all material third-party software, plugins, themes, libraries, APIs, SDKs, and other components (collectively, "Third-Party Components") that Developer reasonably anticipates incorporating into the Deliverables, together with the applicable license or subscription terms governing each component. The Dependency Schedule is incorporated into the SOW by reference. Developer shall promptly update the Dependency Schedule upon identifying any material new Third-Party Component during performance. 2. License Procurement — Client-Procures. (Client-Procures Model — insert if selected): For each Third-Party Component designated in the Dependency Schedule as requiring a paid license, Client shall procure, in its own name, all required licenses, subscriptions, and API keys before or promptly after execution of the SOW, and shall provide Developer with access credentials necessary to perform the Services. Developer is not responsible for the cost, procurement, renewal, or regulatory compliance of any Third-Party Component license. Developer shall use Third-Party Components only within the scope of the licenses provided by Client. (Agency-License Model — insert if selected): Developer may extend agency-tier or multi-site license access to Client for Third-Party Components held by Developer during the Engagement. Upon termination or expiration of this Agreement for any reason, such extended access shall automatically terminate, and Client shall procure its own licenses for any Third-Party Components it wishes to continue using within 30 calendar days following the effective date of termination. Developer shall have no liability for service interruptions, data loss, or functional degradation attributable to Client's failure to timely procure independent licenses. 3. Open-Source Components. The Dependency Schedule shall identify all open-source software incorporated into the Deliverables and the applicable open-source license (e.g., MIT, Apache 2.0, GPL v2/v3, LGPL) governing each component. Developer shall not incorporate any open-source component into the Deliverables in a manner that: (a) requires Client to release, license, or disclose Client's proprietary source code under an open-source license (including any GPL copyleft obligation) without Client's prior written consent; or (b) violates the terms of the applicable open-source license. Where a GPL-licensed theme or plugin is used, Developer shall disclose to Client any copyleft obligations that may apply to derivative works, including custom child themes or plugins, and obtain Client's written acknowledgment. 4. Post-Acceptance Dependency Changes. Developer does not warrant the continued availability, pricing, functionality, or terms of any Third-Party Component after the Acceptance Date. If, after the Acceptance Date, a Third-Party Component that is identified in the Dependency Schedule is deprecated, discontinued, materially modified, or made unavailable or economically impractical (including changes to API pricing, rate limits, or authentication requirements), and such change necessitates modifications to the Deliverables, such modifications shall be addressed through a Change Order and shall not constitute a warranty defect, provided that Developer's implementation of the affected component at the time of delivery was consistent with the component's then-current documentation and terms of use. 5. No Critical Single-Point-of-Failure Dependency. Without Client's prior written consent, Developer shall not architect the Deliverables such that a single Third-Party API, service, or component constitutes an unmitigated single point of failure for core functionality ("Critical Dependency"). Where a Critical Dependency is unavoidable or preferred by Client, Developer shall disclose such dependency in the Dependency Schedule, describe the associated risks in writing, and Client's written consent shall be documented in or attached to the SOW. 6. Developer's Compliance Obligation. Developer represents that, as of the Acceptance Date, Developer's use of each Third-Party Component in the Deliverables is consistent with the applicable license terms for such component. Developer's indemnification obligations under the Agreement with respect to third-party intellectual property claims shall not extend to claims arising from Third-Party Components themselves (as distinct from Developer's non-compliant use thereof), except to the extent such claims arise directly from Developer's material breach of a Third-Party Component's license terms.

LIMITATION OF LIABILITY (a) Exclusion of Consequential Damages. To the fullest extent permitted by applicable law, neither party will be liable to the other for any indirect, incidental, special, consequential, punitive, or exemplary damages — including lost profits, lost revenue, loss of business opportunity, loss of data, or harm to reputation — arising out of or related to this Agreement, even if the party has been advised of the possibility of such damages and even if a limited remedy fails of its essential purpose. (b) Aggregate Cap. Each party's total aggregate liability to the other arising out of or related to this Agreement — whether in contract, tort (including negligence), strict liability, or otherwise — will not exceed the total fees actually paid or payable by Client name / business name to Your name / business name during the Cap look-back period (months)-month period immediately preceding the event giving rise to the claim, or Minimum cap floor amount (e.g. $5,000), whichever is greater. (c) Exceptions. The limitations in Sections (a) and (b) do not apply to: (i) a party's obligation to indemnify the other for third-party claims of intellectual property infringement under the Mutual Indemnification clause; (ii) liability arising from a party's gross negligence or willful misconduct; (iii) a party's obligations under the Data Protection and Confidentiality clauses with respect to a data breach caused by that party's failure to maintain reasonable security; or (iv) a party's obligation to pay amounts owed under this Agreement. (d) Basis of the Bargain. Each party acknowledges that the limitations in this Section reflect a reasonable allocation of risk, are an essential element of the basis of the bargain between the parties, and that Your name / business name would not have entered into this Agreement without these limitations.

GOVERNING LAW; JURISDICTION; VENUE (a) Governing Law. This Agreement and any dispute arising out of or related to it — including its formation, interpretation, performance, breach, or termination — will be governed by and construed in accordance with the laws of the State of Governing law state (e.g. New York), without regard to its conflict-of-law provisions. (b) Consent to Jurisdiction. Each party irrevocably submits to the exclusive personal jurisdiction of the state and federal courts located in Venue county (e.g. New York) County, Governing law state (e.g. New York) for any action or proceeding arising out of or relating to this Agreement that is not subject to arbitration under the Dispute Resolution clause (if any). (c) Venue. Each party waives any objection to the laying of venue in the courts identified in Section (b), and waives any claim that such courts are an inconvenient forum. (d) Service of Process. Service of process in any such action may be made by any method authorized by the applicable court rules or by mailing a copy of the summons and complaint by registered or certified mail, return receipt requested, to the party's address set forth in this Agreement. (e) Prevailing Party. In any dispute arising under this Agreement, the prevailing party is entitled to recover its reasonable attorneys' fees and costs from the non-prevailing party, unless the parties have agreed to a different allocation in the Dispute Resolution clause.

DISPUTE RESOLUTION (a) Good-Faith Negotiation. Before initiating any formal dispute proceeding, the parties will attempt to resolve any dispute, controversy, or claim arising out of or relating to this Agreement ("Dispute") through good-faith negotiation. Either party may initiate this step by delivering written notice to the other describing the Dispute in reasonable detail ("Dispute Notice"). Senior representatives of each party with authority to resolve the Dispute will meet (in person, by phone, or by videoconference) within 10 business days of the Dispute Notice and attempt to resolve the matter in good faith for a period of 30 business days from the date of the Dispute Notice (or longer, if agreed in writing). (b) Mediation. If the Dispute is not resolved through negotiation within the timeframe in Section (a), either party may submit it to non-binding mediation administered by Mediation provider (e.g. JAMS, AAA) (or, if the parties cannot agree on a provider, by the American Arbitration Association under its Commercial Mediation Procedures). The mediation will take place in Mediation city, Mediation state. The parties will share mediator fees equally. Each party will bear its own legal fees for the mediation. (c) Binding Arbitration. If the Dispute is not resolved through mediation within 60 days after the appointment of the mediator, either party may demand binding arbitration. Arbitration will be administered by Arbitration provider (e.g. JAMS, AAA) under its then-current Arbitration rules (e.g. Commercial Arbitration Rules), before a single arbitrator. The arbitration will take place in Arbitration city, Arbitration state. The arbitrator's decision will be final and binding and may be entered as a judgment in any court of competent jurisdiction. The parties agree that the arbitration — including its existence, proceedings, and any award — is confidential. (d) Exceptions to Arbitration. Either party may seek emergency injunctive or other equitable relief from a court of competent jurisdiction without first completing the negotiation or mediation steps, to prevent irreparable harm — including to protect Confidential Information or intellectual property — pending the outcome of arbitration. (e) Small Claims. Either party may bring a Dispute in small claims court if the amount in controversy falls within that court's jurisdictional limit. (f) Class Action Waiver. Each party waives any right to bring or participate in any class action, class arbitration, or representative proceeding relating to this Agreement. (g) Governing Law for Arbitration. The arbitration will be governed by the Federal Arbitration Act (9 U.S.C. §§ 1–16) and, where not preempted, by the laws of Governing law state (e.g. New York).

12.1 General Restriction. Neither Party may assign, delegate, or transfer any of its rights or obligations under this Agreement, in whole or in part, without the other Party's prior written consent, which will not be unreasonably withheld or delayed. 12.2 M&A Exception. Notwithstanding Section 12.1, either Party may assign this Agreement without consent in connection with a merger, acquisition, change of control, or sale of all or substantially all of the assets to which this Agreement relates, provided that: (a) the assignee assumes all obligations of the assigning Party under this Agreement; and (b) the assigning Party provides the other Party written notice within thirty (30) days of the assignment. 12.3 Void Assignment. Any purported assignment in violation of this Section is void. 12.4 Binding Effect. This Agreement is binding upon and inures to the benefit of the Parties and their permitted successors and assigns.

13.1 Form. All notices, requests, demands, consents, and other communications required or permitted under this Agreement ("Notices") must be in writing. 13.2 Delivery Methods. Notices may be delivered by: (a) personal delivery; (b) nationally recognized overnight courier (e.g., FedEx, UPS); (c) certified or registered mail, return receipt requested, postage prepaid; or (d) email to the address specified below, provided that the sender retains proof of transmission and does not receive an automated bounce or delivery-failure notification within twenty-four (24) hours. 13.3 Effectiveness. Notices are effective: (a) upon personal delivery; (b) one (1) business day after deposit with overnight courier; (c) three (3) business days after deposit in the mail; or (d) on the day of email transmission if sent by 5:00 PM recipient's local time on a business day, or on the next business day if sent after 5:00 PM or on a non-business day. 13.4 Addresses. To Provider: Your name / business name, Provider Notice Address, Email: Provider Legal/Notice Email To Customer: Client name / business name, Customer Notice Address, Email: Customer Legal/Notice Email Either Party may change its notice address by providing written notice to the other in accordance with this Section.

If any provision of this Agreement is held by a court of competent jurisdiction to be invalid, illegal, or unenforceable under applicable law, that provision will be: (a) modified to the minimum extent necessary to make it valid, legal, and enforceable while preserving the Parties' original intent; or (b) if modification is not possible, severed from this Agreement. The validity, legality, and enforceability of the remaining provisions will not in any way be affected or impaired. The Parties agree to negotiate in good faith a replacement provision that, to the greatest extent possible, achieves the intended commercial purpose of the severed provision.

15.1 Integration. This Agreement, together with all SOWs, Change Orders, and exhibits executed hereunder, constitutes the entire agreement between the Parties with respect to its subject matter and supersedes all prior and contemporaneous agreements, negotiations, representations, warranties, and understandings, whether written or oral, relating to the same subject matter. 15.2 No Oral Modifications. No oral statement, prior course of dealing, trade usage, or conduct will be used to supplement, interpret, or contradict the written terms of this Agreement. 15.3 Purchase Orders. Any terms set forth in Customer's purchase orders, vendor registration forms, or similar documents are of no force or effect and do not modify this Agreement unless expressly incorporated into a signed SOW or Change Order. 15.4 Results Representations. Customer acknowledges that no employee, agent, or representative of Provider has authority to guarantee specific results or outcomes, and that any such representation made outside this Agreement is not binding on Provider.

16.1 Electronic Signatures. This Agreement and any SOW or amendment may be signed by electronic signature, including signatures created through E-Signature Platform (e.g., DocuSign, HelloSign) or any other electronic signature service compliant with the Electronic Signatures in Global and National Commerce Act (E-SIGN Act), 15 U.S.C. § 7001 et seq., and the Uniform Electronic Transactions Act (UETA) as enacted in the applicable jurisdiction. Electronic signatures have the same legal effect as original handwritten signatures. 16.2 Counterparts. This Agreement may be executed in one or more counterparts, each of which will be deemed an original, and all of which together will constitute one and the same instrument. Delivery of an executed counterpart by electronic transmission (including PDF or electronic signature platform delivery) is equally effective as delivery of a manually executed counterpart.

In the event of a conflict between documents comprising this Agreement, the following order of precedence applies (highest to lowest): (1) any executed Change Order, but only with respect to the specific provision it expressly modifies; (2) the applicable Statement of Work (SOW), but only with respect to the specific Services it covers; (3) the Cover Page (if applicable); (4) these Standard Terms. This order of precedence does not apply to Section [limitation-of-liability] or Section [disclaimer-of-warranties], which control in all cases notwithstanding any contrary term in an SOW or Change Order unless the SOW or Change Order expressly states that it increases the liability cap.

Clause Number / Reference (e.g., 8, 12.3) App-Store Submission, Rejection & Policy-Drift Responsibility. Clause Number / Reference (e.g., 8, 12.3).1 Submission Process. Developer shall prepare the Application for submission to the Apple App Store and Google Play Store (collectively, "Stores") in accordance with each Store's then-current technical and metadata requirements. Unless otherwise specified in the Statement of Work, all submissions shall be made through Client's Apple Developer Program account and Google Play Console account ("Client Accounts"). Client is solely responsible for (a) establishing and maintaining Client Accounts in good standing, including payment of all associated enrollment fees and acceptance of each Store's developer agreement, and (b) providing Developer with the access credentials, provisioning profiles, signing certificates, and any other account-level permissions required to build and submit the Application. Clause Number / Reference (e.g., 8, 12.3).2 Compliance Warranty. Developer warrants that, as of each submission date, the Application complies in all material respects with the Apple App Review Guidelines and the Google Play Developer Program Policies as published on that date ("Store Policies"). Developer's compliance warranty is limited to the Application code, architecture, and design choices made by Developer. It expressly excludes compliance issues arising from: (a) Client Content (as defined in the Statement of Work); (b) Client's business model, pricing, or in-app purchase structure; (c) Client's legal or regulatory status in any jurisdiction; or (d) any third-party SDK or service specified by Client. Clause Number / Reference (e.g., 8, 12.3).3 Rejection Remediation. (a) Developer-Caused Rejections. If a Store rejects the Application for reasons solely attributable to Developer's code, design, or submission preparation errors (a "Developer Rejection"), Developer shall, at no additional charge to Client, remediate the identified deficiencies and resubmit the Application within 10 business days of receiving the Store's rejection notice from Client. (b) Client-Caused and Platform-Caused Rejections. Rejections attributable to Client Content, Client's account standing, Client's business model, or any Store Policy change that took effect after the initial submission date (each a "Non-Developer Rejection") are outside the scope of the Project Fee. Developer shall provide Client with a written assessment of the required remediation within 5 business days of receiving the rejection notice. Remediation of Non-Developer Rejections shall be scoped and billed as a Change Order under Section 2 of this Agreement. (c) Disputed Rejections. Where the cause of a rejection is ambiguous, the parties shall confer in good faith within 5 business days. If the parties cannot agree, the rejection shall be treated as a Non-Developer Rejection pending resolution, without prejudice to Client's right to dispute the classification. Clause Number / Reference (e.g., 8, 12.3).4 Platform Policy Monitoring. For 12 months following the Application's initial public launch on each Store (the "Monitoring Period"), Developer shall monitor each Store's publicly published policy update channels for material changes to Store Policies that would require modification of the Application ("Policy Changes"). Developer shall notify Client in writing within 30 business days of becoming aware of any such Policy Change. Notification shall include Developer's good-faith assessment of (a) which Application features or behaviors are affected, (b) the Store-published compliance deadline, and (c) a preliminary estimate of remediation effort. Policy Changes that require modification of the Application shall be scoped and billed as Change Orders, except that modifications required solely because Developer's original implementation failed to comply with a Store Policy in effect at the time of delivery shall be remediated at no charge. Clause Number / Reference (e.g., 8, 12.3).5 No Guarantee of Acceptance. THE PARTIES ACKNOWLEDGE THAT EACH STORE RETAINS SOLE AND ABSOLUTE DISCRETION TO APPROVE, REJECT, REMOVE, OR RESTRICT ANY APPLICATION OR DEVELOPER ACCOUNT AT ANY TIME, WITHOUT NOTICE AND WITHOUT PROVIDING REASONS, AND THAT NEITHER PARTY CAN GUARANTEE STORE ACCEPTANCE. DEVELOPER MAKES NO WARRANTY, EXPRESS OR IMPLIED, THAT THE APPLICATION WILL BE ACCEPTED BY ANY STORE OR WILL REMAIN AVAILABLE FOR DISTRIBUTION AT ANY TIME AFTER ACCEPTANCE. NEITHER PARTY SHALL BE IN BREACH OF THIS AGREEMENT SOLELY AS A RESULT OF A STORE'S DECISION TO REJECT OR REMOVE THE APPLICATION, PROVIDED THAT THE AFFECTED PARTY HAS PERFORMED ITS OBLIGATIONS UNDER THIS SECTION Clause Number / Reference (e.g., 8, 12.3). Clause Number / Reference (e.g., 8, 12.3).6 Account Suspension Risk. If a Store suspends or terminates a Client Account for reasons attributable to Client (including non-payment of account fees, violation of a Store's developer agreement by Client, or Client's fraudulent conduct), any costs incurred by Developer in connection with such suspension—including resubmission to a new account—shall be borne by Client and billed as a Change Order. Developer shall not be deemed in breach of any delivery obligation during the period a Client Account suspension prevents submission or distribution.

Usage Restrictions. Client shall use the Software solely for Client's internal business purposes in accordance with the Documentation and any applicable Order Form. Client shall not, and shall ensure that its Users do not: (a) Reverse Engineering. Reverse engineer, decompile, disassemble, or otherwise attempt to derive or reconstruct the source code, underlying algorithms, data structures, or trade secrets of the Software, except to the limited extent expressly permitted by applicable law notwithstanding this restriction; (b) Sublicensing and Distribution. Sell, sublicense, rent, lease, lend, transfer, assign, or otherwise make the Software available to any third party, except as expressly authorized in writing by Your name / business name; (c) High-Risk Activities. Use the Software in connection with any High-Risk Activity, including without limitation the design, development, operation, or maintenance of nuclear facilities, aircraft navigation or communication systems, air traffic control systems, medical life-support systems, weapons systems, or any other application in which a failure of the Software could reasonably be expected to cause death, personal injury, or severe physical or environmental damage; (d) Competitive Development. Use the Software, its output, or any proprietary methods, features, or know-how embodied therein to design, develop, or assist in the development of any product or service that competes with the Software or any other product or service offered by Your name / business name, or to benchmark or publicly compare the Software's performance against any competing product without Your name / business name's prior written consent; (e) Security Circumvention. Circumvent, disable, defeat, or interfere with any security feature, access control, license-enforcement mechanism, or technical protection measure incorporated in the Software; (f) Proprietary Notices. Remove, obscure, or alter any copyright notice, trademark, logo, legend, or other proprietary rights notice appearing in or on the Software or its Documentation; (g) Unauthorized Access. Use the Software to gain unauthorized access to any system, network, data, or account, or to conduct vulnerability testing, penetration testing, or denial-of-service attacks on any infrastructure without the prior written consent of the owner of that infrastructure; or (h) Unlawful Use. Use the Software in any manner that violates applicable law, infringes any third-party intellectual property right, or facilitates fraud, harassment, or distribution of malicious code. Client is responsible for all acts and omissions of its Users as if they were Client's own. Your name / business name may suspend Client's access to the Software upon reasonable notice if Your name / business name reasonably determines that Client or any User is violating this Section, and may terminate this Agreement for material breach in accordance with Section Termination-for-Convenience Section Reference if such violation is not cured within 3 days of written notice.