Matchmaking app

Nikah — Privacy-first Matchmaking

Client-first encryption + optional encrypted-server sync (opt-in)

Account (local)

Create a username and passphrase. Passphrase derives your encryption key — keep it safe.

---

Your Profile (encrypted locally)

Public minimal preview shown below. Save to encrypt & store locally.

GenderBrotherSister

Note: photos and wali contact are encrypted — only decrypted with passphrase.

Preview (optional)

---

Local Pool (imported encrypted profiles)

---

Find Matches (local-only or server-sync)

Any deenPracticingModerate

---

Express Interest / Mutual Match

Expressing interest generates an encrypted signed token. For a mutual match both parties need to express interest (by sharing signed token or using server sync).

---

Chat (local encrypted)

Start encrypted chat only after mutual match. Messages stored encrypted locally.

---

Data Controls & Optional Server Sync

By default this app keeps everything local. Toggle server-sync to store encrypted blobs on your server (server only receives ciphertext + iv + salt).

Enable Server Sync (opt-in)

Quick Status

Unlocked: no

Username: —

Local profiles stored: 0

How this protects privacy

1. Encryption in browser (Web Crypto AES-GCM)
2. Passphrase-derived key (PBKDF2). Passphrase not sent to server.
3. Server (if used) stores ciphertext only — cannot read data.

---

Developer notes

This file includes comments showing how to implement a server endpoint that simply stores blobs. If you want, I can also scaffold the Node.js server code for you.