Safety, privacy, and security in OpenGlob Rooms

OpenGlob Rooms is designed for secure, temporary collaboration. Whether you are using the platform as an anonymous guest or a verified OpenGlob user, your safety and data privacy are protected by built-in infrastructure controls.

Participant Tiers: Guest vs. OpenGlob SSO

OpenGlob Rooms supports both anonymous guest access and verified accounts. Choosing to sign in with an OpenGlob account provides higher session limits and enhanced security features.

To extend your limits, sign in at accounts.openglob.com before creating or joining a Room.

Host Controls: Managing Participants

As a Room Host, you have real-time authority over who remains in your session. There are two primary ways to manage participants:

Remove Participant

• Action: Kicks the user out of the current chat.
• Result: Use this for accidental joins or minor disruptions. The user is sent back to the landing page but is allowed to request entry again (Knocking). They will remain in the Waiting Room until you re-admit them.

Ban Participant (Session Lock)

• Action: Permanently removes the user from the active session.
• Result: The user is blacklisted for that specific Room ID. They cannot rejoin or "Knock" again for the duration of that session. Use this for serious violations or persistent disruptions to lock the session to authorized users only.

The Waiting Room & "Knocking"

Every Room acts as a secure container. No user can enter a Room without your explicit permission if the Room is set to private.

1. Request Access: When a user enters your Room ID, they are placed in a Waiting Room.
2. Notification: You receive a "Knock" notification in your chat interface.
3. Admit or Decline: You can see the user's name (and verified status if using SSO) before allowing them to join the conversation.

Data Security & Privacy

OpenGlob Rooms is a "Zero-Footprint" service. We prioritize your privacy by ensuring data is never stored longer than necessary.

• In-Memory Processing: Chat history is stored in volatile memory (RAM). It is never written to a permanent database or long-term storage.
• Encryption in Transit: All messages and media sent within a Room are encrypted while moving between your device and the OpenGlob Socket servers.
• Auto-Purge: When the last participant leaves or the Host ends the session, the Room data is marked for deletion. The server automatically clears the session memory within 60 seconds of inactivity.
• Manual Termination: Hosts can click End Room for All to immediately disconnect every participant and trigger an instant data wipe.

Safety Recommendations

• Verify SSO Status: For sensitive discussions, look for the OpenGlob verification in the participant list to ensure guests are who they claim to be.
• Use Banning for Harassment: If a user is disruptive, use the Ban feature rather than Remove to ensure they cannot re-initiate a join request.
• Close Sessions: Always use the "Leave" or "End Room" buttons to ensure your session is properly closed on the server.

Need more help?
Learn how to create your OpenGlob account or how to reset your password.