Soumyadeep Das

Project 01 · 2026

hushhconnect

A private messenger that never asks for your phone number or email.

hushhconnect homepage: Say hello quietly, with a private chat preview.

Project details

Type
Private realtime messenger
Role
Design, front end, data model
Identity
Chat ID + hashed Recovery ID

hushh is a private, real-time 1:1 messaging app. A React + Vite single-page app talks directly to a Supabase cloud project: Auth gated by hCaptcha, Postgres with row-level security on every table, Realtime for live delivery. Identity is a Chat ID — no email or phone anywhere — and a one-time Recovery ID covers password reset through the recover-password Edge Function, the only server-side code in the project.

Built with

  • React
  • Supabase Realtime
  • hCaptcha
  • Vercel

The problem, in structure

  1. Identity is the price of entry. Mainstream chat starts from a phone number or email — the identifier becomes a scraping and spam surface.
    • contact lists get imported and mined
    • the address is exposed before a conversation exists
  2. Discovery follows the crowd. People find you through mutual contacts, not because you handed them your ID.
  3. Recovery leaks the identity back. Phone or email recovery re-introduces the exact identifier the product removed.
  4. Open sign-up invites bots. Without a gate, bulk automated accounts are free to create.
  5. Chat becomes a feed. Media and noise turn a conversation tool into a distraction machine.

How it answers each one

  1. Nothing to leak. Sign-up asks a name, a unique Chat ID and a password — no phone, no email, ever.
  2. Exact-ID reachability. You are findable only by the ID you chose to share; there is no directory to crawl and no contact import.
  3. Recovery without identity. A hashed Recovery ID plus a security answer restores access — the Chat ID alone never can.
  4. hCaptcha at the door. Registration is gated before an account can exist, pricing out bulk bots.
  5. Text only. No feed, no media noise — Supabase Realtime moves the message, nothing else.

Architecture

hushh User 1. Sign Up / Log In Chat ID Auth (no email, no phone) 3. Browses / Chats 2. Issues Session (JWT) React SPA + Supabase client (Everything client-side) 4. RPC + RLS 5. Live Messages Postgres + RLS (profiles · messages) Realtime Channel (postgres_changes) recover-password Edge Function — the only server code

Next phase

  • Typing and delivery indicators over the existing Realtime channel.
  • Per-device session list with remote sign-out.
  • Delete-for-everyone on sent messages.
  • Optional group threads under the same ID rules.
  • Abuse reporting and rate limits on ID discovery.
Portfolio Live project Source code