There is no single yes or no on face recognition at Indian events: the Digital Personal Data Protection Act, 2023 is commencing in phases, and the safe organiser practice is opt-in consent, a stated purpose, a retention period, a deletion route and a written vendor answer. This guide is not legal advice; ask your counsel.
The honest legal picture
Organisers often want a clean answer: is it legal or not? The accurate answer is that the rules depend on facts and on law that is still taking effect. The Digital Personal Data Protection Act received assent on 11 August 2023. Its commencement is phased: Data Protection Board provisions from 13 November 2025, further provisions from 13 November 2026, and all remaining provisions by 13 May 2027 (Wikipedia summary of the Act, 2025). Today is 19 October 2026, so the next phase is weeks away.
We are an event-technology company, not your lawyer. What we can do is describe how a careful organiser sets up a face-matching feature so that it is easy to defend: the guest chooses, understands and can leave. For the design principles behind that, read our post on consent-first facial recognition at events. This guide is the practical checklist.
Step 1: decide whether you need face matching at all
A photo finder is a convenience. It turns a big gallery into a personal one. Ask whether your guests need it. A three-hundred-person wedding with one photographer and a shared album may not. A conclave with four thousand photos and guests who want only theirs may.
If the answer is no, do not switch it on. Not collecting a selfie is the strongest compliance position there is.
Step 2: define the purpose in one sentence
Write the purpose and keep it narrow: “Your selfie is used to find photos you appear in from this event’s gallery.” Anything beyond that, such as using the selfie for entry, marketing or analytics, is a separate purpose and needs its own consent and its own legal review. Keep face matching out of the entry gate unless you have taken advice.
Step 3: design the consent moment
Consent should be given by a clear action, in plain words, at the moment of use. The participant taps to start, reads what the selfie is for and saves it. Nobody is matched because they attended, or because they ticked a box at registration three weeks earlier.
Check your text against five questions:
- Is it in a language the guest uses?
- Does it say what the selfie is used for?
- Does it say how long it is kept?
- Does it say how to stop and delete?
- Can a guest use the rest of the app without agreeing?
If the answer to any of these is no, rewrite it.
Step 4: scope the gallery you search
Face matching only works on photos you have published. Decide which albums are in, who uploads, whether guests can download and whether Owners and Managers can remove media. A strong consent text does not help if a family album is public. Separate two decisions: what photos exist, and who can find themselves in them.
For weddings and family occasions, think about children and elderly guests. A parent may not want a child matched at all. Agree a rule with the family and document it.
Step 5: fix retention and deletion in writing
Agree, before launch, what happens to saved selfies and to match results when the occasion closes or when a participant leaves. The table below is a checklist, not a standard.
| Question | Your written answer |
|---|---|
| How long is a selfie kept after the event? | A stated period, agreed per occasion |
| Can a participant delete their selfie? | Yes, through an account or deletion route |
| What happens to published photos after closing? | Archive, delete or restrict |
| Who can see match results? | The participant only, or the organiser too |
| Which sub-processors handle matching? | Named in the vendor’s disclosure |
A vendor who cannot answer a row in writing is telling you the feature is not ready.
Step 6: prepare for the awkward requests
Someone will ask to be removed from every photo. Someone will ask for the photo of themselves deleted from the family album. Decide the process now: who receives the request, who removes the media and how quickly you reply. A written process and a named person turn an awkward request into a routine one.
Step 7: record what you agreed
Keep a one-page record: purpose, consent text, retention, deletion route, vendor answers and date. If anyone asks later, you can show what the guest saw and what the organiser decided.
What this does not cover
This is not a statement that any specific use is lawful. Consent is one element of the Act; others include notice, security safeguards, children’s data and the roles of fiduciary and processor. Your counsel can tell you which apply and when. If the audience includes minors, public officials or people in sensitive roles, take advice before you start, not after the first complaint.
A short script for the person at the desk
Guests will ask what the feature is. Give the front-desk team three sentences to use: “This is an optional photo finder. You save one selfie and the app shows you photos from this event that match it. You can stop at any time and ask us to delete your selfie.” If a guest hesitates, say they can use the gallery without it. A calm, short answer protects the guest and the organiser alike.
How Sociana handles this
Smart Lens is a finder inside the event app. The participant saves one selfie, and the app returns gallery photos that match it. It searches only photos the organiser has published, and whether it is offered, and the consent wording shown, is agreed with the organiser for each occasion. We recommend keeping face matching out of the entry gate. Gallery albums and download controls let the organiser moderate media and allow or block downloads, and the admin panel holds roles and activity logs. Sociana is not a photographer platform: it does not do camera-to-cloud transfer, culling or selling.
The Tanvi & Rutwik wedding app (a three-day Pune wedding) is in its pre-event build. Its build notes name moderation of memories and wishes, group visibility and document retention as the three things to settle before publishing.
Frequently asked questions
Do I need consent if the photos are already public?
Treat consent for matching as separate from the photo being shared. A person who agreed to be photographed at a wedding has not necessarily agreed to biometric matching. Take advice and keep the feature opt-in.
Can I use face matching for entry?
We recommend against it. Sociana uses QR entry passes, organiser scans and self check-in for entry, and keeps Smart Lens as a gallery finder.
How long can I keep selfies?
The length is a decision you make, with advice, and write down before launch. Shorter is easier to defend than longer.
What if a guest asks to be removed?
Have a named person and a process. Remove the selfie, stop matching for that guest and, if requested, take down specific photos from the gallery.
Related reading
Glossary: Smart Lens, photobooth, whitelist. Occasion hubs: weddings, social celebrations and conferences. See our trust pages for how we handle data, and templates and checklists for a consent record.