Last updated: July 26, 2026
Share2Me is built on a strict zero-knowledge architecture. All file and text transfers are end-to-end encrypted directly in your browser using AES-GCM-256 before being sent over the network. Our servers only facilitate the initial WebRTC connection (signaling) and route encrypted chunks. We never possess the decryption keys, meaning we cannot read, view, or access your data under any circumstances.
For the purpose of maintaining service stability and preventing abuse, our signaling servers temporarily hold connection metadata (such as the 6-digit OTC code and IP addresses) strictly for the duration of the active transfer. Once the browser session is closed or the transfer completes, this metadata is instantly purged from memory.
Share2Me may use local browser APIs (like Web Workers or temporary buffers) to encrypt, decrypt, and piece together data chunks during an active transfer. This data resides solely on your device and is discarded when you close the browser tab.