SiteViewer for Squarespace: privacy

The browser extension, in plain words. Last updated 1 October 2026.

What the extension does

It shows the comment pins your clients left in SiteViewer on the matching page inside the Squarespace editor, and lets you reply, react, attach a file, resolve, move a pin or leave a comment there, with a panel listing every comment on the site. While the editor is open it keeps a connection to SiteViewer so a change made elsewhere shows at once. Everything it shows or sends is the same feedback you would see and send in SiteViewer itself.

What it keeps in your browser

Your connection to your SiteViewer account (made when you press Sign in in the extension, or Connect on that page), and your settings: whether pins are shown on a site, whether resolved comments are included, whether the Comments panel is open, where it sits, the filters you chose in it and when you last looked at it, whether private replies are offered, the hover outline and the new-comment note; while the editor moves to another page, which comment you picked in the panel there (read once when that page opens); for each site you open in the editor, its id, domain and name as the page shows them (so the editor's own panel knows which site it is), and a note of the sites you added from the editor. These stay in the extension's own storage in your browser and nowhere else. Every browser it is signed in on is listed under Account in SiteViewer, where you can sign any of them out.

What it sends to SiteViewer

The address of the site you have open in the editor, and the site's own id and domain as Squarespace shows them on the page, to find its SiteViewer project whichever address the editor uses. When you press Add this site, those details and the site's name, and the site's password if it has one and you enter it, so SiteViewer can show the site in its review. Then only what you do: the replies, comments, reactions, files and pin positions you choose to send, under your own name. Every request also carries the extension's version number, and Chrome adds which copy of the extension sent it (the store's, or one loaded by hand); SiteViewer keeps both with the connection and counts them across everyone to see which versions are in use. It sends nothing to anyone but SiteViewer.

What it does not do

It does not read, collect or send anything from sites other than the one you are editing, and nothing from that site beyond what is needed to place a pin. It does not track you, it carries no analytics or advertising, and nothing is sold or shared with third parties.

Who can see what you send

The same people as in SiteViewer: your client sees a reply unless you mark it private for your team, and your workspace's team sees everything. SiteViewer's own privacy policy covers what happens to feedback once it reaches SiteViewer.

Ending the connection

Press Sign out in the extension. That removes the connection from your browser and tells SiteViewer to stop accepting it, so it stops working everywhere. Removing the extension from Chrome does the same for your browser. A connection that is never disconnected expires by itself after 180 days.

Questions

Email support@siteviewer.app.

SiteViewer's privacy policy covers the service itself.