// INSIGHTS
AI Photo Galleries: Finding Yourself by Face at an Event
6 min read
A three-day conference produces somewhere between eight and fifteen thousand photographs. Every delegate wants the four they appear in. Scrolling is not a solution, and neither is a shared drive link that nobody opens. Face search solves the retrieval problem: a delegate takes a selfie, the system returns their photos in a few seconds. The engineering is well understood. The consent and retention design is the part that needs real care, particularly under India's DPDP Act.
How face search actually works
The pipeline has four stages. A photographer uploads a batch. A detection model finds every face in each frame. An embedding model converts each face into a numeric vector, typically a few hundred dimensions, which is stored in a vector index alongside a reference to the photo. When a delegate takes a selfie, the same model produces one vector and the system runs a nearest-neighbour search against the index, returning every photo whose faces fall inside a distance threshold. No names are involved at any point unless you deliberately link them.
Threshold tuning is where the quality lives, and it is a straight trade between two kinds of error. A loose threshold returns photos of other people, which is a privacy incident rather than an inconvenience. A tight threshold misses the delegate in the group shot taken from thirty feet away in a dark ballroom. We tune conservatively towards fewer false positives, then compensate with a browse-by-session fallback and a clear way for a delegate to flag a photo that is not them. Indian and Gulf events add specific challenges: heavy stage lighting, spectacles, turbans and dupattas partially framing the face, and large formal group photographs where individual faces occupy very few pixels.
Throughput is the operational constraint. Photographers upload in bursts, often four hundred frames at a time between sessions, and indexing has to keep pace so the gallery is useful during the event rather than a week later. Serve previews through a CDN at modest resolution with a watermark, and release full-resolution files on request. That keeps bandwidth costs sane and gives the organiser control over how the images get used.
Gallery scale for a three-day event
What the gallery has to include
Selfie-based search
One photo from the front camera returns the delegate's images, with a browse-by-session fallback for anyone who declines. Nobody should be forced into face search to see the gallery.
Separate, explicit consent
Face matching is consented to on its own, in plain language, at registration, in English and the relevant local language. A general line about photography being taken on site does not cover it.
Working opt-out and takedown
Withdrawing consent deletes the face vectors, not just the delegate's view of the gallery. Takedown requests for a specific photo route to a named organiser and resolve within a stated window.
Sharing that people will use
Direct WhatsApp share, bulk download of a delegate's own photos, and full-resolution originals on request. Galleries that only support one-by-one downloads get abandoned.
Standing up a face-search gallery
Write the consent language first
Legal wording goes into the registration form before development starts, because it determines what the system is allowed to store. Retrofitting consent after an event is not possible.
Wire the upload path
Give photographers a wired or dedicated connection and an upload agent that resumes after a drop. Four hundred files over hotel Wi-Fi at midnight is a predictable failure.
Tune on a test set
Use a few hundred images from a comparable venue and lighting setup to set the distance threshold before day one. Tuning live, against real delegates, means tuning with real mistakes.
Set the deletion date
Agree the retention window with the organiser, put it in the consent notice, and schedule the deletion job so it runs without anyone remembering. Retention that depends on someone remembering does not happen.
What usually goes wrong
Consent handled as an afterthought is the most serious failure, and it is common. The DPDP Act requires clear notice and purpose limitation, and a blanket line in the terms saying photographs may be taken at the venue does not constitute informed consent for biometric matching against a stored face index. Delegates need a separate, plainly worded checkbox, a version in Hindi or the relevant regional language, and an opt-out that genuinely removes their face vectors from the index rather than just hiding results from them. For UAE events, run the same review against the applicable federal data protection law and confirm where the data physically sits.
The technical failure that matters most is a threshold set too loosely. When a delegate opens the gallery and sees photos of a stranger, that is not a false positive to be tuned away later, it is somebody's images being shown to a person with no right to them. Be conservative and accept that some group shots will be missed. Two operational problems round out the list: photographers with no reliable upload path, which quietly means no gallery until the event is over, and galleries left sitting in an open storage bucket for years after the event. Set the deletion date, automate it, and tell delegates what it is.
Common questions
Do you store delegates' faces?
The system stores numeric embeddings derived from faces, plus the event photographs themselves. The selfie used for searching does not need to be retained beyond the search and can be discarded immediately. On opt-out or at the end of the retention window, embeddings are deleted, which removes the ability to match that person entirely.
How accurate is it in poor light or large group shots?
Accuracy is very good for well-lit photos where the face occupies a reasonable share of the frame, and it degrades on distant group shots, heavy backlighting and partial profiles. We tune towards missing a few photos rather than returning the wrong person's. A browse-by-session view covers what face search misses.
What does the DPDP Act require for event photography?
In practice: clear notice of what is collected and why, consent obtained for that specific purpose, a defined retention period, and a workable mechanism for withdrawal and deletion. Face matching is a distinct purpose from taking photographs, so it needs its own consent. Get this drafted with the organiser's legal counsel before registration opens, not after the photos exist.
Photos your delegates can actually find
Tell us your photo volume and retention requirements and we will scope the gallery.


