Zero-Knowledge Security Architecture
Cryptographic Privacy by Architecture, Not Just Policy
- DTLS
- WebRTC Encryption
- 0 Bytes
- Server Disk Storage
- WebRTC
- Direct P2P Tunnel
- No
- Account Needed
How Your Data Travels Securely
Every phase of transmission is designed to maintain cryptographic blindness across all intermediate networks.
- Phase 01
Client-Side In-Memory Slicing
Your browser reads files in 64KB binary slices. Nothing is uploaded until the receiver connects.
- Phase 02
Ephemeral Signaling Handshake
A temporary 6-digit code pairs sender and receiver via WebSockets. Only connection details (ICE candidates) are exchanged at this stage—no file content.
- Phase 03
Direct Encrypted P2P Streaming
Peers establish a direct, DTLS-encrypted WebRTC DataChannel and chunks stream device to device. On networks that block direct links, chunks are relayed through our server's memory instead.
- Phase 04
Immediate Memory Dissolution
Incoming chunks assemble into the recipient's local download buffer. When either browser tab closes, the ephemeral link terminates with zero cloud traces.
Six Architectural Pillars of Non-Custodial Privacy
We replace corporate trust with verifiable browser cryptographic guarantees.
Encrypted in Transit
Direct transfers run over WebRTC data channels, which browsers always encrypt with DTLS. If a direct connection is blocked, data is relayed through our server over an encrypted HTTPS/WebSocket connection instead.
Zero-Knowledge & Zero Server Storage
Files are never written to our hard drives or to cloud object storage. Our server introduces the two browsers to each other; when a direct link is impossible it passes data through in memory only, without saving it.
Short-Lived, Unguessable Sessions
Every transfer gets a random 128-bit session ID and a one-time 6-digit code. Codes are rate-limited against guessing, and sessions expire after 10 minutes of inactivity.
Zero Identity Tracking & No Accounts
No account registration, email verification, or identity profiling. File names and sizes are held in memory only while a session is open, so the receiver can see what's coming, and are deleted when it ends.
WebRTC DTLS Transport Layer
Direct DataChannels operate over DTLS (Datagram Transport Layer Security) with SCTP. This provides transport-level encryption and tamper protection between the two browsers.
Hardened Signaling Server
The site is served over HTTPS through our host's CDN. The signaling server accepts same-origin connections only, rate-limits session codes, and only lets a browser exchange data inside a session it has joined.
Threat Model & Vulnerability Comparison
Why zero-storage P2P transfers protect against systemic risks inherent in legacy cloud storage lockers.
| Threat Vector | SendFiles.in (P2P Streaming) | Legacy Cloud Staging (WeTransfer, Dropbox) |
|---|---|---|
| Cloud Storage Database Breaches | Not exposed — Files are never stored on server disks | Vulnerable — Stored for days/weeks on central buckets |
| Subpoenas & Third-Party Inspection | Minimal — No accounts and no stored files to hand over | High Risk — Central hosts retain files, logs, and account IDs |
| Insider Threat & Staff File Access | Limited — No stored files for staff to open | Possible — Server administrators often hold decryption access |
| Man-In-The-Middle Network Sniffing | Protected — DTLS on direct links, TLS on relayed ones | Protected only up to edge server TLS termination point |
| Data Farming & Advertising Telemetry | Low — No accounts; ads and analytics are disclosed in our Cookie Policy | Common — Email profiling and user behavioral tracking |
Responsible Vulnerability Disclosure
Security Researcher or Penetration Tester?
We welcome independent security audits and responsible vulnerability disclosures. If you discover an issue in our signaling relay or WebRTC orchestration, please notify us immediately.
Experience 100% Private File Sharing Today
No registration, no stored files, and zero disk exposure. Start moving your data securely.