Current static capability
Static profile orientation can explain future preferences, privacy expectations, activity context, and connected product areas.
Wallet authentication is disabled for this environment. No wallet provider is requested and no signature is requested.
Vitality app preview
Static module workspace. Live actions remain approval-gated.
Profile controlled preview
Review the planned account and preference experience without authentication changes, identity verification, personal-data collection, wallet access, live activity reads, or account mutations.
Static controlled preview only. No wallet connection, RPC provider, live on-chain or contract read, balance or treasury read, signature, claim, reward, staking, charging, payment, or token action is active.
Continuity path
This route remains static and safe. Use the continuity links to return to the app command surface, compare module context, and verify status before assuming any feature is active.
Profile preview depth
This route should explain the future profile layer as user orientation, preferences, and readiness context without activating login, wallet identity, or personal data flows.
User question
What will the profile area help users understand before personalisation is enabled?
Current preview state
Static profile orientation only. The route can explain future profile modules, preferences, activity summaries, and privacy expectations without authentication or wallet identity.
Product readiness education
This is a static product sequence. It explains what exists now, why live capability remains unavailable, and what must be approved before any future activation.
Current static capability
Static profile orientation can explain future preferences, privacy expectations, activity context, and connected product areas.
Why this remains unavailable
Authentication, account creation, wallet identity, personal data collection, preference storage, and profile writes remain inactive.
What must be approved next
Approved identity, consent, privacy, data-retention, authentication, security, and account-recovery designs must exist before personalisation.
Step 1
Available in this previewUnderstand the future profile modules and privacy expectations without creating an account.
Step 2
Intentionally unavailableNo identity, preference, wallet, account, or activity information is collected or stored.
Step 3
Future capability requiredFuture personalisation depends on approved consent, authentication, privacy, storage, and recovery infrastructure.
Readiness state legend
No user-specific result
This sequence describes product readiness only. It does not evaluate you, your wallet, an account, eligibility, entitlement, allocation, or claim status.
No live result is produced and no personal evaluation is performed.
Identity
Describe the profile as a future place for preferences, app readiness, activity context, and safety settings once approved identity flows exist.
Privacy
Make clear that the preview does not collect personal data, create accounts, connect wallets, or store user preferences.
Continuity
Connect the profile preview to wallet, rewards, claims, and activity routes as future context surfaces without implying live personalisation.
Safe boundaries
Continue review
These links stay inside the static controlled-preview layer and do not activate wallet, claim, reward, staking, charging, payment, treasury, or token actions.
25H route continuity polish
These pathway groups help users move through the static app preview without implying any live wallet, chain, balance, treasury, claim, reward, staking, charging, payment, or token action.
Start at the dashboard, then move into the ecosystem and route status layers before reviewing preview modules.
Use contracts, treasury, and safety pages to understand the static source-of-truth boundary before any future live capability.
Review wallet, rewards, claims, and charging as inactive preview modules with informational links only.