Skip to main content
Platform security guideReviewed

Squarespace security: contributors, code injection and where form data goes

Squarespace runs the hosting and the editor.

Who can sign in, what code your pages load and where visitors' details are sent are set inside your own account. This guide reports what Squarespace's own help guides, security page and terms say about them, and comes with a map to fill in: read-only parts on contributors, code and form storage, then an offboarding and code removal checklist that changes the site.

Squarespace contributor, code and data map

Paste this into a document or spreadsheet and keep one map for each Squarespace site. Part A inventories contributors, each person's account settings, the activity history, code injection and code blocks; Part B maps each form to its storage and covers contacts, mailing lists, connected accounts, extensions, API keys, commerce and domain access; Part C lists findings.

How to use it

Parts A to C only read. Part D is the offboarding and third-party code removal checklist, with its limits written in. Each panel location and permission it gives was taken from Squarespace's help guides on 14 November 2026.

squarespace.txt

Introduction13 lines

SQUARESPACE CONTRIBUTOR, CODE AND DATA MAP One copy per Squarespace site. Parts A, B and C only read: panels in your own Squarespace account, your published pages as a visitor receives them, and answers from the people involved. Part D is the only part that changes anything, and its limits are written at the top of it. HOW TO FILL IT IN 1. Write down that something exists, never its value. No password, backup code, app password, API key, bank detail or form submission goes into this map. Where code or a setting may hold a key, token or account ID, write "key present: yes, no or unsure" and whose service it belongs to. 2. Make no new exports for this review: no contact, submission, order or mailing list export. Where an export already exists, record who made it and where it is kept, if anyone knows. 3. Read published pages logged out, in a private window, as an ordinary visitor. Squarespace's code injection guide says to open the site URL in a private or incognito window to see it with custom code enabled, and its code blocks guide says code sometimes does not appear while you are logged in. No scanners, crawlers or repeated requests. 4. Each person reads only their own account: two-factor method, app passwords, sessions, AI assistant connectors. Nobody signs in as anyone else. Section 1.8 of Squarespace's Acceptable Use Policy says not to use any other person's username and password or manage the Services through shared credentials. 5. Where a line gives a panel or menu, the Squarespace help guide that gives it is named beside it. A line with no guide beside it names only what to look at, because none of the guides used here says where it sits. 6. Lines marked "Example" are invented, for an invented business. Replace them with your own. Site: __________ Domains: __________ Plan: __________ Filled in by: __________ Date: __________ Panels I could not open: __________

Squarespace security: the platform and your account

Squarespace website security covers the platform and what is set inside each account.

Squarespace's security page describes its fully managed cloud hosting. Inside a site, the owner and the contributors given the right permissions decide who can sign in, what code is added to the pages, where form submissions and customer details are sent, and which outside services are connected. This guide covers those decisions, and its map lets you record them for your own site.

Squarespace describes its own measures on its security page. It says all domains correctly added to a Squarespace site get free SSL certificates automatically, that it has implemented solutions designed to protect against and mitigate the effects of denial-of-service attacks, and that its security operations centre monitors for threats and vulnerabilities around the clock.

On payments, the page says sensitive card data is not handled by Squarespace and goes directly to the payment processor's servers. Those are Squarespace's statements about its own systems, and this guide does not assess them.

Squarespace's Terms of Service, in the version effective 27 March 2025, speak to the code and third-party services a customer adds. Section 3.7 says custom code added to a site will be considered the customer's User Content and that the customer is solely responsible for it. Section 4.1 gives extensions listed on Squarespace Extensions and eCommerce payment processors among its examples of third-party services, says information such a service collects, stores and processes from you or your sites is subject to that service's terms of service, privacy notice or similar terms, and not to Squarespace's Privacy Policy or Data Processing Addendum, and asks customers to evaluate and ensure they trust each service before connecting it.

It also says: "When using Third Party Services, your security is your responsibility." Section 1.2 asks customers to make sure others do not have access to their accounts or passwords.

Your own adviser is the person to ask what those clauses mean for you. For this guide they set the ground the map covers: the people with access, the code added to pages, and every service that receives data from the site.

Contributors and roles: who can change what

People who work on a Squarespace site are invited as contributors and given permissions.

Squarespace's contributor roles guide describes basic permissions that it says most subscriptions include: each subscription has one owner, usually the person who created the account, who can manage all content and settings and transfer ownership. Administrators can do almost everything the owner can except transfer ownership.

Billing contributors can change or cancel subscriptions and view invoices, and cannot add or edit content. The roles it lists for Squarespace websites are Analytics, Comment moderator, Email Campaign editor, Store manager, Viewer and Website editor.

The permission tables in that guide are where the security questions sit. Adding code injection is marked for the owner and administrators only, but adding code blocks is marked for website editors and store managers as well. Connecting third-party accounts, connecting Squarespace Extensions, connecting third-party storage to form blocks and managing permissions are marked for the owner and administrators.

Deleting the site is marked for billing contributors as well as the owner and administrators. Store managers are marked for viewing orders, cancelling and refunding them, and exporting contacts.

Squarespace's guide to editing contributor permissions adds that Squarespace does not support per-page editing permissions, and that administrators can edit the permissions of any other contributor, including other administrators, except the owner.

Two-factor authentication is switched on by each person, not by the owner. Squarespace's two-factor authentication guide says contributors can choose to enable two-factor authentication for their own accounts and that there is no way to enable it for them. Its security tips page says anyone who has a contributor account for your website should have two-factor authentication enabled, and that each person who needs access can have their own account as a contributor instead of sharing the same account.

Section 1.8 of the Acceptable Use Policy says not to provide your password to any other person or manage the Services through shared credentials.

The map therefore asks each person to confirm their own two-factor method, and treats a login that two people share as a finding.

Squarespace's account activity guide describes a 90-day history of logins, permission changes, website and domain events and account settings changes, plus a list of active sessions, which it says stay open for 30 days unless the person logs out or is logged out remotely.

It says the Domains, Websites and Permissions tabs show only for site owners, site administrators and domain managers, and show actions taken by all contributors, and that the history does not track contributor logins or specific site edits.

So the history can show when someone was added or removed, and the map does not rely on it to show who changed a page.

Squarespace code injection security: where added code runs

Squarespace's custom code guide says Squarespace does not support server-side code, including PHP, Ruby, Ruby on Rails and SQL.

It describes custom code options including code injection, code blocks and custom CSS, and covers embed blocks for content from services that use the oEmbed standard. The questions this guide asks of any added code are what it loads and who put it there.

Code injection has the widest reach. Squarespace's code injection guide says code in the Header field is injected into the head of every page, and code in the Footer field before the closing body tag of every page. Page Header Code Injection adds code to a single page's head, and Post Blog Item Code Injection adds code to every blog post, though the guide says page-specific code can appear differently depending on the site's version.

Code injected for the lock page displays above the password field of a password-protected site or page.

The guide says code injection is available on the Core, Plus and Advanced plans and some legacy billing plans, and that checkout pages do not support code.

The order confirmation and order status fields deserve their own line in any review. The guide says code entered there runs on those pages after checkout, and that tags add customer-specific details, among them the order number, the grand total and {customerEmailAddress}, the customer's email address as they enter it at checkout.

It also notes that customers can revisit the order status page, which might trigger tracking scripts more than once. The map records which of those tags each snippet there uses, and whether anyone still needs it.

Code blocks reach further down the permission list. Squarespace's custom code guide says code blocks support plain text, HTML, Markdown and CSS inside style tags on all plans, and that adding JavaScript or iframes to code blocks is available on the Core, Plus and Advanced plans and some legacy billing plans.

Its code blocks guide says the site needs to be on the Core, Plus or Advanced plan. The contributor roles guide marks adding code blocks for website editors and store managers, roles it does not mark for code injection. The map therefore lists code blocks separately from code injection, with who added each one.

Squarespace's code blocks guide also says code sometimes does not appear while you are logged in, even when visitors can view it, which is why the map reads each page in the editor and again logged out.

Squarespace's own pages add more. The code injection guide says third-party code added through code injection may add cookies in visitors' browsers, and describes using the cookie banner with code injection to adjust those integrations. Both the code injection guide and the custom code guide say added code falls outside what Squarespace support helps with.

How a third-party script is controlled once it is on a page is covered in the supply chain attacks guide; this one stays with where Squarespace lets code in and who can add it.

Where Squarespace form submissions and contacts end up

Squarespace calls the destination of a form's submissions its storage.

The form storage guide says each form needs at least one storage option and that, depending on the form, submissions can be added to the Contacts panel, added to mailing lists, downloaded to a .csv file, sent to an email address, sent to a Google Drive spreadsheet, sent to Mailchimp, or used to trigger actions in other apps through Zapier, the last two, that guide says, on the Core, Plus and Advanced plans and some legacy plans. One enquiry form can therefore leave copies in several systems, each with its own people and settings.

The email option is the one to check on any site that has changed hands. The form storage guide says email storage is available for form blocks, that the default email address is the account email of the site owner or contributor who added the form, that each form can only have one email address connected, and that changing your email address does not update the form's storage automatically.

Neither that guide nor the form blocks guide says the address changes when that person stops being a contributor. The map reads the Email Notifications address on every form block and records whose inbox it is.

How long Squarespace keeps a submission depends on how the form is built. The form blocks guide says a form with a required email address field keeps submissions until the contact or the submission is deleted; without one, the block keeps each submission for 30 days.

Submissions can be exported from the block to a .csv file, and the guide says uploaded files are not in the export but are reached through links in it.

The form storage guide says connecting a form to Google Drive means logging into a Google account and creates a new spreadsheet for the submissions. The map records whose Google account was used for each connection.

The Contacts panel is the other store. Its guide says the panel shows everyone who has given an email address or phone number during a transaction, marketing opt-in or form submission, and that contacts can be exported to a .csv file. The contributor roles guide marks exporting contacts for the owner, administrators and store managers.

The map records who can export and any exports already made, and makes no new one. Whether a form should ask for a detail at all belongs to the sensitive data exposure guide.

The form storage guide recommends sending a few test submissions after connecting storage. In this guide's map, test submissions appear only in the removal part, under its limits, because a submission to a form that feeds a mailing list or an automation reaches real systems and can reach real people.

Extensions, connected accounts, API keys and payment processors

Squarespace's Extensions guide describes extensions as third-party tools, built and managed by third-party services, that connect to a site and are the equivalent of plugins, add-ons or apps.

It says connecting one includes clicking Allow to grant the service the permissions it needs, and that extensions can be connected on all plans. It also says disconnecting an extension stops the data sync between the site and the service, that the service may still have the data sent while it was connected, and that an extension has to be disconnected through Squarespace to ensure success.

Social and similar accounts sit in the Connected Accounts panel. Squarespace's guide to connecting social profiles lists platforms including Facebook, Instagram, LinkedIn, Pinterest, Google Search Console and Tumblr, and connecting one means logging in to that account and authorising the connection. The guide says password updates or permission changes on connected platforms can cause account connections to fail. The map records whose account on each service each connection uses.

API keys let other software reach site data. Squarespace's API keys guide says a key permits authenticated access to the Squarespace account, is made in the Developer tools panel under Developer API Keys with permissions for Orders, Forms, Inventory or Transactions, each of which the guide ties to particular plans, and that a Forms key is what Squarespace's Zapier integration uses.

It says to treat a key like an account password, that Squarespace does not store it and it cannot be retrieved after the window closes, and that deleting a key breaks the connection while the app or service may still have data it was sent.

An AI assistant connection does not show in Squarespace at all. Squarespace's guide to connecting an AI assistant says the connection lives in the assistant, that nothing appears in the Squarespace account or on the site, and that it can only be disconnected in the assistant.

It says store tools, which it describes for Claude and ChatGPT, need Administrator or Store Manager permissions for the site and can, among other things, add or update contacts and update orders. The map asks each person with those permissions whether they have connected one.

For payments, Squarespace's API keys guide says orders on a site can be processed only through Squarespace Payments, Square for point of sale, Stripe or PayPal. Its Payments permissions guide says whoever creates the Squarespace Payments account is the Payments Manager by default, and its table marks connecting a bank account and updating the payout bank account for the Payments Manager only.

Squarespace's Stripe guide says disconnecting Stripe cancels active subscriptions, and that updating the Stripe account password could disconnect Stripe from Squarespace. The map treats a payment processor as a decision for the owner, never a clean-up step.

Domain access: managers, locks and the transfer code

A domain registered through Squarespace can have people of its own.

Squarespace's domain permissions guide says each domain manager needs their own Squarespace account and that there is no limit to how many can be added. Its table marks managing domain settings and DNS, adding or removing other domain managers and transferring a domain away for domain managers as well as the domain owner, while viewing payment details, deleting the domain and moving it to a website are marked for the domain owner alone.

The guide says collaborators with any domain permission level can start a transfer away from Squarespace, and that only the Owner contact, where the registrar is Squarespace Domains LLC, or the Admin contact, where it is Tucows, receives the email with the transfer authentication code.

When a domain is moved to a Squarespace website, the guide says its domain permissions are removed and it shares the website's contributor permissions.

Squarespace's domain locks guide covers the locks Squarespace applies to Squarespace-managed domains. It says all domains have an additional lock you can remove at any time, enabled by default for your security, separate from locks that may apply after a new registration, a transfer in or a change to registration data.

It recommends keeping the Domain lock toggle on unless you are transferring the domain away, and lists .au and .com.au among the domain endings that can be transferred at any time without a 60-day wait.

Squarespace's account activity guide says the Domains tab of the activity history tracks changes to DNS records and nameservers. A DNS record that still points at a service you have stopped using is a separate risk, covered in the subdomain takeover guide.

How to work through the map

The map works as a Squarespace security checklist you fill in for your own site.

Make one copy per site and work through it with the people who hold access, in order: people, then code, then where data goes, then findings. Part D comes last, and only after Part C has a decision against each finding.

  • Parts A to C open panels, read pages and ask questions. None of them saves a setting, exports data or submits a form.
  • Write down that a key, token, account ID or app password exists and whose it is. Never its value, and never a whole snippet pasted into the map.
  • Each person reads their own account: two-factor method, app passwords, active sessions and any AI assistant connector. Nobody signs in as anyone else.
  • Read published pages logged out in a private window, as an ordinary visitor would. No scanners, crawlers or repeated requests, for the reasons in the section on the Acceptable Use Policy below.
  • Where a Squarespace help guide gives a panel or menu, the map names it alongside the guide. The guides were read for this map on 14 November 2026, so check each location and permission on the day you fill it in.
  • Date the map, and redo it when someone leaves, an agency hands over, a new form or extension goes in, or the plan changes.

Offboarding people and removing third-party code

Someone leaving is a natural point to act on the map, and the order matters.

This guide's advice is to move what sits in a person's name before removing them: the Email Notifications address on their forms, API keys and extensions they set up, accounts connected with their logins, and domain manager access. Squarespace's guide to removing a contributor says that removing a Payments Manager brings up a warning to transfer the role so you do not lose access to the Squarespace Payments account.

The same guide says removing a contributor cannot be undone, though the same email address can be invited again, that the person is not notified, and that their login becomes a basic author named Guest User on the content they wrote. For a pause instead of a removal, it describes Remove Permissions, on a computer only.

Squarespace's security tips page suggests removing a contributor who is inactive or no longer needs access, so that if their account is compromised, the attacker cannot log into your site through it.

An agency handover adds ownership. Squarespace's guide to changing the site owner says only the current site owner can transfer ownership, that before the transfer the owner invites the new owner as a contributor and ensures they accept, and that the transfer also moves subscriptions, Squarespace domains and Acuity Scheduling subscriptions attached to the site.

It tells the new owner to update billing, to change a connected Squarespace domain's contact email address, and to remove the previous owner if they no longer need access or limit their permissions if they still need to contribute.

It describes a separate step for moving a Squarespace Payments account: making the new owner the Payments Manager.

Removing third-party code needs the same care, and Part D of the map writes its limits in. One change at a time, each checked before the next. A way back recorded first. A quiet period agreed with everyone who can edit, so nobody else's change is mixed into the result.

No test submission that reaches a real customer, a mailing list or anyone outside the business. No scanners and no load.

When the code is what stops the editor

Squarespace's code injection guide says custom code can sometimes prevent you from editing the site securely. It describes clicking Disable Scripts in Preview, or typing /safe after /config in the editing address, to switch scripts off in the editor's preview, and says this does not affect how the site looks to visitors.

If that does not work, it says to check the areas where custom code was added and remove it for a while as you troubleshoot.

Either can give a way to reach a snippet that breaks the editor and remove it, one change at a time, within the limits above.

What reading your own Squarespace account leaves out

The map records your people, your code and the routes your data takes.

Several things sit outside it:

  • Squarespace's own systems, such as its hosting and monitoring. What you can know of them is what Squarespace itself publishes, its security page first.
  • How an outside script behaves on later visits. For a script loaded from another host, the map records that host, and the file the host serves can change after the review.
  • What each destination does with the data: the inbox, the Google account, Mailchimp, Zapier, an extension's provider. Section 4.1 of Squarespace's Terms says information a third-party service collects is subject to that service's own terms and privacy notice.
  • Who edited which page. Squarespace's account activity guide says the history does not track contributor logins or specific site edits.
  • Connections that live elsewhere, such as an AI assistant connector or the workflows set up inside Zapier, unless the person who made them tells you.
  • Two-factor on other people's accounts, except as they report it.
  • Copies already made: exports, forwarded notification emails and spreadsheets shared on from Google Drive.
  • Changes after the review date. Any setting read for the map can be changed later.

Squarespace's Acceptable Use Policy, scanning and vulnerability reports

Anyone planning to run a testing tool against a Squarespace-hosted site should first read the Acceptable Use Policy in its form on that day.

The version last updated 24 February 2020 sets out examples of prohibited conduct. Among them: do not probe, scan or test the vulnerability of any system or network (section 1.1); do not breach or otherwise bypass any security or authentication measures (section 1.2); and do not take action that imposes an unreasonable load on Squarespace's infrastructure or its third-party providers, where Squarespace reserves the right to determine what is reasonable (section 1.7).

Squarespace's vulnerability reporting page encourages security professionals to practise responsible disclosure, and asks them to follow its guidelines and submission criteria before reporting. Its in-scope list includes server-side remote code execution, SQL injection, cross-site scripting, cross-site request forgery and access control issues. Its out-of-scope list includes all Squarespace customer websites or other customer content not owned by the researcher, network level and application level denial of service, and password brute-forcing.

The same list says that a request that takes too long to respond should be reported, and: "Do not DoS the system."

This guide names no Squarespace vulnerability, and its map runs no scanner against a site. Parts A to C read settings and make ordinary page visits, and Part D makes its changes through Squarespace's own editor and panels, apart from an AI assistant connector, which is disconnected in the assistant, with at most one test submission per affected form under the limits written there.

This guide's own position is to hold any more active check against a site Squarespace hosts until Squarespace has replied in writing, and to file that reply with the date it arrived.

Clever Ops and the applications beside a Squarespace site

This is an informational guide.

Clever Ops does not test Squarespace's platform, and nothing here describes a Squarespace-specific testing service. The Clever Ops methodology puts your host's platform outside the method, and keeps services run by other businesses out of scope unless their owner agrees.

Where a Squarespace site passes data to a web application you own that customers or staff sign in to, such as an internal order tool fed by Squarespace's APIs or a customer portal on another domain, active testing of that application sits within a scoped web application and API penetration test.

That test signs in as each role to check what it can see and change, and calls the application's own API directly as well as through its screens. Squarespace's APIs are a service run by another business, which the methodology keeps out of scope unless its owner agrees.

Before any request is sent, the methodology checks the hosting provider's testing policy for each target. When Clever Ops built or hosts that application itself, it is assessed as a security review and not as an independent test, and the report states that Clever Ops built or hosts it.

Round-the-clock monitoring and incident response are outside what Clever Ops offers. If a contributor account, an API key or an extension may be in someone else's hands now, the first calls are to Squarespace and to an incident response specialist.

Section 1.2 of Squarespace's Terms says customers must immediately notify Squarespace if they know or have any reason to suspect that their accounts or passwords have been stolen, misappropriated or otherwise compromised.

Frequently asked questions

Squarespace's security page describes its own measures, among them free SSL certificates for domains correctly added to a site, solutions designed to protect against denial-of-service attacks, round-the-clock monitoring by its security operations centre, and sensitive card data that it says goes directly to the payment processor's servers. This guide gives no verdict. Squarespace's Terms of Service speak to what a customer adds: section 3.7 says the customer is solely responsible for custom code added to a site, and section 4.1 says: "When using Third Party Services, your security is your responsibility."

Squarespace's contributor roles guide marks adding code injection for the owner and administrators only, and adding code blocks for website editors and store managers as well. Squarespace's custom code guide says code injection, and adding JavaScript or iframes to code blocks, are available on the Core, Plus and Advanced plans and some legacy billing plans. Its code blocks guide says JavaScript or an iframe in a code block needs the Core, Plus or Advanced plan. The map in this guide therefore records code blocks as well as code injection, with who added each one.

Squarespace's two-factor authentication guide says contributors can choose to enable it for their own accounts and that there is no way to enable it for them. Its security tips page says anyone with a contributor account for your website should have it enabled. This guide's advice: ask each person to switch it on and confirm their method.

Squarespace's form blocks guide says that by default a form block sends responses to the account email of the site owner or contributor who added the form and stores submitters and their details on the site. Squarespace's form storage guide says changing your email address does not update the form's storage automatically. The form blocks guide adds that a form with a required email field keeps submissions in the block until they or the contact are deleted, and that one without keeps each submission for 30 days.

The connection stops, but copies can remain. Squarespace's Extensions guide says disconnecting stops the data sync and the service may still have data you sent while it was connected, and that you must disconnect the extension through Squarespace to ensure success. Its API keys guide says deleting a key breaks the connection and the app or service may still have data it was sent. Ask each provider about the data it holds.

Read Squarespace's Acceptable Use Policy first. The version last updated 24 February 2020 lists, among examples of prohibited conduct, probing, scanning or testing the vulnerability of any system or network, and taking action that imposes an unreasonable load on Squarespace's infrastructure or its third-party providers. Squarespace's vulnerability reporting page lists all Squarespace customer websites or other customer content not owned by the researcher as out of scope for its reports.

Scope the right test for your application

Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.