Terms

Master Service Agreement

Between: CommandKey AI, LLC, an Alabama limited liability company ("Provider," "we," "us"), and the client named in the order form, a business or a person acting for a business ("Client," "you"). Each is a "Party."

Effective Date: the date Client accepts its first order form | Version: 6.19, published November 8, 2026

1. Services, Order Forms, and Order of Precedence

Provider supplies planning documents, self-install release packages, configuration materials, documentation, and ongoing release support for a client-controlled AI system built to run with Anthropic's Claude. Provider will not intentionally start a login to, remotely control, or open a remote-access session with Client's computers or Client-controlled accounts. The only exception is the Service Control described in Section 10, which works through a signed notice the installed system checks, not through a login or remote session. Provider receives only what Client or the installed system sends through the channels this Agreement and the Client Security Disclosure describe.

Each engagement is described in an order form. An "Engagement" means an accepted order form and the services under it. An order form is accepted in either of two ways: (a) Client signs it through the electronic signature service Provider sends it with (for example, DocuSign), entering the full name and title of the person signing and confirming their authority to bind Client; or (b) Client replies by email to the message that attached it, from an email address Client has designated or has used to deal with Provider, with the words "I accept the attached order form, this Master Service Agreement, and its jury waiver" and the typed full name and title of the person accepting. Either way, acceptance covers the order form and the versions of this Agreement and the Client Security Disclosure identified in it, and the signed copy or the reply is the record of acceptance. The person accepting represents that they are authorized to bind Client, and each Party represents that it has authority to enter into this Agreement.

Prices are fixed once an order form is accepted, except Care prices, which may change only as Section 2 allows. Provider's website is descriptive only and is not part of this Agreement. No purchase order, supplier portal, or other Client form adds to or changes these terms.

Order of precedence. If documents conflict: (1) an applicable open-source or third-party license controls, but only for the material it governs; (2) the order form controls on price, scope, users, computers, schedule, payment, and any provision it expressly says amends this Agreement; (3) this Agreement controls on all other terms; (4) the Client Security Disclosure controls on the technical description of the security controls and their known limits.

Engagement types:

Work outside an order form's scope needs a new order form or a written change accepted by both Parties.

Definitions. "Business day" means Monday through Friday, excluding US federal holidays, US Central time. "Minimum Requirements" means the computer and account requirements stated in the Client Security Disclosure or the order form. "Security Layer" has the meaning in Section 12. "Release" means a versioned software package Provider distributes through its designated release channel.

2. Fees, Payment, and Taxes

3. How the Work Is Delivered

Communications, instructions, reports, approvals, notices, and support are delivered in writing by email. Support may also be given in the CommandKey app; anything that changes this Agreement, and every formal notice, is by email. No calls are required. Any call is optional, informational, and does not change this Agreement. Releases are delivered through Provider's designated release channel. A cancellation submitted through the cancellation method stated in Section 2 is a written notice under this Agreement even though it is not sent by email.

Client runs and supervises the installation using Client's own Claude subscription, Client's own agent, Provider's written instructions, and the release package. Client controls every step and can stop at any time. No Engagement runs on Provider's accounts or credentials. Client's Claude subscription and other accounts, including their billing, are Client's own.

Before installation, Client confirms in writing that a current backup of the computer exists and that full-disk encryption is on (Section 7).

Go-live is the date that starts the free month and the 30-day install warranty. It is the earliest of: (1) the day the delivered release first completes the daily Service Control check described in Section 10, as shown in Provider's records (the first check normally runs when the install finishes); (2) the date Client confirms in writing that the system is running; or (3) 30 calendar days after Provider delivers the setup package and emails Client that it was delivered, provided Provider sent Client a written reminder at least 5 calendar days before that date (if the reminder is sent late, this date becomes the fifth calendar day after the reminder). An order form may turn off clause (3). Using the installed release for Client's business counts as Client's written confirmation that it is running. Provider emails Client the go-live date and the date the free month ends within one business day after go-live. A check-in shows only that the release is installed and running. It is not an inspection of Client's computer and not a certification that every check passed or that Client's computer is secure.

Reporting a failed check. If a post-install check fails, Client may email Provider, within 5 business days after the go-live notice, a failure report that names the install, the post-install check or function that failed, what Client expected and what happened, the steps that produced it, and any error message or screenshot reasonably available. A report that only says the system does not work does not change go-live; Provider will say what is missing. Provider responds within 3 business days. If Provider confirms a reproducible failure of the release as delivered, Provider supplies a corrected release or written correction instructions, and go-live moves to the day the correction is applied (or the day Provider sends written correction instructions), so Client's free month starts again from that day. If Provider finds no such failure, Provider explains why in writing and go-live stays as notified. A repeat report about the same issue without material new information does not change go-live again. Go-live does not change because of a failure caused by Client's computer not meeting the Minimum Requirements, by Client's modification or misuse, or by Client blocking or disabling the daily Service Control check, nor because Client does not install, run the checks, or respond. If Client does not give Provider reasonably available diagnostic information within 5 business days after Provider asks for it in writing, the report stops affecting go-live.

Service standard. Provider will perform the services in a professional and workmanlike manner, consistent with generally accepted industry practice for similar services. If Client tells Provider in writing within 30 days after delivery that a deliverable does not meet this standard, Provider will re-perform or correct it at no charge, and if Provider cannot do so within a reasonable time, will refund the fees paid for that deliverable. A refund of Install fees ends Client's license to that release, and Provider may then remove the installed release through the Service Control as Section 10 allows. The 30-day window sets when the free re-performance is available. It does not shorten any time the law gives Client to bring a claim. Re-performance or refund is Client's exclusive remedy for breach of this service standard, and any other claim about a deliverable is subject to Section 5. For an Install, "delivery" for purposes of this service standard means go-live.

Limited install warranty. For 30 calendar days beginning at go-live, Client may report in writing a reproducible failure of the release accepted at go-live to perform materially as described in the Handoff Documentation. For a timely reported covered failure, Provider will, at no additional charge and within a reasonable time, supply a corrected release or written correction instructions.

The install warranty does not cover a failure caused by Client's modification or misuse; Client's failure to follow the Handoff Documentation; alteration, disabling, or bypass of the Security Layer; hardware, operating systems, networks, internet service, or accounts that do not meet the Minimum Requirements; a third-party service, outage, change, or discontinued function; Client's data; or a change made after go-live that Provider did not supply or approve in writing. Client will provide the status reports and other non-confidential diagnostic information reasonably needed to reproduce the reported failure.

Client must report a covered failure before the 30-day period expires, but Provider's obligation to complete a correction for a timely report continues after expiration. A correction does not restart or extend the warranty period. Correction under this paragraph is Client's sole remedy under the install warranty, without limiting any separate remedy that applies under the service standard or the First-Workflow Guarantee in this Section.

First-Workflow Guarantee. This paragraph applies only to an Install whose accepted order form names one job the installed system is to do for Client (the "Named Job"), described and agreed in writing by both parties on the order form before Client signs. The Named Job is working when the installed release performs it materially as the order form describes, on Client's normal workdays and on a computer that meets the Minimum Requirements, judged against that description and the Handoff Documentation. If it is not working, Client may email support@commandkey.ai a notice, sent within 30 days after go-live (Section 16's next-business-day rule does not apply to this deadline), that says it is a notice under the First-Workflow Guarantee and describes what is not working. The 30 days run from go-live as finally set under this Section. Provider then has 5 business days after receiving the notice to make the Named Job work, by a corrected release or written correction instructions. That time pauses while Provider waits on Client for diagnostic information or for Client to apply a correction. If the Named Job is still not working when that time ends, Provider refunds as stated below. This paragraph does not apply to a failure caused by anything the install warranty excludes, including Client's changes to the system and third-party outages, by Client not installing or not running the install, or by a suspension under Section 10. A disagreement over whether the Named Job is working is a dispute under Section 15. Provider refunds, within 15 business days after that time ends, all Install fees Client paid in money under that order form (not a credited Blueprint or One-Job Fix fee). Any Install payment not yet paid is cancelled and no longer due. Care for that install ends on the refund date. Care fees already charged for a month that has started are not refunded, except that Provider refunds an annual Care fee for each unused whole month after the refund date, calculated as stated in Section 2 for annual Care that Provider ends. Fees refunded under this paragraph cannot also be refunded under the service standard, and a refund under the service standard ends this guarantee for that order. A refund under this paragraph ends Client's license to that release, and Provider may then remove the installed release through the Service Control as Section 10 allows. Each Client may receive one refund under this paragraph across all of its orders. It does not expand any other remedy under this Agreement. Section 5 still applies, and a refund under this paragraph counts toward its cap.

Not a security or compliance service. The services are planning, configuration, documentation, and software-release services. They are not managed security, monitoring, incident-response, legal, audit, or compliance services. Provider does not promise to find or prevent every vulnerability, malicious instruction, unauthorized action, or security incident.

Provider's tools and subcontractors. Provider uses AI tools, under human accountability, to draft, review, and deliver its work. The AI providers that may receive Client information are named in the Client Security Disclosure. Provider may use subcontractors and remains responsible for their work under this Agreement.

4. Data Handling

Client's data. Client's data, files, and business information remain Client's property. The installed system's files and memory stay on Client's computer. Provider does not host the system. In ordinary operation, Provider receives only (a) what Client sends by email, which is stored in Provider's business email account and processed with the AI providers named in the Client Security Disclosure, and (b) Care metadata, described below.

Client grants Provider a limited, non-exclusive right to receive, store, copy, and process information Client sends only as needed to perform the Engagement, administer this Agreement, secure Provider's systems, and comply with law. Provider does not sell Client information and does not itself use it to train any AI model. Provider will not send Client information to an AI provider not named in the Client Security Disclosure without first telling Client and getting Client's written consent.

Care metadata. While Care is active, the installed system emails Provider a monthly status summary: counts and categories of actions the system attempted, blocked, or held for approval; component status and release version; whether the Security Layer is enabled; and, as counts only and never names, how many user profiles on the computer have the system or Claude Code set up and how many distinct phones have answered approvals. Until automatic sending is available in Client's installed release, the system saves this summary on Client's computer and Client sends it to Provider when Provider asks. Provider uses commercially reasonable measures to design this summary to exclude Client content, prompts, command text, credentials, and file names. If Provider learns that materially different information was sent, Provider will stop or correct the transmission and handle the information under Sections 4, 8, and 11. The installed system also performs the daily Service Control check described in Section 10, which sends no Client content. Provider will not add any other automated communication from the installed system to Provider unless the Client Security Disclosure describes it and Client approves the change in writing.

Third parties in the data path. The system runs on Client's own Claude subscription, so the content it processes is sent to Anthropic under Client's own Anthropic account terms. If Client uses the CommandKey phone app, its messages and notifications travel through Provider's relay and the phone operating system's push notification service, a third party. The Client Security Disclosure explains what data leaves Client's computer and to whom.

Data Client may not send to Provider or through the CommandKey app: passwords, authentication tokens, or private keys; full Social Security numbers; payment card data or bank account numbers; protected health information; Federal Contract Information, Controlled Unclassified Information, export-controlled technical data, or classified information; and any other information the law or Client's contracts bar from that channel or from disclosure to Provider.

Excluded use. The standard service is not offered for, and Client will not use it with, Controlled Unclassified Information, export-controlled data, classified information, protected health information, or regulated financial-services data. Client remains responsible for access, permissions, retention, and safeguards for all information on its own systems.

Retention and deletion. While an Engagement continues, Provider purges emailed content older than 12 months that it no longer needs. When the last Engagement ends, or on Client's written request, Provider deletes the Client information it holds within 30 days, except billing records, copies the law requires Provider to keep, and copies in routine provider backups until they expire, which stay covered by Section 8.

4A. Security Disclosure

Before accepting, Client acknowledges receiving and reviewing the Client Security Disclosure. It describes the security controls in the installed system, the categories of attack they do not fully defend against, and what data leaves Client's computer. The disclosure describes the system as Provider understood it on the Effective Date. Provider prepared it with reasonable care and will tell Client without unreasonable delay if Provider learns of a material change or a material error that affects Client's installed release or Provider's handling of Client's information. The disclosure is not a warranty. No security control described in this Agreement or the disclosure is absolute or guaranteed, and Client agrees not to treat any statement in the disclosure as a promise that a listed control will catch every action it targets.

5. LIMITATION OF LIABILITY

THIS SECTION LIMITS WHAT EITHER PARTY CAN RECOVER. PLEASE READ IT.

5A. AI Output; No Guaranteed Results; DISCLAIMER

The installed system and some of Provider's written deliverables use probabilistic AI models. Outputs may be inaccurate, incomplete, biased, outdated, not unique to Client, or fabricated, and factual statements that look reliable may be wrong. Outputs are not legal, tax, accounting, financial, medical, cybersecurity, or other professional advice. Unless an order form says otherwise, outputs are not reviewed by a human on Provider's behalf. Client is responsible for reviewing outputs before relying on them, making a decision with them, or sending them outside Client's organization.

Provider does not promise any particular time saved, revenue, cost reduction, or other business result.

DISCLAIMER. EXCEPT FOR THE SERVICE STANDARD IN SECTION 3 AND ANYTHING ELSE THIS AGREEMENT EXPRESSLY STATES, THE SERVICES, THE RELEASES, THE PROVIDER MATERIALS, AND THE INSTALLED SYSTEM ARE PROVIDED "AS IS" AND "WITH ALL FAULTS," WITHOUT ANY WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, OR NON-INFRINGEMENT. PROVIDER DOES NOT WARRANT THAT THE SYSTEM OR ANY AI OUTPUT WILL BE ACCURATE, COMPLETE, SECURE, UNINTERRUPTED, OR ERROR-FREE. Section 6 is Client's exclusive remedy for infringement claims.

5B. Third-Party Services

The installed system depends on services Client contracts for directly, including Anthropic, Client's phone and notification services, and Client's email and calendar providers. Provider does not accept, negotiate, or sign any provider's terms for Client, does not control those services, and is not responsible for their availability, pricing, terms, model changes or retirements, or actions on Client's accounts.

6. Indemnification

7. Client Responsibilities

Client is responsible for:

Authorized Users are the people named in the order form. An Authorized User is one named individual who gives the system instructions or approvals through any channel, including a messaging app or shared credentials; sharing credentials does not combine two people into one Authorized User. Each Authorized User uses their own Claude account. Client may reassign an Authorized User seat when the named person leaves Client or stops using the system. A Professional order covers at most two Authorized Users; three or more require a Team order. An approval given by any Authorized User is Client's approval. Client is responsible for its Authorized Users' use of the system.

Always-on work. Scheduled and after-hours agent work runs on Client's own computer and happens only while that computer meets the Minimum Requirements and is powered on, awake, and connected to the internet.

8. Confidentiality

9. Intellectual Property, License, and Attribution

9A. Case Study and Publicity

Provider will not publish a case study, Client's name or logo, or anything that reasonably identifies Client without Client's written approval of the final version. Any case-study commitment tied to founding pricing is stated in the order form. Unless it says otherwise: Client completes Provider's case-study questionnaire within 30 days after go-live; Provider sends a draft; if Client neither approves, corrects, nor objects in writing within 10 business days, the draft is approved; Client may choose an anonymized version instead, and because it does not identify Client, Client's approval is not required for it; and if Client does not take part, the difference between the standard and founding Install price, both stated in the order form, becomes due 15 days after Provider's written notice.

10. Care, Corrections, Term, and Termination

Care, the "Care Package": the free month, then optional and paid. Every Install includes the first 30 days of Care free, starting at go-live (the free month described in Section 2). If Client does not enroll, Care ends on day 31: updates, security updates, phone approvals (Command Keys), the monthly report, and support stop, the installed release keeps running, and Client may enroll at any time. After the free month, Care is optional and paid. Client may select monthly or annual Care, where offered, by completing the separate automatic-renewal consent described in Section 2. Care selected with an Install continues from the free month without a break, and billing begins on day 31. A Client that did not select Care with the Install may enroll later through a Care enrollment containing the same disclosures and separate unchecked consent box. The order form or Care enrollment will state the plan, recurring price, start date, renewal term, cancellation terms, and refund terms. Continued use of an installed release, or the free month, does not enroll Client in paid Care.

Updates and security updates are part of Care. While Care is active, Provider makes its tested releases available to Client, including security updates and security fixes for Provider Materials. Updates of every kind, security updates included, and support by email and in the CommandKey app are Care benefits. Provider does not provide them to a Client whose Care has ended, including a Client whose free month ended without enrolling. Approving actions from Client's phone (phone approvals), as made available to Client's installed release, is also a Care feature: it relies on a Care authorization Provider issues for the free month and for each paid Care term, and without active Care, actions that need Client's approval are approved at Client's computer instead. As made available to Client's installed release, the CommandKey phone app, its relay and push notifications, phone approvals (Command Keys), and the Command Center are Care features and stop when Care ends. Approvals and chat at Client's computer, and every other function of the installed release, keep working without Care. This paragraph applies to orders accepted on version 6.17 or later. An order accepted on an earlier version keeps the terms it was signed under, and a signed order form's own terms control as stated in the acceptance paragraph of Section 1.

What Care corrects. Care includes commercially reasonable correction of reproducible failures of the installed release to perform materially as described in the Handoff Documentation. There is no monthly limit on corrections. A correction request is one written report of one reproducible failure of one documented behavior, with the post-install check's status report attached. Corrections for a material security vulnerability in Provider Materials, or for a defect Provider's own release introduced, are also included. Care does not include new functionality, changed requirements, or restoring functionality a third-party provider discontinued, and does not cover problems caused by Client's changes, Client's hardware, operating system, network, or internet, Client's third-party accounts and their outages or terms, or data Client put into the system. Work outside Care needs a fixed-price order form.

Upstream changes. If Anthropic or another upstream provider makes a change that materially affects installs, Provider will assess it promptly and give Care clients a written status and plan, and a tested release or documented workaround when one is reasonably available.

Term. This Agreement starts on the Effective Date and continues until every Engagement has ended and, after that, until either Party ends it by written notice. A Blueprint is complete on delivery. An Install is complete at go-live plus the 30-day install warranty.

Inactive Engagements. If Client does not respond to Provider's written requests for 60 days during an Install, Provider may close the Engagement by written notice. Amounts paid are kept for work performed, nothing further is due, and Client may restart within 6 months under a new order form at then-current pricing, with the amount paid credited in full.

Termination for cause. Either Party may end this Agreement or any Engagement by written notice if the other materially breaches it and does not cure the breach within 30 days after written notice describing it (10 days for non-payment). Either Party may end it immediately if the other stops doing business in the ordinary course.

After termination. Client pays fees for work delivered through the end date and keeps its license under Section 9 unless that license ends as Section 9 provides. Except for the Service Control below, nothing in this Agreement gives Provider any ongoing access or control. When Care ends, Provider stops release notices, updates, security updates, reports, corrections, and support, including email and app support, and Client may keep using the last installed release. Provider will tell Client in writing, when Care ends, that security updates have stopped. Without active Care, Provider has no obligation to provide any update, security update, or security fix, and Client is solely responsible for keeping the installed release, its computer, and its accounts secure and up to date. Provider is not responsible for a vulnerability that becomes known, or an attack that happens, while Client is not enrolled in Care, or for changes Client or a third party makes after Care ends. This does not limit the 30-day install warranty in Section 3.

Service Control. Every installed release, on every plan, checks once a day for a notice signed with Provider's service-control key, using only a hash of its installation identifier and sending no Client content. Provider may issue (a) a suspension notice, which pauses the installed system (chat, scheduled jobs, phone-app messaging and voice stop) while leaving all of Client's files, data, memory vault, and accounts untouched, or (b) a removal notice, which removes Provider's software and the Security Layer's CommandKey components from the computer and leaves all of Client's files, data, memory vault, and accounts in place. Provider may issue a suspension notice only after (1) Client fails to pay an undisputed amount when due, materially breaches this Agreement, or starts a chargeback, and (2) Provider has given Client written notice describing the problem and the suspension date at least 15 days in advance (or the cure period under Termination for cause, if longer), and Client has not cured by that date. Provider may issue a removal notice only after Client's license has ended under Section 9 and Provider has given Client at least 15 days' written notice. Provider lifts a suspension within one business day after Client cures. Provider will never use the Service Control to read, copy, change, or delete Client's files or data, and will never use it for any other purpose, except that Provider records the time of each installation's first and most recent daily check and the number of checks, and uses those records to set go-live under Section 3 and to support the installation. Client agrees to this Service Control as a condition of the license and will not disable or tamper with it; doing so is a material breach.

11. Security Incidents

A "Security Incident" means (1) confirmed unauthorized access to or disclosure of Client information held in Provider's own systems, or (2) Provider's confirmation that malicious or unauthorized code was introduced into a release Provider delivered to Client. Provider will notify Client within 3 business days after confirming a Security Incident, unless the law requires earlier notice, with the information reasonably available to it, written containment or remediation instructions or a corrected release where available, and reasonable cooperation with Client's own legally required notifications. Provider does not monitor Client's computer or accounts and may not detect an incident occurring there. Client handles containment and investigation on its own systems, following Provider's written instructions where they apply.

12. Approval for High-Risk Actions

The installed release is designed so that the system drafts by default and asks an Authorized User for approval before taking the high-risk actions listed in the Client Security Disclosure. The Disclosure states which of those actions are enforced by the Security Layer (a code-level check that runs before the AI model's own judgment and outside the customizable persona configuration) and which depend on configuration that Client controls and Section 7(h) protects. Client acknowledges that configuration-based controls are less reliable than code-enforced controls. A reply to an Authorized User through the channel that user used to make a request counts as approved by that request. Model-processing calls, read-only retrieval, and the Care metadata email are not communications for this section. Approving a workflow in advance does not approve each action in it, unless the order form and release documentation expressly identify a specific recurring action as approved in advance.

The Security Layer reduces risk but can be bypassed by defects, unsupported tools, Client modifications, malicious instructions or code, third-party changes, or the other limits described in the Client Security Disclosure. It is not a guarantee that every covered action will be caught. Approvals are given on Client's computer unless the release documentation states that another channel is supported.

13. No Compliance or Certification Claims

Provider does not certify, and does not represent, that Client is compliant with any law, regulation, or framework, including CMMC, FAR 52.204-21, HIPAA, or GLBA. Any mapping of system controls to a framework is supporting evidence only. Compliance remains Client's responsibility. The services are commercial services and the Provider Materials are commercial computer software and documentation. If Client intends to use any deliverable in performing a Government contract or subcontract, Client will say so before ordering, and no Government contract clause applies to Provider unless Provider expressly accepts it in a signed addendum.

14. Insurance

During each paid Engagement, Provider carries professional liability and cyber liability insurance and will give Client a certificate of insurance on reasonable written request. The certificate, not this Agreement, states the coverage in force.

15. Governing Law, Courts, and Disputes

This Agreement is governed by the laws of the State of Alabama, without regard to its conflict-of-laws rules. Client is a business and enters this Agreement for business purposes, not for personal, family, or household use.

Before filing any claim, the Parties will try in good faith to resolve the dispute by email between their decision-makers for 30 days. After that, any suit must be brought exclusively in the state courts located in Coffee County, Alabama, Enterprise Division, or, if federal subject-matter jurisdiction independently exists, the United States District Court for the Middle District of Alabama. Each Party consents to personal jurisdiction and venue in those courts and waives any objection based on inconvenient forum. This does not prevent either Party from filing an eligible claim in the small-claims division of the Coffee County District Court, or from seeking an injunction in any court to protect its Confidential Information or intellectual property without waiting out the negotiation period. In any suit to collect fees or to enforce Section 8 or Section 9, the prevailing Party may recover its reasonable attorneys' fees and costs.

JURY WAIVER. EACH PARTY KNOWINGLY, VOLUNTARILY, AND INTENTIONALLY WAIVES ANY RIGHT TO A TRIAL BY JURY IN ANY ACTION, PROCEEDING, OR COUNTERCLAIM ARISING OUT OF, RELATING TO, OR IN ANY WAY CONNECTED WITH THIS AGREEMENT, ANY ORDER FORM, ANY ENGAGEMENT OR DELIVERABLE, THE CLIENT SECURITY DISCLOSURE, OR THE RELATIONSHIP BETWEEN THE PARTIES, WHETHER THE CLAIM SOUNDS IN CONTRACT, TORT, FRAUD, OR STATUTE, AND INCLUDING CLAIMS ABOUT HOW THIS AGREEMENT OR ANY ORDER FORM WAS FORMED OR INDUCED. EACH PARTY CONFIRMS THAT IT HAS READ THIS WAIVER, HAS HAD THE OPPORTUNITY TO REVIEW IT WITH A LAWYER OF ITS CHOICE, AND IS A BUSINESS ENTERING THIS AGREEMENT FOR BUSINESS PURPOSES.

16. General Terms

ACCEPTANCE. Accepted as described in Section 1: by electronic signature on the order form, with the full name and title of the person signing, or by email reply stating: "I accept the attached order form, this Master Service Agreement, and its jury waiver," with the typed full name and title of the person accepting.

Every order form carries, directly above its acceptance line: "This order form is governed by the Master Service Agreement, version 6.19, published November 8, 2026, including its limitation of liability in Section 5, its disclaimer in Section 5A, and its jury waiver in Section 15, which apply to this order form."

← Back to home