The best photos of the event are
spread across every attendee's phone.

Event photography commissioned by the organiser tends to look like event photography: a speaker mid-gesture, a wide shot of a full room, three people in a considered huddle by the branded wall. Useful for the report, and almost interchangeable between one conference and the next.

What actually demonstrates an event worked is the material attendees generate themselves. The two people who hadn't seen each other since a previous job. The queue for a stand that was supposed to be quiet. The half-empty room at 4pm that filled up because word got round. These are photographed constantly, by attendees, and almost none of it ever reaches the organiser.

Gathering it changes what you can do afterwards: your recap, your next year's promotion, your internal case for the budget. All of it is stronger with material that visibly wasn't art-directed.

Any tool that requires attendees to install something is dead on arrival at a corporate event. Half your room is on a managed device where they can't install anything, a proportion are visitors on guest wifi with no interest in your app, and a meaningful number simply won't create an account for a company they met that morning.

That constraint is why this runs entirely in a browser with no attendee account at all. An attendee points a camera at a code, taps a link, selects photos, types their name. Nothing is installed, no credentials are created, and no personal data beyond a name they type themselves is collected. There is nothing for a security team to approve, because there's nothing being deployed.

For the organiser it means the practical answer to "can everyone use this?" is yes — including the contractor, the journalist, the client's client, and the person whose laptop is locked down to within an inch of its life.

Attendees at a work event are more self-conscious than guests at a party, so the ask has to be framed as useful rather than fun. What works is being specific about what you want and where it's going: "Send us your photos from today — we'll pull the best into the recap" outperforms a bare code with a logo, because it explains the point.

The two placements that do most of the work are the holding slide between sessions and the badge. The slide catches a captive seated room at exactly the moment attention drifts to phones. The badge means the code is still on them at the drinks afterwards, which is where the photographs you'll actually want get taken.

Then send it once more the next morning in the follow-up email with the slides. A significant share of uploads arrive from a desk the day after, and they're the best-selected ones, because people go through their camera roll properly when they're not standing up holding a coffee.

Two things make this straightforward. First, uploading is entirely voluntary and the attendee chooses each photo — nobody's camera roll is accessed, and nothing is collected passively. Second, the gallery is private by default: uploads go to the organiser's gallery, not to a public feed, and nothing is visible to the outside world unless you deliberately publish a curated selection.

The data footprint is deliberately small. An attendee supplies a first name and the photos they chose, and nothing else — no email, no account, no tracking of who they are. Everything is permanently deleted a month after the event date by an automated job, which means you aren't quietly accumulating a photo archive of your staff and customers that somebody has to answer for later.

If someone asks for a photo of them to be removed, email us and it's taken out. If your organisation has its own event photography notice, the usual practice is a line on the signage next to the code pointing at it — the same way you'd handle a hired photographer.

Once the event is over, browse the gallery and download the full-resolution originals as a zip. Every photo carries the name of the attendee who took it, which matters more here than at a private event: if you want to use a shot externally, you know exactly who to go back to for permission.

For the public recap, publish a curated highlights gallery. You choose which photos go into it, so the version the outside world sees is a deliberate edit rather than everything anyone happened to upload — and it gets its own link rather than being loose on the internet.

One operational note worth putting in your own calendar: the photos are deleted a month after the event date, permanently and with no backup. Download the zip into wherever your organisation actually keeps things in the first week, not the fourth.