FlashDrop Pro is a browser tool for peer-to-peer transfer, not a cloud “inbox” for your content.
What we optimize for: moving bytes directly between two browsers with WebRTC when the network allows. The file payload is not uploaded to FlashDrop Pro as a hosted download link backed by our storage in the way traditional “send files” web apps do.
What still exists in the real world: small amounts of signaling—session codes, ICE candidates, and metadata so both sides can find each other—may traverse third-party infrastructure (e.g. WebRTC signaling providers). That is not the same as storing your file on our servers as the product’s delivery mechanism. If strict NAT or firewalls block P2P, the transfer may fail; we still don’t position ourselves as the cloud mailbox for your blob.
Cloud inbox vs browser P2P (plain language)
| Typical cloud “send” flow | FlashDrop Pro (this app) |
|---|---|
| You upload; their servers hold the object until downloaded or expiry. | Peers exchange directly when WebRTC succeeds; no FlashDrop-operated cloud inbox for the payload. |
| Terms may cover scanning, AI training, or analytics on content—read each provider’s policy. | Optional AES-256-GCM adds a password layer in your browser; we don’t receive that password. |
| Mobile/Wi‑Fi drops can interrupt uploads to the cloud. | When supported by the browser, local checkpointing can resume partial receives from device storage—useful on flaky networks. |
Industry context (without naming outcomes)
Large file-transfer brands have revised terms, AI-related language, collaboration features, and free tiers as ownership and product strategy evolve. Users comparing vendors should read the current Terms and Privacy notices for each service. FlashDrop Pro’s differentiator for privacy-conscious users is architectural: peer delivery with optional extra file encryption, not a centralized inbox copy of your data.
No AI training on your payload
FlashDrop Pro does not use your transferred file contents to train AI models. Your payload is delivered peer‑to‑peer; we don’t run a cloud inbox that stores it.
What happens during a transfer
A quick timeline so you can reason about exposure points.
1) Stage locally: you pick files in your browser; they’re not uploaded as a hosted link.
2) Find each other: small signaling data (codes + ICE) helps peers connect.
3) Transfer: WebRTC delivers data between devices; optional AES-256 adds a file password layer.
4) Save: receiver stores the file locally; session expires by time/limits.
Security you can see during a session
In the app, live badges summarize transport (WebRTC), ECDH session verification state, ICE path (direct / NAT / relay), and whether optional AES-256-GCM is applied to the file layer—so the protection story is visible while you transfer, not only in documentation.
Try FlashDrop Pro
Direct browser-to-browser transfer with visible security signals.
Useful if you want to link this privacy promise in discussions, comments, or reviews.
This page explains product intent and architecture; it is not legal advice. For retention, accounts, and jurisdictional detail, see our Privacy page.