Legal

Website Terms of Use

These Website Terms of Use describe terms that may apply to use of Sites LLC (“Sites,” “we,” “us,” or “our”) public website, pricing pages, forms, onboarding pages, checkout surfaces, customer dashboard, Help Center, support surfaces, account areas, and related online surfaces, but only where these Terms are posted or referenced and the relevant surface is actually launched and made available.

These Terms are written for Sites’ business-to-business managed website service model. Signed customer documents, including any master services agreement, order form, scope appendix, subscription/payment terms, payment authorization, default/nonpayment terms, migration appendix, ownership transfer terms, add-on terms, or other signed scope, may apply separately to customer services.

1. Scope

1.1 Covered surfaces. These Terms may apply to Sites-controlled public website pages, pricing pages, forms, onboarding surfaces, checkout surfaces, customer portal surfaces, dashboard surfaces, Help Center pages, support surfaces, account areas, and related online surfaces only where these Terms are posted or referenced.

1.2 Customer websites. These Terms do not replace the terms, privacy notices, cookie notices, accessibility statements, customer legal obligations, or customer-specific documentation that may apply to customer websites built, migrated, hosted, supported, or managed by Sites.

1.3 Surface-specific terms. Certain surfaces may have additional terms, notices, disclosures, customer agreements, payment authorizations, privacy/cookie notices, accessibility statements, or support rules. Those additional terms may apply to the relevant surface or transaction.

1.4 Business-use model. Sites’ services are designed for business use. Personal, family, household, consumer, sole-proprietor, mixed-use, public-sector, child-directed, regulated, non-U.S., or sensitive-category use cases may require different terms, separate authorization, or a different service path before Sites accepts or performs work.

2. Relationship To Signed Customer Documents

2.1 Signed documents control customer services. Customer service scope, pricing, payment obligations, billing timing, support responsibilities, migration work, ownership-transfer rights, default remedies, cancellation handling, refund or credit handling, privacy obligations, accessibility obligations, platform handoff, and other customer-service terms are governed by the applicable signed customer documents.

2.2 No modification by website copy. Public website pages, pricing pages, dashboard messages, onboarding prompts, Help Center articles, support scripts, checkout labels, invoices, receipts, customer portal labels, sales materials, or other online copy do not modify signed customer documents unless the signed documents or another signed amendment expressly allow that modification method.

2.3 Dashboard and portal actions. Dashboard, account, support, portal, email, or checkout actions do not approve change orders, add-ons, cancellations, refunds, credits, payment changes, ownership transfers, migration obligations, default remedies, or other contract changes unless the signed customer documents authorize that surface and action.

2.4 Order of control. If these Terms conflict with signed customer documents for customer services, the signed customer documents control for the applicable customer-service scope unless the signed documents state otherwise.

3. Account, Dashboard, Support, And Access

3.1 Account access. Sites may provide account, dashboard, support, billing, onboarding, customer-portal, or administrative access where supported by the applicable service process and signed customer documents.

3.2 User authority. Users who access account, dashboard, support, billing, onboarding, customer-portal, or administrative areas on behalf of a customer are responsible for having authority from that customer and for keeping account contact information current.

3.3 Access limits. Sites may restrict, suspend, revoke, condition, or restore access based on security, incident response, platform risk, misuse, customer-requested offboarding, legal or operational needs, or payment, default, and ownership-transfer conditions handled under the applicable signed customer documents.

3.4 Security responsibilities. Customers and users are responsible for using appropriate account-security practices, including strong passwords, multi-factor authentication where available, role-based or delegated access where supported, and prompt notice to Sites of suspected unauthorized access or inaccurate account information.

4. Customer Submissions, Content, And Permissions

4.1 Customer submissions. Customers and users may submit business information, website content, images, logos, service descriptions, menus, pricing, hours, locations, contact details, form content, customer data, project notes, support messages, analytics information, Search Console information, integration information, and other materials for service or support purposes.

4.2 Customer responsibility. Customers are responsible for the accuracy, legality, ownership, rights, permissions, completeness, and approval of materials they submit or authorize for use.

4.3 Service-use permission. For public forms and support contacts, Sites may use submissions to respond to the request, evaluate the request, and operate the relevant online surface. For signed customer service work, the customer permits Sites to use submitted or authorized materials as reasonably needed to evaluate, provide, support, document, revise, migrate, host, publish, maintain, report on, or otherwise perform the applicable services, subject to the applicable signed customer documents.

4.4 Restricted information. Customers and users should not submit privacy-sensitive, credential-sensitive, accessibility-sensitive, payment-sensitive, regulated, confidential, or restricted information unless the applicable intake path, service scope, privacy/security workflow, and signed customer documents support that submission.

4.5 Public use of customer materials. Sites must not use customer names, logos, testimonials, case studies, portfolio entries, screenshots, project descriptions, analytics/results, dashboard data, payment/support data, tracking data, or customer-site examples for public marketing unless the customer has given separate permission and the use is appropriate for the relevant privacy, claim, and sensitive-data context. The publication record must identify the exact approved material, intended surface, source and actual experience, permission scope, claim support, representative-results treatment if relevant, material-relationship disclosure if relevant, and correction, withdrawal, or removal status.

4.6 Feedback. Feedback, suggestions, or ideas submitted to Sites do not authorize Sites to publicly use confidential information, personal data, payment data, tax/accounting records, security information, customer credentials, regulated content, customer-site visitor data, or customer materials beyond authorized service operations under the applicable signed customer documents or support process.

5. Sites Content, Materials, And Online Surfaces

5.1 Sites materials. Sites-owned website content, Help Center materials, templates, visuals, copy, components, design systems, workflows, prompts, documentation, dashboards, methods, and proprietary materials may be protected by intellectual property and other rights.

5.2 Customer deliverables. These Terms do not transfer customer deliverables, ownership-transfer rights, website platform project rights, export rights, platform accounts, domain/DNS access, analytics access, Search Console access, source files, templates, third-party assets, or other assets except as stated in the applicable signed customer documents.

5.3 Platform and third-party limits. Third-party assets, software, hosting platforms, website platforms, plugins, integrations, fonts, media, templates, and other tools may be subject to their own terms, licenses, restrictions, export limits, access limits, and account controls.

6. Acceptable Use

Visitors, prospects, customers, account users, dashboard users, customer admins, support users, and other users must not use Sites-controlled online surfaces to:

  • submit false, misleading, unlawful, infringing, harmful, deceptive, unauthorized, privacy-invasive, platform-abusive, or regulated content;

  • access, probe, test, disrupt, overload, bypass, scrape, harvest, reverse engineer, or interfere with Sites systems, accounts, forms, dashboards, support surfaces, checkout surfaces, or platform integrations without authorization;

  • misuse credentials, tokens, API keys, forms, tracking tools, payment tools, support tools, customer accounts, customer-site data, or third-party systems;

  • upload malicious code or interfere with security, privacy, payment, accessibility, support, or platform operations;

  • violate third-party rights, platform terms, payment rules, privacy/security rules, advertising rules, or applicable law; or

  • submit customer content that is outside the applicable service scope, unsupported, high-risk, or requires separate permission before publication.

Sites may review, reject, remove, restrict, suspend, or route content or access issues through applicable support, security, platform, payment, default, legal, or signed-document workflows.

7. Service Information, Pricing, Claims, And Availability

7.1 Public information. Public plan, pricing, scope, support, migration, ownership-transfer, payment, accessibility, privacy, security, and service information should be read together with applicable signed customer documents.

7.2 No expansion of signed scope. Public information does not add pages, integrations, support, migration, reporting, ownership-transfer rights, refunds, credits, cancellation rights, warranties, remedies, service commitments, payment obligations, tax treatment, or platform handoff rights beyond the applicable signed customer documents.

7.3 Claims and results. Sites does not promise revenue, leads, conversions, search ranking, indexing, traffic, accessibility status, security outcome, privacy outcome, platform approval, ad approval, vendor approval, absence of operational disruption, or any particular customer outcome unless the exact statement is expressly included in applicable signed customer documents or another written statement authorized for that specific use.

7.4 Availability. Online surfaces, dashboards, third-party tools, platforms, checkout tools, forms, support tools, portals, analytics, Search Console, and other integrations may be unavailable, delayed, changed, suspended, limited, or affected by third-party decisions, maintenance, incidents, customer access, customer content, platform capabilities, or other operational factors.

7.5 Reviews and testimonials. Sites will not create, purchase, publish, republish, or disseminate a review or testimonial that materially misrepresents the speaker, the speaker’s actual experience, or the stated results. A customer review selected for Sites advertising or marketing is treated as testimonial or claim content and must pass the applicable permission, authenticity, substantiation, privacy, and publication review.

7.6 Incentives and material relationships. Sites will not condition compensation, credits, discounts, gifts, services, or another incentive on a review expressing a particular positive or negative sentiment. A material relationship or incentive that is not reasonably apparent from the context must be disclosed with the applicable endorsement, testimonial, review, case study, or results statement.

7.7 Representative results. A customer result, testimonial, case study, report excerpt, analytics screenshot, or performance example may be published only when the record supports the stated experience, period, source, configuration, and context. If the featured result is not supported as representative of what similarly situated customers generally achieve, the use must include approved expected-results context where needed. A general results disclaimer does not replace claim-specific support.

7.8 Review presentation. Sites will not present a Sites-controlled review site or collection as independent, or represent a selected review set as all or most submitted reviews when the selection is based on rating or positive sentiment.

7.9 Digital disclosures and corrections. A qualification or material-relationship disclosure needed for a digital claim must be presented with the claim in a manner designed to be noticeable and understandable on the device and surface where the claim appears. If a necessary disclosure cannot be presented effectively on a surface, the claim should not be used there. Inaccurate, misleading, unsupported, unauthorized, or materially incomplete claim content may be corrected, qualified, withdrawn, or removed, with the prior version and action record preserved.

8. Payments, Checkout, Billing, Tax, And Accounting

8.1 Payment documents control. Payment, checkout, billing, invoice, refund, credit, dispute, failed-payment, default, tax, and accounting terms are governed by the applicable signed customer documents, payment authorization, subscription/payment terms, default/nonpayment terms, and order form. Payment processor settings and records are operational records and do not create different customer terms.

8.2 Public payment summary. For Sites’ standard subscription structure, the signed payment documents describe the first monthly plan payment at signup, no setup fee, and recurring billing after Launch Approval, where that structure is selected and documented.

8.3 No override by online labels. Website, pricing, checkout, customer portal, Help Center, dashboard, invoice, receipt, onboarding, support, email, and sales payment explanations do not override signed payment documents.

8.4 Payment processor records. Payment processors and customer portals may maintain payment, subscription, invoice, saved payment-method reference, refund, credit, dispute, chargeback, tax/accounting, and account-status records. Sites does not intend to store full card or bank details when those details are handled by a payment processor.

8.5 Tax and accounting records. Customer-location, invoice category, exemption/tax-document, refund, credit, dispute, chargeback, tax/accounting status, and service-period records may need separate retention and integrity controls. Requests involving those records may be limited, delayed, or routed to an exception where tax/accounting, dispute, default, ownership-transfer, or audit-trail needs apply.

8.6 No automatic outcome. A payment, checkout, billing, invoice, accessibility, support, portal, or account issue does not automatically create a refund, credit, cancellation right, default defense, ownership-transfer right, tax treatment, or payment adjustment unless the applicable signed documents or written customer-specific decision provide that outcome.

9. Third-Party Links, Tools, Platforms, And Vendors

9.1 Third-party tools. Sites online surfaces and services may use or link to third-party website platforms, payment processors, hosting providers, analytics tools, Search Console, tag-management tools, business-profile tools, advertising tools, forms, CRM, booking, scheduling, menu, ordering, email/SMS, chat, support, dashboard, database, AI, automation, domain/DNS, registrar, CDN, security, and monitoring providers.

9.2 Third-party limits. Third-party tools may have their own terms, privacy practices, security controls, accessibility behavior, export limits, account ownership rules, outages, pricing changes, API limits, feature changes, policy changes, data-processing practices, and suspension rules. Sites may not control every third-party action, outage, feature change, policy change, suspension, security incident, privacy practice, export limit, API limit, or platform decision.

9.3 Customer-controlled accounts. Customer-controlled accounts, customer-selected tools, third-party customer accounts, prior-agency accounts, and shared accounts may involve separate access, ownership, privacy, security, accessibility, offboarding, and handoff issues.

9.4 Agency and end-client authority boundary. Website, dashboard, portal, support, account, or tool access does not by itself establish authority for an agency, end client, third-party payer, domain/account owner, or other person to accept paid service terms, approve Launch Approval, authorize payment, request cancellation/refund/default resolution, or request transfer/offboarding unless the applicable Order Form, Payment Authorization, authority record, or written customer-specific authorization supports that role.

10. Privacy, Cookies, Data, And Tracking

10.1 Privacy Policy. Sites’ collection, use, disclosure, retention, and handling of information is described further in the Privacy Policy.

10.2 Cookie Policy. Sites’ use of cookies, pixels, tags, analytics, session tools, tracking tools, forms, checkout tools, and related technologies is described further in the Cookie Policy.

10.3 Tracking and customer websites. Customer-site analytics, pixels, tags, forms, CRM, booking/menu, email/SMS, dashboard, reporting tools, or other tracking tools may require customer authorization, customer-specific notices, consent choices or controls, vendor-specific terms, and customer-site offboarding/deletion paths.

10.4 Configuration-specific statements. Public privacy, cookie, tracking, browser-signal, sale/share, targeted-advertising, consent, opt-out, customer-site, vendor, or data-flow statements are configuration-specific and are addressed in the applicable policy notices.

10.5 No override by policy pages. Website Terms, Privacy Policy, Cookie Policy, cookie banners, preference controls, dashboard labels, Help Center articles, or customer-site notices do not by themselves authorize customer-site tracking, expand customer service scope, approve customer legal notices, or change signed customer obligations unless the signed customer documents or a written customer-specific authorization say so.

11. Accessibility

11.1 Accessibility Statement. Sites’ accessibility approach is described further in the Accessibility Statement.

11.2 Customer websites. Sites’ Accessibility Statement for Sites-owned surfaces does not automatically apply to customer websites, customer content, widgets, forms, platform constraints, industry context, third-party tools, payment/checkout/authentication flows, customer responsibilities, or remediation responsibilities.

11.3 No accessibility outcome promise. Public accessibility wording does not promise a legal status, universal access in every circumstance, third-party widget behavior, assistive-technology behavior, customer-content outcomes, or remediation timelines unless the exact statement is supported for the applicable surface and use.

12. Support, Help Center, Dashboard, And Sales Copy

Support scripts, chat responses, email templates, Help Center articles, dashboard notices, billing/support macros, sales scripts, proposal language, onboarding prompts, invoice notes, receipt notes, portal labels, and customer explanations must match the signed customer documents and written customer-specific terms.

They must not promise refunds, cancellation rights, timelines, ownership transfer, migration results, support levels, accessibility status, privacy/security status, search results, credits, default remedies, transfer rights, tax treatment, payment timing, or professional advice beyond applicable signed customer documents or written customer-specific statements.

Sites should preserve customer-visible support policy versions, Help Center versions, dashboard notices, support macros, and support-ticket records used to explain a customer’s support tier, support window, response target, Priority or severity classification, escalation route, billing status, default status, credit request, or transfer/offboarding status.

13. Additional Legal Terms

Certain warranty, liability, indemnity, dispute-resolution, governing-law, venue, waiver, arbitration, class-action, jury-trial, public-visitor, customer, prospect, account-user, or signed-document-hierarchy terms may apply only if included in the applicable signed customer documents or other terms for the relevant surface. These Website Terms do not add those terms unless they are separately included in the applicable documents.

14. Changes To These Terms

Sites may update these Terms to reflect service changes, website changes, dashboard changes, checkout behavior, support workflow, policy changes, vendor changes, payment workflow, customer geography, changes in law, or service practices.

Changes to signed customer obligations require the process stated in the applicable signed documents. Website Terms, policy pages, pricing pages, checkout flows, onboarding flows, dashboard features, Help Center articles, support scripts, invoices, receipts, customer portal labels, accessibility statements, privacy/cookie disclosures, and claim rules must not be used to change signed obligations without signed written authority.

15. Contact

Questions about these Terms may be sent through the contact method listed on the Sites website.