Master Network and Software Services Agreement (MNSA)
版本 3 · 更新于 2026年11月18日
This Master Network and Software Services Agreement (this “MNSA”) is entered into by and between 12Times Inc., a Delaware limited liability company with an address at 13 West Main Street, Felton, Delaware 19943 (“12Times” or “Provider”), and the customer identified in an applicable Order Form (“Customer”). This MNSA governs Customer’s access to and use of the Services and is incorporated by reference into each Order Form executed by the parties.
1. AGREEMENT STRUCTURE AND ORDER FORMS
1.1 Agreement Documents. The parties’ complete agreement for the Services consists of: (a) each Order Form (an ordering document executed by the parties, which may be titled a “Purchase & Subscription Agreement”); (b) this MNSA; (c) the Service Level Agreement provided by 12Times and identified in or attached to an Order Form (the “SLA”); (d) any Business Associate Agreement executed by the parties or incorporated into an Order Form (the “BAA”); and (e) any exhibit or policy expressly incorporated by an Order Form (collectively, the “Agreement”).
1.2 Acceptance. Customer accepts this MNSA by signing an Order Form that incorporates it, electronically accepting it, or accessing the Services after receiving an Order Form that identifies this MNSA, except where applicable law requires a different method.
1.3 Order Forms. Each Order Form identifies the Customer, the Services purchased, fees, subscription term, usage limits, implementation scope, and any customer-specific terms. No purchase order or vendor-portal term modifies the Agreement unless expressly signed by an authorized 12Times representative.
1.4 Order of Precedence. If the Agreement documents conflict, the following order applies (higher prevails):
| Priority | Document |
|---|---|
| 1 | The BAA — but only as to PHI, HIPAA, and matters expressly governed by it. |
| 2 | An Order Form — only where it expressly identifies the modified provision. |
| 3 | This MNSA. |
| 4 | The SLA. |
| 5 | Documentation and incorporated policies. |
1.5 Affiliates. An Affiliate may purchase Services under a separate Order Form, which creates a separate agreement with the entity signing it unless expressly stated otherwise.
2. DEFINITIONS
Capitalized terms have the meanings below; terms defined in the BAA or HIPAA have those meanings where used here.
“Affiliate” an entity that controls, is controlled by, or is under common control with a party.
“AI Features” artificial-intelligence, machine-learning, natural-language, or workflow-orchestration capabilities included in the Services.
“Authorized User” Customer personnel and contractors authorized to use the Services for Customer’s internal business purposes.
“Business Hours” 9:00 a.m. to 6:00 p.m. Eastern Time, Monday–Friday, excluding U.S. federal holidays, unless an Order Form states otherwise.
“Customer Data” data, content, records, instructions, templates, credentials, and information submitted to or accessed by the Services on Customer’s behalf, including End-User information and, for healthcare or PHI deployments, Patient Data and PHI.
“Customer Systems” Customer’s EHR/EMR, scheduling, messaging, portal, identity, network, and other systems or third-party accounts connected to the Services.
“Documentation” 12Times’ then-current user, configuration, and technical documentation provided for the Services.
“EHR” an electronic health/medical record, practice-management, scheduling, or similar healthcare information system.
“End User” an individual with whom Customer communicates or interacts through the Services, such as a patient, client, customer, guest, or other contact.
“Patient Data” information relating to an identified or identifiable patient, prospective patient, caregiver, or authorized representative; a subcategory of Customer Data and End-User information applicable to healthcare deployments.
“PHI” Protected Health Information as defined by HIPAA (including electronic PHI where applicable).
“Provider Materials” the Services, software, workflows, models, prompts, orchestration logic, Documentation, methods, know-how, and technology owned or licensed by 12Times, excluding Customer Data.
“Security Incident” an actual unauthorized acquisition, access, use, disclosure, alteration, loss, or destruction of Customer Data in systems under 12Times’ control, excluding routine unsuccessful attempts that do not compromise data.
“Services” the hosted software, AI-assisted administrative agents, communication routing, workflow automation, integrations, support, and professional services identified in an Order Form.
“Third-Party Service” a product, network, platform, API, EHR, messaging channel, cloud service, or other service not controlled by 12Times.
“Usage Data” technical and operational data regarding use and performance of the Services that does not identify an End User or Customer and does not contain PHI or message content.
3. SERVICES AND IMPLEMENTATION
3.1 Provision. 12Times will provide the Services identified in each Order Form in material accordance with the applicable Documentation, this MNSA, the SLA, and the BAA.
3.2 Scope of Services. The Services are hosted software and AI agents for customer communication and workflow automation. The specific functions, modules, communication channels, industry context, and data-handling model for each Customer are as specified in the applicable Order Form (channels may include WeChat, Gmail, WhatsApp, iMessage, or others). For healthcare or PHI deployments, the Services are limited to administrative functions — such as appointment scheduling (and rescheduling only where supported by the applicable system interface; otherwise routed to Customer staff); notification of a Customer-approved result status (such as normal, or abnormal—please contact the Customer), based solely on a status supplied by the Customer or its system of record or on Customer-defined deterministic rules and without independently interpreting any result; follow-up and recheck reminders; practice information; and routing or transfer to Customer personnel. The general provisions of this Agreement — including the AI-reliability, human-oversight, automated-agent-disclosure, and correction provisions of Section 6; the channel, consent, TCPA/CAN-SPAM, and opt-out provisions of Section 7; and the third-party-integration provisions of Section 8 — apply to all Customers. Only the clinical, PHI, and EHR-specific provisions — including Section 10, Exhibit A, the clinical provisions of Section 6, the minimum-necessary, result-status, and PHI-marketing provisions of Section 7, and the EHR-as-legal-record and result-confirmation provisions of Section 8 — apply only to healthcare or PHI deployments as indicated in an Order Form or a Business Associate Agreement, and do not apply to non-healthcare Customers.
3.3 Implementation. The parties will cooperate on implementation (workflow mapping, template approval, credentials, integration testing, training, acceptance). Dates dependent on Customer, an EHR vendor, or a Third-Party Service will be adjusted for delays outside 12Times’ reasonable control.
3.4 Changes. 12Times may update the Services to improve security, reliability, compliance, or functionality. During a paid term, 12Times will not materially reduce purchased core functionality except where required by law, to address a security or safety risk, or caused by a Third-Party Service change.
3.5 Subcontractors. 12Times may use subcontractors and subprocessors, contractually restricting their use of Customer Data and, where HIPAA requires, ensuring applicable business-associate obligations.
3.6 Preview Features. Alpha, beta, pilot, or preview features are provided for testing, may change or be discontinued, and are excluded from the SLA unless an Order Form states otherwise.
4. ACCESS RIGHTS AND USE RESTRICTIONS
4.1 Access Right. Subject to the Agreement and payment, 12Times grants Customer a limited, non-exclusive, non-transferable, non-sublicensable right during the Order Term to permit Authorized Users to access and use the Services solely for Customer’s internal business operations.
4.2 Accounts. Customer will designate an administrator, keep account information accurate, assign least-privilege access, protect credentials, and promptly disable access for personnel who no longer need it. Customer is responsible for activity through its accounts unless caused by 12Times’ breach.
4.3 Restrictions. Customer will not, and will not permit others to: (a) reverse engineer or attempt to discover source code or model weights except as law permits; (b) resell, sublicense, or provide the Services to an unaffiliated third party; (c) bypass security or usage controls; (d) introduce malicious code; (e) conduct penetration testing without 12Times’ written approval; (f) use the Services to build or train a competing product; (g) scrape Provider Materials; or (h) use the Services unlawfully or in breach of the Agreement.
4.4 Usage Limits. Usage limits and overage fees are stated in the Order Form. 12Times may reasonably throttle usage that materially threatens security, service integrity, or other customers, with notice where practicable.
5. CUSTOMER RESPONSIBILITIES
5.1 Cooperation. Customer will provide timely access to personnel, approved workflows, credentials, test data, technical information, and Customer Systems reasonably necessary for the Services.
5.2 Accuracy and Authority. Customer is responsible for the accuracy, legality, and completeness of Customer Data, schedules, operational and administrative rules, End-User contact information, templates, and instructions, and represents it has all rights and authority for 12Times to process Customer Data and access Customer Systems as directed.
5.3 Operational Oversight. Customer will appoint qualified personnel to supervise the Services, review escalations, address failed transactions, and maintain appropriate staffing for End-User requests requiring a human response.
5.4 End-User Rights and Preferences. Customer is responsible for documenting and honoring End-User communication preferences, confidential-communication requests, opt-outs, language and accessibility needs, and any legally required notices or authorizations.
5.5 Customer Security. Customer will maintain reasonable safeguards for Customer Systems, endpoints, credentials, and exported data, and will promptly notify 12Times of suspected unauthorized access.
5.6 Prohibited Instructions. For healthcare or PHI deployments, Customer will not instruct the Services to provide a medical diagnosis, interpret clinical results, recommend or alter treatment, prescribe or modify medication, make an emergency determination, or take another clinical action outside the approved scope. More generally, Customer will not instruct the Services to take any action outside the approved scope stated in the Order Form.
6. AI-ASSISTED SERVICES AND CLINICAL LIMITATIONS
6.1 Administrative Tool; No Practice of Medicine. 12Times provides software and administrative communication tools. 12Times is not a healthcare provider, does not practice medicine, and does not provide diagnosis, treatment, medical advice, clinical interpretation, or clinical decision-making.
6.2 Approved Use Cases. Subject to Customer-approved workflows, the Services may assist with: (a) appointment requests, confirmations, cancellations, and rescheduling where supported by the EHR interface (otherwise routed to Clinic staff); (b) notification of a Clinic-approved result status (such as normal, or abnormal—please contact the Clinic), based on a status supplied by the Clinic or its EHR or on Clinic-defined deterministic rules, without independently reading or interpreting the result; (c) follow-up and recall reminders; (d) approved administrative information; and (e) routing or escalation to Customer personnel.
6.3 Human Oversight. AI-generated content may be incomplete, inaccurate, or inappropriate for a particular patient. Customer remains responsible for approving workflows and templates, supervising operation, reviewing escalations, and determining whether any output may be used in patient care or the legal medical record.
6.4 High-Impact Decisions. Customer will not use AI output as the sole basis for diagnosis, triage, treatment, medication, benefit eligibility, emergency response, or another decision materially affecting a patient’s health, rights, or access to care.
6.5 Emergency Communications. The Services are not an emergency service and are not a substitute for 911, emergency medical services, or an on-call clinician. Customer will provide and approve an appropriate emergency notice and escalation workflow.
6.6 Escalation. Customer will define circumstances requiring human intervention, including requests for clinical advice, urgent symptoms, self-harm or harm to others, medication issues, result interpretation, identity-verification failure, EHR conflicts, and express requests for a person.
6.7 AI and Bot Disclosures. Customer is responsible for determining and providing notices, disclosures, or consents required by law for interactions with an automated agent, synthetic voice, recording, transcription, or messaging, except to the extent an Order Form expressly assigns a notice to 12Times.
6.8 Correction. Customer will promptly report materially incorrect or unsafe behavior; 12Times will use commercially reasonable efforts to investigate reproducible defects and adjust Provider-controlled configurations, subject to Customer approval where an approved workflow is affected.
6.9 No Representation Beyond Scope. Neither party will represent, publicly or to an End User, that the Services perform diagnosis, clinical interpretation, or any function beyond the administrative scope documented in the applicable Order Form and Exhibit A.
7. PATIENT COMMUNICATIONS
7.1 Minimum Necessary Content. The parties will configure patient communications to use the minimum information reasonably necessary for the approved administrative purpose. Non-secure or consumer channels should not include substantive test results, diagnoses, medication instructions, detailed clinical history, or other sensitive clinical content.
7.2 Result-Status Notices. 12Times may transmit a result status supplied by the Clinic or its EHR (such as normal, or abnormal), or apply Clinic-defined and Clinic-approved deterministic notification rules together with Clinic-provided recheck timing. 12Times does not independently read, interpret, or determine whether a result is normal, abnormal, urgent, or clinically significant. A result status, and any notice that a result is available, may themselves constitute PHI; an abnormal-status notice sent over a non-secure channel such as WeChat will direct the patient to contact or return to the Clinic and will not disclose the test, values, or clinical detail.
7.3 Communication Channels. The current channel is WeChat. Customer may, through an Order Form, direct 12Times to communicate through additional channels such as Gmail, WhatsApp, or iMessage. These channels are Third-Party Services, are not secure medical-record systems, and may transmit or store data outside the United States. Customer is responsible for approving which content categories may be sent through each channel, for obtaining any patient authorization required for the channel (including cross-border transmission), and for offering a reasonable alternative where required.
7.4 Recipient Accuracy. Customer is responsible for accurate patient contact information and patient-channel associations. 12Times applies configured identity and routing controls but does not warrant that a third-party account or endpoint is controlled by the intended patient.
7.5 Consent and Opt-Out. Customer represents that it has obtained and will maintain all consents, permissions, or other legal bases required for communications initiated through the Services (including messaging, email, recording, and automated communications, and any applicable requirements such as the TCPA or CAN-SPAM), and will promptly communicate opt-outs and restrictions to 12Times.
7.6 No Marketing Without Written Scope. The Services will not be used for marketing, advertising, or promotional communications involving PHI unless expressly included in an Order Form and lawfully authorized.
8. EHR AND THIRD-PARTY INTEGRATIONS
8.1 Authorization. Customer authorizes 12Times to access Customer Systems and process Customer Data solely as reasonably necessary to provide the Services, and represents that the credentials, permissions, and access methods it supplies are authorized.
8.2 System of Record. Customer’s designated EHR remains the authoritative system of record for clinical and scheduling information. 12Times is not responsible for maintaining the legal medical record or independently validating the clinical accuracy of Customer System data.
8.3 Transaction Confirmation. A patient-facing confirmation that an appointment or other EHR transaction is completed will be sent only after the integration receives a success response or Customer-approved confirmation. If confirmation is unavailable, the Services may state that a request was received and is pending review.
8.4 Third-Party Dependencies. Performance may depend on Third-Party Services. 12Times is not responsible for outages, latency, rate limits, API changes, policy changes, data errors, or other failures originating outside systems under 12Times’ reasonable control.
8.5 Reasonable Integration Practices. For Provider-controlled integrations, 12Times will use commercially reasonable efforts to follow available interface specifications, validate responses, prevent unintended duplicate submissions, retry transient failures where appropriate, and surface persistent errors to Customer.
8.6 Third-Party Terms. Customer’s use of a Third-Party Service remains subject to its agreement with that provider. 12Times need not access a Third-Party Service in a manner prohibited by its terms.
8.7 Changes or Discontinuation. If a Third-Party Service materially changes or discontinues an interface, the parties will cooperate on a commercially reasonable alternative; additional work may require a change order. If no reasonable alternative exists, either party may terminate the affected Service without terminating unaffected Services.
9. DATA RIGHTS AND PERMITTED PROCESSING
9.1 Customer Ownership. As between the parties, Customer retains all right, title, and interest in Customer Data. No ownership of Customer Data transfers to 12Times.
9.2 Processing License. Customer grants 12Times and its authorized subprocessors a limited, non-exclusive right to access, host, transmit, transform, and otherwise process Customer Data solely to provide, secure, support, and comply with law regarding the Services.
9.3 Provider Ownership. 12Times retains all right, title, and interest in Provider Materials and all improvements and derivative works. Customer receives only the access rights expressly granted.
9.4 Usage Data. 12Times may collect and use Usage Data to operate, secure, measure, and improve the Services. Usage Data will not include PHI, identifiable Patient Data, or message content, and 12Times will not attempt to re-identify it.
9.5 No Sale or Model Training. 12Times will not sell Customer Data, will not use PHI for advertising, and will not use Customer Data, End-User information, message content, or agent memory to train or improve a generalized or shared AI model for other customers or third parties, unless Customer expressly authorizes it in writing (and, for PHI, the use is permitted by the BAA and applicable law). 12Times may use Usage Data and properly de-identified, aggregated data to operate, secure, measure, and improve the Services.
9.6 Feedback. 12Times may use Customer feedback without restriction, provided it does not disclose Customer Confidential Information or PHI.
9.7 Agent Memory and Configuration. Where an AI agent retains context or memory to perform follow-up or continued service, the underlying End-User information and conversation content are Customer Data owned by Customer under Section 9.1. The prompts, agent configuration and logic, models, workflows, orchestration logic, training, and system schemas that 12Times develops or uses to deliver the Services are Provider Materials under Section 9.3, are not transferred to Customer, and are not Customer Data, whether or not they were tuned or configured for Customer’s deployment.
10. HIPAA AND BUSINESS ASSOCIATE AGREEMENT
10.1 BAA Required for PHI. To the extent 12Times creates, receives, maintains, or transmits PHI on Customer’s behalf and acts as a business associate, the parties will execute or incorporate a HIPAA-compliant BAA.
10.2 BAA Controls. The BAA governs permitted uses and disclosures of PHI, safeguards, breach and Security-Incident reporting, subcontractors, individual-rights support, regulatory access, and return or destruction of PHI. The BAA controls over this MNSA for PHI/HIPAA matters.
10.3 Covered Subprocessors. 12Times will use cloud, AI, and other subprocessors for PHI only where an applicable BAA or other legally sufficient arrangement is in place and the service is configured for the intended HIPAA use. (12Times currently maintains BAAs with AWS and its large-language-model provider, Google.)
10.4 Customer HIPAA Responsibilities. Customer remains responsible for its own HIPAA compliance, including privacy practices, risk analysis, minimum-necessary determinations, patient rights, workforce controls, notices, authorizations, and configuration choices.
10.5 Specially Protected Data. Customer will not submit substance-use-disorder records subject to 42 C.F.R. Part 2, psychotherapy notes, genetic data, or other specially regulated data unless an Order Form or written addendum expressly authorizes and governs that processing.
10.6 No HIPAA Certification. The parties acknowledge that HIPAA provides no single government “certification” of a business associate; 12Times’ obligations are those stated in the Agreement and applicable law.
11. DATA RETENTION AND SYSTEM OF RECORD
11.1 Data-Handling Model. The data-handling model for each deployment is specified in the applicable Order Form. (a) Retained model (default): Provider retains Customer Data as reasonably necessary to provide, support, secure, and improve and configure the Services for Customer’s own deployment — including the context or memory an AI agent needs to perform follow-up and continued service — Customer owns such data under Section 9, and Customer may export it under Section 11.6. (b) Hybrid model: where an Order Form so specifies, some functions or modules operate on a retained basis (such as a sales, conversion, or relationship-management agent that requires memory for follow-up) while others operate on a zero-storage basis (such as an intake or front-desk function handling regulated data); the Order Form identifies which functions fall into each category. (c) Zero-Storage model: where an Order Form so specifies, typically for PHI or other regulated data, raw message content and the information extracted from it are transmitted to the Customer’s designated system of record and then purged from Provider’s data store, and are not intentionally retained in Provider’s primary application database after completion of the applicable transaction, except for the limited categories described in Section 11.2. For each profile, the Order Form will identify the applicable functions or modules, the data categories that may be retained, the data categories that must not be retained, the retention period, and the system of record. Where an Order Form does not specify a model, the Retained model applies only to non-PHI Customer Data; no data-handling model applies to PHI by default. Any Retained or Hybrid processing of PHI must be expressly authorized in both the applicable Order Form and the applicable BAA, and the BAA controls with respect to PHI; a BAA may permit limited retention of PHI where it expressly so provides, and zero-storage is required for PHI only where the applicable Order Form or BAA so specifies.
11.2 Permitted Limited Retention. Limited data may be retained where reasonably necessary for: (a) transient processing, caching, or queues; (b) failed-transaction retry and reconciliation; (c) security, access, and audit logs; (d) delivery status, timestamps, identifiers, and error codes; (e) Customer-requested records; (f) legal holds or obligations; or (g) protected backups or subprocessor systems that do not permit immediate selective deletion.
11.3 Log Minimization. 12Times will use commercially reasonable controls designed to prevent raw message bodies and unnecessary direct End-User identifiers from being written to ordinary application logs. Metadata retained for security may itself constitute Customer Data (and, in healthcare deployments, PHI) and will be protected accordingly.
11.4 No Archival Obligation. Unless an Order Form states otherwise, 12Times is not Customer’s archive, backup provider, or system-of-record custodian (including, for healthcare deployments, the medical-record custodian). Customer is responsible for ensuring information required for its records — and, for healthcare deployments, the legal medical record — is recorded and retained in Customer’s designated system of record (such as the EHR).
11.5 Return and Deletion. Upon expiration or termination, 12Times will return or destroy Customer Data as required by the applicable Order Form, any applicable BAA, applicable retention policy, and applicable law; for PHI, the BAA controls. Where immediate return or destruction is infeasible, 12Times will continue to protect retained data and limit further use to the purpose making it infeasible.
11.6 Export. Where the applicable data-handling model results in 12Times retaining Customer Data, Customer may request a commercially reasonable export of that retained Customer Data during the term or within thirty (30) days after termination, subject to technical feasibility, payment of undisputed fees, and applicable professional-services charges. Provider Materials — including prompts, agent configuration and logic, models, workflows, orchestration logic, and system schemas — are not Customer Data and are not subject to export.
12. INFORMATION SECURITY
12.1 Security Program. 12Times will use commercially reasonable efforts to maintain administrative, technical, and organizational safeguards designed to protect the confidentiality, integrity, and availability of Customer Data in systems under its control.
12.2 Baseline Controls. Subject to the nature of the Service, safeguards are intended to include access controls, least-privilege practices, workforce confidentiality obligations, encryption in transit and at rest in Provider-controlled environments, audit logging, vulnerability management, incident response, change management, and secure-deletion practices.
12.3 Shared Responsibility. Customer is responsible for Customer Systems, endpoints, End-User channel choices, credentials, account permissions, network security, exported data, and Customer-controlled configurations. Third-Party Services remain subject to their own controls.
12.4 Security Documentation. Upon reasonable request and subject to confidentiality, 12Times will provide available security documentation reasonably necessary for Customer’s vendor review. 12Times need not disclose source code, sensitive penetration-test details, other customers’ information, or subprocessor-restricted information.
12.5 No Absolute Security. No network or service is completely secure. 12Times does not warrant that unauthorized access or Security Incidents will never occur, but this does not reduce obligations expressly imposed by the BAA or applicable law.
13. SECURITY INCIDENTS
13.1 Notice. 12Times will notify Customer of a Security Incident affecting Customer Data without undue delay and within any shorter period required by the BAA or applicable law.
13.2 Information and Cooperation. To the extent reasonably available, notice will describe the incident’s nature, affected systems or data, mitigation taken, and recommended Customer actions; 12Times will provide reasonable cooperation for Customer’s legally required investigation and notifications.
13.3 Unsuccessful Events. Routine unsuccessful events (blocked scans, pings, failed logins, attacks not compromising Customer Data) do not require individual notice unless required by the BAA or law.
13.4 Communications. Neither party will issue a public statement identifying the other regarding a Security Incident without prior consultation, except where required by law. Allocation of notification costs is governed by the BAA or, if silent, by the parties’ relative fault.
14. CONFIDENTIALITY
14.1 Confidential Information. “Confidential Information” means non-public business, technical, financial, security, product, End-User, and commercial information disclosed by a party that is marked or reasonably understood as confidential. Customer Data and Provider Materials are the Confidential Information of their respective owners.
14.2 Use and Protection. The receiving party will use Confidential Information only to perform or exercise rights under the Agreement, protect it with at least reasonable care, and limit disclosure to personnel, advisers, and subcontractors with a need to know and confidentiality obligations.
14.3 Exclusions. Confidential Information excludes information that is publicly available without breach, lawfully known without restriction, lawfully received from a third party without duty, or independently developed without use of Confidential Information.
14.4 Compelled Disclosure. A party may disclose where legally required, giving notice where permitted and reasonable cooperation, at the disclosing party’s expense, to seek protection.
14.5 Equitable Relief. Unauthorized use or disclosure may cause irreparable harm; the injured party may seek injunctive relief in addition to other remedies.
15. PROFESSIONAL SERVICES
15.1 Scope. Implementation, integration, configuration, training, data mapping, and other professional services are described in an Order Form or statement of work; out-of-scope work requires a written change order.
15.2 Dependencies. Customer will make knowledgeable personnel available, provide timely decisions, and obtain EHR/vendor cooperation. 12Times is not responsible for delay caused by unmet dependencies.
15.3 Deliverables. Customer owns materials it supplies; 12Times owns Provider Materials and reusable tools, templates, code, workflows, and know-how. Subject to payment, Customer may use Customer-specific deliverables with the Services for internal operations.
15.4 Acceptance. Unless an Order Form provides otherwise, a deliverable is accepted on the earliest of productive use, written acceptance, or five (5) business days after delivery without written notice of a material nonconformity.
16. FEES, TAXES, AND PAYMENT
16.1 Fees. Customer will pay the fees in each Order Form, in U.S. dollars, non-cancelable and non-refundable except as expressly stated.
16.2 Invoices. Unless an Order Form states otherwise, invoices are due within fifteen (15) days of the invoice date. Customer must dispute an invoice in good faith within ten (10) days and timely pay undisputed amounts.
16.3 Late Amounts. Overdue undisputed amounts may accrue interest at the lesser of 1.5% per month or the maximum lawful rate, plus reasonable collection costs.
16.4 Taxes and Third-Party Charges. Fees exclude taxes, telecommunications and messaging fees, EHR fees, and other third-party charges; Customer is responsible for these other than taxes on 12Times’ net income.
16.5 Overages. Usage above Order Form limits may be billed at the stated or then-current overage rate, with commercially reasonable prior notice where monitoring permits.
16.6 Renewal Pricing. 12Times may change renewal pricing on at least thirty (30) days’ prior notice unless the Order Form states otherwise.
17. TERM, RENEWAL, AND TERMINATION
17.1 MNSA Term. This MNSA begins on the first Order Form’s effective date and remains in effect while any Order Form is active.
17.2 Order Term and Renewal. Each Order Form states its initial term. Unless otherwise stated, it automatically renews for successive periods equal to the shorter of its initial term or twelve months, unless either party gives at least thirty (30) days’ written notice of non-renewal.
17.3 Termination for Cause. Either party may terminate the affected Order Form or the Agreement for a material breach not cured within thirty (30) days after notice. Termination may be immediate if the breach is incurable, creates an imminent security or patient-safety risk, or involves unlawful use.
17.4 Insolvency. Either party may terminate if the other becomes insolvent, makes a general assignment for creditors, or is subject to a bankruptcy proceeding not dismissed within sixty days.
17.5 Termination for Convenience. A party may terminate for convenience only as permitted by the applicable Order Form. Terminating this MNSA does not by itself terminate an Order Form with a committed term.
17.6 Effect. Upon termination, Customer will stop using the terminated Services and pay accrued fees; 12Times will handle Customer Data under Section 11 and the BAA. Provisions that by nature survive (payment, ownership, confidentiality, disclaimers, indemnity, liability limits, dispute terms) survive.
18. SUSPENSION
18.1 Grounds. 12Times may suspend affected Services if reasonably necessary to address a security, privacy, clinical-safety, or legal risk; respond to material misuse; comply with law or a Third-Party Service requirement; protect service integrity; or address undisputed fees more than fifteen (15) days overdue.
18.2 Process. 12Times will provide notice and an opportunity to cure where practicable, and will limit suspension in scope and duration to what is reasonably necessary. Customer remains responsible for fees during a suspension it caused.
19. WARRANTIES
19.1 Mutual Authority. Each party represents it has authority to enter into the Agreement and will comply with laws applicable to its performance.
19.2 Service Warranty. 12Times warrants that the hosted Services will materially conform to any Documentation 12Times provides, and that professional services will be performed in a professional and workmanlike manner.
19.3 Exclusive Warranty Remedy. Customer must notify 12Times of a warranty claim within thirty (30) days of discovery. 12Times will use commercially reasonable efforts to correct or reperform; if it cannot within a reasonable period, Customer may terminate the affected Service and receive a prorated refund of prepaid unused fees. SLA failures are governed exclusively by the SLA.
19.4 Customer Warranties. Customer represents that Customer Data, instructions, workflows, consents, and use comply with law and do not infringe third-party rights.
20. DISCLAIMERS
20.1 General. Except for the express warranties in the Agreement, the Services, AI Features, outputs, Third-Party Services, and Provider Materials are provided “AS IS” and “AS AVAILABLE.” To the fullest extent permitted by law, 12Times disclaims implied warranties of merchantability, fitness for a particular purpose, title, non-infringement, and those arising from course of dealing or usage.
20.2 AI Output. 12Times does not warrant that AI output will always be accurate, complete, lawful, or suitable for a particular End User; it is not a substitute for Customer’s professional judgment and human oversight.
20.3 Clinical Disclaimer. For healthcare or PHI deployments, 12Times does not warrant any clinical outcome and is not responsible for diagnosis, treatment, medical judgment, patient triage, or the adequacy or timeliness of Customer’s human response.
20.4 Third-Party Services. 12Times does not warrant the availability, security, accuracy, or continued functionality of Third-Party Services, including EHRs, consumer messaging platforms (such as WeChat), email providers, cloud providers, or third-party APIs.
20.5 No Legal/Regulatory Advice. Documentation and configuration assistance are not legal, medical, or compliance advice; Customer determines whether its use complies with law and professional obligations.
20.6 Data Preservation. Unless an Order Form states otherwise, 12Times does not warrant that the Services will preserve a complete conversation history or substitute for Customer’s backup, EHR, or legal-record-retention systems.
21. INDEMNIFICATION
21.1 12Times IP Indemnity. 12Times will defend Customer against a third-party claim that authorized use of the Services infringes a U.S. patent, copyright, or trademark, and pay damages finally awarded or agreed, provided Customer promptly notifies 12Times, gives control of the defense, and reasonably cooperates.
21.2 IP Remedies and Exclusions. 12Times may modify or replace the affected Service, obtain continued rights, or terminate it and refund prepaid unused fees. 12Times has no obligation for claims arising from Customer Data, Customer instructions, unauthorized modifications, non-12Times combinations, continued use after notice, or Third-Party Services.
21.3 Customer Indemnity. Customer will defend and indemnify 12Times and its Affiliates from third-party claims arising from: (a) Customer Data or Customer-provided content; (b) Customer’s clinical decisions, medical services, or failure to respond to an escalation; (c) communications made without required consent or in violation of law; (d) use outside the approved scope; (e) Customer Systems or credentials; or (f) Customer’s breach of Sections 5–8.
21.4 Procedure. The indemnified party will give prompt notice, reasonable cooperation, and control of defense; no settlement may admit fault by or impose non-monetary obligations on the indemnified party without consent, not unreasonably withheld.
22. LIMITATION OF LIABILITY
22.1 Excluded Damages. To the fullest extent permitted by law, neither party is liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or lost profits, revenue, goodwill, or business interruption, even if advised of the possibility. This does not limit Customer’s payment or indemnification obligations.
22.2 General Cap. Except as in Section 22.3, each party’s aggregate liability arising out of or relating to the Agreement will not exceed the fees paid or payable by Customer for the affected Services in the twelve (12) months preceding the event giving rise to the first claim.
22.3 Enhanced Cap. 12Times’ aggregate liability for its breach of confidentiality; a Security Incident or breach of the BAA caused by 12Times’ failure to comply with its express obligations; its gross negligence; or a HIPAA/PHI breach caused by 12Times — will not exceed two (2) times the amount in Section 22.2.
22.4 Uncapped Matters. Sections 22.1–22.3 do not apply to fraud, willful misconduct, liabilities that cannot lawfully be limited, or a party’s infringement or misappropriation of the other’s intellectual property.
22.5 SLA Credits. Service Credits under the SLA are Customer’s sole and exclusive remedy for failing to meet the monthly availability commitment; they do not limit remedies for an independent breach of the BAA, confidentiality, or security obligations.
22.6 Allocation of Risk. The parties acknowledge fees reflect this allocation of risk and that these limitations apply even if a limited remedy fails of its essential purpose.
23. COMPLIANCE WITH LAWS
23.1 General. Each party will comply with laws applicable to its performance. Customer is responsible for laws applicable to its own business, communications, recording, licensure and professional or regulatory obligations, clinical or other services, and use of Customer Data.
23.2 Prohibited Uses. Customer will not use the Services for unlawful discrimination, deceptive impersonation, harassment, unauthorized surveillance, emergency dispatch, or another prohibited or high-risk purpose.
23.3 Trade Controls. Each party will comply with applicable anti-bribery, sanctions, and export-control laws; Customer will not permit access by a prohibited person or from a comprehensively sanctioned jurisdiction.
23.4 Not a Medical Device. The Services are not represented as a medical device and are not intended to perform a function requiring FDA clearance or authorization unless an Order Form expressly states otherwise.
24. AUDIT AND ASSURANCE
24.1 Assurance Information. On reasonable written request no more than once annually, 12Times will provide available information reasonably necessary for Customer to assess compliance with express security and privacy obligations, subject to confidentiality and security restrictions.
24.2 Audit Process. Customer will first rely on available questionnaires, policies, summaries, certifications, or independent reports. Any additional audit must be mutually scoped, conducted during Business Hours without unreasonable disruption, protect other customers and Provider Materials, and be at Customer’s expense unless it identifies a material breach by 12Times.
24.3 BAA Rights Preserved. Nothing here limits audit or access rights that cannot be restricted under the BAA or applicable law.
25. PUBLICITY
25.1 Consent Required. Neither party may use the other’s name, logo, patient information, or marks in public marketing without prior written consent. A party may identify the other in confidential investor, insurer, auditor, or legal diligence subject to confidentiality.
26. CHANGES TO THESE TERMS
26.1 Updates. 12Times may update the MNSA or SLA for new features, law, security, or operational needs, and will make the updated version available to Customer with a revised effective date and maintain a reasonable archive of prior versions.
26.2 Committed Terms. A material change that adversely affects Customer’s rights or materially increases its obligations will not apply to an active committed Order Term until renewal, unless required by law, necessary for a security or patient-safety risk, or accepted by Customer.
26.3 Acceptance. Continued use after a change becomes applicable constitutes acceptance to the extent permitted by law; a signed amendment or Order Form controls over a general update.
27. NOTICES
27.1 Method. Legal notices must be in writing and delivered by personal delivery, recognized overnight courier, certified mail, or email with confirmation. Notices to Customer go to the address or legal contact in the Order Form.
27.2 Notices to 12Times. 12Times Inc., 13 West Main Street, Felton, Delaware 19943; email: sales@12times.com. Operational and support communications may use the support channel in the Order Form or SLA.
27.3 Effectiveness. A notice is effective on receipt, except an email sent after 5:00 p.m. recipient local time is effective the next business day.
28. GOVERNING LAW AND DISPUTES
28.1 Governing Law. The Agreement is governed by the laws of the State of New York, without regard to conflict-of-law rules. The U.N. Convention on Contracts for the International Sale of Goods does not apply.
28.2 Informal Resolution. Before filing a claim, an executive of each party will attempt in good faith for thirty (30) days to resolve the dispute, except for payment collection, injunctive relief, or matters requiring immediate action.
28.3 Forum. The state and federal courts located in Queens County, New York (and the U.S. District Court for the Eastern District of New York) have exclusive jurisdiction, and each party consents to personal jurisdiction and venue there.
28.4 Jury Waiver. To the extent permitted by law, each party waives trial by jury for any dispute arising from the Agreement.
28.5 Injunctive Relief. Either party may seek equitable relief to protect Confidential Information, Customer Data, security, or intellectual property without first completing informal resolution.
29. GENERAL PROVISIONS
29.1 Assignment. Neither party may assign the Agreement without consent, except to an Affiliate or in a merger, reorganization, or sale of substantially all relevant assets with the assignee assuming obligations. Customer’s assignment to a direct competitor of 12Times requires consent.
29.2 Force Majeure. Neither party is liable for delay or failure caused by events beyond its reasonable control (natural disaster, war, terrorism, labor disruption, utility or internet failure, government action, epidemic, or widespread Third-Party Service failure), except Customer’s payment obligations for Services already provided.
29.3 Relationship. The parties are independent contractors; the Agreement creates no partnership, fiduciary, employment, clinical, or agency relationship, except limited authorization to access Customer Systems as directed.
29.4 No Third-Party Beneficiaries. No patient or other third party is a beneficiary of the Agreement.
29.5 Waiver and Severability. A waiver must be in writing and applies only to the stated instance. If a provision is unenforceable, it will be modified to the minimum extent necessary and the remainder remains effective.
29.6 Entire Agreement. The Agreement supersedes prior or contemporaneous proposals and agreements on its subject matter; reliance is limited to representations expressly stated in the Agreement.
29.7 Counterparts; E-Signature. Order Forms and amendments may be executed electronically and in counterparts, each an original.
29.8 Interpretation. Headings are for convenience; “including” means “including without limitation”; singular includes plural; no provision is construed against the drafter.
Electronic acceptance: this MNSA is intended to be incorporated by reference into an Order Form. Signature of the Order Form constitutes acceptance of this MNSA as of the applicable Order Effective Date.
EXHIBIT A — Baseline Functional Scope and Clinical Guardrails
This Exhibit describes the baseline intended use of the healthcare administrative Services. An Order Form may narrow or expand scope, but no expansion into clinical decision-making is effective unless expressly documented and legally reviewed.
| Function | Baseline Permitted Scope | Required Guardrail |
|---|---|---|
| Appointment scheduling / rescheduling | Receive requests, query approved availability, submit or route a request, confirm only after a success response. | Customer controls scheduling rules; EHR is source of truth; rescheduling only where supported by the EHR interface, otherwise (and any unresolved conflict) routed to staff. |
| Result-status notice | Transmit a Clinic/EHR-supplied result status (e.g., normal, or abnormal—please contact the Clinic), or apply Clinic-defined deterministic rules; direct the patient to the Clinic or a secure method. | 12Times does not read, interpret, or judge the result; an abnormal notice on a non-secure channel (e.g., WeChat) says only to contact the Clinic and discloses no test, values, or clinical detail. |
| Follow-up / recall reminders | Send Customer-approved reminders that follow-up is due or recommended. | Customer sets timing and clinical rule; the Agent does not independently decide the interval. |
| Administrative FAQs | Provide approved hours, location, forms, preparation logistics, and contact methods. | No individualized medical advice or clinical interpretation. |
| Human routing / escalation | Transfer, create a task, or instruct the patient how to reach Customer personnel. | Urgent symptoms, medication, result interpretation, identity failure, or a request for a person must escalate. |
| Emergency content | Display an approved emergency notice directing the person to 911 or Customer’s approved pathway. | The Services do not assess emergencies, dispatch care, or replace emergency services. |
A.1 Prohibited Clinical Uses
- Diagnosing a disease/condition, interpreting symptoms, or determining clinical urgency.
- Communicating or interpreting substantive lab, imaging, or pathology results on a non-secure channel.
- Recommending, prescribing, discontinuing, or changing medication or treatment.
- Making individualized clinical, triage, or medical-necessity decisions.
- Replacing a licensed clinician, emergency service, or Customer’s legal medical-record obligations.
A.2 Customer Approval Items
- Patient identity and channel-verification rules.
- Message templates and content categories permitted for each channel.
- Escalation triggers, staffing contacts, operating hours, and expected human response.
- EHR fields, scheduling rules, retry behavior, and wording used when confirmation is pending.
- Emergency, privacy, automated-agent, recording, and opt-out notices.
EXHIBIT B — Baseline Security and Data-Handling Commitments
B.1 Subprocessor Boundary. PHI is processed only through Provider-approved services for which 12Times maintains an applicable BAA or other legally sufficient arrangement and which are configured for the intended HIPAA use.
B.2 Data Minimization. Workflows are designed to process the minimum Customer Data reasonably necessary for the approved function.
B.3 Transmission and Storage. 12Times will use encryption in transit and at rest for PHI in Provider-controlled systems, subject to the capabilities of a Customer-selected Third-Party Service.
B.4 Data Handling by Profile. Where the Order Form specifies a Zero-Storage profile, or a Hybrid profile for a zero-storage function, raw End-User message content is not intentionally persisted in 12Times’ primary application database after completion of the applicable transaction, subject to the limited-retention categories in Section 11. Where the Order Form specifies a Retained profile (or a retained function under a Hybrid profile), Customer Data is retained and handled under Sections 9 and 11.
B.5 Model Use. Customer PHI will not be used to train or improve a generalized model for other customers or third parties without Customer’s express written authorization and a legally permitted basis.
B.6 Access. Access to systems processing PHI is restricted to authorized personnel and subprocessors with a need to know and appropriate confidentiality or BAA obligations.
B.7 Audit and Security Logs. 12Times may retain security and operational metadata to detect abuse, investigate incidents, reconcile transactions, and satisfy audit obligations; logs are minimized and protected as applicable.
B.8 Incident Response. 12Times will maintain an incident-response process and provide notice in accordance with the BAA and Section 13.
B.9 Customer Responsibilities. Customer remains responsible for Customer Systems, End-User contact information, channel approvals, credentials, workforce access, device security, and, in healthcare deployments, recording information required in the legal medical record.
B.10 Technical Confirmation. Before production launch, the parties should confirm in writing the applicable cloud accounts, covered services, subprocessors, message channels, EHR interface, data fields, retention settings, and support contacts.