SaaS Terms of Service

SAAS TERMS OF SERVICE — TRANSACTION INTAKE AND DRAFTING PACKET

NOT TERMS OF SERVICE — DO NOT PUBLISH OR PRESENT FOR ACCEPTANCE. Use
this packet to design a coordinated contract set. Operative terms must be
separately drafted, versioned, approved, and connected to a verified method
of presentation and assent.

1. Matter control

2. Transaction classification

☐ Business customer negotiated agreement

☐ Business customer click-through or online order

☐ Individual or household customer

☐ Free service or free trial

☐ Paid subscription

☐ Marketplace, reseller, channel, or embedded offering

☐ Public-sector, education, healthcare, financial, or other regulated customer

☐ Developer, API, platform, or infrastructure service

☐ Mobile application or app-store distribution

☐ Other: [________________________________]

Primary sales channel: [________________________________]

Why this document set fits the transaction: [________________________________]

3. Party and customer map

4. Service description

5. Commercial terms worksheet

Do not select renewal, cancellation, refund, notice, or price-change language
until counsel has reviewed the customer type, channel, presentation method,
and every connected jurisdiction.

6. Data and content map

Identify personal data, confidential information, customer content, telemetry,
support data, credentials, logs, derived data, deidentified or aggregated data,
training data, backups, and data supplied by authorized users or third parties.

7. Security and operations register

Do not promise a certification, encryption method, response time, uptime,
recovery objective, deletion period, or audit right that the responsible team
has not verified and approved.

8. Contract-document architecture

9. Current-authority register

Complete from current official law for every relevant jurisdiction and role.

10. Rights and license design

11. Risk-allocation worksheet

12. Termination and transition plan

13. Presentation and assent controls

14. Drafting decisions

☐ Customer and channel are classified

☐ Provider and contracting customer are correctly identified

☐ Service, limits, dependencies, and support are accurate

☐ Commercial terms match billing operations and disclosures

☐ Data, privacy, security, vendor, and retention documents are coordinated

☐ Licenses match actual technical uses

☐ Warranty, remedy, liability, indemnity, and insurance terms are approved together

☐ Suspension, termination, export, deletion, and transition are operationally possible

☐ Governing law and dispute terms are selected for the actual transaction

☐ Presentation, assent, amendment, and version evidence are implemented

15. Launch gate

☐ Current-law review is complete for every customer population and jurisdiction

☐ All linked documents have approved versions and precedence

☐ Product, finance, privacy, security, support, and legal owners approved their promises

☐ Checkout, order, signature, and renewal flows match the approved terms

☐ Customer-facing claims match actual service capabilities

☐ Operational teams can perform every notice, support, security, data, and exit duty

☐ Legacy customers and prior versions have a documented treatment

☐ Change management triggers renewed review where required

16. Final disposition

☐ Draft negotiated business terms

☐ Draft online business terms

☐ Draft consumer or individual-user terms

☐ Create separate service, data, security, SLA, or sector addenda

☐ Return for product or operational remediation

☐ Do not launch or offer the proposed service

Conditions and unresolved issues: [________________________________]

Approved operative documents and version numbers: [________________________________]

This packet itself remains non-operative and unsigned.