Files, beamed device to device.
Nothing in the middle.

Pick files, share a one-time code, done. End-to-end encrypted over a direct connection — nothing is uploaded, nothing is stored, and delivery comes back verified. No account to send or receive.

Drop files here, or click to choose

Files stay on this device until the other side accepts.

↑ This is the whole app — no install, no signup

How it works

Send and share files in three steps

Both devices open this page. One sends, one receives — phones, laptops, whatever has a browser.

beam-7-otter-quartz
STEP 1

Pick files, get a code

Drop your files in and Beamaroo mints a one-time code. Your files haven't gone anywhere — they stay on your device until the other side says yes.

STEP 2

Share it — say it, text it, scan it

Codes are four friendly words. Read it across the room, paste the link, or point a phone camera at the QR. The code pairs exactly two devices, then it's burnt.

STEP 3

They accept, it beams across

Files stream straight between the two devices, encrypted end-to-end. Every file is integrity-checked on arrival and the confirmation comes back to the sender: delivered, verified.

A simpler way to share files

Most tools upload your file to a server, sit it in a bucket somewhere, and hand the other person a link to download later. Beamaroo doesn't. When you send files with Beamaroo they travel straight from your device to theirs — a live, peer-to-peer beam, encrypted end to end, with nothing parked in the middle.

That's the whole idea behind the name. You beam it, they catch it, and the moment the transfer finishes there's no copy left on any server to leak, expire, or get scanned. No account to sign up for, no app to install — just two browser tabs and a short code.

The trade-off is honest: it's a live transfer, so both devices need to be online at the same time — there's no leaving a file to download tomorrow. If that suits you, Beamaroo is the fastest, most private way to share files device to device. Nothing in the middle.

Privacy

Private by construction, not by promise

We didn't write a policy saying we won't look at your files. We built it so we can't.

  • End-to-end encrypted Transfers run over WebRTC's DTLS encryption. The keys live on your two devices and nowhere else.
  • No servers holding your files Bytes go device to device. Our server only introduces the two ends — it never sees file names, contents, or your code words. If a direct path isn't possible, an encrypted relay passes the bytes along without being able to read them.
  • Delivery comes back verified Like a boomerang, every transfer returns: the receiving device checks each file's fingerprint and confirms it landed intact. "Delivered ✔" means verified, not just sent.
  • Codes are single-use A code pairs one sender with one receiver, once. Used, mistyped by a stranger, or expired — it's burnt either way.

Under the hood

Nothing stored — by architecture, not by policy

Most "private" file tools ask you to trust a promise: we'll delete your file after a week, we won't look at it, we won't train on it. That's a policy — and policies change, as WeTransfer's users found in July 2025 when a terms update briefly claimed the right to train AI on uploaded files. Beamaroo doesn't ask for that trust, because there is no file on our side to make a promise about. Your file is never uploaded: it travels directly from your browser to the other person's over an encrypted connection, and our server's only job is to introduce the two devices — it never receives the file, its name, or your code. When a direct link isn't possible, an encrypted relay forwards scrambled bytes it cannot read; even then, nothing is kept. "Deleted after 30 days" still means a copy sat on a server for 30 days, waiting to leak, be subpoenaed, or fall under new terms. "Never uploaded" means it was never there at all — the difference between privacy by policy and privacy by architecture, and the whole reason Beamaroo works the way it does.

What a verified pairing code actually does

When you send with Beamaroo you share a short code like beam-7-otter-quartz — three friendly words and a number. It looks casual, but it's doing real work. A normal share link is a bearer token: anyone who gets it can grab your file, and you'd never know. A Beamaroo pairing code is verified — it cryptographically proves the device on the other end is the one that typed your exact code, and nothing else can slip into the connection. Get one word wrong and the channel burns on the spot; there's no second guess and no brute-forcing the list. So a code read aloud across a room, texted, or scanned from a QR pairs exactly two devices and then stops working. It's the difference between "anyone with the link" and "the one person I gave the code to" — verification, not just a hard-to-guess address.

Delivery receipt — you'll know it landed

With most tools, "sent" just means the file left your hands and reached a server. You don't actually know whether the other person got it, or whether it arrived intact. Beamaroo gives you a delivery receipt: the receiving device checks every file against its fingerprint and beams a confirmation back to you — "Delivered, verified on their device." Like a boomerang, it comes back. If a single byte were wrong you'd know; if it never arrived, you'd know that too. For anything that matters — a contract, a tax return, a final cut — "probably sent" isn't good enough. A verified receipt is.

Why both devices are online at once — and why that's the point

Here's the honest trade-off: Beamaroo is a live transfer, so both devices have to be online at the same time. There's no leaving a file to be collected tomorrow — and if that's what you need, a cloud service is the better tool. But the constraint is also exactly why nothing is ever stored. A "pick it up later" service can only work by parking your file on a server in the meantime; that stored copy is the thing that leaks, expires, or gets scanned. Beamaroo's live-only model is the reason there's no copy sitting anywhere, no link to leak, no bucket to breach. The limitation and the privacy are the same fact, seen from two sides.

FAQ

Fair questions

Short honest answers.

Do both devices need to be online at the same time?

Yes — Beamaroo is a live beam between two devices, not a locker. That's the point: your files never sit on anyone's server waiting to be fetched.

What if we're on different networks?

Beamaroo always tries for a direct device-to-device path. When a network won't allow one, an encrypted relay carries the traffic — it forwards scrambled bytes and can't read them.

Could someone guess my code?

They'd need the exact words within the few minutes the code lives, and the first wrong attempt burns the channel. Even the connection itself is verified against the code — a wrong code can't silently connect to the wrong device.

What's with the boomerang?

Beamaroo is built in Brisbane, Australia. A boomerang comes back — and so does every transfer: delivery is confirmed to the sender, verified on arrival. It's the whole product in one shape.

Do my files ever touch your servers?

No. Your file goes directly from your device to the other person's, encrypted end to end. Our server only introduces the two devices — it never receives the file, its name, or your code words. If a direct connection is blocked, an encrypted relay forwards scrambled bytes it can't read; even then, nothing is stored.

How big can a transfer be?

There's no cap on what you can choose to send, but today the receiving browser holds each file in memory before saving, so a beam is happiest under a gigabyte or two — larger multi-gigabyte transfers are limited for now. Streaming straight to disk — which lifts that ceiling — is on the roadmap. For everyday files, photos, videos and documents, you're well within range.

Beamaroo

Peer-to-peer via WebRTC · codes are single-use · your files never touch a server
© 2026 Beamaroo · Made in Brisbane, Australia · Privacy · Terms