How Selfie Search Finds Event Photos—and Protects Face Data

Summary

Pixel shares how FotoNest selfie search helps guests find their event photos using a single selfie, with matches ranked and available for full-resolution download. The announcement outlines the guest and upload flows and explains how face data is processed, a key consideration for event privacy.

DEV Community

How selfie search for event photos works, and what happens to the face data

After any big event (a wedding, a conference, a 10K race) someone ends up holding a folder of a few thousand photos. Everyone in those photos wants the handful they're in. The usual ways of handing them out are a shared Drive or Google Photos link, where everyone scrolls through everything and anyone with the link sees all of it, or a group-chat dump, where photos get buried and recompressed. Selfie search is the pattern a lot of event-photo tools have settled on: a guest takes one selfie, and the system returns only the photos that guest appears in. We build one of these tools, FotoNest. This post walks through how the flow works and, because it's what people actually ask about, what happens to the face data at each step. The guest flow From the guest's side there are five steps: Open the event. The host gets one QR code and one shareable link per event. A guest scans the code or taps the link, in the Android app or in any browser. Sign in with Google. One tap: no password, no OTP, no phone number. Tap "Find my photos" and take one selfie. See the matches. Only the photos you appear in, ranked by how strongly they match. Download. One at a time or in bulk, as the original full-resolution files. The photos arrive from the other direction. The host, the photographers and, depending on the event's privacy mode, the guests add them from a phone camera, a phone gallery, a public Google Drive link or desktop drag-and-drop. Several photographers can upload to the same event at once, and uploads resume if the connection drops. What happens between the selfie and the results Face search systems generally work in two halves. Cataloguing the gallery. When photos are added, each face in each photo is detected and turned into an embedding: a list of numbers that describes the face in a way that stays stable across lighting, angle and expression. Two photos of the same person produce embeddings that sit close together; photos of different people sit further apart. This happens once per photo, not once per search. Searching. The guest's selfie goes through the same process. The system compares that one embedding against the event's catalogue and returns the photos whose faces are closest, best match first. In FotoNest, the selfie becomes an encrypted face embedding, it's matched only against the photos of the event the guest joined, and the results come back ranked by match. A few behaviours follow from that: Group selfies work. If several faces are in one selfie, the search returns photos of any of them, combined. One selfie with your friends returns everyone's photos. Angles and small obstructions are fine. Side and profile shots match, and so do faces behind small sunglasses, a hat or light makeup. A face that's mostly covered won't. Low light, children and twins were all tested, and all work. No tagging, ever. Nobody labels faces by hand. Late photos aren't pushed. If more photos are added after you've searched, you re-run your selfie to pick them up. It's a retrieval flow for after the event, not a live feed during it. No match is an answer too. You get a "photos not found" state and can search again later. Matching quality is the number everyone asks for first. FotoNest's figure, from internal testing, is 99.8% match accuracy. Why sign-in is required Plenty of photo-sharing tools let anyone with the link browse. FotoNest requires Google sign-in for every guest on every event, with no exceptions. The reasoning: a gallery of people's faces shouldn't have anonymous visitors, so everyone inside one is a verified identity. Keeping it to one tap is what makes the requirement bearable at a wedding. Two other controls do similar work: Searching is selfie-only. You search with your own live selfie. You can't upload someone else's photo to find them. Event URLs are auto-generated, with no custom slugs, so nobody can guess a URL from an event's name. The three privacy modes The host picks a mode when creating the event, and it locks once the...
How Selfie Search Finds Event Photos—and Protects Face Data
Powered by Readybot.io

The latest from Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …