SecureBitChat/securebit-chat
1
0
Fork 0
Code Issues Pull Requests Actions 5 Packages Projects Releases Wiki Activity

Fix formatting for Privacy by design section in README
CodeQL Analysis / Analyze CodeQL (push) Has been cancelled
Details
Deploy Application / deploy (push) Has been cancelled
Details
Mirror to Codeberg / mirror (push) Has been cancelled
Details
Mirror to PrivacyGuides / mirror (push) Has been cancelled
Details

Browse Source 
fix text
This commit is contained in:
Volodymyr
2026-06-24 15:44:54 -04:00
committed by GitHub
parent ab49d7485d
commit 5eaf57c8da
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+1 -1
View File
@@ -36,7 +36,7 @@ It is designed for people who need a small, auditable, zero-infrastructure way t
- Interactive **Short Authentication String (SAS)** verification — you confirm a code out-of-band before the session is trusted, defeating man-in-the-middle attacks. - Interactive **Short Authentication String (SAS)** verification — you confirm a code out-of-band before the session is trusted, defeating man-in-the-middle attacks.
- Replay protection, message integrity (HMAC), and a live security report you can open at any time during a call. - Replay protection, message integrity (HMAC), and a live security report you can open at any time during a call.
**🕶️ Privacy by design** ** Privacy by design**
- Direct peer-to-peer connection — messages never touch a SecureBit server. - Direct peer-to-peer connection — messages never touch a SecureBit server.
- No accounts, no phone numbers, no message history on disk. - No accounts, no phone numbers, no message history on disk.
- Optional **relay-only mode** routes traffic through your own TURN server so your IP is never exposed to the peer. - Optional **relay-only mode** routes traffic through your own TURN server so your IP is never exposed to the peer.