LEGAL / PRIVACY
Privacy
This preview site minimises data collection. Most state stays on your device until you choose to download a demonstration compile or contact the publisher.
Local storage
Cart contents, workflow chains, destination picks, order history, and Weft lease previews are stored in your browser's local storage. Clearing site data removes them. We do not sync this state to a user account on the preview origin.
Downloads and compiles
When you process a demonstration order, compile artefacts are generated for download. Package ids and destination hosts selected in the cart are used for that compile. No payment or billing data is collected because payments are not enabled.
Sign in
Sign-in confirms an email with a magic link or a one-time code. The account then holds your name, package notes, and compile receipts. A passkey can be added after that confirmation. The library stays closed until you register. This preview does not charge a card. In production, mail is sent only when Resend is configured.
Journey record
A header snippet, the same shape as a tag-manager entry, starts a first-party data layer on each page. Nothing is sent until you allow it. The record is an anonymous device id, the page, and catalogue actions such as search, cart, and download. A SensAffect reading of the visit (valence, arousal, direction) can ride with those actions. It is not a diagnosis, it is not tied to your email, and it is not stored as memory. Decline discards the queue. The local file of events is gitignored. On a production host without a database, events go to the service log. The operator page leads with one figure: visitors who allowed the record over everyone who chose. A decline is counted without a device id. It does not show one person’s event list, and it does not list device identifiers. It is not linked from the catalogue. Until production it opens without a token. In production it stays closed without the operator token.
Publisher contact
If you email the publisher contact on this site, standard email handling applies to that message. This notice does not describe third-party mail provider policies.
Hosting logs
Your hosting provider may collect request logs (IP address, user agent, timestamps) independent of SUPPLY application code. Consult your deployment operator for retention and access controls.