PeerBox replaces corporate promises and opaque legal terms with verifiable cryptographic mechanics and serverless architecture.
PeerBox operates strictly without application backends, cloud databases, or TURN relay servers (ADR-0001). All signaling takes place over public, decentralized Nostr relays with end-to-end encrypted negotiation envelopes. Relays never see plaintext room contents or metadata.
Room Keys reside exclusively in the client-side URL hash fragment
(#key=...,
ADR-0003). Per RFC 3986, web browsers mathematically never send URL
hash fragments to HTTP hosting servers or DNS providers. Encryption keys are derived
locally via Web Crypto AES-GCM (256-bit).
Messages and binary file chunks exist exclusively in browser RAM and evaporate the instant a tab is closed or a peer leaves. Zero tracking cookies, zero analytics pixels, zero telemetry beacons, and zero accounts. Local IndexedDB persistence is strictly opt-in and never leaves your machine.
In accordance with ADR-0004, establishing direct WebRTC DataChannels between two computers across the internet inherently reveals each peer's public IP address to participating peers in that room. We transparently disclose this technical reality: if you require IP masking, use a reputable VPN.
Compare what PeerBox does (and does not) touch compared to conventional cloud transfer apps.
| Data Dimension | Standard Cloud Platforms | PeerBox Architecture |
|---|---|---|
| User Identity | Emails, phone numbers, OAuth cookies | None (Ephemeral random Persona) |
| File & Message Storage | Stored on remote AWS/GCP buckets | 0 Bytes (Direct browser memory / OPFS) |
| Encryption Keys | Held or escrowed by cloud server | Local Web Crypto AES-GCM (client-side only) |
| Traffic Logs | Access logs, IP logs, audit trails | Zero server logs (Static GitHub Pages shell) |
| Intermediate Relay Bandwidth | Routed through third-party TURN servers | Zero-TURN (Direct peer-to-peer only) |