Session Messaging App

Website

getsession.org

Pricing URL

-

$ Details

-

Release Date

-

Categories

#Communication #Group Chat & Notifications #Instant Messaging #Text Messaging #Chat

OffCode Tor Chat E2EE

Website

dev-offcode.com

Pricing URL

Official OffCode Tor Chat E2EE Pricing

$ Details

freemium $49.0 / One-off (Source-code)

Release Date

2026 July

Categories

#Chat #Group Chat & Notifications #Network Security #Security & Privacy #Encryption #Messaging #Group Messaging #Instant Messaging #Web App #Web Hosting #Self Hosting #Tor

Startup details

Country

Finland

Session Messaging App features and specs

• Privacy-Focused
  Session Messaging App is designed to prioritize user privacy by not requiring phone numbers or email addresses for registration, reducing the risk of data exposure.
• Decentralized Infrastructure
  The app uses a decentralized network of servers, which makes it more resistant to censorship and points of failure compared to centralized messaging services.
• End-to-End Encryption
  Messages are secured with end-to-end encryption, ensuring that only the intended recipients can read the messages, safeguarding user conversations from potential eavesdroppers.
• No Metadata Logging
  Session claims to minimize the collection of user metadata, further enhancing user privacy as it reduces traceability and the ability to profile users based on their communication patterns.
• Open Source
  The app's code is open source, allowing the public to inspect, verify, and contribute to the app’s development, fostering transparency and community trust.

Possible disadvantages of Session Messaging App

• Limited Adoption
  Session may have a smaller user base compared to more established messaging apps, which could limit communication with a broader audience.
• Performance Issues
  Due to its decentralized nature, some users may experience slower message delivery times or connectivity issues compared to centralized apps.
• Feature Limitations
  The app may lack some features that are considered standard in other messaging apps, such as video calls or extensive media sharing capabilities, which could affect user experience.
• Unfamiliar Interface
  Users accustomed to mainstream messaging apps might find the interface and workflow of Session unfamiliar or less intuitive, potentially impacting ease of use.
• Dependency on Onion Routing
  The reliance on onion routing (similar to Tor) for message delivery can introduce latency and affect the overall performance of the app.

OffCode Tor Chat E2EE features and specs

• Ciphertext storage
  SQLCipher database under LocalAppData (Windows) or Docker volume. DPAPI / env key. Parameterized queries. Plaintext is never written to disk.
• Close room to new members
  blocks all joins (including invites); members stay
• Slow mode
  Send cooldown 1 min … 4 h (applies to everyone, including creator)
• Delete this room
  Same wipe path as Server Manager room delete
• Creator recovery code
  Binds rooms you create; My rooms lists hidden; Copy / Restore
• Rooms, invites & TTL
  Open, password-protected, and/or hidden rooms with invite links and required per-message lifetime.
• Server manager
  Start ChatServer first (Production, waits for /api/health), then enable Tor Copy and share the published .onion URL Optional Full Vanguards checkbox (Python + Stem) for long-lived HS hardening Locks CORS to your onion: TORCHAT_ALLOWED_ONION on start + live POST /api/admin/cors-onion (no ChatServer restart) Live room list (room id, locked flag, online count only, no message content) Remove a selected room in realtime: connected users are forced back to the lobby; ciphertext for that room is deleted with secure_delete + VACUUM Remove SQL data: securely overwrites (then deletes) the SQLCipher DB, WAL/SHM, and db.key.dpapi; optional checkbox also wipes Tor Hidden Service keys (.onion identity) Generate new address: securely wipes HS keys and publishes a new .onion (chat DB unchanged) Point at your ChatServer project path and load/save host config as needed
• Full Vanguards Guard-Discovery Protection
  A standard Tor Hidden Service chooses its entry (guard) nodes randomly on every circuit build. Over time a network-level adversary can watch which relays the server connects to and gradually narrow down the real server IP. This is called a guard-discovery attack and is especially dangerous for long-lived hidden services.
• Encryption
  WebCrypto AES-256-GCM; PBKDF2-v2 domains at 600 000 iterations (torchat-join-v2 / torchat-e2ee-v2 locked = server-blind; torchat-open-v2 open = public key material). Envelopes: pbkdf2-v2 / ecdh-hybrid-v1
• XSS hardening
  No user innerHTML; messages and room ids via textContent / createElement
• ECDH + safety number
  1:1 hybrid ECDH; safety number from sorted SPKI pubs (3×5 decimal); Mark verified / TOFU change warning (sessionStorage)

No Session Messaging App videos yet. You could help us improve this page by suggesting one.

Add video

OffCode Tor Chat Showcase