Beacons

One channel. The same people. Every time you send.

A beacon is a named, encrypted channel you share with a fixed group. Create it once, add the people once, and from then on simply publish to it — every member sees what you post, and every file stays end-to-end encrypted.

Why beacons exist

A single transfer is built for a one-off: upload, send a link, done. That falls apart the moment you are sending to the same people every week.

No more starting over
Sending to the same ten people each month means ten fresh invitations every time. A beacon keeps the audience in place, so publishing again is one step instead of ten.
One place to look
Scattered links get buried in inboxes. Members open the beacon and find everything published to it, in order, without hunting for the right email.
Access you can take back
Revoking a share link means chasing whoever received it. Remove someone from a beacon and their key is deleted — access ends everywhere at once.
How it works
1
Create the beacon
Give it a name and choose whether it stays private or is listed publicly. You get an address for the channel, and you are its owner.
2
Add the people
Add members by the email on their account. Publishers can post new shares to the channel; viewers can only read what is published.
3
Publish and grant access
Attach a share you have already uploaded, then grant access. Your browser wraps the file key to each member individually — the server never sees it.
Who can do what

Every beacon has one owner, and any number of publishers and viewers.

Owner
Creates the beacon, adds and removes members, changes its name and visibility, and can delete it. Is a publisher as well.
Publisher
Attaches shares to the channel and grants members the keys to open them. Cannot change who belongs to the group.
Viewer
Reads the channel and downloads what has been published to it. Cannot post anything.
Private or public
Private
The default. Only members can see the beacon or anything in it. To everyone else it simply does not exist — no page, no error, no hint that the channel is there at all.
Public
Anyone with the address can browse what has been published — titles and dates, nothing more. Downloading still requires being a member, so a public beacon is a shop window, never an open door.
Still end-to-end encrypted

A beacon changes who a file reaches, not how it is protected. Files are encrypted in your browser before they are uploaded, and the key that opens them is wrapped separately for every member using their own public key. We never hold that key, so we can never read what you publish — not to a beacon, not anywhere.

That is also why removing someone works instantly and completely: their copy of the key is deleted, and nothing else has to change. The files stay where they are, and everyone else keeps their access.

What people use them for
Recurring client delivery
Monthly reports, drafts and finished work going to the same client team, in one place they already know.
Board and investor updates
A standing channel for the people who receive every update, with access that ends the moment someone leaves.
Branch and franchise rollouts
Publish once to every location instead of mailing the same files to a dozen addresses.
Ongoing case files
Long-running matters where documents arrive over months and everyone involved needs the current set.

Beacons are part of the paid plans — any paid subscription includes them. Members you invite do not need one; a free account is enough to receive.

Common questions

Yes. Access is tied to each person’s own account and keys, which is what makes it individually revocable. Members are added by the email on their account, and a free account is enough. Only creating a beacon requires a paid plan.

No. A public beacon lists what has been published so people can find it, but opening a file still requires being a member with access granted to you. There is no anonymous download, by design.

Their key is deleted and they immediately lose access to everything the beacon gave them. If they also received one of those files through a direct share, that separate access is left untouched.

A beacon holds as many shares as you attach to it. The usual limits of your plan still apply to the files themselves — size, retention, and how many transfers you send.
Ready to set one up?
Create a beacon, invite your group, and publish.