GUIDES · BETSLIP DOCTOR
What happens to cached BSD data when I sign out or change accounts?
The warm cache is keyed to the signed-in owner and session generation, so one account’s saved view is not rebound as another account’s answer. The sign-out path forgets the in-memory warm cache and clears account-private storage before a new private account is activated. This describes local saved display data only; it does not make claims about server records or backups.
For BSD readers signing out or switching between accounts · Updated
Cache keys include the account context
A cached query is eligible only when its key matches the current owner and includes a session generation. The account session updates that scope when identity changes. This keeps a saved answer associated with the account that produced it rather than treating it as a general screen snapshot.
A screen from one account should not be used as evidence about the next account. Current source data and permissions still govern what the newly signed-in account can see.
- The cache is account-scoped.
- The session generation fences answers from an earlier session context.
Sign-out retires saved display data
In the sign-out path, BSD forgets the in-memory warm cache and clears the account-private storage. A subsequent private activation uses the verified owner and begins loading that owner’s eligible cache. If the owner changes, the prior owner’s saved view is not used as the new owner’s answer.
This describes the app’s local warm-cache lifecycle. It is not a statement about server-side account deletion, backups, or a separate security audit.
A second account opens the same screen
Imagine a reader signs out of one account and then signs in to another. The old account’s warm view is forgotten and its private local storage is cleared by the sign-out path. Any saved answer for the second account must come from that account’s own scoped cache or a fresh read; the first account’s screen is not carried over.
Related questions
Can the next account inherit the previous account’s cached screen?
The cache is scoped to the owner and session generation, and sign-out clears the local warm cache and account-private storage.
Does this mean server data or backups are deleted?
No such claim follows. This guide describes only the local warm-cache and private-storage path.