Privacy

Applies to the qbeam apps for Android and iOS, the qbeam command-line tool and the web receiver at qbeam.dev/r. Last updated 2 October 2026.

The short version

qbeam collects no data. There are no accounts, no analytics, no ads and no tracking. Files move from one screen to a camera and never pass through a server.

The apps

• Camera. The app uses the camera only while it's open, to read the codes on the sending screen. Frames are processed on the phone and discarded; nothing is recorded or uploaded.
• Received files are saved on your phone only: in Downloads/qbeam on Android, and in the app's folder in the Files app on iOS. Deleting them, or the app, removes them.
• No network. The Android app doesn't request internet access, and the iOS app makes no network connections.
• Purchases. If you buy the one-time unlock, Google Play or the App Store handles the payment. We receive only the store's sales reports, which don't identify you to us.

The command-line tool

It makes no network connections: no telemetry and no update checks. Installing it from PyPI or npm is governed by those services' own policies.

The website and web receiver

qbeam.dev is a static site hosted on GitHub Pages, which may log requests (such as IP addresses) under GitHub's privacy statement. The receiver at qbeam.dev/r runs entirely in your browser: the camera stream and the files you receive stay on your device. Once added to your home screen it works offline.

Security of a transfer

Anyone who can see the sending screen can read an unencrypted transfer. Use --encrypt to protect it with a passphrase (AES-256-GCM), and only move data you're authorised to move.

Contact

Questions or concerns: open an issue on GitHub.