Privacy & data model
OrdiFi is designed to minimize personal data. Membership identity is asset-based and verified via ownership — not via email accounts.
No email is required
OrdiFi does not require an email address to access core features. Wallet connection and asset ownership are sufficient for membership recognition and collector functionality.
- Reduces identity leakage and spam vectors.
- Removes third-party dependencies.
- Keeps the system aligned with self-custody and on-chain ownership.
Flickerbox identity: asset-bound by design
A Flickerbox is treated as a member card. Identity (presence, avatar, username surface) is derived from the owned asset, not from a separate registered profile.
On transfer of the Flickerbox, member personalization resets for the new owner. Personal content does not automatically transfer.
Local transfer token (optional)
Owners may optionally export personal settings using a local transfer token generated on their device. This enables importing personalization into a newly acquired Flickerbox later.
- Local by default (privacy-first).
- Opt-in, user-controlled.
- Not required to use OrdiFi.
Mailbox (no email) — planned, optional
A mailbox feature may be introduced as an opt-in communication surface addressed to the Flickerbox (the asset), not to an email identity.
- Intended for ecosystem-relevant notifications and contextual messages.
- Not designed to replace email.
- Only shipped if it can stay simple and privacy-first.
Expectation management
OrdiFi separates what is live at launch from what may be added later. Launch features are designed to provide immediate utility (cases + showroom + member home). Post-launch items are demand-driven to avoid empty promises.
