Beam app logo

Beam – Privacy Policy

Effective September 25, 2026 · Beam version 1.1 for macOS, Windows, iOS and Android, provided by RiekApps

Key Points

  • Beam sends files directly from one of your devices to another over the local network you are both on. There is no Beam server, and nothing you send passes through RiekApps.
  • There is no account, no sign-up and no analytics or advertising SDK in any version of Beam.
  • To be found, each device announces its name, its kind (Mac, PC, phone) and a random device ID on the local network. Anyone on the same network can see that name.
  • Transfers are verified but not yet encrypted in transit: someone capturing traffic on the same network could read a file while it is being sent.
  • What Beam remembers — your settings, the devices you trust, and a list of recent transfers — stays on each device.
  • Contact: riekapps@gmail.com

1. How Beam Works

Beam is an app for macOS, Windows, iOS and Android that moves photos, videos, documents and text between devices on the same Wi-Fi or local network. The apps find each other on that network and the sending device connects straight to the receiving one. Beam does not use the internet to send a file, and there is no RiekApps server in the middle.

There is no Beam account and no sign-up.

2. What Your Network Can See

So that your devices can find each other, each running copy of Beam announces itself on the local network every few seconds, by UDP broadcast and by Bonjour (mDNS). The announcement contains:

  • the device name shown in Beam (by default your device’s own name, which you can change in Beam’s Settings),
  • the kind of device (Mac, Windows, iPhone, Android),
  • a random device ID created when Beam was first opened, and the network port Beam listens on.

Anyone else on the same local network can see these announcements. On a shared network such as a café, office or hotel, choose a device name you are comfortable showing there.

3. Transfers

When you send, the receiving device is told the names, sizes and types of the files and any text you are sending, together with the name of the sending device, so it can show you what is arriving. The file bytes then go directly from one device to the other.

Every sender proves which device it is by signing a random challenge with its own key, and every file is checked against a SHA-256 hash before it is saved. A file that fails the check is discarded.

Transfers are not yet encrypted in transit. Someone able to capture traffic on the same network could read the contents of a file while it is being sent. On your home network the risk is small; on a shared network it is real. Encryption is planned for a future version, and this policy will be updated when it ships.

4. What Is Stored On Your Device

Beam keeps the following in its own app storage on each device:

  • Your settings: the device name, the folder received files are saved to, whether to accept from everyone, and (on Windows) whether Beam starts with Windows.
  • The devices you chose to trust: their names and key fingerprints.
  • A list of your most recent transfers (up to 50): the file or text name, the other device’s name, the time, and where a received file was saved. The files themselves are not copied into this list.
  • Parts of files from interrupted transfers, so that sending again can resume. These are deleted when the transfer completes, or after seven days.
  • On Windows, a small log file (beam.log) with the times Beam started, the port it used, its firewall status and the text of error messages it showed you, which can include a file name. It never contains file contents and is never sent anywhere.

Files you receive are saved to the folder you chose (Downloads by default). On a Mac and on Windows they are marked as having come from another computer, as a browser does with downloads, so the system can check a received program before it runs.

5. Device Keys And Trust

Each copy of Beam creates its own signing key on the device the first time it runs. The private key is kept in the platform’s protected storage — the Keychain on Apple devices, the Android Keystore on Android, and a file protected by Windows’ data protection (DPAPI) on Windows — and it never leaves the device. Only the public key is shared, with the device you send to. “Always accept from this device” remembers that public key’s fingerprint, locally.

6. Permissions

  • Local network (all platforms): to find your other devices and send to them.
  • Notifications (Android, Mac, Windows): to tell you when a file arrives or a device asks to send.
  • Photos and files: Beam reads only the items you pick or share to it, through the system picker or share sheet, and writes received files to your chosen folder.
  • Windows Firewall: if Windows is blocking other devices from reaching Beam, Beam offers to add a single inbound rule for itself. This asks for administrator approval once and changes nothing else.

7. The Website And Downloads

Beam is downloaded from beam.riekapps.com. Like any website, our hosting provider sees the connecting IP address in server logs, which are kept briefly for operational purposes. The site uses no cookies, analytics or trackers.

8. What RiekApps Never Collects

  • Your name, email, contacts, or any account information.
  • The files, text, file names or device names you send or receive.
  • Usage analytics, crash reports, location or advertising identifiers.

9. Your Choices

You can rename your device, forget any trusted device, clear the recent list and turn off accepting from everyone in Beam’s Settings. Quitting Beam stops it announcing itself; uninstalling it removes the app and its stored data.

10. Children

Beam is not directed at children under 13 and collects no personal information from anyone.

11. Changes

If this policy changes, the new version will be published at this address with an updated effective date.

12. Contact

Questions about privacy in Beam: riekapps@gmail.com. Website: beam.riekapps.com.