GUIDES · BETSLIP DOCTOR
Why should a notification respect the account currently signed in on the device?
A club notification is activity for a particular recipient account, not for everyone who uses the same device. After an account switch, the new account must not use an old notification as permission to read or act on the previous account’s private club content. BSD reads notifications under the authenticated account, and the inbox waits for its session owner to match the active account namespace before showing that activity. This describes the in-app inbox checks; it does not promise that every device cache is erased or make a claim about encryption or operating-system previews.
For BSD members who switch accounts and want to see the right community activity · Updated
The notification belongs to its recipient account
A community notification points to activity addressed to one account. The backend looks up notifications for that authenticated recipient, and the iOS inbox compares the ready session owner with the account namespace currently in use. A shared phone does not turn one person’s activity into another person’s permission.
The new account needs its own current session
During sign-out, sign-in, or account switching, the inbox can show a signed-out or session-pending state instead of using the previous account’s items. A source notification is also checked again against the current recipient and club access before its discussion opens.
Check which account is active before opening activity
Confirm that the intended BSD account is signed in and that its own activity view has loaded. If the account state is still pending or the source cannot be checked, wait for the current session or refresh the inbox. Do not treat an old notification as authority for another account.
Hypothetical example: two people share a device
Imagine Alex signs out of a shared tablet and Jordan signs in. A saved community notification addressed to Alex does not become Jordan’s club activity. Jordan’s inbox must load under Jordan’s own signed-in account and current club permissions before a source can open.
Related questions
Does using the same device mean another account can open my club notification?
No. The notification is read for its authenticated recipient, and opening the club source checks the current account and access.
Does this mean every local device cache is erased when I switch accounts?
No such guarantee is made here. The described behavior is the current account check for the in-app notification view.