DRAFT — Terms of Service Not Approved
LEGAL_DRAFT_NOT_APPROVED
This is a mother-template worksheet, not approved Terms of Service. It creates no project-specific pricing, refund, cancellation, intellectual-property, liability, dispute, or other promise. Replace every
PROJECT_BRIEF_REQUIREDitem with verified Project Brief facts, obtain approval from the responsible legal owner, and remove this marker before launch.
Document status
| Field | Required project fact |
|---|---|
| Product or service | PROJECT_BRIEF_REQUIRED: product_name_and_scope |
| Contracting operator | PROJECT_BRIEF_REQUIRED: terms_contracting_operator |
| Support contact | PROJECT_BRIEF_REQUIRED: support_contact |
| Effective date | PROJECT_BRIEF_REQUIRED: terms_effective_date |
| Last updated | PROJECT_BRIEF_REQUIRED: terms_last_updated_date |
| Approved by | PROJECT_BRIEF_REQUIRED: legal_approver_and_approval_record |
Parties, product, and acceptance flow
PROJECT_BRIEF_REQUIRED: identify the contracting operator, product, production domain, covered users or customers, and the exact interface where users are shown or asked to accept these Terms. State separately if the privacy controller/operator or seller/merchant is a different party. Do not infer an entity, address, or jurisdiction from the source-code vendor.
Eligibility, accounts, and security
PROJECT_BRIEF_REQUIRED_OR_NOT_APPLICABLE: record the approved eligibility or age conditions, available sign-in methods, account responsibilities, credential and security expectations, and the tested account-support route.
Service scope and product rules
PROJECT_BRIEF_REQUIRED: describe only the launched capabilities, material limitations, user obligations, task or credit behavior, service availability facts, and prohibited uses that the project owner has approved. Do not describe the mother template, its source code, or its components as the end-user product.
Third-party services and AI providers
PROJECT_BRIEF_REQUIRED: identify only third-party and AI services the launched product actually depends on, the user-facing dependency or separate terms, the verified data or content flow, and the tested behavior when a provider is unavailable or changes. Do not list every provider supported by the mother template, and do not add a blanket liability waiver by default.
Privacy and data practices
PROJECT_BRIEF_REQUIRED: reference the actual, approved Privacy Policy URL and approved version for this project, then describe only the reviewed boundary between these Terms and that policy. Use a verified locale-aware internal route or production URL; never insert an absolute placeholder domain. Keep any data-practice statement aligned with the implemented product and the approved Privacy Policy.
User inputs, uploads, outputs, and intellectual property
PROJECT_BRIEF_REQUIRED: state the approved rules for ownership or permitted use of product branding, site content, user inputs, uploaded files, prompts, generated outputs, saved assets, feedback, and third-party material. Include product-specific deletion and takedown paths where applicable. Do not copy the ShipAny vendor license into these end-user Terms.
Plans, payments, credits, and taxes
PROJECT_BRIEF_REQUIRED_OR_NOT_APPLICABLE: record the actual seller or merchant role, enabled payment providers, currencies, billing cadence, displayed and charged amounts, auto-renewal behavior, trials, promotions, taxes, credits or entitlements, validity, and the place where the user confirms the charge. Keep this section aligned with Pricing and the provider checkout.
Cancellation
PROJECT_BRIEF_REQUIRED_OR_NOT_APPLICABLE: describe the tested cancellation path, which plans can be cancelled, when cancellation becomes effective, what remains accessible afterward, and the support fallback. The presence of a cancellation button or provider API does not define these policy facts.
Refunds
PROJECT_BRIEF_REQUIRED_OR_NOT_APPLICABLE: insert only the approved refund eligibility, exclusions, request route, decision owner, timing, payment-method treatment, and effect on credits, subscriptions, outputs, or other entitlements. Do not assume that purchases are refundable or non-refundable, and do not promise automatic refund handling unless it is implemented and tested.
Suspension, termination, and user data
PROJECT_BRIEF_REQUIRED: state the approved grounds, notice process, account and entitlement effects, appeal or support route, and treatment of user data or saved assets. Do not add a sole-discretion or no-notice rule by default.
Service statements, responsibility, and remedies
PROJECT_BRIEF_REQUIRED_LEGAL_REVIEW: the responsible legal owner must supply and approve any availability statement, warranty language, liability allocation, indemnity, remedy, or mandatory-rights qualification. The mother template provides no default clause.
Governing law and dispute process
PROJECT_BRIEF_REQUIRED_LEGAL_REVIEW: add a governing law, forum, arbitration term, class-action term, or other dispute process only when the responsible legal owner has supplied and approved the exact text. Do not use the ShipAny license's governing law for the end-user product.
Changes and notice
PROJECT_BRIEF_REQUIRED: state the approved versioning, effective-date, notice, and acceptance process. Do not claim that every change is immediately binding merely because a file was deployed.
Contact
PROJECT_BRIEF_REQUIRED: provide the verified Terms or support contact and any additional contact details approved for publication.
Release check: this page must continue to display LEGAL_DRAFT_NOT_APPROVED until all applicable facts above are complete and the responsible legal owner has approved the final text. The marker is a searchable procedural safeguard; it is not a runtime publication gate.