What is public
Alias or Anonymous Owner, stable public owner code, optional processed avatar, current plot content, public marketplace actions after screening, ownership periods, completed sales, and privacy-safe aggregated traffic.
Policy v0.1 · Pre-launch draft
Privacy in a public square.
Public identity is deliberately small. Private identity and payment information are collected only when needed to secure accounts, operate transactions, satisfy law, prevent abuse, and support users.
Launch gateThis sandbox uses fictional data and does not accept real payment, KYC, or support information.
What stays private
Legal name, email, phone, birth data, address, PAN or tax identifiers, bank/UPI/card details, provider IDs, raw IP/device data, risk notes, moderation evidence, support correspondence, and payout requirements.
How data is used
Authentication, fraud prevention, provider reconciliation, payout/KYC status, support, safety review, content processing, link defense, privacy-safe analytics, legal compliance, audits, and service reliability.
Retention and rights
Raw analytics identifiers are short-lived and rotating; aggregates are longer-lived. Financial and audit records follow legal retention. Users may request access, correction, deletion where applicable, optional public snapshot removal, or raise a privacy complaint.
Service providers and transfers
Payment, KYC, storage, media scanning, communications, monitoring, and hosting vendors process limited data under contract. Final regions, cross-border transfer safeguards, cookie consent, controller identity, and grievance contact require launch configuration.
Still curious?