Understand profile and account states
Customer App separates the signed-in Profile overview from the My Account form. Profile presents conditionally available account destinations and status. My Account presents configurable identity fields and account actions. Opening either surface is not guaranteed to be read-only.
The exact menus, fields, providers, and account actions depend on the current project, account, session, configuration, and app version. Source inspection does not certify deployed availability.
Profile overview and My Account
| Surface | What it can present | What it does not prove |
|---|---|---|
| Profile overview | Conditional shortcuts, rewards/account/information groups, connection status, app version, Logout, and optional support access | That every item is available, current, authorized, or free of passive reads/effects |
| My Account form | Configured identity fields, avatar control, contact/verification state, password field, Update, and Remove account | That opening is an edit, that every field can change, or that a visible value is fresh |
| Loading or error | Profile, field, validation, wallet, capability, provider, or session work is unresolved | That an account option does not exist or that a mutation failed safely |
| Local success or navigation | One local/request layer reported success or changed screens | That profile, verification, password, provider, session, and retained data settled together |
Profile can refresh account data and resolve conditional menu items such as languages, wallets, or saved-card capability. Those reads can update shared session state or invoke other account services. Treat the overview as an active account surface, not as a static menu.
Conditional menu gates
An option can be hidden or shown because of authentication, project plan, feature configuration, theme, provider capability, consent, or returned data. Absence does not reveal whether another account or project has the feature.
Addresses, saved cards, wallets, messages, languages, notifications, sessions, help, support, and other destinations own separate authorization and settlement contracts. Profile visibility is only an entry signal; it is not proof that the destination is usable or current.
Avatar, contact, and password boundaries
These actions are separate and can have different effects:
- Opening My Account or enabling edit mode is not an explicit Update action, but the shared form can still perform passive mount or remount work; do not treat entry as read-only or zero-write.
- Choosing an avatar can invoke the operating system's media library and can begin an immediate image update in the current source. Selection is therefore not a private local preview or durable-success receipt.
- Editing contact information can invoke a separate verification provider. A provider result does not prove that the profile update or session refresh completed.
- Entering a new password is a credential change, not an ordinary display-field update. A local success message does not prove rotation of every session or credential-related record.
Do not use real personal information, a personal photo, a password, or a phone number to test Profile or My Account. This guide does not provide update, verification, avatar, or password procedures.
Session and socket freshness
Profile can refresh the current user, show connection state, listen for account- related events, and update shared session data. A late response or socket event must be bound to the exact current account, project, session, role, and revision before it changes visible identity or availability.
Switching account or project, signing out, closing Profile, or losing connection must invalidate old reads, wallet/card/provider state, form changes, media, listeners, and callbacks. A changed greeting, menu, connection indicator, or form value is not an authoritative session receipt.
Logout and Remove account are different
| Action/state | Safe interpretation |
|---|---|
| Logout offered | A session-ending action is available; no action has occurred |
| Logout requested | Local and server/provider session cleanup may still be pending or partial |
| Signed-out screen appears | Local navigation/session state changed; remote revocation and provider cleanup are not proved |
| Remove account confirmation | A destructive decision is being presented; nothing has been deleted |
| Removal requested | Account deletion/anonymization, session revocation, related-data handling, provider cleanup, and logs can settle separately |
| Removal reports success and logs out | The UI received one accepted-looking result; complete erasure and retention outcome are not proved |
| Removal error or lost response | Outcome is unknown; do not repeat automatically or create a replacement account as a test |
Logout does not mean Remove account. Remove account does not mean immediate, complete, or irreversible erasure of every related record. Retention and provider responsibilities require an authoritative product/privacy policy, not an inference from the current screen.
Unknown and partial outcomes
| Situation | Safe response |
|---|---|
| Profile data and greeting disagree | Treat shared session state as stale or partial; do not edit to force convergence |
| A menu changes after refresh | Re-evaluate current account/project gates; do not infer entitlement or removal |
| Avatar disappears or stays unchanged | Do not infer whether media upload or profile persistence occurred |
| Contact verification succeeds but value is unchanged | Keep provider and profile settlement separate |
| Password update reports an error or closes | Do not infer whether any credential/session changed |
| Logout returns to signed-in state | Do not repeat rapidly; session revocation outcome is unresolved |
| Removal returns no clear result | Stop and use an approved support/privacy channel without submitting PII |
| Old data appears after account/project switch | Leave the surface and avoid acting on it; the old generation must be discarded |
Repeated updates, media selection, Logout, Remove account, Back, reopening, or account switching are not safe reconciliation methods while an outcome is unknown.
Privacy and accessibility
Profile fields, contact data, photo, credentials, account identifiers, wallet state, session state, provider identity, and deletion/retention status are private. Do not include them in screenshots, copied links, diagnostics, logs, support notes, or documentation fixtures. Use value-free descriptions such as “profile refresh unresolved” or “account-removal outcome unknown.”
Profile groups and conditional options need headings and semantic structure. Avatar/edit, Update, Logout, Remove account, confirmations, support, connection, loading, error, success, destructive, disabled, and unknown states need distinct names, roles, states, focus order, and predictable focus return. Large text, keyboard, safe areas, screen readers, and iOS/Android Back behavior must not hide critical confirmation or status. This is a verification requirement, not a claim of current accessibility certification.
Troubleshoot safely
- Confirm the active account and project before interpreting any Profile state.
- Treat missing menu items as conditional, not as proof of account/provider data.
- Do not refresh repeatedly while a profile, password, logout, or removal action is pending.
- Do not use another person's information, a personal photo, a test password, wallet activity, or support chat to diagnose the page.
- Keep provider, profile, session, navigation, and retention outcomes separate.
- If foreign or stale data appears, stop and avoid copying, editing, logging out, or removing the account from that stale surface.
Recertification triggers
Revalidate this reference after changes to Profile/My Account routing, menu gates, validation fields, passive reads/writes, shared user/session refresh, wallet or saved-card capability, socket events, avatar/media handling, contact verification, password updates, Logout, Remove account, retention policy, support/provider identity, consent, navigation, or accessibility.
Related guides: Complete your profile · Account settings · Manage saved addresses · Understand saved card states · Understand privacy and consent · Understand platform and accessibility behavior