agniwar uses a signaling service to introduce browsers. The service observes your network address, temporary device identity, browser-reported device category and connection setup messages. It does not store or process file contents.
Finding and connecting
Devices sharing a public network address can appear together automatically; this is not the same as a verified shared Wi-Fi network. Carrier-grade NAT and VPNs can group unrelated people or separate nearby devices. In local development, the server also groups devices on its directly attached private IPv4 subnets. Neither mechanism proves that devices share Wi-Fi.
Where file data goes
After explicit approval, files are sent using an encrypted WebRTC data channel, normally directly. If a TURN relay is configured and used, encrypted traffic passes through it. Each file is checked with SHA-256 before it is offered for saving. Signaling is not end-to-end authenticated against a compromised server, so verify the recipient by another channel for sensitive files.
What stays temporary
The signaling server maintains availability in memory while browsers are connected. Verified files may remain in browser storage for re-download, subject to eviction or site-data clearing. A selected destination folder and browser Downloads are separate copies. An interrupted transfer may leave temporary site data; clearing site data does not delete files saved elsewhere.
What “nearby” does not prove
Discovery is a convenience, not identity verification. A shared public IP can include unrelated users, and local development groups by the server host’s directly attached subnet. Check the recipient’s name and confirm sensitive transfers through a separate trusted channel.