Privacy
Last updated 11 November 2026
What wesaw collects, about whom, why, who else receives it, and for how long. wesaw is server-side conversion tracking for online shops and SaaS products that advertise. This page covers five kinds of people: a merchant with a wesaw account, a shopper or visitor on a site that uses wesaw, someone who joins the waiting list, someone who runs the Signal Scan, and a visitor of this site. Every section describes what the product does today, and nothing it might do later.
Who we are, and our two roles
wesaw is operated by AVEC TROIS E SAS, 47 quai Carnot, 92210 Saint-Cloud, France, SIREN 914 595 657, RCS Nanterre. For your wesaw account, your billing, the waiting list, the Signal Scan and this site, we decide why and how data is processed, which makes us the controller. For the shoppers and visitors of a merchant's site or shop, the merchant is the controller and wesaw processes their data on the merchant's behalf and only on the merchant's instructions, under the data processing agreement linked in the footer. Every question about this page goes to hello@getwesaw.com.
What a merchant's site or shop sends us
Three sources, depending on what the merchant connects. From a Shopify shop: each order, received from a webhook Shopify signs, and the shop's page, cart and checkout events through the wesaw web pixel and theme extension. From a SaaS product: payment and subscription events received from a Stripe webhook the merchant creates. From any website: the events our script collects on the pages where the merchant loads it, such as page views, add to cart and the start of a checkout. Together these carry the order or subscription number, its amount and currency, the products bought, the page addresses visited and the referring page, the campaign parameters (utm) and advertising click identifiers in the link the visitor arrived on, the visitor's IP address and browser user agent, an approximate location (region, city, postal code and country) derived from that IP address, and identifiers our own script creates in the browser. When they are available they also carry identity fields: email address, phone number, first and last name, city, region, postal code and country. Those come from the order or payment itself, from the signed-in user the merchant's site hands to our script, from the sign-in session the site keeps when it is built on Supabase, or from the site's own forms, as described in the next section.
Contact details typed into a site's forms
On the sites where the merchant loads our script, an email address, phone number, first name or last name that a visitor types into a field that declares itself as such (by its type, its autocomplete attribute or a recognisable name) is read when the field changes or the form is sent. A password, a hidden field or a free-text field is never read. The value is kept in that site's own browser storage, attached to the visitor's later events on that site, and hashed on our servers as described below. A detail typed into a form that is never sent is kept as well. An explicit refusal in the site's consent banner stops this and erases what was kept.
How identity fields are handled
Email addresses, phone numbers, names, city, region, postal code and country are normalised and hashed with SHA-256 on our servers, never in the browser. Only the hashes are stored, and only the hashes are sent to an advertising platform. Before an event is stored it waits in a buffer pinned to the European Union, usually for about a second and longer only while the warehouse is unreachable; the identity fields are still in clear there, and leave the buffer once the event is written. The IP address, the user agent and the approximate location derived from the IP address (region, city and postal code) are stored in clear, because that is what lets a merchant see where activity on their shop comes from and lets an advertising platform recognise a conversion. The country derived from the IP address is used as the buyer's country when the event carries none, and is then hashed like the other identity fields.
Cookies and browser storage
wesaw sets no third-party cookie. On the merchant's site, our script keeps in that site's browser storage a first-party visitor identifier, the campaign parameters and click identifiers of the visit, and the contact details described above; they stay until the visitor clears the site's data or refuses consent. It sets or reuses Meta's own first-party cookies, _fbp and _fbc, for ninety days, so that the merchant's browser pixel and our server send Meta one identifier for one browser. It reads Klaviyo's first-party cookie __kla_id when the site uses Klaviyo, and from it only Klaviyo's own visitor identifier, never the email address it may contain, and writes nothing to it. On a Shopify shop the same identifiers also travel in the cart's attributes and in hidden line item properties, so that the order can be tied to the visit. Our script reads the site's consent state from Shopify's customer privacy settings, from Google Consent Mode and from the consent tool the site uses. This site, getwesaw.com, sets no advertising cookie, and one measurement cookie while it compares two versions of its home page: ws_ab, which keeps a visitor on the same version for thirty days and holds only a random identifier, the version and the name of the test, linked to no email address, IP address or device; it records, once per visitor, that the page was shown and whether a link to sign-up was clicked. the wesaw application sets only the cookies it needs to run: the session, the store being viewed, the language and the chosen period.
Recognising the same person across visits and browsers
To credit a sale to the ad that brought it, wesaw links events that belong to the same person. Deterministic links come first: the same advertising click identifier, the same first-party visitor identifier, or the same hashed email address. Two inferred links come after them. Device recognition: only for a visitor who has accepted the site's consent banner, our script sends the device characteristics the browser already exposes to every page (user agent, platform, screen size, colour depth, pixel ratio, time zone, languages, processor count, memory and touch points), never a canvas, WebGL, audio or font reading; they are hashed on our servers with the shop's identifier, stored in our application database, expire thirty days after the device was last seen, and are deleted the moment the visitor refuses. Connection matching: for any visitor who has not refused, including one who has not answered, a sale can be attributed to an ad visit made from the same IP address with the same operating system version within the previous twenty-four hours. Both inferred links can be wrong, for instance when two people share a connection and the same phone model, and every sale they attribute is labelled with how it was attributed. An inferred link is never sent to an advertising platform as a click. When an event sent to a platform lacks a matching parameter, it can be completed from other events of the same person, deterministic links first, then inferred ones, without ever overwriting a value the event carries, and the origin of each completed field is recorded.
Consent
Whether and how to ask a visitor for consent is the merchant's decision and their banner's job; wesaw records the answer on every event and applies it. After an explicit refusal, nothing about the event is sent to any platform, the contact details kept in the browser are erased, and neither device recognition nor connection matching applies; a record that nothing was sent is kept. After an acceptance, everything this page describes applies. When there is no answer, because the site has no banner or the visitor has not answered yet, events are collected, sent to Meta and can be matched by connection, but device recognition does not run and nothing is sent to Klaviyo.
Why we use it
Shoppers' and visitors' data is used for the merchant's purposes and no other: sending their conversions to the advertising and marketing platforms they connected, so those platforms can measure and optimise their campaigns; showing the merchant their sales, the revenue and return on ad spend of each campaign, ad set and ad, and a record of every conversion with what was sent and what the platform answered; and detecting collection or delivery errors. It is never used for wesaw's own advertising, never sold and never rented. Merchants' and our own visitors' data is used to run the account and the product, to bill a subscription, to send the emails described below, to keep the service secure and to prevent abuse, and to meet our legal obligations.
Legal bases
For shoppers' and visitors' data, the merchant, as controller, chooses the legal basis, typically consent collected by their banner or their legitimate interest, and wesaw processes on their instructions. For our own processing: performing the contract for your account, your shops and your subscription; our legitimate interest for security, rate limiting, the access log and the reliability of the service; your consent for waiting list emails, confirmed by a click before anything is sent; and our legal obligations for invoices and accounting records.
Who receives it
The platforms a merchant connects, and only those. Meta receives conversion events with the hashed identity fields, the IP address, the user agent, Meta's browser identifiers and the event's details. Klaviyo receives events identified only by Klaviyo's own visitor identifier and ours, with no email address, phone number, name or IP address. Each connection is listed, and can be removed, in the merchant's Integrations screen. Our service providers process data for us under their own written terms: Cloudflare (collection at the edge, the buffer that holds events before storage, hosting of this site, email routing), Railway in Amsterdam (the event warehouse and the application database), Resend (the emails we send), Stripe (subscription billing; card details go to Stripe and never reach us), Google (only if you choose to sign in with Google) and Shopify (when the app is installed on a shop). We may also disclose data when the law requires it, or to a buyer of the business, who would remain bound by this page.
Where it is processed
Stored in the European Union: the buffer is pinned to an EU jurisdiction in code, and the warehouse and the application database are in Amsterdam. Cloudflare runs the collection code at the point of presence nearest the visitor, which is not necessarily in the EU. Cloudflare, Resend, Stripe, Google, Meta and Klaviyo are, or belong to, companies based in the United States. Where data reaches them outside the European Economic Area, the transfer relies on the safeguards their own terms provide, such as the European Commission's standard contractual clauses or the EU-US Data Privacy Framework where the provider is certified under it.
Your wesaw account and billing
If you create an account, we store your email address and your name, your password as a hash or, if you sign in with Google, the identifiers and tokens Google returns. Each signed-in session records the IP address and browser user agent it was opened from. We also store the teams and shops you belong to, your preferences, and which version of the terms you accepted. Every time an account reads a shopper's personal data in the dashboard, an access log records which account read what, when, and from which IP address. If you subscribe, Stripe processes the payment; we keep the Stripe customer and subscription identifiers, the plan, its status and the invoices. The Shopify app is free to install and charges nothing through Shopify. If you connect a Meta account, 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, ad set's and ad's name, spend, impressions, clicks and the purchases Meta attributes to it, to show them next to the sales we recorded. Only when an owner or administrator of your wesaw workspace asks for it, wesaw adds URL parameters that carry the campaign, ad set and ad ids to your ads, so each sale can be tied to the ad that brought it: it creates a new creative on the same post with these parameters and points the ad at it, keeps the previous creative, and records each change; an optional setting, off by default, does the same for new ads that have no parameters. Apart from that, we never create, edit or pause anything in your Meta account, and we read no audiences. If you connect Klaviyo, we store its private key, encrypted at rest, and the account id.
The waiting list
If you join it, we store your email address and, optionally, the site URL, monthly ad spend range and platform you chose, with the language you were reading in, the country your request came from, the host name of the page the form was sent 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. It is held in a Cloudflare D1 database created with a Western Europe location hint, which is a preference and not a guarantee of where the data sits. Resend receives only your email address, to send one confirmation email, which you must click before anything else happens, then build notes and the access invitation. Every email carries an unsubscribe link; unsubscribing stops them and marks your entry as unsubscribed.
The Signal Scan
When you run the Signal Scan, we fetch the public page you name and report which advertising tags it carries. Your IP address is used, as it arrives, to limit how many scans one address can run per minute; that counter expires after two minutes. The scan result for a page is cached for fifteen minutes. Nothing else about you is kept.
This site
getwesaw.com 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.
How long it is kept
A shop's events, the delivery log and the browser emission records: fourteen months after the event, then the database deletes them itself. Device recognition: thirty days after the device was last seen, and immediately on a refusal. What our script keeps in a visitor's browser: until the visitor clears the site's data or refuses consent. A shop's data is erased ahead of these windows when Shopify sends its shop redaction request after an uninstall, or when the merchant asks. A Meta or Klaviyo connection: until it is removed or deletion is requested. Your account: until you ask us to delete it; two records outlive it on purpose because they prove what happened, the version of the terms accepted and the access log. Invoices and accounting records: as long as French law requires, currently ten years. The waiting list: until you ask for deletion. What was already delivered to an advertising platform is held in the merchant's account there and is deleted there.
How it is protected
Traffic is encrypted in transit, and the warehouse, the database and their backups are encrypted at rest. Platform tokens, keys and webhook secrets are encrypted with AES-GCM under a key held only by the application server. Webhooks are rejected unless their signature verifies. Accounts that reach the data use two-factor authentication, and every read of a shopper's data through the dashboard is logged. No system is perfectly secure; the data processing agreement lists the measures we have, and the ones we do not have yet.
Your rights
You can ask to access your data, to correct it, to delete it, to restrict or object to its processing, to receive it in a portable format, and to withdraw a consent you gave, without affecting what was done before. Write to hello@getwesaw.com; we answer within one month. If you are a shopper or a visitor of a merchant's site, the merchant is your first contact because they decide how your data is used, but you can also write to us and we will act or pass your request on. On Shopify, a deletion request a shop receives reaches us automatically and erases that person's events. You can also stop our script from recognising you by refusing in the site's consent banner or clearing the site's data in your browser. You have the right to lodge a complaint with a supervisory authority, in France the CNIL, or the authority where you live.
Residents of the United States
We do not sell personal information and do not use it for our own advertising. For shoppers' and visitors' data we act as a service provider to the merchant, who decides which advertising platforms receive it; requests about that data can be sent to the merchant or to us. Requests about your own wesaw account go to hello@getwesaw.com.
Children
wesaw and this site are meant for businesses and are not directed at children under sixteen. We do not knowingly collect a child's data for our own purposes. A merchant whose site is used by children is responsible for collecting the consent their law requires.
Do Not Track
Our script does not read the Do Not Track signal some browsers send. A refusal given in the site's consent banner is applied as described above.
Changes to this page
This page carries its date. A change that affects what is collected, who receives it or where it is processed is announced to merchants by email before it takes effect. A change that only clarifies wording is published with a new date.
Contact
The controller is AVEC TROIS E SAS, 47 quai Carnot, 92210 Saint-Cloud, France, SIREN 914 595 657, RCS Nanterre. Write to hello@getwesaw.com for any question about this page or to exercise your rights.