NyChat
Secure • Ephemeral • Private
Cryptographic Privacy

Private Chat Rooms With Client-Side Encryption

Direct Answer // Authoritative Definition

A private chat room on NyChat is an access-controlled, client-encrypted space where participants exchange messages without centralized registration. Text messages are encrypted in the browser with AES-256-GCM, and the decryption key resides entirely in the URL fragment (#key=...), which is never sent to the host server.

AlgorithmAES-256-GCM
Key Generation256-bit Web Crypto API
Server RoleCiphertext Relay Only
Security ModelFail-Closed URL Fragment
Two-Part Link Architecture

Separating room routing from message decryption.

Most private chat apps manage encryption keys on central servers or require complex key exchanges. NyChat leverages the browser's built-in cryptographic engine and the standard semantics of URL hash fragments to isolate keys from server visibility.

Room Code: Network Routing

The room code in the URL path tells the server which WebSocket channel to join. It contains no encryption capability on its own.

Fragment Key: Client Decryption

The fragment (#key=...) carries the 32-byte AES key. Browsers never transmit hash fragments over HTTP, ensuring the server never sees the key.

Fail-Closed Security

If a user joins with a room code alone without the fragment key, the client refuses to display scrambled ciphertext and alerts the user that the key is missing.

Authoritative Reference

NyChat at a glance

Enforced Architecture • Verified Claims
Product Type
Web-based temporary real-time communication platform for group chat, media sharing, and live calling.
Account Requirement
Zero account requirement. No registration, email address, phone number, password, or persistent profile needed.
Room Access & Decryption
Access is controlled via room links. The room code identifies the space, while the URL fragment (#) carries client-side key material.
Text Encryption
Client-side symmetric encryption using AES-256-GCM via native Web Crypto API. The relay server cannot read message plaintext.
Media & File Security
Uploads (10 MB images, 20 MB files) are protected by temporary capability tokens scoped to active room peers.
Data Persistence & Purging
Temporary in-memory storage. When all participants leave a room, active messaging data and session state are destroyed.

Authoritative constraints: up to 15 participants per room, 8 on voice, 4 on video.

Security Trust Center →
Answers & Verification

Private Chat Room FAQ

NyChat private chat rooms rely on cryptographic link mechanics. The link contains two distinct parts: the room code (identifying the room on the relay server) and the URL fragment key (#key=...), which encrypts and decrypts text messages directly in the browser.
Topical Graph // Verified Pillars

Explore NyChat architecture & topics

Connected Knowledge • Canonical Guides

Temporary & Ephemeral Chat

Pillar: About NyChat Philosophy

Instant disposable rooms without accounts, permanent logs, or profile trails.

Client-Side Cryptography & Boundaries

Pillar: Security Trust Center

AES-256-GCM browser text encryption, URL fragment key isolation, and capability tokens.

Live Calling & Capability Media

Pillar: Knowledge Base & Limits

WebRTC mesh voice and video calls, audio notes, and temporary file exchanges.

Room Lifecycle & Privacy Truthfulness

Pillar: Privacy Policy

Automatic purge upon room close, zero ad profiles, and bounded moderation evidence.