Data we handle
Account enrollment requires a shielded-capable address. Payment processing handles unique receivers, memos, amounts, transaction observations, and confirmation state. Creation handles raw prompts, normalized trait intent, moderation results, generated images, and model provenance.
How sensitive values are protected
- Addresses and prompt text are encrypted at rest and accessed only for their stated workflow.
- Public collection and marketplace APIs do not expose owner identity or address correlation.
- After enrollment, the interface uses a random private alias instead of displaying a full address.
- Operational and analytics events exclude raw prompt, address, memo, auth code, and account-linked transaction ID.
Analytics
We may measure anonymous page and funnel events, broad rejection categories, generation latency and cost, candidate ordinal, invoice-state conversion, and marketplace conversion. Images awaiting moderation and private order references are never sent to third-party analytics.
Retention and deletion
Final production policy must publish exact retention windows for authentication challenges, raw prompts, payment evidence, security logs, and legal records. Immutable token artifacts and signed registry events cannot be treated like ordinary editable profile data.
Important Zcash note
Shielded transactions conceal chain-visible details, but participants, wallet providers, network metadata, and application records may still reveal information. Use a dedicated address and protect memo contents.