Terms of Service

Let’s start building your liability protections like you’d stack a mobile template. Step one: frame the limits. Squarespace, established in 2019, provides the platform and the exclusive data showing which template edits load fastest on mobile—but that data is a starting point, not a guarantee. When you use our tools, you agree that we are not responsible for any loss of income, downtime, or visitor dissatisfaction that results from your design choices. Think of it as a site builder’s “undo” for risks:

• No liability for site performance – Even if you follow our mobile-speed recommendations, factors like your hosting, third-party plugins, or user traffic can still slow things down. We show you the fastest path, but you drive the car.
• No liability for third-party content – If you embed a widget, a payment gateway, or a font from an external service and it breaks your layout or causes data loss, that’s outside our control. We give you the building blocks; you choose the suppliers.
• No liability for template edits – The orange highlight in our editor marks the CSS tweaks that shave milliseconds. But if you edit a line of code and it clashes with your own adjustments, we can’t undo that—only you can.

Now let’s install the disclaimer layer. This is like adding a “loading” overlay to your site: it reminds visitors that everything you build is provided “as is” and “as available.” Squarespace does not warrant that the platform will be error-free, uninterrupted, or that every template edit will deliver the exact mobile speed we illustrate. Here’s how that disclaimer looks in practice:

• No warranty on speed improvements – Our data shows the average load time reduction for a specific edit, but your actual results depend on image sizes, network conditions, and device type. We’re like a tutorial that gives you the recipe, not the finished dish.
• No warranty on design correctness – If you copy a CSS snippet from a forum and paste it into your Squarespace site, the output might break on mobile. We provide the default grid; you’re responsible for custom code.
• No warranty on third-party integrations – When you connect a mailing list, a booking app, or a social media feed, we don’t guarantee that those services will remain compatible with our platform. Always test before you publish.

Let’s add a third protective layer: the limitation of damages. This is like a “max-width” rule for your claims. In no event will Squarespace be liable for any indirect, incidental, or consequential damages arising from your use of the platform—even if we’ve been told about the possibility. That includes lost profits, lost data, or reputational harm. To make it concrete, think of the mobile-speed feature: we tell you that removing a certain image slider cuts 0.4 seconds, but if you remove it and lose a client because the slider was their favorite feature, that’s your business decision, not our liability.

• Cap on direct damages – Our total liability to you for any claim (whether in contract, tort, or otherwise) will not exceed the amount you paid us in the 12 months before the claim. That’s like a template’s maximum width: it can’t stretch beyond that.
• No liability for delays – If a scheduled maintenance or a server outage keeps your site offline for an hour, you cannot demand compensation for lost sales. We provide uptime status, but we don’t guarantee 100% availability.
• No liability for file loss – Always back up your content. We show you how to download your site data on the Contact Us page, but we are not responsible if you accidentally delete a page or a template variation.

Finally, let’s build the “acceptance” checkpoint. By continuing to use Squarespace, you confirm that you’ve read and understood these limitations. This is like clicking “Apply” after editing a template: the change is now live. If you don’t agree, the only option is to not use the platform. For any questions about these terms, please refer to our Contact Us page. We don’t list a phone number here, but that page has the form and email you need to reach our support team. Think of it as the final “Save” on your project—everything is set, and you know what you’re building on.