Signing out is more than hiding an avatar. A podcast app may still hold subscriptions, recent searches, history, playback positions, and short-lived credentials in memory or local storage.
On a shared device, the next person should not see those records simply because the previous screen remains cached.
Give listener caches an owner
Key private caches by the authenticated account and workspace. When the active account changes, stop requests for the old account and clear or detach its private state. A public catalog image cache can often remain, but a followed-show list is not public catalog data.
Remove client credentials according to your platform's storage design. If your backend supports session or token revocation, call the documented sign-out flow as part of the process. Do not assume that deleting a local variable revokes every server-side session.
Check the player too. Audio already playing may need to stop, while a locally downloaded public episode may follow a different policy. Choose and explain the behavior instead of leaving it to the order in which components unmount.
Test a two-person sequence
Sign in as account A, follow a show, open history, and start an episode. Sign out. Then sign in as account B without restarting the app. B should receive only B's private state.
Repeat while a slow response for A is in flight. It must not populate B's screen after the account changes. Include browser back navigation and restoration after the operating system suspends the app.
A clear ownership model makes logout predictable. It also makes support easier when someone reports “the app showed another person's list,” because each cache has a known account boundary.