1. Parties & scope

This agreement is between you (the "Client") and CoreTV LLC. The "Scope" is the specific deliverables, features, services, assumptions, and exclusions in an approved quote, order, statement of work, or estimate that the interface expressly identifies as a formal acceptance document. An estimator or cart preview is not Scope. Work outside Scope requires the applicable reviewed and approved change.

2. Pricing & previews

Amounts shown in the estimator, cart, and on marketing pages are previews—not a final project commitment—and may exclude tax and variable usage. The binding price and included allowances are stated in the quote or order you approve. Metered voice, AI, messaging, email, infrastructure, or similar usage is charged only at the rate and method disclosed before approval; available usage records appear in the dashboard or invoice.

3. Milestones & approvals

Projects may be delivered in stages such as discovery, design, build, and launch. The accepted order identifies required approvals and any action the client has authorized CORE to perform automatically. A client approval, signature, legal acceptance, or final payment action is never inferred from an AI recommendation or remote-assist command. Delayed content or approval may reasonably shift a dependent schedule.

4. Client responsibilities

You agree to provide the content, access, and approvals we need in a timely way (brand assets, copy, logins, and similar), and to confirm that material you supply is yours to use. We treat your credentials and data in line with our Privacy Policy and Data Processing Addendum.

5. Ownership & licensing

Rights the Client already owns in its supplied domain, trademarks, content, and brand assets remain with the Client, subject to third-party and registry rights. Ownership or licensing of the delivered build, reusable CORE materials, third-party components, source code, and any buyout is determined by the approved order. No marketing phrase transfers rights beyond that written scope.

6. Launch & care handoff

When included in scope, launch may cover domain or DNS coordination, certificates, deployment, monitoring, maintenance, hosting, and an edit allowance. The portal identifies the primary account representative and any assigned project or support team. Coverage, response targets, and escalation paths follow the selected plan and Service Level Agreement.

7. Cancellation & termination

An authorized account member may request or schedule cancellation through the permitted flow. Timing, committed terms, earned fees, vendor commitments, refunds, export availability, and transition work follow the approved order, Terms of Service, Refund Policy, and applicable law. Where included and technically available, CoreTV LLC provides the agreed export or handoff after required identity, security, and payment checks.

8. Relationship to our other terms

This Service Agreement is supplemented by our Terms of Service, Privacy Policy, Refund Policy, AI Disclaimer, and (where we process your customers' data) our Data Processing Addendum. Together with your approved order documents, they form the complete terms of the relationship.

---

9. Scope, proposal & approval workflow

The approved quote, order, statement of work, catalog snapshot, and written change orders define the contracted scope. An estimate co-pilot, architecture canvas, proposal scenario, AI summary, ROI illustration, comment, or recommendation helps the parties evaluate scope but does not amend it. Assumptions and client dependencies remain part of the review until incorporated into an approved document.

A client-intake concierge may extract a draft brief, source references, open questions, architecture facts, and dependency suggestions from material the client submits or identifies. The client must review and correct that draft before it becomes an approved requirement. General intake and AI fields are not secret stores; credentials must use the designated credential or delegated-access process.

An authorized delivery-blueprint action may instantiate versioned tasks, milestones, dependencies, and readiness requirements while preserving the recorded project history. A readiness verification or waiver must come from the role identified by the workflow. Timeline and capacity calculations are planning forecasts; only a date expressly committed in the accepted order or written change controls.

Requests for a revision, upgrade, cancellation, refund, risk exception, discount, vendor purchase, or change order enter the applicable review workflow. CORE may require a designated approver based on price, margin, scope, risk, or account authority. Work and billing begin only when the controlling document and required approval state say they do.

New staff-added billables are approval-first. If an authorized client billing manager deliberately turns that gate off in the portal, the recorded setting operates prospectively as the client's instruction to permit authorized CORE staff to attach a disclosed new item with the configured notice and without a separate item-by-item approval. Re-enabling the gate restores approval-first handling for later items.

10. Communications, AI & booking operations

If selected, CORE may operate an AI receptionist, sales or support chat, calling, transcription, email/SMS automation, appointment booking, and follow-up workflows according to the approved playbook, business hours, templates, escalation contacts, consent rules, and provider configuration. The client must validate names, prices, policies, regulated statements, recipients, and escalation instructions before launch and when they change.

Bookings are created only from available time presented by the configured scheduling system. AI may collect a minimal confirmation and offer a free 15-minute review, but it may not promise an unavailable person, guaranteed outcome, emergency response, or unapproved commercial term.

11. Remote assistance & client authorization

Remote assistance is available only through an active, auditable, time-limited grant from the person using the supported session. CORE may navigate, highlight, or prefill only the approved CORE page and fields. The participant reviews and performs any required final submission, signature, acceptance, or payment. The grant can be revoked at any time.

The client is responsible for ensuring that its personnel and end users have authority to share the data and grant the access involved. CORE may refuse a command that would expose credentials, payment data, secrets, unrelated tenant data, or a control reserved to the participant.

12. Client data, consent & team access

The client is responsible for the legality and accuracy of supplied content, contact lists, recordings, knowledge sources, instructions, and credentials, and for obtaining permissions from its customers, callers, staff, and other data subjects. The client must not provide special-category, regulated, or highly sensitive data unless it is necessary, lawful, and expressly included in the signed scope and security design.

CORE limits staff access through role, assignment, primary account representative, and project-team relationships. The client should promptly request removal of a person who no longer needs access and must review portal approvals, notices, usage, and outstanding requests.

A person who invites a collaborator, grants project or billing visibility, comments for an organization, supplies an approval, or waives a readiness item represents that they have authority for that action. Search, relationship, and decision-history tools remain permission-scoped and do not make a restricted record visible merely because it is linked to an accessible record.

13. Renewal notices & request administration

A recurring service renews only under the amount, cadence, cancellation method, and term accepted in the controlling order or later made effective through the required notice and approval process. The platform may prepare and send renewal or price-change notices, preserve provider-acceptance evidence, and hold a changed amount or cadence until its earliest lawful effective cycle. Where a qualifying fixed-term automatic-renewal law applies, the reminder is measured against the contractual cancellation deadline in the legally required window. A catalog edit alone does not amend an active order.

Refund, cancellation, revision, upgrade, privacy, support, and change-order submissions are administered as permission-scoped cases with status, assigned reviewer, communications, evidence, and decision history. The client must keep billing recipients and authorized contacts current, review notices and requests, and respond to reasonably necessary verification or scope questions. CORE remains responsible for the deadlines, notices, decisions, and remedies that the agreement or applicable law assigns to CORE.