What this form collects
Last updated 8 September 2026
This page has one form, and it does one thing: it puts you on a waiting list. Here is exactly what is stored when you use it, then three sections on the wesaw product itself: what a connected shop sends us, how long it is kept, and what connecting a Meta account records.
What we store
Your email address. Optionally, the site URL, monthly ad spend range and platform you chose. The language you were reading in, the country your request came from, and any campaign parameters in the link you arrived on. Your IP address is not stored: only a salted SHA-256 hash of it, used to rate-limit abuse of the form.
Where it is stored
In a Cloudflare D1 database created with a Western Europe location hint. A location hint is a preference, not a guarantee of where the data physically sits, and we would rather say that plainly than imply otherwise.
Who else sees it
Resend, to send you the confirmation email and later announcements. Your email address is the only thing sent to them. No ad spend, no country, no IP hash, no campaign parameters.
What we send you
One confirmation email, which you must click before anything else happens. After that, build notes and the access invitation. Every email carries an unsubscribe link, and unsubscribing removes you from the list.
Getting your data out or deleted
Write to hello@getwesaw.com and we will send you what we hold or delete it. There is no form to fill in.
Analytics
This site runs no analytics and no advertising pixel. Its fonts are served from this domain, not from a font CDN. The only script it may load from elsewhere is Cloudflare Turnstile, the anti-spam check on the form, and only when that check is switched on.
What a connected shop sends us
When a merchant installs the wesaw app, every order produces one conversion event. It carries the buyer's email address, phone number, first and last name, city, region, postal code and country, read from the order itself. Those eight fields are normalised and hashed with SHA-256 on our servers before anything leaves them: only the hashes are stored, and only the hashes are sent. The event also carries the order number, its amount and currency, the products bought, the buyer's IP address and browser user agent, and the first-party identifiers our own script minted in the browser. Their single purpose is to let the advertising platform the merchant connected recognise a conversion it would otherwise miss. Nothing is sold, and nothing reaches anyone the merchant has not connected themselves.
How long a shop's data is kept
Fourteen months after the event happened, then it is deleted by the database itself rather than by anyone remembering to. That covers a full year of history plus the margin a merchant needs to compare a month against the same month a year earlier, and we keep nothing past it because nothing past it serves a purpose we can name. The delivery log and the browser emission records expire on the same window. Erasure on request is separate and faster: it is described on the data deletion page, and Shopify's own shop redaction request, which follows an uninstall, erases a shop's events without waiting for the fourteen months.
Connecting a Meta account
If you connect a Meta account to wesaw, we store the id and name of the dataset you chose, the ids of the pixels you granted, and an access token, encrypted at rest and never displayed again. If you also grant an ad account, wesaw reads, without storing them, each campaign's name, spend, impressions, clicks and the purchases Meta attributes to it, to show them on the Ads screen next to the sales we witnessed. We never create, edit or pause anything in your account, and we read no audiences. How to have all of it deleted, and how to revoke access on Meta's side without asking us, is on the data deletion page linked in the footer.