Your information should not become everyone's information.
This page describes the privacy principles used by the current product design. It is informational and should be aligned with the final production data model, providers, retention settings, and applicable law before launch.
Information visibility
Public profile fields are intended to be visible to other community members. Private account credentials and protected application data should not be exposed as public profile content.
Conversations
Public room messages are community content. Private conversations are intended for the participants involved. Access to protected conversation data should be enforced by server-side authorization and database row-level permissions, not only by the interface.
Posts, likes and comments
Posts, reactions, and comments are community features. Users should assume that content intentionally published to a public community may be visible to other members.
Account information
Do not publish passwords, authentication tokens, payment details, private contact information, or other secrets in profiles, rooms, posts, or messages.
Third-party services
The final privacy policy must list the actual authentication, database, storage, analytics, email, hosting, and other providers used by the production deployment, together with their relevant processing purposes.
Your responsibility
No online service can guarantee absolute privacy or security. Avoid sharing information that could harm you if disclosed, and report suspicious activity or abuse through the mechanisms provided by the service.