Terms changes

**Draft**Expanded working draft for legal review |\| Version 0.10.2 |\| 28 September 2026** > **Important:****DRAFT — NOT APPROVED FOR PUBLICATION.** This document is a detailed working draft,draft prepared from the AMS institutional-portal context, the supplied strategic planning and financial-structuring materials, the supplied product/pricing workbook structure, and a supplied reference agreement as a breadth-and-organization reference. It is not a reproduction of the reference agreement and is not legal adviceadvice. It deliberately leaves unresolved legal, commercial, technical and jurisdictional facts as bracketed fields or andecision approvedpoints. agreement. Before activation,Qualified counsel must review it, complete all fields, confirm the contracting legal entity, supported countries, governing law, privacy/data map, fees, cancellation/refund terms, required local noticesentity and contacts.launch Replace every bracketed fieldmarkets, and linkapprove theall consumer, privacy, export-control, subscription, liability and dispute provisions before clickwrap activation. **Document owner:** \[AMS LEGAL / GOVERNANCE OWNER\] **Contracting entity:** \[FULL LEGAL NAME, ENTITY TYPE, JURISDICTION\] **Registered address:** \[ADDRESS\] **Effective date:** \[DATE\] **Version:** 0.2 **Related documents:** Privacy Notice,Notice; CookieCookie/Tracking Notice,Notice; Data Processing Addendum (DPA),(DPA); acceptable-useAcceptable policyUse and service-specificSecurity schedules.Policy; DoService/Subscription notOrder; publishAI orFeature enableNotice; clickwrapCommunity/Collaboration acceptanceRules; untilRecords reviewed.Retention Schedule; Export-Control and Restricted-Access Rules; applicable project, research, manufacturing, quality, commercial and partner agreements. ---

“Confidential22.1 Information”**Protection meansobligation.** non-publicEach informationparty markedreceiving confidentialthe orother reasonablyparty’s understoodConfidential toInformation be(“Receiving confidential,Party”) includingwill technical designs, process parameters, unpublished research, customer/supplier information, security information, personal data and restricted institutional records. Useuse it only for the authorizedpurpose purpose,for which it was disclosed and will protect it withusing at least reasonable care,care limitand accessno less than the care it uses for its own comparable confidential information. 22.2 **Permitted recipients.** The Receiving Party may disclose Confidential Information to thoseits employees, professional advisors, contractors and approved service providers who need to know it for the permitted purpose and are bound by appropriateconfidentiality duties,obligations at least as protective as these Terms, subject to applicable law and doany stricter agreement. 22.3 **Exclusions.** Confidential Information does not disclose it externally without written authorization. Exceptions apply toinclude information the Receiving Party can demonstrate: (a) is or becomes public through no breach; (b) was lawfully known without restriction,restriction publicbefore withoutreceipt; breach,(c) is independently developed without use of the disclosing party’s Confidential Information; or (d) is lawfully received from a third parties.party without a duty of confidentiality. 22.4 **Compelled disclosure.** If disclosure is legallyrequired compelled,by givelaw, noticecourt order or competent authority, the Receiving Party will, where lawfullegally permitted and practicable, give prompt notice, disclose only what is legally required and reasonably cooperate in seeking protection.confidential treatment or protective measures. 22.5 **Return and destruction.** Upon request or termination, the Receiving Party will return or destroy Confidential Information within its control, subject to legal holds, records retention, backup cycles, security logs and any continuing rights or obligations. The Receiving Party may retain archival copies required by law or legitimate compliance obligations, which remain protected. 22.6 **Duration.** Confidentiality continuesobligations continue during the relationship and for [five\[five (5)](5)\] years after access ends;ends, except that trade secrets andsecrets, personal data remainand information that remains confidential by its nature will be protected for as long as required by law or theirwhile nature.it remains protected information. A stricter NDA or project agreement controls.controls where applicable.

**Expanded working draft for legal review \|| Version 0.20.3 \|| 28 September 2026** > **DRAFT — NOT APPROVED FOR PUBLICATION.** This document is a detailed working draft prepared from the AMS institutional-portal context, the supplied strateg ... ting entity and launch markets, and approve all consumer, privacy, export-control, subscription, liability and dispute provisions before clickwrap activation. **Document owner:** \[AMS[AMS LEGAL / GOVERNANCE OWNER\] OWNER] **Contracting entity:** \[FULLAVYRA LEGALMICROSYSTEMS NAME,PRIVATE ENTITYLIMITED, TYPE,a JURISDICTION\] company limited by shares incorporated under the Companies Act, 2013 (India). **Registered address:**office \[ADDRESS\] state:** Karnataka, India. **Address shown in the Certificate of Incorporation as mailing address per ROC records:** [street address withheld until the owner approves its publication] **Effective date:** \[DATE\] [TO BE COMPLETED AFTER LEGAL APPROVAL] **Version:** 0.2 0.3 **Related documents:** Privacy Notice; Cookie/Tracking Notice; Data Processing Addendum (DPA); Acceptable Use and Security Policy; Service/Subscription Order; AI Feature Notice; Community/Collaboration Rules; Records Retention Schedule; Export-Control and Restricted-Access Rules; applicable project, research, manufacturing, quality, commercial and partner agreements. ---

1.1 **Agreement.** These Subscriber Terms and Conditions (“Terms”) form a legally binding agreement between the subscriber identified in the account or applicable order (“Subscriber,” “you,” or “your”) and \[FULLAVYRA LEGALMICROSYSTEMS NAMEPRIVATE OF AMS CONTRACTING ENTITY\]LIMITED (“AMS,” “we,” “us,” or “our”). These Terms govern access to and use of the AMS Institutional Core and any enabled portal, workspace, institutional information service, collaborati ... s unenforceable for a particular Subscriber or jurisdiction, it will be applied only to the maximum lawful extent and the remaining provisions will continue, subject to Section 34.

3.1 **Institutional purpose.** The Institutional Core is intended to support institutional knowledge, technology, research, engineering, manufacturing, quality, project execution, ... sample, demonstration, catalog entry or planning model is not a promise of commercial availability, certification, production capacity, performance, delivery date or outcome. 3.4 **Separate**Yantra Semitech — sales arm and commercial core.** Yantra Semitech is designated by the separateCompany commercial/customer-facingas interfaceits associatedsales arm and customer-facing commercial core for the Company’s authorized and licensed business activities, subject at all times to the actual scope of each applicable licence, registration, approval, corporate authorization and delegation. Yantra is intended to connect qualified institutional capability with customers, projects, suppliers, OEMs, channels and markets; support customer discovery, market development, technical-commercial coordination, offers, proposals, quotations, order intake, fulfilment coordination and lifecycle relationships; and maintain the broaderrelevant ecosystem.commercial Productworkflow and records. The legal contracting party for a particular sale, supply, service or other transaction must be identified on the applicable quotation, order, invoice and transaction agreement. Nothing in this clause itself grants Yantra or any individual a licence, regulatory permission, agency, authority to bind the Company, or authority to conduct a regulated activity. The Certificate of Incorporation confirms incorporation but expressly is not a business licence or sectoral permission. Commercial listings, supplier/distributor relationships, customer opportunities, sales negotiations, pricing, quotations, purchase orders, invoicing, payment, logistics, fulfillment,fulfilment, warranties and commercial customer records are not authorized by these Terms unless a separate agreement expressly incorporates them. Those activities are governed by the applicable Yantra commercial terms and transaction documents.documents, and by the relevant legal entity’s approved authority matrix. Access to AMS institutional content does not itself authorize a Subscriber to buy, sell, resell, represent, distribute, sourcesource, quote or commit to any product or service. 3.5 **Separate institutional functions.** Education, credentialing, investment, enterprise engagement, information, communications, entertain ... manufacturing yield, commercial sales, financing, investment returns, regulatory approval, customer acceptance, employment, certification or any other business or technical result.

4.1 **Legal capacity and minimum age.** You must have legal capacity to accept these Terms. The minimum age for account creation and use is \[MINIMUM[MINIMUM AGE, SUBJECT TO LOCAL LAW\].LAW]. Where a permitted education, training or institutional program allows minors, access requires the legally required parent, guardian, school or institutional authorization and must ... cess.** Meeting eligibility criteria does not guarantee acceptance, continued access, access to a particular workspace, inclusion in a project or availability of a Service Feature.

5.1 **Account integrity.** Each account must identify the individual who uses it, except for expressly approved technical or service accounts governed by separate controls. You mus ... rs, recovery codes, devices and session access. Do not share passwords, one-time codes, security keys or recovery secrets. Do not permit another person to use your Account. Notify \[SECURITY[SECURITY CONTACT\]CONTACT] promptly if you suspect unauthorized access, lost credentials, compromised devices or an account takeover. 5.4 **Authentication controls.** Depending on role, risk and Service Fe ... ty ends. Administrators may manage membership and access only within delegated scope and must not use administrative access to inspect private content unless authorized and lawful.

7.1 **Availability.** The Services may require compatible devices, supported browsers, network access, software, identity services and third-party infrastructure. Performance may d ... city management. Services may be temporarily unavailable, delayed, degraded or limited. Where practicable, AMS will provide advance notice of material planned interruption through \[STATUS[STATUS PAGE / ACCOUNT NOTICE\],NOTICE], but emergency or security work may occur without prior notice. 7.3 **No universal uptime commitment.** No uptime, response time, recovery time, recovery point, support window or ... impact purposes unless an approved written schedule expressly permits that use. Beta access does not imply certification, service-level coverage or a commitment to general release.

15.1 **Privacy Notice.** AMS’s collection and processing of Personal Data is described in the Privacy Notice at \[PRIVACY[PRIVACY NOTICE URL\].URL]. The notice must identify the relevant controller or responsible entity, purposes, categories, legal bases where required, recipients, international transfers, retention, rights, c ... r geographic region unless a written commitment expressly provides it. 15.7 **Requests and rights.** Where applicable law grants privacy rights, requests may be submitted through \[PRIVACY[PRIVACY REQUEST URL/EMAIL\].URL/EMAIL]. AMS may need to verify identity and authority, clarify the request, apply lawful exceptions and coordinate with the relevant Organization or controller. Nothing in these Terms removes a statutory right. 15.8 **Security incident reporting.** Report suspected unauthorized access, loss, disclosure, alteration or compromise through \[SECURITY[SECURITY CONTACT / INCIDENT PORTAL\].PORTAL]. Do not investigate beyond your authorization, delete evidence, notify external parties on behalf of AMS or make public statements about an incident unless authorized or required b ... -protection obligations are separate. Information may be confidential without being Personal Data, and Personal Data may be subject to statutory rights even if marked confidential.

16.1 **Security controls.** AMS may use access controls, authentication, encryption, monitoring, rate limits, backups, malware scanning, vulnerability management, logging and other ... sting, load testing, scanning, social engineering or security research against the Services without prior written authorization and an agreed scope. Report vulnerabilities through \[SECURITY[SECURITY DISCLOSURE CHANNEL\].CHANNEL]. AMS may acknowledge, investigate and remediate reports under its security process. 16.5 **Incident response.** AMS may isolate accounts, revoke sessions, disable integrations, su ... , avoid unauthorized exports and follow applicable security instructions. You must promptly report a suspected compromise and cooperate reasonably with containment and remediation.

18.1 **Fee disclosure.** Fees, subscription tier, feature scope, user limits, usage allowances, billing period, renewal terms, payment method, taxes and any setup or overage charge ... contracting entity, amount, currency, taxes, payment deadline and dispute contact. You must pay undisputed amounts by the due date. If you dispute an invoice in good faith, notify \[BILLING[BILLING CONTACT\]CONTACT] with reasonable detail within \[DISPUTE[DISPUTE WINDOW\],WINDOW], and pay undisputed amounts while the parties resolve the dispute, to the extent permitted by law. 18.5 **Taxes.** Fees are exclusive of applicable taxes unless stated otherwise. ... culators, financial projections and commercial materials do not constitute investment advice, lending commitments, valuation opinions or guarantees of future financial performance.

19.1 **Subscriber cancellation.** You may cancel a Subscription using \[CANCELLATION[CANCELLATION METHOD\]METHOD] or by contacting \[SUPPORT/BILLING[SUPPORT/BILLING CONTACT\],CONTACT], subject to the order and mandatory law. The cancellation confirmation should identify the effective date and whether access continues through the paid term. 19.2 **Effect of canc ... ip, project records, security logs, unresolved disputes or required retention. The process and expected effects must be described in the Privacy Notice or account-closure workflow.

20.1 **Operational communications.** AMS may send service notices, security alerts, account messages, administrative updates, billing notices and other communications necessary to ... void collecting government-ID numbers or device fingerprints unless necessary, lawful, disclosed and proportionate. 20.5 **Notice delivery.** Legal notices to AMS must be sent to \[LEGAL[LEGAL NOTICE ADDRESS / EMAIL\]EMAIL] with the subject “Legal Notice under Subscriber Terms.” AMS may send notices to the registered email, account inbox or other legally permitted channel. Notices are deemed received according to applicable law and the relevant agreement; no deemed-receipt rule overrides mandatory requirements.

22.1 **Protection obligation.** Each party receiving the other party’s Confidential Information (“Receiving Party”) will use it only for the purpose for which it was disclosed and ... hival copies required by law or legitimate compliance obligations, which remain protected. 22.6 **Duration.** Confidentiality obligations continue during the relationship and for \[five[five (5)\](5)] years after access ends, except that trade secrets, personal data and information that remains confidential by its nature will be protected for as long as required by law or while it remains protected information. A stricter NDA or project agreement controls where applicable.

24.1 **Grounds.** AMS may suspend, restrict or terminate all or part of your access where reasonably necessary to: (a) address a material breach; (b) prevent or respond to a securi ... s, evidence may be destroyed, or notice would compromise security or an investigation. 24.3 **Review and appeal.** Where supported and appropriate, you may request review through \[ACCESS[ACCESS REVIEW / APPEAL CHANNEL\].CHANNEL]. A review does not automatically restore access and may be limited by law, confidentiality, security or third-party rights. 24.4 **Organization-managed access.** An Organization A ... nformation beyond its legitimate authority. 24.5 **Termination for convenience.** AMS may terminate a free or no-fee Service or a Service not subject to a fixed committed term on \[NOTICE[NOTICE PERIOD\],PERIOD], subject to mandatory law and any express service commitment. Termination of a paid fixed-term Subscription is governed by the applicable order and law.

25.1 **Subscriber termination.** You may stop using the Services and close your Account through \[ACCOUNT[ACCOUNT SETTINGS / SUPPORT CONTACT\].CONTACT]. An Organization may terminate an organizational Subscription through its authorized Administrator or contractual contact, subject to the order. 25.2 **Effect on access.** On expi ... ership of Subscriber Content, project IP, licenses, credentials, records or commercial rights to AMS or another user. Such matters remain governed by applicable agreements and law.

27.1 **Excluded categories.** To the maximum extent permitted by law, neither party will be liable to the other for indirect, incidental, special, exemplary, punitive or consequent ... greement expressly provides otherwise. 27.2 **Aggregate cap.** Subject to Section 27.4, each party’s aggregate liability arising out of or relating to these Terms will not exceed \[COUNSEL-APPROVED[COUNSEL-APPROVED CAP; for example, fees paid or payable for the affected Service during the twelve (12) months preceding the event giving rise to the claim\].claim]. The cap must be selected and reviewed by counsel for the contracting entity, subscriber type, jurisdiction, insurance and risk profile. No cap is finalized in this draft. 27.3 ** ... ervice scope, safeguards and contractual documents inform the allocation of risk. This statement does not reduce any non-waivable right or replace a required negotiated allocation.

29.1 **Good-faith escalation.** Before commencing formal proceedings, the parties will attempt in good faith to resolve a dispute through written notice and escalation to authorized representatives for \[30\][30] days, unless urgent injunctive relief, a statutory deadline, consumer right or law makes escalation inappropriate. 29.2 **Proposed governing law.** **Proposed for counsel review only:** these Terms are governed by the laws of \[CALIFORNIA[CALIFORNIA / OTHER APPROVED JURISDICTION\],JURISDICTION], excluding conflict-of-law rules, subject to mandatory consumer and other non-waivable laws. The proposed forum is \[COUNTY/COURT\].[COUNTY/COURT]. Counsel must confirm that the contracting entity, Subscriber type and relevant market can lawfully use this provision. 29.3 **Mandatory local rights.** A consumer or individual m ... bitration, jury-trial waiver or class-action waiver. Any later proposal for such a clause requires separate, jurisdiction-specific legal review and clear acceptance where required.

Where applicable, federal and state consumer, privacy, electronic contracting, accessibility, subscription, data-breach and other laws apply. For California residents, applicable p ... rmation is “sold,” “shared,” “not sold” or “not shared” should be made until actual data flows, analytics, advertising and vendor arrangements have been reviewed. Privacy contact: \[CALIFORNIA[CALIFORNIA PRIVACY CONTACT / URL\].URL]. Other state privacy and consumer laws may apply based on user location, thresholds and processing.

Where applicable, the GDPR, ePrivacy rules and local consumer, accessibility and electronic-contracting requirements apply. The Privacy Notice and DPA must identify controller/proc ... national transfers must use a valid mechanism where required. Mandatory consumer protections, withdrawal rights, language requirements and courts remain unaffected. Local contact: \[EU[EU REPRESENTATIVE / DPO, IF REQUIRED\].REQUIRED].

Where applicable, UK GDPR, the Data Protection Act, electronic privacy rules and consumer laws apply. The privacy materials must address UK-specific roles, rights, transfers, regulator contact and representative/DPO requirements where applicable. Consumer rights and mandatory local forums are preserved. Local contact: \[UK[UK REPRESENTATIVE / PRIVACY CONTACT, IF REQUIRED\].REQUIRED].

Where applicable, Indian data-protection, information-technology, consumer, electronic-contracting, cybersecurity, export and sectoral requirements apply as in force and applicable ... ny, and any rules applicable to children or sensitive data. This draft does not appoint a grievance officer or assert that a specific statutory role is required. Verified contact: \[INDIA[INDIA PRIVACY / GRIEVANCE CONTACT, IF REQUIRED\].REQUIRED].

Where applicable, Japan’s Act on the Protection of Personal Information and related requirements apply, including notices, use purposes, third-party provision, cross-border transfer disclosures and rights. Local consumer protections and restrictions on excluding liability, including where intentional misconduct or gross negligence is involved, remain unaffected. Contact: \[JAPAN[JAPAN PRIVACY CONTACT, IF REQUIRED\].REQUIRED].

Applicable federal and provincial privacy, consumer, electronic-marketing and accessibility requirements apply. Where Quebec law applies, counsel must assess French-language requirements, privacy-impact assessments, transparency, consent, transfer safeguards, contractual language and complaint processes. Non-waivable consumer guarantees and statutory rights remain unaffected. Contact: \[CANADA/QUEBEC[CANADA/QUEBEC CONTACT, IF REQUIRED\].REQUIRED].

Applicable privacy, consumer, electronic contracting, spam and other laws apply. Nothing in these Terms excludes non-excludable consumer guarantees or statutory rights under applicable Australian or New Zealand law. Any limitation of liability or remedy must be consistent with mandatory law. Contact: \[LOCAL[LOCAL PRIVACY/CONSUMER CONTACT, IF REQUIRED\].REQUIRED].

31.1 **Accessibility.** AMS intends to make applicable Services reasonably accessible, subject to the relevant design, technical environment and legal requirements. Specific accessibility standards or conformance levels must not be claimed unless assessed and documented. Report accessibility barriers through \[ACCESSIBILITY[ACCESSIBILITY CONTACT\].CONTACT]. 31.2 **Language.** These Terms may be provided in multiple languages. The governing version is \[LANGUAGE/VERSION\],[LANGUAGE/VERSION], except where local law requires a local-language version to control or requires that a translated version be provided. Translations should be reviewed for legal equivalence before ... consumer disclosures and cancellation processes may vary by location. A locale selection does not by itself establish residency, tax status, supported access or legal eligibility.

33.1 **Support.** Support channels, operating hours, response targets, languages and scope are described at \[SUPPORT[SUPPORT URL / SUPPORT SCHEDULE\].SCHEDULE]. Unless a signed schedule states otherwise, no guaranteed response or resolution time is promised. 33.2 **Complaints.** Complaints about access, billing, content, privacy, security, accessibility or conduct may be submitted through the applicable channel listed below. A complaint does not waive statutory rights, regulator access or urgent remedies. 33.3 **Contact directory.**- Subscriber support: \[SUPPORT[SUPPORT EMAIL / PORTAL\] PORTAL] - Account and access administration: \[ACCOUNT[ACCOUNT SUPPORT\] SUPPORT] - Legal notices: \[LEGAL[LEGAL EMAIL / POSTAL ADDRESS\] ADDRESS] - Privacy requests: \[PRIVACY[PRIVACY EMAIL / REQUEST URL\] URL] - Security incidents and vulnerability reports: \[SECURITY[SECURITY EMAIL / PORTAL\] PORTAL] - Billing and cancellation: \[BILLING[BILLING CONTACT / PORTAL\] PORTAL] - Accessibility: \[ACCESSIBILITY[ACCESSIBILITY CONTACT\] CONTACT] - Complaints and escalation: \[COMPLAINTS[COMPLAINTS CONTACT\] CONTACT] - India grievance contact, if required: \[VERIFIED[VERIFIED APPOINTMENT AND DETAILS\] DETAILS] - EU/UK representative or DPO, if required: \[VERIFIED[VERIFIED DETAILS\] DETAILS] - Contracting entity: \[FULLAVYRA LEGALMICROSYSTEMS NAMEPRIVATE ANDLIMITED; REGISTEREDregistered ADDRESS\]office state: Karnataka, India; address recorded as mailing address in the Certificate of Incorporation: [street address withheld until the owner approves its publication]

An Organization Administrator must: 16.1. Maintain a current roster of Authorized Users and role assignments. 17. 2. Verify that users have a legitimate purpose and any required training or qualification. 18. 3. Apply least-privilege access and avoid broad default permissions. 19. 4. Promptly revoke access when a user leaves, changes role or no longer needs it. 20. 5. Protect administrative credentials with required MFA and secure recovery. 21. 6. Review access and administrative logs at the frequency set by policy. 22. 7. Avoid inspecting user content beyond delegated, lawful need. 23. 8. Maintain appropriate internal policies for Content classification, sharing, retention and incident reporting. 24. 9. Escalate requests that exceed delegated authority to the proper owner or superuser. 25. 10. Not use admin tools to bypass legal, safety, privacy, commercial or governance separation. 26. 11. Cooperate with data-subject requests and incident handling where the Organization is responsible. 27. 12. Ensure the Organization has authority to upload or share its Content and that its users are informed of applicable terms.

The following is a proposed handling framework. Actual classification names, labels and controls must match the implemented AMS information-classification policy. | **IllustrativeIllustrative class** class | **TypicalTypical examples** examples | **HandlingHandling expectation** expectation | |----------------------------------|-----------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------||---|---|---| | Public| Approved public pages, published brochures, released notices| May be shared publicly only in the approved form; do not alter attribution or imply additional endorsement.| | Internal| Routine non-public institutional material| Use only for authorized institutional purposes; do not publish externally without approval.| | Confidential| Non-public project, commercial, partner, customer, supplier or personnel information| Limit to named or approved roles; use approved storage and sharing; do not forward externally without authorization.| | Restricted / Highly Confidential | Trade secrets, proprietary process data, sensitive designs, security details, restricted financial/pricing data| Need-to-know access, approved environment, enhanced controls and explicit authorization for export or external sharing.| | Regulated / Controlled| Export-controlled technical data, regulated personal data, legally privileged material or other controlled categories | Use only in a specifically approved environment after lega ... neral-purpose tools. | A classification label is not a substitute for legal classification, export-control determination, privacy assessment or a contractually required safeguard.

**Required unchecked checkbox (proposed):** > “I have read and agree to the AMS Institutional Core Subscriber Terms and Conditions, version \[VERSION\],[VERSION], and acknowledge that I have been provided the Privacy Notice. I confirm that I am accepting for myself or am authorized to accept on behalf of the Organization identified in my ac ... nization identifiers, locale/country, affirmative action, applicable order and separate consents. Do not collect more identity or device data than necessary and lawfully disclosed.

**Legal and contracting**- \[[ \]] Confirm contracting entity, registration, address, authority and signing process.- \[[ \]] Approve governing law, forum, liability cap, indemnity, limitation carve-outs and claim process.- \[[ \]] Confirm supported countries and prepare required local addenda and translations.- \[[ \]] Review age, capacity, consumer contract, electronic contracting, renewal, cancellation and withdrawal requirements.- \[[ \]] Complete privacy notice, cookie notice, DPA, AI notice and records-retention schedule.- \[[ \]] Verify required privacy, security, grievance, regulator, representative and legal contacts. **Service and product**- \[[ \]] Confirm the exact Services and Service Features covered by these Terms.- \[[ \]] Separate institutional core from commercial, education, investment and other distinct functions.- \[[ \]] Identify beta, preview, restricted, third-party and non-operational features.- \[[ \]] Confirm service maturity labels, support commitments, availability statements and service-level schedules.- \[[ \]] Confirm public content does not expose internal pricing, supplier quotes, confidential models or restricted records. **Security and data**- \[[ \]] Test authentication, MFA, account recovery, session revocation and role-based access.- \[[ \]] Test Organization and tenant isolation, data export permissions and administrator boundaries.- \[[ \]] Validate audit logging, incident response, backup/restore, retention and deletion.- \[[ \]] Complete vendor/subprocessor review, data-flow mapping and international transfer analysis.- \[[ \]] Test privacy request handling, consent records, cookie controls and required opt-out signals.- \[[ \]] Review AI source permissions, prompt handling, output disclaimers, human approvals and model-training settings.- \[[ \]] Confirm export-control and sanctions screening for restricted technical information. **Commercial and operational**- \[[ \]] Configure and test fee disclosure, checkout, payment, receipts, taxes, cancellation and refunds.- \[[ \]] Confirm billing ownership, dispute route, finance reconciliation and authorized approval roles.- \[[ \]] Test support, complaints, escalation, accessibility and language presentation.- \[[ \]] Confirm clickwrap captures the correct document version and evidence.- \[[ \]] Conduct security, legal, accessibility and user-acceptance testing.- \[[ \]] Obtain documented sign-off from Legal, Privacy, Security, Product/Service Owner, Finance and Governance.- \[[ \]] Publish only the approved version; archive prior versions and retain approval evidence. ---

The following items are deliberately unresolved and must be decided before publication: 28.1. Contracting legal entity, jurisdiction, registration number and registered address. 29. 2. Whether the Subscriber is a consumer, business, institutional user or a combination, and whether separate terms are needed. 30. 3. Exact Service definition and list of live features; excluded or separately governed services. 31. 4. Supported countries, restricted countries, languages and localized contract versions. 32. 5. Minimum age, permitted minor use and guardian/institution authorization. 33. 6. Role taxonomy, role-tier meanings, access delegation and governance approval matrix. 34. 7. Privacy controller/processor roles, data map, purposes, lawful bases, retention and subprocessor list. 35. 8. Whether any data is sold/shared for advertising, used for targeted advertising, or subject to opt-out obligations. 36. 9. AI providers, AI data processing, training/improvement position, model versions and high-impact use restrictions. 37. 10. Security commitments, certifications, encryption statements, data residency, incident notice and service levels. 38. 11. Subscription plans, fees, billing frequency, auto-renewal, usage charges, cancellation, withdrawal and refunds. 39. 12. Liability cap, excluded losses, carve-outs, indemnity scope, insurance and claims procedure. 40. 13. Governing law, venue, dispute escalation and local consumer exceptions. 41. 14. Retention, deletion, export, account closure, backup cycle and legal hold process. 42. 15. IP ownership and license treatment for commissioned work, research, joint development and project deliverables. 43. 16. Contact details for legal notices, support, privacy, security, billing, accessibility and complaints. 44. 17. Required local addenda and translations for each supported territory. 45. 18. Whether any separate acceptable-use, confidentiality, research, partner, supplier, customer or project agreement must be incorporated. 46. 19. Whether any feature is subject to special rules for regulated data, export-controlled technology, safety-critical operations or minors. 47. 20. Publication owner, approval record, versioning method and process for future amendments. ---

---