GUIDES · BETSLIP DOCTOR
Why should private club content not appear in an unauthorized notification preview?
A notification preview is not the source of permission to read a club discussion. If a preview quotes private content before the viewer’s current identity and club access are confirmed, it could expose material outside its intended audience. BSD’s recorded in-app community item uses generic text such as “New community reply” and “Open the current discussion to view this activity”; opening then checks the current source and access. This describes the in-app item only, not device lock-screen behavior, encryption, or how long any metadata is retained.
For BSD club members wondering why a notification does not quote the private reply · Updated
The in-app notification names activity without quoting the reply
For the recorded free-club reply and like activity, the backend projects a generic title and body that point the recipient to the current discussion. The notification item is not a copy of the private reply text. This keeps the preview separate from the content the recipient must be authorized to read.
The discussion is checked when the recipient opens it
The current account and club access are checked before the source discussion opens, and the source revision and visibility are checked again. A notification does not bypass a later change in membership, permissions, or source availability.
Do not infer device-level protections from in-app copy
The cited behavior establishes generic copy for the in-app notification item. It does not establish what an operating-system banner displays, whether every device surface hides content, how the data is encrypted, or when metadata is erased. Keep privacy claims within the exact surface and behavior that have been verified.
Hypothetical example: a private reply preview
A fictional club member receives an in-app item that says “New community reply” and directs them to the discussion. The item does not quote the reply. When the member opens it, BSD checks that the signed-in recipient can still read the current source.
Related questions
Does the in-app notification show the private reply itself?
For the recorded free-club reply and like inbox behavior, the item uses generic title and body copy that points to the current discussion.
Does this prove that lock-screen previews are always hidden?
No. The cited source supports generic in-app title and body copy; it does not establish operating-system preview behavior.