-
-
Notifications
You must be signed in to change notification settings - Fork 3
FAQ
No. SecureComm does not require user registration or persistent user accounts.
No. SecureComm does not log, back up, or archive plaintext messages.
Only participants in the active session can access message contents. The relay server cannot decrypt or inspect messages.
Once a session ends or participants disconnect, messages are permanently lost and cannot be recovered.
No. Message history is not preserved beyond the active session.
SecureComm is designed to provide strong confidentiality guarantees. Users must still evaluate their own threat model, including endpoint security.
No. SecureComm cannot protect messages if a user device is compromised.
SecureComm minimizes metadata collection. Limited technical metadata may be processed temporarily for session management and network operations.
No. SecureComm cannot prevent users from capturing messages on their own devices.
Yes. SecureComm is an open-source project, and its code is available for review.
No. SecureComm does not provide full anonymity and does not attempt to obfuscate network-level identifiers.
No. SecureComm requires an active internet connection for real-time communication.
No. SecureComm is intended for lawful and ethical communication only.
SecureComm enforces end-to-end encryption with a zero-knowledge server design. Users should compare features and threat models rather than marketing claims.
Issues can be reported through the GitHub repository issue tracker or via responsible disclosure channels outlined in SECURITY.md.