A practical Session privacy-settings checklist

Secure the device and its notifications

Begin with a strong device unlock method, then enable Session’s local application lock. Configure lock-screen notifications so they do not expose names or message text, particularly on shared workspaces and in public settings. Notifications are a common plaintext leak because they sit outside the protected conversation view.

Reduce unnecessary social signals

Read receipts and typing indicators are convenient, but they also reveal patterns of attention. Users who need fewer behavioral signals can turn them off. Review message requests and community contact settings at the same time, limiting the ability of unknown accounts to create direct contact.

Treat calls and disappearing messages precisely

Official guidance states that current calls are peer to peer and may expose IP information to the call partner. Higher-risk users should not enable them by default. Disappearing messages reduce long-term retention but cannot erase a recipient’s copy. Good settings respond to a specific risk rather than creating a vague sense of invulnerability.