Security Protocol
Mathematical proof of zero-trace communication
Peer-to-Peer Cryptography
Every message is encrypted locally before transmission. A temporary symmetric key is established using ECDH key exchange. No unencrypted content ever leaves your local environment.
Zero-Knowledge Architecture
Incogniq doesn't store active message indices, metadata links, or user association lists. Active ephemeral room keys self-destruct once all users disconnect. What we do not possess cannot be leaked, compromised, or demanded.
Direct Transport
Real-time WebRTC channels facilitate direct browser-to-browser data routing. By removing intermediate relays, the threat surface is reduced strictly to the end-user endpoints.
Safety Enforcement
We balance safety with privacy. Automated local heuristics filter hate speech and harassment prior to transmission, maintaining a clean communications channel without centralized oversight.
Technical Specifications
| Protocol / Standard | Specification Details |
|---|---|
| Key Exchange | ECDH-256 (Elliptic Curve Diffie-Hellman) |
| Data Encryption | AES-GCM-256 (Symmetric Encryption) |
| Connection Type | Direct browser-to-browser P2P WebRTC channels |
| Authentication | Room PIN (shared securely by creator) |
| Message Retention | Self-destructs immediately on disconnect / 24h expiry |
Cryptographic Standard
Your data remains in your control. No persistent states are maintained, and all active channels rely on temporary cryptokeys designed to decay as soon as sessions terminate.