What this site collects
Short version: your catalogue stays in your browser. We count a handful of anonymous events so we can tell whether this tool is worth building further.
Never collected
- Your product data — names, SKUs, prices, descriptions, categories, photos.
- Your business name, subtitle or logo.
- Any CSV or spreadsheet you import. It is read in your browser's memory and never transmitted.
- Email addresses. There is no signup form on this site.
- Cookies, advertising trackers, session recording or fingerprinting of any kind.
Collected
Anonymous counts of seven things, with no identifier attached to them:
page-view— a page was opened.tool-started— someone typed or imported something.catalogue-generated— a catalogue was produced.pdf-downloaded— the PDF/print step was reached.offer-49-shown— the pricing research question was displayed. Recorded at most once per browser.price-49-yes— the visitor answered that they would want the hosted product at the price shown.price-49-toohigh— the visitor answered that they would want it, but not at the price shown.
These exist so we can tell whether the tool is useful to anyone. They cannot be linked back to a person, a company or a catalogue.
How those counts are recorded
There are two separate mechanisms, and it is worth being precise about both.
1. The validation ledger
When one of those things happens, your browser sends a very small message to our own address on this site (/api/e). It contains the name of the event and nothing else. That message is stored in our database, and each stored row holds exactly four values:
- the event name, for example
offer-49-shown - which version of the pricing question was shown
- whether the row came from our own testing
- the time the server received it
Our application code deliberately does not read or store your name, your email, your catalogue or product data, your business details, your IP address, your browser's user agent, or any fingerprint or identifier. There is no column in that table for any of them.
To be accurate rather than reassuring: Cloudflare operates the network that delivers this site, and any web server necessarily handles the technical details of a request in order to answer it. What we are telling you is what our code does — it does not read those details, and it does not put them in our database. We also cannot tell two visits apart, because we store nothing that would let us.
2. Aggregate traffic analytics
Separately, we use Cloudflare's privacy-first, cookieless Web Analytics for ordinary traffic figures — how many people opened a page, and which site they arrived from. It sets no cookies and does not track you between sites. Some events also load a tiny marker page such as /e/catalogue-generated/ in a hidden frame so that it appears in those aggregate figures.
Neither mechanism ever receives your product data.
Stored in your browser
Your working draft is kept in your browser's local storage so that reloading the page does not lose it. It stays on your device, is not synced anywhere, and you can clear it with the "Clear all" button or by clearing site data.
Checking this yourself
Open your browser's developer tools, go to the Network tab, and use the generator normally — including importing a CSV and adding photos. You will see small event messages to /api/e containing only an event name, and you will see no request carrying your products, prices or photos.