“Private” often means a service still receives your file but promises to handle it carefully. PixeDrop takes a narrower architectural approach: the transfer payload never goes to a PixeDrop server.
A visible, local data path
The web sender compresses and encodes content inside your browser. It displays a sequence of QR frames. The iPhone app scans those frames and reconstructs the content on the device.
The path is deliberately short: browser → screen → camera → iPhone. There is no upload endpoint, transfer account, inbox, or cloud copy in the middle.
What that removes
- No transfer database to breach or misconfigure.
- No payload retention policy to interpret.
- No account identifier attached to the transfer.
- No network dependency once the sender page is available.
The iPhone app declares that it does not collect data. The website also avoids analytics and tracking SDKs. Its public pages still use ordinary server access logs at the hosting edge, but the content you choose to transfer is not sent in an HTTP request.
The tradeoffs are real
Optical transfer is not a replacement for a cloud drive. It needs both devices in the same place, works best with a steady camera view, and is capped at about 1 MB per transfer. Larger payloads take more frames and more time.
Those limits are acceptable for the intended jobs: a terminal snippet, a screenshot, a small configuration file, or a document that should move directly between nearby devices.
Privacy you can reason about
The useful property is not a slogan. It is the absence of a transfer backend. You can save the offline sender as one HTML file, disconnect the computer, and complete a transfer with no network at all.