Skip to main content

FAQ

⚠️ WARNING: Enkrypted Chat is experimental, unaudited, and unstable. Expect breaking changes and an evolving setup flow. For testing and evaluation only; not for sensitive communications or production use.

Is Enkrypted Chat production-ready?

No. It is a proof of concept with no professional security audits. Not for sensitive communications or production use.

How is encryption handled?

Messages use end-to-end encryption with a cascading cipher on top of WebRTC. Keys are managed locally on your device — no central authority.

Do I need to register?

No. Your peer ID and keys are generated on your device when you open the app.

Can I use Enkrypted Chat on mobile?

Yes, in any modern browser with WebRTC support. Experience may vary by platform.

Is my data stored on a server?

No. Your peer ID, keys, and conversations stay on your device. A peerjs-server only brokers the initial WebRTC connection — it does not store messages. If a direct connection fails, TURN servers may relay encrypted traffic without persisting content. Files follow the same model — encrypted locally, no server-side plaintext storage.

Is there a file or folder explorer?

Yes — file management is built into the app. See Getting Started — section 4 and Features.

Can I browse files on my own computer?

By default, files live in private browser storage (OPFS) — they persist in the app but are not visible in your OS file manager. You can optionally mount a folder via the File System Access API for on-disk storage.

Remote folder browsing over WebRTC is planned but not available yet.

Are files and documents production-ready?

No — same experimental, unaudited status as the rest of the app. Not a replacement for services like Nextcloud. See the caution note on Features.

How do I connect with someone?

  1. Click Create new chat.
  2. Click Add peer.
  3. Exchange connection links, QR codes, or peer IDs.
  4. Open the chat once connected.

See Getting Started for the full walkthrough.