Privacy and consent.

Here is what the Dragon Warrior First Edition list asks for, why it is needed, and how collector consent is handled.

Front portrait render of Dragon Warrior Ming Dynasty Gunner
Privacy for the collector journey around this character.

Data collected

The First Edition list collects email, optional name, phone if SMS alerts are selected, Instagram handle if Instagram DM alerts are selected, country, optional province or state, collector type, interest level, preferred edition, price range, preferred deposit method, optional preferred crypto network, optional payment preference note, source, preferred alert channel, drop intent, UTM data, marketing consent, channel consent, consent version, and timestamps. If paid deposit access opens, the reservation record also keeps the selected edition, deposit amount, payment provider, payment state, tax total when returned by the provider, accepted terms version, and timestamps. For an approved direct stablecoin transfer, it also keeps the quoted subtotal, tax amount, tax jurisdiction, exact transfer total, token/network, and settlement reference needed to reconcile the payment.

Entering a private drop code also creates an access-claim record: which code was used, timestamps, the referring page, UTM data, and a hashed network signature (IP address and browser identifier hashed with a server-side secret, used only for abuse review — never stored in plain form). Private-access actions such as joining the First Edition list are recorded as first-party interaction events linked to that claim. These records are kept for the duration of the launch and follow-up window, then deleted or anonymized.

Campaign parameters in a public launch URL are carried onto same-origin buyer links so the original channel remains attached if you read the story or process before joining. This uses only the visible UTM values in the URL; it does not create a visitor id, attribution cookie, browser profile, or cross-site tracking record.

If you request a private collector account link, we create a short-lived, single-use login challenge tied to your collector profile or waitlist email. The challenge keeps the email, customer profile id, hashed token, expiration time, use time if consumed, and hashed network/browser signals for rate limiting and abuse review.

Use of data

Data is used to measure demand, segment the presale, send production updates, plan edition details, estimate tax and shipping readiness by region, understand card/wallet/crypto demand by preferred network, open private collector-account access, and notify list members if private deposit access opens. It is not sold or shared as a marketing list.

Site analytics

Cloudflare Web Analytics measures page visits, referral sources, approximate country, browser and device type, and page-performance signals so we can understand which parts of the collector story are useful and keep the site fast. This measurement does not use cookies, create a cross-site profile, fingerprint visitors, or attach browsing activity to a First Edition list, collector account, drop-code, or payment reservation.

Email consent

Waitlist emails identify the sender, include an unsubscribe mechanism, and preserve consent records for commercial electronic messages.

The unsubscribe link contains a signed collector-record token rather than an email address. Confirming it stops email, SMS, and Instagram release updates immediately while retaining a suppression record so the address is not added back by mistake. A new, explicit waitlist registration can grant fresh consent later.

Deletion requests

For access, correction, or deletion requests, emailcollectors@kukosh.art. Collector updates should also include a reply path and unsubscribe option so consent stays clear.

Payment providers

Card, wallet, and supported stablecoin checkout is handled on hosted payment pages. The collector launch does not collect raw card details. Payment providers send confirmation after checkout so the deposit status can be updated.

Tax and address data

If paid access opens, hosted checkout may request billing and shipping address details so tax and shipping treatment can be shown before payment. Provider-returned tax totals, reservation identifiers, selected edition, payment state, and accepted terms version may be stored with the reservation record.