Privacy Policy
Sovereign Engine is designed around a real-person mint path. When Yoti is used, it is used to help verify that one person is tied to one account path. It is not used to publish private identity details inside artifacts, character lore, public metadata, or marketplace descriptions.
Purpose
Sovereign Engine is built around one real participant, one account path, and one Genesis mint claim. When Yoti is used, the purpose is to help verify that a participant is a real person and is not creating duplicate accounts to bypass the one-person rule.
Yoti
We use Yoti verification only for the account and eligibility decision. In plain English: the result helps us decide whether this person should be allowed through a single account or mint path. We do not use Yoti information to create public artwork, public metadata, marketing profiles, or public character lore.
Storage
Our goal is to keep only the minimum information needed to operate the account, verify eligibility, prevent duplicate claims, process orders, and maintain required records. Raw identity details should not be placed in public NFT metadata, public URLs, or public readouts.
Wallets
Wallet addresses, token ownership, token IDs, contract activity, and on-chain mint events are public by nature. We can limit what personal details we publish, but we cannot make public blockchain records private after they are written on-chain.
Depending on the page or feature, you may provide a wallet address, name fields, date of birth, order information, agreement confirmations, or account-verification information. Some of this may be required before a mint or future account action can continue.
If Yoti verification is enabled, Yoti may collect and process identity information according to Yoti's own privacy notices. Sovereign Engine uses the verification outcome for eligibility, duplicate-account prevention, and account safety. We are not trying to turn that information into a public profile.
The project is designed to favor real people over bot farms, repeat claims, or automated account farming. Verification helps protect a fair launch path, future Progeny eligibility, and the idea that each participant begins from one real origin.
Generated artifacts should use public-safe markers, token references, wallet-linked ownership state, derived stats, and approved metadata. Raw personal identity data should stay out of public artifact descriptions and ordinary marketplace metadata.
When checkout is active, payment and order data may be handled by payment providers and backend services so the mint path can confirm whether an order is paid, pending, failed, or ready. Payment providers have their own privacy and data practices.
If you have a privacy question, contact the project through the public contact link. Some information can be corrected or removed from app systems, but public blockchain transactions cannot be erased by us once they exist on-chain.