Customer Agreement

This Customer Agreement (the "Agreement") governs the website service that Sites provides to the business named in the Order Form.

In plain English. This is the one document that says what you get from Sites, what we expect from you, how the service ends, and who owns what. The Order Form holds your plan, term and price. The Billing Terms hold the detailed money rules. Four short public pages (website terms, privacy, cookies, accessibility) sit alongside.

1. Who This Agreement Is Between

In plain English. Bureau Enterprise LLC provides the service under the name "Sites". You are a business, and the person who signs you up must have the authority to do so.

1.1 Provider. The provider is Bureau Enterprise LLC, a Wyoming limited liability company, which provides its services under the name "Sites" ("Sites"). Its address for legal notices is legal@joinsites.com.

1.2 Customer. The customer is the business named in the Order Form ("Customer").

1.3 Business use. Customer enters this Agreement for business purposes only, not for personal, family or household use.

1.4 Authority. The person who accepts this Agreement for Customer confirms that they have authority to bind Customer, to authorise the payment method used, and to approve the launch of the website. Customer is responsible for keeping that information accurate.

1.5 Agencies and other payers. If Customer is acting for another business (for example, an agency acting for a client), or someone other than Customer pays, Customer must tell Sites in writing before Launch who the end client, the payer, the domain owner and the person who approves the launch are. Customer stays responsible for the order and for this Agreement.

2. What The Agreement Is

In plain English. The Agreement is a short stack of documents. If two of them disagree, the order in Section 2.3 decides. Only a written change from Sites counts: a sales call or a help article does not change the contract.

2.1 The documents. The Agreement consists of:

• the Order Form;

• this Customer Agreement;

• the Billing Terms, which set out the detailed rules on prices, payment authorisation, invoices, taxes, refunds, failed payments and the nonpayment steps; and

• the public policies: the Website Terms of Use, the Privacy Policy, the Cookie Policy and the Accessibility Statement.

It also includes any written change, add-on or special term made under Section 2.5.

2.2 "Accepted". A document is "Accepted" when Customer accepts it online during Sites' signup and checkout, when a party's authorised representative accepts it by email, or when Customer accepts it in another way Sites offers. Online acceptance has the same effect as a signature, and nobody needs to sign on paper. Sites accepts the order by collecting the first payment or, if none is collected, by beginning work. Wherever a document of the Agreement asks for something to be "in writing", an email or a written chat message sent by a party's authorised representative counts.

2.3 Order of precedence. If two parts of the Agreement conflict, the part that comes first in this list controls, and only for the point in conflict: (1) the Order Form; (2) this Customer Agreement; (3) the Billing Terms, for money matters; (4) the public policies. A written special term or change made under Section 2.5 controls over all of them, for the subject it covers. This is the only order of precedence in the Agreement. A sentence elsewhere that says a document "governs" a subject says where that subject is dealt with; it does not change this order.

2.4 Explanations are not promises. Help articles, pricing pages, sales messages, proposals, checkout labels, support replies and similar material explain the service. They do not enlarge the service, the payment terms, the ownership terms or Sites' liability unless Sites confirms the enlargement in writing under Section 2.5.

2.5 Changes need to be in writing. A call, a chat or an email summary does not change the Agreement. A change, a special term or an out-of-the-ordinary scope binds Sites only if an authorised representative of Sites makes it in writing and says that it changes the Agreement or is a special term.

2.6 No dashboard today. Sites does not currently offer a customer dashboard or login. Customer makes requests and gives approvals by email or chat, and manages its payment method and sees its invoices in the payment processor's billing portal. If Sites later offers an online account area, Sites will say so in writing, and what it can do will be described there.

2.7 Defined words. In the Agreement:

• "Customer Materials" means the content, text, photos, images, videos, logos, trademarks, brand assets, menus, prices, business information, data and other material that Customer or anyone acting for Customer provides.

• "Sites Assets" means Sites' reusable templates, components, design systems, code, workflows, tools, methods, know-how and other material that is not specific to Customer.

• "Website" means the website Sites builds, hosts and maintains for Customer under the Order Form.

• "Launch" means the day Sites makes the Website live on Customer's domain (or another approved destination) after Customer has approved it.

• "Update" has the meaning in Section 4.

• "Paid Month" and "Account Standing" have the meanings in Section 14.11.

• "Content Copy" has the meaning in Section 13.5.

• "Handover" has the meaning in Section 14.8.

• "Support Hours" has the meaning in Section 7.2.

3. The Service

In plain English. Sites builds, hosts and looks after one website for you, on the plan you chose. This section lists what each plan includes and what it does not. The prices are in the Order Form.

3.1 What Sites provides. For the Website, Sites provides: a website build; the migration of an existing website within the plan's allowance (Section 5); the integrations the plan includes; the monthly Updates the plan includes (Section 4); mailboxes on Customer's domain (Section 6); the reporting the plan includes; support (Section 7); hosting and publishing of the Website; and the related work needed to keep the Website running as built.

3.2 What each plan includes.

Every plan includes 2 rounds of pre-launch revisions. A third round on the same item is a quoted job. Prices are only in the Order Form.

3.3 Pages. A page is a distinct public page of the Website. It does not include system pages, hidden internal screens, screens of third-party platforms, or legal-policy pages unless the plan includes them. A page with unusually large content, complex media or a complex content structure can be treated as more than one page or as a quoted job even if the page count is within the allowance. Pages beyond the plan's allowance are Updates (a new page counts as 3) or a quoted add-on.

3.4 Integrations. An integration is a connection to a third-party tool, such as a form, a booking or scheduling tool, a CRM, an analytics tool or a menu or ordering tool. Integrations depend on the platform's capability, Customer's access to its own accounts and the third party's terms. Custom APIs, multi-step workflows, custom applications, payment flows and sensitive-data or regulated workflows are not standard integrations. They are quoted separately or declined.

3.5 Online store. Professional and Premium include an online store on the Website, within these limits: the products, payment providers and store features described in Customer's plan and confirmed at kickoff. Essential does not include an online store. Customer is responsible for its products, prices, fulfilment, sales tax, returns and refunds to its own buyers, and for its own payment-processor account and fees. A marketplace (a store that sells other sellers' goods) is not included on any plan.

3.6 Reporting. Reports are delivered monthly (Premium's review quarterly) by email, depend on Customer giving Sites the analytics access the report needs, and are informational. They do not promise traffic, rankings, leads, revenue or any other result.

3.7 Launch targets. The launch targets in Section 3.2 are targets, not guarantees. They run from the day Sites has what it needs from Customer (content, access, approvals, domain readiness) and move when Customer's side is late (Section 8.8).

3.8 What is not included. Unless Sites agrees otherwise in writing, the service does not include: open-ended edits, redesigns, pages, meetings, strategy, copywriting or consulting; custom software, custom applications or marketplaces; workflows involving health information protected under HIPAA; paid advertising management; legal, tax, accounting, medical or other professional advice; review of Customer's claims for legal compliance; emergency support outside Support Hours; work that needs a platform feature the platform does not have; or work that would break the law, a platform's rules or a third party's rights. Anything on this list that Customer wants is quoted separately under Section 3.10 or declined.

3.9 Third-party costs. The plan price does not include domain registration, third-party platform or plugin fees, paid stock media or fonts, advertising spend or the fees of tools Customer owns. Sites does not buy anything on Customer's behalf unless Customer approves the cost in writing first.

3.10 Add-ons and quoted work. Customer may ask for work the plan does not include. Sites gives a written quote with the scope and the price. Sites is not required to quote or perform the work, and nothing is charged for it until Customer approves the quote in writing. Add-ons do not change the selected term, the payment dates, the ownership terms or the default remedies unless the approved quote says so. A change requested after Customer has approved the direction, content or launch readiness may be treated as an Update, a quoted job or a later item, and may move the launch target. Doing a small favour or urgent work once does not waive the limits of the plan.

3.11 Process, not results. Sites provides a process. Sites does not promise search rankings, traffic, indexing, leads, sales, accessibility or legal compliance, security results, or the approval of any third party. The Website's design, copy and technical set-up follow good practice, but results depend on many things Sites does not control.

4. Monthly Updates

In plain English. Each plan includes a number of small changes to your website every month. We call each one an Update. A small change is one Update, bigger jobs count as more, and a fix to our own work is always free. Unused Updates carry over for one month.

4.1 What an Update is. Each plan includes 4, 10 or 20 Updates a month, as the plan table in Section 3.2 shows. One Update is one small change, such as editing text or photos, a blog post or an SEO fix. Bigger jobs count as more: a new page counts as 3. Fixes to our own work are always free.

4.2 What counts as how many Updates.

4.3 Starting and confirming. Customer asks for an Update by chat or email. If the work is up to 2 Updates in size, Sites starts right away. If it is bigger, Sites first tells Customer how many Updates it counts as and waits for Customer's agreement before starting. Sites never uses more than 2 Updates' worth of Customer's allowance without asking.

4.4 Carry-over. Each month's Updates can be used that month and the next month, oldest first. An unused Update therefore carries over one month and then ends. The most a website can hold is 8 on Essential, 20 on Professional and 40 on Premium.

4.5 Running out. If a job counts as more Updates than the Website has left, Sites tells Customer the shortfall and the price of the extra Updates before doing the job, and goes ahead only if Customer agrees. Sites does not charge for extra Updates without asking.

4.6 What Updates are not. Updates are a service allowance, not money. They have no cash value, do not reduce the monthly price, cannot be exchanged for a refund, and cannot be used on another website. Sites does not measure or sell time by the hour.

4.7 When Updates start. Updates start with the first month the Website is live. Work before Launch is part of the build and the 2 rounds of pre-launch revisions in Section 3.2.

4.8 What Updates do not cover. Updates do not cover a new website build beyond the plan's page allowance, a redesign, migration (Section 5), custom development, custom workflows, complex integrations, advertising management, review of regulated claims, large amounts of content entry, major copywriting, large media processing or emergency recovery. Those are quoted under Section 3.10.

4.9 Counting is fixed when you ask. Sites may revise this list from time to time. A revision applies only to requests made after it is published, and never changes the number of Updates a plan includes except through Section 25.1. Work Customer has already asked for keeps the count it was given.

4.10 Goodwill. There are no free periods, trial periods or free months. If Sites chooses to make a goodwill gesture it takes the form of extra Updates or, where Sites agrees in writing, a refund.

5. Moving An Existing Website

In plain English. If you already have a website, each plan includes moving a number of its pages onto your new one. Moving more is an extra monthly charge. We do not promise the new site will rank the same in search.

5.1 What is included. Each plan includes moving the pages of an existing website, up to the allowance in Section 3.2. This means: reviewing the old site; listing its pages; deciding with Customer which pages to rebuild, merge, redirect or drop; carrying the relevant content over; rebuilding or combining the priority pages; setting up redirects where appropriate; helping keep the domain working; and coordinating analytics and Search Console where applicable. Premium also includes a Migration Plan, which is a planning document for a larger or more complex move and is not execution beyond Premium's page allowance.

5.2 Pages, not everything. The allowance counts pages. It does not include every post, file, image, archive entry, plugin, script, user account or database item. A page can be rebuilt, merged, redirected, held back or dropped, and Sites does not have to recreate the old site pixel for pixel.

5.3 Moving more pages. Moving more pages than the plan includes is sold in blocks of 10 additional pages. The price per block, and the number of blocks added to the order at signup for each plan, are in the Order Form. A block is a monthly charge, added to the Website's monthly invoice, and it is the same on both terms. The blocks within the plan's limit are set at signup from the size of the current website Customer states, and are shown at checkout; Customer's acceptance of the order approves them. Any further block is added only with Customer's written approval.

5.4 Larger moves. A migration that is large or complex (for example a big archive, a multi-site consolidation, a login or membership area, a custom database or an ecommerce-style catalogue) is a Complex Migration. It is quoted separately under Section 3.10 and does not start until Customer approves the quote. If Sites finds out during the work that the move is bigger than the plan or the approved blocks cover, the affected work waits for Customer's approval, and nothing extra is charged without it.

5.5 Customer's part. Customer must give Sites access to the current website, the domain and DNS, and analytics and Search Console where they apply; decide what to keep; confirm it has the rights to the content; tell Sites about regulated or sensitive content; review the migrated pages; and keep its own backup of the old site if it wants one.

5.6 No search promises. Sites does not promise rankings, traffic, indexing, search placement, an unbroken transition or identical search results after a move.

5.7 Not included in a move. A move does not include: pixel-perfect reproduction; custom applications; ecommerce, marketplace, membership or user-account migration; HIPAA-sensitive workflows; legal, medical or financial claim review; repair of the old site's hosting or malware; paid-advertising or review-platform account migration; business listings; historical analytics; the transfer of domains, platform accounts or analytics properties; or the migration of existing mailboxes and messages from another email provider, which is a separate service where Sites offers it (Section 6.10).

5.8 No ownership by moving. Access Sites is given to move a website, or work done to move it, does not give Sites any ownership of Customer's domain, accounts or content, and does not give Customer any ownership of Sites Assets.

6. Email

In plain English. Each plan includes mailboxes on your own domain. We set them up after your website is live and send the first password once. Email is for business correspondence between people, not for newsletters or bulk sending.

6.1 Mailboxes. Each plan includes mailboxes on Customer's domain. The number included, and the rates for additional mailboxes, additional storage and email migration, are those published on Sites' pricing page when Customer signs up or, where no figure is published there, the figures Sites confirms to Customer in writing before email is set up. Additional mailboxes and storage are charged on the monthly invoice, only after Sites tells Customer the price and Customer asks for them.

6.2 Setting up. Mailboxes are set up after Launch. Email works only after Customer adds the domain records Sites asks for, using written instructions Sites provides. Customer is responsible for adding them and for any later change to them that interrupts email.

6.3 Passwords and access. Sites creates each mailbox and sends its username and first password once, by email, to the business contact address on Customer's account. Sites does not keep a copy of the password. Customer is responsible for keeping mailbox passwords confidential, for changing a password it believes has been disclosed, and for activity under its mailboxes' credentials. Customer reads and sends mail through Sites Mail, Sites' webmail service, or any standard email application, and can change a mailbox's password in Sites Mail. Customer does not receive access to the email provider's administration tools.

6.4 Changes. Customer asks Sites by chat or email to add, remove or change mailboxes, and Sites makes the change. If Sites later lets Customer make some changes itself, it will say so in writing. Paid additions are always confirmed before they are charged.

6.5 Storage. Each mailbox has a storage allowance. When a mailbox is full it can stop receiving new messages until space is freed or storage is added.

6.6 Removing a mailbox and changing plan. When a mailbox is removed, its charge stops at the next invoice and the mailbox stays usable until the end of the period Customer has already paid for. If a plan change would leave Customer with more mailboxes than the new plan includes, the extra mailboxes keep working at the rate for additional mailboxes, and Sites shows Customer the monthly difference before the change takes effect.

6.7 Rules for email. Sites' mailboxes are for business correspondence between people. Customer must not use them to:

• send marketing email or newsletters, even to people who asked for them (use a dedicated email-marketing service);

• send to a mailing list unless every recipient confirmed the subscription by double opt-in;

• send unsolicited email, or email that is unlawful, deceptive or harmful;

• send as, or for, a domain Customer does not own or manage;

• exceed the sending limits of Sites' email provider, or create extra mailboxes to get round them;

• use "warm-up" or automated cold-email services, or send automated messages not meant to be read by a person; or

• send repeatedly to addresses that do not exist.

Sites tells Customer the current sending limits on request, because the provider sets them and they can change. Because misuse threatens every customer's delivery, Sites may suspend a mailbox at once and tell Customer why (Section 10.5).

6.8 During nonpayment. While an overdue amount is unpaid, the Website may be suspended under the Billing Terms without affecting email. If the overdue amount is still unpaid after 30 days, the mailboxes may be made receive-only, which means they can receive messages but not send them, until Customer pays. Mailboxes return to normal promptly after payment, without a request and without a fee.

6.9 After the Agreement ends. Mailboxes stay available for 30 days after the Agreement ends so that Customer can collect its messages and move its email to another provider. During that time Customer may ask Sites for an export. After that Sites may permanently delete the mailboxes and their messages.

6.10 Email migration. Moving existing mailboxes and messages from another provider is not part of moving a website. Where Sites offers it, it is a separate service charged once for each mailbox moved, at the rate described in Section 6.1.

6.11 Keep your own copies. Sites and its email provider do not guarantee that deleted or lost messages can be recovered. Customer should keep copies of messages it needs, for example in an email application that stores mail on its own devices.

7. Support

In plain English. You can reach us by chat or email during our support hours. The response targets are for a first reply, not for finishing the job.

7.1 Channels. Support is by chat and by email at support@joinsites.com. Customer asks for Updates, reports problems and asks questions through these channels.

7.2 Support Hours. Support is available Monday to Friday, 9am to 5pm Central Time, except U.S. federal holidays ("Support Hours"). A request received outside Support Hours is treated as received when Support Hours next begin.

7.3 Response targets. Sites aims to give a first response within the target for the plan, counted in Support Hours: Essential, 48 hours; Professional, 24 hours; Premium, the same business day. A response target is for a first response only. It is not a promise of completion, a fix, a launch date, a third party's response or a remedy for any loss. Premium's same-business-day target applies only to requests received during Support Hours.

7.4 What support covers. Support covers questions and requests about the Customer's plan, the live Website, its documented integrations and the platform set-up. It does not cover undocumented add-ons, custom development, recovery of Customer's accounts with third parties, troubleshooting of Customer's own devices, advertising support, business consulting, professional advice, or emergencies outside Support Hours.

8. Launch, Term And Cancelling

In plain English. Your term starts the day your website goes live. You choose 6 or 12 months. You can cancel any time by email or chat, but the cancellation takes effect at the end of your term, and you keep paying monthly until then. After the term it runs month to month, and you can cancel effective the end of any paid month.

8.1 Launch. Customer approves the Website for launch by email or chat. Sites then makes the Website live, and that act is Launch. Launch starts the term and the monthly plan, and Sites never starts them before the Website is live. At or before Launch, Sites tells Customer the monthly amount and the date of the next charge. If something small is still outstanding, Sites may complete it after Launch, and Launch is not delayed by it. A missing payment card does not block Launch: the website still goes live and the first invoice is issued for payment.

8.2 If Customer rejects the launch. Customer must say specifically what is wrong. Sites then treats each item as a correction, a change request, a later item, an Update or a quote, and tells Customer which. A defect in work Sites delivered is corrected free (Section 4.2).

8.3 Term. The term is the one Customer selected at signup, 6 months or 12 months, counted from Launch. Sites does not sell a 24-month term.

8.4 After the term. When the term is complete, the service continues month to month at the same monthly price. It does not roll into a new fixed term. Completing the term does not change the price.

8.5 How Customer cancels. Customer cancels by email to support@joinsites.com or legal@joinsites.com, or by chat. Sites confirms the cancellation and its effective date in writing. The effective date is the one this Section sets, whether or not Sites has yet confirmed it. An online way to cancel will come with the customer app, and Sites will say so in writing when it does.

8.6 The term is binding, billed monthly. If Customer cancels before the selected term ends, the cancellation takes effect at the end of the selected term. Monthly fees continue to be billed monthly until then. Sites charges no early-termination fee and does not bill the remaining months as a lump sum. Sites may agree an earlier end date in writing. After the selected term, a cancellation takes effect at the end of the then-current paid month.

8.7 One website, one subscription. Each website is its own subscription, with its own plan, term, price, allowances and Updates. Nothing is shared between websites, a second website is a second order whose term starts at its own Launch, and the suspension or ending of one website does not suspend or end another.

8.8 Customer delay. If Customer does not provide required content, access or approval within 5 business days after Sites asks (2 business days for urgent launch, domain, payment, security or access items), the affected timelines, targets and response commitments are extended, and Sites may pause the affected work until Customer responds. A silence, a preview link, a screenshot or the setting up of a domain connection is not an approval to launch.

9. Customer's Responsibilities

In plain English. You give us accurate information, the right to use the content you give us, and the access we need, and you answer our questions in reasonable time.

9.1 Information. Customer must provide accurate business information (identity, contacts, services, prices, hours, locations, billing and location details) and update it when it changes.

9.2 Rights and claims. Customer is responsible for the accuracy and legality of Customer Materials and of the claims in its content, and for having the rights to use them, including photos, music, fonts, logos, testimonials and reviews. Customer is responsible for claims about regulated matters (health, legal, financial, and similar) and for its own advertising and consumer-law obligations.

9.3 Access. Customer must provide the access Sites needs (domain and DNS, current website, analytics, Search Console, booking, forms, CRM, and similar tools) in good time. Where the platform allows, Customer should use collaborator, role-based or delegated access instead of sharing passwords.

9.4 Approvals. Customer must respond to Sites' requests for direction, content, feedback and approval within the times in Section 8.8, and approvals must come from a person authorised to give them.

9.5 No circumvention. Customer must not interfere with the platform set-up, remove Sites' access while the Agreement continues, copy Sites Assets, or access Sites' internal systems.

9.6 Who the service is for. The service is for business use. Sites does not support: adult content; gambling; crypto or investment offers; high-risk legal or medical claims; marketplaces or custom apps; workflows involving HIPAA-protected health information; customers who need a promise about search ranking, traffic or indexing; tobacco shops; alcohol businesses; or other uses Sites reasonably considers unlawful, misleading, high-risk or outside the service.

9.7 Screening. Health, wellness, dental, medical, legal, accounting, financial, real-estate and similar businesses are screened before work starts. Sites may decline, condition or narrow the work if it raises a claim, licensing, privacy or professional-responsibility risk. Sites may also ask for address-level business and billing information, and may decline or condition service where a tax, regulatory or payment review shows the service should not go ahead under the standard model.

10. Acceptable Use

In plain English. Do not use the service to break the law, harm others, attack our systems or send spam. Tell us at abuse@joinsites.com if you see misuse. We usually give you a chance to fix things first, but we can act first when there is a real threat.

10.1 Websites and content. Customer must not use the service, its Website or its mailboxes to publish, store or send content that is unlawful, infringing, deceptive, defamatory, harassing, sexually exploitative or harmful to minors; malware, phishing or code designed to harm, deceive or gain unauthorised access; or content that violates another person's privacy or rights.

10.2 Systems. Customer must not probe, attack, overload or interfere with Sites' systems or its providers' systems; use the service to mine cryptocurrency or place an unreasonable load on it; share access with people Customer has not authorised; or resell the service except as the Agreement allows for agencies.

10.3 Email. Email use is also governed by Section 6.7.

10.4 Provider rules. Sites provides parts of the service through the providers described in the Privacy Policy. Where a provider's rules apply to how Customer uses its part, they are set out in the Agreement, and Customer must follow them.

10.5 Reporting and enforcement. Anyone may report abuse to abuse@joinsites.com. If Customer breaks this Section, Sites will tell Customer what the breach is and give Customer a reasonable time to stop. If it continues, Sites may remove or disable the content, or suspend the affected website or mailbox. Where the breach threatens the service, other customers or the law, including email sent in breach of Section 6.7, Sites may act first and tell Customer promptly afterwards. Fees or penalties that Sites incurs because of the breach are invoiced to Customer with an explanation and charged to Customer's saved payment method only as the Billing Terms allow. A suspension under this Section is not termination and does not follow the nonpayment steps.

11. Money In Brief

In plain English. You pay the first month when you sign up and nothing extra when the website goes live. Refunds follow one plain rule. The Billing Terms hold the details. The price, the term and the first month are in your Order Form.

11.1 Where the money rules are. Prices, the term, and the amount due at signup and each month are in the Order Form. How payment is authorised and charged, invoices, taxes, refunds, failed payments and the nonpayment steps are in the Billing Terms. This Section states the main rules so that the Agreement reads on its own; the order in Section 2.3 decides any conflict.

11.2 The first month. Customer pays the first month at signup. There is no setup fee. That payment covers the first month of service after Launch, and the first monthly invoice is issued one month after Launch. The first month is charged exactly once: at signup or at Launch, never twice and never zero.

11.3 If the first payment is refunded or disputed. If the signup payment is refunded in full before Launch, or is reversed because a payment dispute is decided against Sites, the first month has not been paid and is charged at Launch. If a dispute about the signup payment is still open, Sites may postpone Launch until it is decided. A partial refund of the signup payment reduces the amount Customer paid; it does not change when monthly billing starts, and the first month is not charged again at Launch.

11.4 Refunds. Sites refunds a payment in full if Sites declines Customer, or cannot serve Customer, before Sites begins onboarding or work, and refunds any charge made in error. Once Sites has begun onboarding or work, fees are not refundable, except where Sites agrees in writing or the law requires. Sites reviews every refund request. If Customer cancels before Launch and Sites agrees to refund part of the signup payment, the refund is of the part of the fee not yet earned; the amount Sites keeps pays for the work done and the capacity reserved, and is not a payment for a month of service.

11.5 Held prices. The price Customer pays is not increased without Customer's agreement. The Agreement can change under Section 25.2, but a change never increases Customer's fees or held price without Customer's agreement.

11.6 Payment disputes. Customer must tell Sites promptly if it disputes a charge, and give the details. Disputes, chargebacks, failed payments, refunds and collections are handled under the Billing Terms. Raising a payment dispute does not by itself stop the reminder steps in Section 12.1, which continue unless Sites pauses them.

11.7 Taxes. Fees are exclusive of taxes unless the Order Form or the invoice says otherwise. Customer is responsible for applicable taxes, except taxes on Sites' income. The Billing Terms state how tax is collected and how Customer claims an exemption.

12. Late Or Failed Payment

In plain English. If a payment fails we remind you, try again, and warn you before anything happens. Your website can be switched off from day 7, but we do not end the agreement before day 60, and never until a final notice has been sent at least 7 days earlier. Paying brings everything back.

12.1 The steps. Counting from the day a payment first fails as day 0: Sites tells Customer the payment failed and how to pay; on or about day 3 and day 6 Sites tries again and sends another notice, and the day-6 notice is a Final Notice that the Website will be suspended; from day 7 Sites may suspend the Website, and visitors see a holding page; if the amount is still unpaid after 30 days the mailboxes may be made receive-only (Section 6.8); and Sites may terminate no earlier than day 60. The Billing Terms hold the full schedule.

12.2 Ending waits for a notice. Sites will not terminate for nonpayment until at least 7 days after Sites has sent a Termination Notice stating the date and how to pay. A notice sent to the business contact email address on Customer's account counts as sent even if it does not reach Customer, so Customer must keep that address current.

12.3 Suspension is not termination. While the Website is suspended, the Agreement continues and so does Customer's obligation to pay amounts already billed.

12.4 Paying restores. If Customer pays at any time before termination, Sites restores the Website and any mailbox limits promptly, without a request and without a fee.

12.5 Limits on remedies. The Agreement does not provide for acceleration of future fees, liquidated damages, aggressive collection, or termination without notice and a chance to cure, except where this Agreement or the Billing Terms expressly say so.

13. Suspension And Ending

In plain English. Either of us can end the agreement for a serious reason after a warning. We can also end it for convenience, and if we do you get back any unpaid-for time you paid in advance. When it ends you can get a copy of your content for 60 days and your mailboxes stay for 30.

13.1 Suspension for other reasons. Besides nonpayment, Sites may suspend the Website, support, Updates or other services where security, access, misuse, unlawful activity or legal risk justifies it, and will tell Customer why as soon as practicable. Suspension is not termination.

13.2 Ending by Sites for cause. Sites may end the Agreement for unsupported use, unlawful activity, repeated default, serious obstruction by Customer, a platform or security risk, misleading claims that create regulatory risk, abusive conduct, or another material breach. Except for nonpayment (which follows Section 12) and where the threat is immediate, Sites first gives written notice of the breach and 30 days to cure it.

13.3 Ending by Sites for convenience. Sites may end the Agreement for a website for any reason by giving Customer written notice at least 30 days before the ending date. If Sites does so, it refunds the part of any month Customer has already paid that covers days after the ending date, and Customer remains entitled to the Content Copy and the mailbox period in Sections 13.5 and 13.6. Customer owes no further monthly fees for the period after the ending date, including the rest of the selected term. If Sites ends the service this way before 12 Paid Months, Customer may still ask for the Handover in Section 14.8.

13.4 Effect of ending. On ending, Customer remains responsible for amounts that were due before the ending date and for approved add-ons already delivered. Sites may remove Customer's access to the service, and Customer must stop using Sites Assets, subject to Section 14.4.

13.5 Content Copy. For 60 days after the Agreement ends, Customer may ask Sites for a copy of its content, and Sites will provide it within 10 business days. The copy contains the text and other content entered into the Website, the images and files Customer provided, a static snapshot of the published pages, Customer's invoice history, and a copy of the Agreement (the "Content Copy"). It is not an editable website project, and it does not give Customer the Website's design. Sites does not prepare a Content Copy unless Customer asks. Customer may keep and use for its own business the text, images and files in the Content Copy without time limit.

13.6 Mailboxes after ending. See Section 6.9.

13.7 Deletion. After the periods in Sections 13.5 and 6.9, Sites may permanently delete the Website's content, the mailboxes and their messages, except records Sites must keep for legal, tax or accounting reasons.

13.8 Customer-owned things stay Customer's. A payment dispute, a nonpayment, a cancellation or an offboarding does not by itself allow Sites to block, delete or hold back Customer's domain, Customer's own accounts or Customer's business data, or notices Sites must give about billing, privacy or security.

14. Ownership, Licence And Handover

In plain English. Your content, your logo and your domain are yours. While you are a customer you have the right to use the website we build for you. After 12 paid months, if you ask, we hand over your content, your images and a full copy of the site's design, and help you move your domain. The website project on our platform account stays ours unless we agree otherwise.

14.1 Customer Materials. Customer keeps ownership of Customer Materials, including its content, logos, trademarks, photos, media, business information, data and its own accounts.

14.2 Domain. Customer's domain name belongs to Customer, and Sites acquires no right in it. Customer is responsible for keeping the domain registered and renewed.

14.3 Licence from Customer to Sites. Customer gives Sites a non-exclusive licence to use, copy, modify, publish, display, host, move and adapt Customer Materials as needed to provide, support, move, maintain and document the service. This licence does not let Sites use Customer's confidential content, marks, media or customer-specific work outside the Agreement. Sites may use non-confidential operational learnings from the work to improve its service.

14.4 Licence to Customer. While the Agreement continues, Sites gives Customer a non-exclusive right to use the Website Sites builds and hosts for Customer, including its design, text, images and code as built, for Customer's own business. This right ends when the Agreement ends, except for what Section 13.5 and Section 14.8 provide.

14.5 Sites Assets. Sites keeps all rights in the Sites Assets, including its templates, components, design systems, workflows, tools, generic layouts, code snippets, methods and know-how. Using Sites Assets in Customer's Website does not transfer them to Customer.

14.6 Third-party materials. Third-party software, fonts, stock media, plugins, integrations, platform features and similar materials are subject to their owners' licences, platform terms and export limits.

14.7 Platform control. During the Agreement Sites controls the website platform workspace and project (currently Framer), the hosting, the publishing, and the collaborator access, to maintain, support, update and protect the service. The platform project itself stays Sites' unless Sites and Customer agree otherwise in writing.

14.8 Handover after 12 Paid Months. If, when Customer asks, the Website has had 12 Paid Months and Customer is in Account Standing, Sites will hand over:

• Customer's content: the text and other content entered into the Website;

• Customer's images and files;

• a full copy or export of the Website's design, in the formats the website platform allows, such as static files of the published pages; and

• help moving Customer's domain to wherever Customer chooses (Section 14.10).

This is the "Handover". Sites delivers it within 15 business days of the request, and Customer may ask once the conditions are met, including after the Agreement has ended, for up to 60 days after it ends. On Handover, Sites assigns to Customer the rights Sites holds in the customer-specific parts of the design delivered, and gives Customer a perpetual, non-exclusive licence to use any Sites Assets that are built into the delivered copy, as part of that copy and for Customer's own business. Sites Assets are not otherwise transferred and are not sold or sublicensed.

14.9 What Handover is not. Handover does not include: the platform project, workspace or account itself (Section 14.7); the Sites Assets as separate items; third-party materials that cannot be passed on; Sites' internal systems, records and tools; or support, hosting or maintenance after the Agreement ends. Customer pays any fees of the new platform, hosting, domain and tools it chooses after Handover, and is responsible for backing up, securing and maintaining what it receives. Handover does not create any promise about the performance of the delivered copy on another platform.

14.10 Moving the domain. Because the domain is Customer's, Sites gives Customer the information and help it reasonably needs to point the domain at a new host, to move its DNS, and to remove Sites' access to Customer's accounts. Sites does not hold Customer's domain hostage.

14.11 Counting Paid Months. A "Paid Month" is a monthly service period of the Website, counted from Launch, for which the plan fee has been paid or has been resolved in writing by Sites. Each period counts once. A month for which the plan fee was not paid, or in which the Website was suspended for nonpayment, does not count, and does not reset the months already counted. "12 Paid Months" is 12 of these, not necessarily in a row; "continuous" means the service relationship stays in place. "Account Standing" means no amount of the plan fee is overdue and unpaid, and no payment dispute or chargeback on the Website's fees is unresolved, or that Sites has agreed in writing to treat the account as in good standing. Customer may ask Sites at any time how many Paid Months the Website has, and Sites will tell Customer.

14.12 Six-month term. The same 12 Paid Months apply on a 6-month term and a 12-month term. A 6-month customer reaches 12 Paid Months only if the service continues month to month after the term ends. A customer who ends the service before 12 Paid Months does not receive Handover, but does receive the Content Copy under Section 13.5.

14.13 Feedback. If Customer gives suggestions or feedback about Sites' service, Sites may use them without paying for them.

15. Data, Privacy And Security

In plain English. We handle your data only to run your service, we never sell it, and we do not use your content to train AI models. Nobody can promise perfect security, but we use sensible safeguards and tell you promptly if something goes wrong with your data.

15.1 Privacy Policy. How Sites collects, uses, shares and keeps personal data, and the types of service providers it uses, are described in the Privacy Policy and the Cookie Policy.

15.2 Data Sites handles for Customer. For personal information in Customer Materials, Customer's Website, Customer's mailboxes, or collected by Customer's Website from its visitors ("Customer Personal Data"), Sites acts as Customer's service provider. Sites will: (a) use Customer Personal Data only to provide the service, on Customer's instructions in the Agreement, or as the law requires; (b) not sell it or use it for its own purposes; (c) use the types of providers described in the Privacy Policy, remain responsible for them, and tell Customer by email at least 10 business days before a new provider that will process Customer Personal Data starts to do so; (d) tell Customer without undue delay, and no later than 72 hours after becoming aware, of a security incident that leads to unauthorised access to Customer Personal Data; and (e) after the Agreement ends, keep and delete Customer Personal Data as Section 13 describes, except where the law requires Sites to keep it. Customer is responsible for having the rights and giving the notices needed for Sites to process Customer Personal Data.

15.3 No AI training. Sites does not use Customer Materials or Customer Personal Data to train artificial-intelligence models, and does not allow its providers to do so. Sites may use artificial-intelligence tools to help perform the service, under the confidentiality and data terms of the Agreement, and gives Customer the notice that Section 15.2(c) requires before a provider of such tools processes Customer Personal Data.

15.4 Access. Sites prefers collaborator, delegated and role-based access, and revokes access when it is no longer needed. Customer remains responsible for the accuracy and availability of access it provides.

15.5 No security guarantee. Sites uses reasonable security controls, but does not guarantee complete security, uninterrupted access, the absence of incidents, or the security of its providers or platforms.

15.6 Sensitive data. Customer must not give Sites sensitive personal data, regulated health information or other high-risk data unless Sites has agreed in writing and the review required for it is done.

15.7 Customer's tracking. If Sites installs analytics, pixels, forms or similar tools on Customer's Website, Customer is responsible for the notices, consents and policies its own visitors need.

16. Confidentiality

In plain English. Each of us keeps the other's non-public information private and uses it only for this Agreement.

16.1 Confidential information. Confidential information is non-public business, technical, financial, customer, project, payment, access, credential, pricing or other information that one party discloses to the other and that is reasonably understood to be confidential.

16.2 Protection. Each party uses the other's confidential information only for the Agreement and takes reasonable care to protect it.

16.3 Exceptions. Confidential information does not include information that is public without breach, was already known, was independently developed, or was lawfully received from a third party without a duty of confidence. A party may disclose it if the law, a court, a regulator, a payment processor or the party's professional advisers require, using reasonable efforts to limit the disclosure where permitted.

16.4 Return or deletion. On ending or reasonable request, each party returns or deletes the other's confidential information where feasible, subject to backups, and legal, tax, accounting, insurance and dispute record needs.

17. Publicity

In plain English. We do not name you as a customer or show your site in our portfolio unless you agree.

17.1 Sites may identify Customer as a customer, or use the Website, screenshots, logo or results in portfolio or marketing, only if Customer agrees in writing. Sites does not publish a Customer review, testimonial or result without the exact content approved by Customer, and does not invent, buy or distort reviews. Customer grants Sites permission to use Customer's marks only as needed to provide the service unless Customer agrees to more.

18. Third Parties And Content Risk

In plain English. Parts of the service rely on other companies' platforms, and we cannot control them. You are responsible for what your website says about your business.

18.1 Platforms. The service depends on third-party platforms and tools, including the website platform, payment processor, domain registrars, analytics tools and email provider. Sites is not responsible for their outages, pricing changes, feature changes, export limits, account suspensions, policy changes or discontinuation. Customer is responsible for the standing, payment and security of accounts that Customer owns, and for complying with the terms of third-party services it uses.

18.2 Claims in Customer's content. Customer is responsible for claims in its content, including prices, offers, testimonials, reviews, photos, before-and-after claims, and health, legal, accounting and financial statements. Sites may reject or require changes to content or claims that are misleading, unsupported, unlawful, regulated or prohibited by a platform.

18.3 No outcome claims. Sites will not state or imply in public claims that it guarantees rankings, traffic, indexing, results, accessibility compliance or legal compliance.

18.4 Accessibility and search. Sites builds with accessibility and search practice in mind and may carry out accessibility or SEO work as an Update or quoted job. It does not guarantee that any website, content or later change meets an accessibility law or standard, or achieves any search result.

19. Warranties And Disclaimers

In plain English. We will do the work with reasonable care. We do not promise results, and the service is provided as it is, apart from what this Agreement says.

19.1 Authority. Each party confirms it has authority to enter into the Agreement.

19.2 Customer's confirmations. Customer confirms that it has the rights to Customer Materials; has authority for the people who sign up, pay, approve the launch and give instructions for it; has identified accurately any agency, end-client or third-party payer role; will give accurate information; and will not ask for unlawful or unsupported work.

19.3 Disclaimer. Except as the Agreement expressly states, Sites disclaims implied warranties, including merchantability, fitness for a particular purpose, non-infringement, uninterrupted or error-free operation, search or revenue performance, and satisfaction of any legal, tax, accessibility, privacy, security or platform requirement.

19.4 No professional advice. Sites does not give legal, tax, accounting, investment, medical, insurance or other regulated professional advice, and the service creates no professional relationship.

19.5 No guaranteed outcomes. Sites does not guarantee business results, leads, conversions, revenue, rankings, traffic, indexing, vendor or advertising approval, or satisfaction of accessibility or privacy requirements.

20. Indemnity

In plain English. Each of us covers the other against third-party claims that come from our own side's content or work.

20.1 By Customer. Customer will defend and indemnify Sites against third-party claims, and the resulting losses and costs, arising from Customer Materials, Customer's products or services, Customer's data, access Customer provides, Customer's violation of law or third-party rights, or Customer's breach of the Agreement.

20.2 By Sites. Sites will defend Customer against a third-party claim that the customer-specific design Sites created, used as authorised, infringes that party's intellectual property rights, and will pay damages finally awarded or settlements Sites approves. This does not apply to claims arising from Customer Materials, Customer's instructions, third-party platforms or materials, Customer's changes, combinations not provided by Sites, Sites Assets, open-source materials or use outside the Agreement.

20.3 Procedure. The indemnified party must give prompt notice, reasonable cooperation and control of the defence to the indemnifying party. Neither party may settle a claim in a way that admits fault for the other, imposes non-monetary obligations on the other, or affects the other's rights without the other's consent.

21. Limits Of Liability

In plain English. If we are at fault, what we owe you is capped at the greater of six months of fees or $1,000, and we are not liable for indirect losses such as lost profit. These limits do not apply to things like fraud or your obligation to pay.

21.1 Cap. Except for the categories in Section 21.3, Sites' total liability arising out of or related to the Agreement will not exceed the greater of the fees Customer paid Sites for the affected Website in the six months before the event giving rise to the claim, or $1,000.

21.2 Excluded damages. To the fullest extent permitted by law, Sites is not liable for indirect, incidental, consequential, special, exemplary or punitive damages, or for lost profit, revenue, data or goodwill, business interruption, search-ranking loss, advertising-performance loss or replacement-service costs.

21.3 Exceptions. The cap does not apply to Customer's payment obligations; either party's breach of its confidentiality obligations (other than a claim arising from a security incident affecting data, which remains subject to the cap); either party's misuse of the other's intellectual property; indemnity obligations; fraud, gross negligence or wilful misconduct; or liability that cannot be capped under the law.

21.4 Basis of the bargain. The parties acknowledge that the prices and the risk allocation depend on these limits.

22. Law, Compliance And Copyright

In plain English. Each of us follows the laws that apply to our own business. Report copyright problems through the process on our website terms page.

22.1 Compliance. Each party is responsible for complying with the laws, professional rules and platform terms that apply to its own business, content and conduct. Customer remains responsible for obligations specific to its industry, advertising, licences, privacy, accessibility and consumer disclosures.

22.2 Export control and sanctions. Customer confirms that it is not named on, or owned or controlled by anyone named on, a U.S. government sanctions or restricted-party list, and is not in a country or region under comprehensive U.S. sanctions, and will not use the service in breach of U.S. export-control or sanctions law. Sites may suspend or end the service where needed to comply.

22.3 Copyright complaints. Copyright complaints about content on a website or in a mailbox Sites hosts are handled under the copyright-complaints section of the Website Terms of Use, including the removal of content and the ending of repeat infringers' services.

23. Notices

In plain English. Legal notices go by email. Send yours to legal@joinsites.com, and keep your contact email address up to date because that is where we send ours.

23.1 By email. Notices under the Agreement are given in writing by email. Notices to Sites go to legal@joinsites.com. Notices to Customer go to the business contact email address on Customer's account. Each party keeps its address current.

23.2 When a notice is given. A notice to Customer is given when it is sent to that address, even if it does not reach Customer. A notice to Sites is given when it is sent to legal@joinsites.com, unless the sender receives a message that it could not be delivered.

23.3 Everyday messages. Routine project, support, billing, approval and access messages may also be sent by chat, by email and through the payment processor's emails and invoices.

23.4 Support is not a notice. Support and billing requests go to support@joinsites.com or chat. They are not formal notices under this Section, except that a cancellation under Section 8.5 may be sent to support@joinsites.com or legal@joinsites.com or made by chat.

23.5 Electronic communications. Customer agrees to receive the Agreement, notices, invoices and other communications electronically, and agrees that its online acceptance has the same effect as a signature.

24. Governing Law And Disputes

In plain English. Wyoming law applies. Disputes go to the courts in Sheridan County, Wyoming. We try to talk first. There is no arbitration, class-action waiver or jury waiver.

24.1 Talking first. Before starting formal proceedings, the parties try in good faith to resolve the dispute through designated representatives, unless urgent relief is needed.

24.2 Governing law. The Agreement is governed by the laws of the State of Wyoming, without regard to its conflict-of-laws rules.

24.3 Courts. Any legal action arising out of or relating to the Agreement must be brought only in the state courts located in Sheridan County, Wyoming, or the United States District Court for the District of Wyoming, and each party submits to the exclusive jurisdiction of those courts.

24.4 No arbitration or waivers. The Agreement does not require arbitration, and contains no class-action waiver and no jury waiver.

24.5 Urgent relief. Either party may seek an injunction or other urgent relief to protect confidential information, intellectual property, credentials, platform access, data or other urgent interests, where the law permits.

25. Changes

In plain English. We can improve and change the service. We can change this Agreement with 30 days' email notice. A change never raises your price without your agreement, and if it takes away important rights you can cancel without finishing the term.

25.1 The service. Sites may improve, change, replace or retire tools, workflows, providers, platforms and support channels. A change does not materially reduce the plan Customer bought unless Sites gives notice and substitute functionality or another fair adjustment.

25.2 The Agreement. Sites may update the Agreement by emailing Customer at least 30 days before the update takes effect. The update applies to Customer from the start of Customer's first billing period that begins after the 30 days (or, for a website not yet live, from the end of the 30 days), and Customer's continued use of the service after that is acceptance. An update never increases Customer's fees or held price without Customer's agreement (Section 11.5). If an update materially reduces Customer's rights, Customer may, by notice before it takes effect, cancel with effect from the end of the then-current paid month, without the commitment for the rest of the selected term. An update does not change rights or amounts that arose before it. Revisions to the Updates list follow Section 4.9.

25.3 Preview features. Features Sites labels as preview, early access or beta are provided as they are, may change or end at any time, and are outside any commitment in the Agreement.

25.4 Platform changes. Sites may recommend or require a change of platform where needed for security, reliability, supportability or a provider's discontinuation, subject to Sections 14.7 and 25.1.

26. General

In plain English. The usual contract housekeeping.

26.1 Assignment. Customer may not assign the Agreement without Sites' written consent, except to a successor of its whole business that takes over the Agreement and that Sites reasonably approves. Sites may assign the Agreement without Customer's consent to an affiliate, a successor, or a separate company formed to operate the Sites business, with reasonable continuity of service, and will notify Customer under Section 23. The Agreement binds permitted successors.

26.2 Force majeure. Neither party is responsible for delay or failure caused by events beyond its reasonable control, including natural disasters, internet or platform outages, cyber incidents, labour disruptions, government action, payment-processor disruptions, war or civil unrest. The affected party must use reasonable efforts to limit the effect and resume performance. Force majeure does not excuse payment for services already provided or due.

26.3 Relationship. Sites is an independent contractor. Nothing creates a partnership, joint venture, franchise, employment, fiduciary or agency relationship. Neither party may bind the other.

26.4 Subcontractors. Sites may use employees, contractors and service providers. Sites remains responsible for their work under the Agreement and requires them to protect confidentiality and Customer's data.

26.5 Entire agreement. The Agreement is the whole agreement about the service and replaces earlier discussions, proposals and marketing statements on the same subject.

26.6 Severability, waiver, interpretation. If a provision is unenforceable, the rest remains in effect and the provision is modified to the minimum extent needed. Not enforcing a provision is not a waiver. The Agreement is not interpreted against a party just because that party drafted it. Headings and summary boxes are for convenience only.

26.7 Survival. Provisions on payment, confidentiality, ownership and licences, Handover, disclaimers, liability limits, indemnity, governing law and disputes, and rights that have already arisen continue after the Agreement ends.

26.8 Promises Sites makes. Where the Agreement says Sites will give notice, allow a chance to cure, ask for Customer's consent before a charge, restore the service, provide the Content Copy or the Handover, provide a copy of Customer's recorded order, or tell Customer where it stands on Paid Months, those are commitments to Customer.