Service scope
Every client order must name the enabled modules, users, environment, usage measure, pricing, credits, support, and launch state.
Smoozen terms placeholder
This page is a product placeholder only. It is not an executed agreement, subscription schedule, data-processing agreement, network opt-in, or legal advice.
Required agreement topics
These topics describe the decisions a final agreement must make visible; they do not create terms by themselves.
Every client order must name the enabled modules, users, environment, usage measure, pricing, credits, support, and launch state.
The client remains authoritative for identity, consent, provider records, bookings, payments, safety, and final records.
Provider and venue recommendations across clients require explicit source-client, provider, venue, attribution, consent, and removal approvals.
Suspension disables new capability use and outbound work while preserving required client records and lawful retention obligations.
Recommendations remain advisory. Human review, client approvals, and deterministic controls govern publication and consequential action.
Launch profiles, data schedules, approvals, incident contacts, and material changes need a traceable owner and review path.
Approval path
Keep commercial, legal/privacy, and operational ownership distinct so no single approval silently expands the product boundary.
Confirms scope, tier, pricing, support expectations, and the environment covered by the client order.
Approves the applicable notice, data schedule, retention, deletion, and incident language.
Confirms readiness, monitoring, rollback, human handoff, and client system-of-record responsibilities.
Until the required owners approve the final terms, capabilities remain governed by the existing launch profile, controls, and release gates.