Frequently Asked Questions
Everything you need to know about PeerBox architecture, privacy, file transfers, and limits.
Common Questions
Are files or messages ever uploaded to a central server?
No. PeerBox is 100% serverless. The application code is served as static HTML/JS from GitHub Pages. All messages, voice recordings, and binary file chunks stream directly between peers via encrypted WebRTC DataChannels.
What is the maximum file size that can be transferred?
There is no hard-coded file size limit. Files 25MB and larger stream directly into your browser's Origin Private File System (OPFS), supporting multi-gigabyte transfers without exhausting JavaScript heap memory.
Does PeerBox require an account, phone number, or email?
No. PeerBox requires zero authentication, accounts, or persistent identifiers. When joining a room, a temporary randomized Persona (friendly animal name and pastel avatar) is generated client-side.
Can a room host or network eavesdropper intercept my Room Key?
No. The Room Key resides strictly in the URL hash fragment (#key=...).
RFC 3986 guarantees that browsers never send URL hash fragments to HTTP servers or
signaling relays. Encryption keys are derived client-side using Web Crypto AES-GCM.
How do I share a room with a mobile user?
Inside any active room, tap the Share button in the header. PeerBox renders a high-contrast SVG QR code that any smartphone camera can scan to instantly join with or without the encrypted key included.
What happens if a symmetric NAT firewall blocks direct connection?
PeerBox operates strictly with zero TURN relay servers (respecting ADR-0001). If two peers are both behind double-symmetric enterprise firewalls that prevent STUN hole punching, PeerBox displays a diagnostic banner recommending that peers share a local LAN or use a VPN.