Vitality identity
Account, linked-wallet, preference, privacy and activity architecture prepared before personalisation is enabled.
Static profile orientation can explain future preferences, privacy expectations, activity context, and connected product areas.
Authentication, account creation, wallet identity, personal data collection, preference storage, and profile writes remain inactive.
Approved identity, consent, privacy, data-retention, authentication, security, and account-recovery designs must exist before personalisation.
Describe the profile as a future place for preferences, app readiness, activity context, and safety settings once approved identity flows exist.
Make clear that the current view does not collect personal data, create accounts, connect wallets, or store user preferences.
Connect the profile current view to wallet, rewards, claims, and activity routes as future context surfaces without implying live personalisation.
- 01Review profile purposeAvailable now
Understand the future profile modules and privacy expectations without creating an account.
- 02Keep personal data inactiveNot active
No identity, preference, wallet, account, or activity information is collected or stored.
- 03Approve identity and privacy controlsInfrastructure required
Future personalisation depends on approved consent, authentication, privacy, storage, and recovery infrastructure.
Safety + activation boundaryView controls
No authentication is active.
No wallet identity is active.
No personal data collection is active.
No profile write or preference save is active.