DARKP2P // DEAD DROP

E2E AES-256-GCM + DTLS P2P STREAM • ZERO SERVER STORAGE
TUNNEL: STANDBY IP STATUS: WAITING FOR PEER
SHARE LINK WITH PEER:
PRO RELAY TOKEN (OPTIONAL — UNLOCKS TURN):
WAITING FOR PEER HANDSHAKE...
Direct WebRTC exposes your IP to your peer. Mask it with a zero-log VPN.
SUPPORT ZERO-LOG INFRASTRUCTURE:
SYSTEM FAQ // ZERO-KNOWLEDGE SPEC
How does DARKP2P work without server storage?

Files stream directly browser-to-browser over WebRTC DataChannels. The signaling node only pairs two peers in RAM and never stores or logs file payloads.

Can the server read or decrypt my files?

No. Every chunk is encrypted client-side with AES-256-GCM using a 256-bit key stored only in the URL fragment (after #), which browsers never transmit to the server.

Is there a file size limit?

No server cap for direct P2P transfers. Incoming chunks stream directly to disk via the browser's Origin Private File System (OPFS) so multi-gigabyte files won't crash your tab.

Does WebRTC hide my IP address?

No. Direct P2P connections expose your IP address to the other peer during NAT traversal. Use Force WebSocket Relay, a Pro TURN token, a zero-log VPN, or Tor Browser to mask your IP.