What Sonder reads, keeps, and never does.

• The sites you point it at. When you ask for a redesign or a pitch, Sonder opens that site's public pages in a browser on its server (or a hosted browser service) and reads them as a visitor would: the words, pictures, colours, type and layout. It never signs in to a site to read it.
• Your references. Sites you admire, images you upload, and a Figma file or a Pinterest board. Figma and Pinterest are read only through a connection you make to your own account, with read-only access, and never by scraping.
• What your agent sends it. In Claude, ChatGPT, Cursor or another agent, your agent does the thinking and sends Sonder the pages, words and files it needs to fill, check, review or publish a site.

Through your agent, Sonder's server makes no AI calls of its own. Two things do use an AI service on Sonder's account: pictures you ask Sonder to make with your image credits (the description of the picture is sent to an image service), and the invite-only web app, which writes and builds on Sonder's own AI account.

Your projects

Each project's pages, pictures, review comments, pitch views and form enquiries are kept in Sonder's data folder on its server, and copied to Cloudflare R2 object storage as they change, so nothing is lost when the server restarts or is updated.

Your account

Your email, your name and studio, and your plan, in Sonder's account database (Supabase). Payments go through Stripe's own checkout: Sonder never sees your card.

Your connections

The keys for your Figma and Pinterest connections stay on Sonder's server and never reach your browser. Sonder keeps only a fingerprint (a hash) of your API key, never the key itself.

Your sign-in

A cookie on Sonder's own address that scripts can't read, for 30 days.

This website

No advertising cookies and no outside trackers. If you arrive from an AI answer engine, one cookie notes which one and the day, for 90 days, with nothing personal in it. The pages load their fonts from Google Fonts.

• Projects and pitches stay until you ask for them to be deleted. Nothing expires on its own.
• A published site stays online until it is taken down. Its address is then held for you for 30 days, so an old link never shows someone else's site.
• Connections last until you disconnect them. An agent connected to Sonder can be disconnected from your account page at any time.
• Deleted files leave the R2 copy within seconds of leaving the server.

• You. Each project belongs to one account, and only that account can open it in Sonder.
• Anyone you send a link to. Preview and review links carry a long random key; whoever has the link can open that one site, and nothing else of yours. A published site is public at its address.
• Your prospects, a little, in return. When someone opens a pitch, Sonder notes for you when they opened it, how long they stayed, how far they scrolled and what they clicked. No cookies and no stored IP address. A client's live site is only counted, never tracked: see counting a live site.
• Sonder's team runs the server and the storage, so it can reach what is stored there.

Every site Sonder makes runs on its own separate address, sealed off from the app and from every other site, so a site's code can never reach your account.

• It never posts or sends on your behalf. A site goes online only when you, or your agent at your word, publish it. A pitch email is a draft: your agent puts it in your own mail and you send it.
• It never emails your prospects or clients. The only emails Sonder sends are a published site's form enquiries, to the address you choose, and the comments left on a review link, to you.
• It never reaches Figma or Pinterest on its own. Only through the connection you made to your own account, read-only, and never once you have disconnected it.
• It never tracks your clients' visitors. No cookies of Sonder's on a client's site, and nothing kept that could tell one visitor from another: a live site only gets daily totals (below).

So a studio can show its client how the new site is doing, a site published with Sonder counts a few things, as totals for each day. A small script is added as each page is served; it sets no cookie and uses no storage.

What is kept

For each day: how many times each page was viewed; how many times each main button, booking link, shop link, email link or phone link was clicked, with the button's own words (the site's, not the visitor's); and, from the site's own forms, how many enquiries and newsletter sign-ups arrived.

What is never kept

No cookie, no IP address, no browser or device, no screen size, no address the visitor came from, no time of day, and no id for a visitor or a visit, so two views can't be linked to one person. The IP address is only held in memory, scrambled with a key that changes whenever the server restarts, to stop one machine flooding the counts.

Who isn't counted

Anyone whose browser sends Do Not Track or Global Privacy Control: the script doesn't run, and the server throws away anything that arrives with either. Link previews, search crawlers and automated browsers aren't counted either.

Where, for how long, who sees it

With the project, in the same place and copied the same way as its other files; up to 400 days of totals. The studio sees them in its agent and on its account page, and its client sees the first 30 days in the launch report. Each site's privacy page says the same in plain words.

The launch report itself is a private page at a long random address, marked so search engines leave it out; it is made by visiting the live site from Sonder's server, and that visit isn't counted.

When your agent uses Sonder, Sonder notes what happened, not what was in it: that an edit was undone, that a site was made again, that a step failed, that a project was started and not yet published, and how long the first result took. Each note carries your account's id, your plan, the tool and the time; a project is a short scrambled code, never its name or address. Sometimes a reply ends with an optional “what did you expect?”, at most once a day for a project and never on your first one: if you answer, your agent sends those words. Your clients can give a thumbs up or down, with a note if they like, on the review page. Your clients' content, their pages, words and pictures, is never part of any of it.

This is only for Sonder's connector on its server; run on your own machine, Sonder notes nothing. Only the people who run Sonder see these notes, on a private page. They are kept for 90 days, then deleted. Anything you've written in reply can be deleted sooner: ask us, as below.

Email us from the address you sign in with and say which project, or that it's the whole account. We delete the project's files from the server, which removes them from the R2 copy too; for an account, also your sign-in and profile, and we cancel your plan. We reply when it's done.

There is no delete button yet: for now it's by email. To take a published site down, ask us the same way (people invited to the web app can take one down there at once). An agent can be disconnected from your account page whenever you like.