The first edition is taking shape

Privacy / pre-launch notice

Only the details the workflow needs.

Customer accounts are not part of this version. The production privacy notice, retention periods and contact channel are still being finalized and must be published before personal-data forms go live.

Document status

Pre-launch notice

Operational details can change before launch. The terms shown during a live order are the terms that apply to that order.

Data the live workflow may collect

An enabled order flow may collect a name, phone number, optional email, delivery address, product choices, public order ID and payment-submission references. Custom-merch and contact forms may collect the details and optional files a visitor chooses to send.

Why it is used

The intended purposes are to create and fulfil orders, verify submitted payments, provide order tracking and support, review custom-merch inquiries, prevent misuse and maintain the operational record connected to a public order ID.

Public tracking

Tracking requires an order ID plus phone verification or a secure token saved in the same browser. The public result is designed to omit the full delivery address, transaction ID and internal notes.

Service providers and transfers

The production system may process data through configured hosting, database, file-storage, courier, messaging and payment-verification services. The final notice must describe the relevant categories and any cross-border processing before those integrations are enabled.

Retention, choices and contact

Exact retention periods and the verified privacy-contact route are not published yet. The final notice will explain how to request access, correction or deletion where applicable, and what records may need to be retained for legitimate operational or legal reasons.