Your attendee recording policy
Wearable cameras that recognize faces and record on their own are no longer hypothetical. Ten decisions to make before they walk into one of your session rooms, plus language you can paste into your registration terms today.
The rule you never had to write
Event organizers have always decided who may record in their rooms. Press access, AV capture, sponsor filming, closed-door sessions: those are settled questions with settled processes.
Attendee-worn devices that identify people automatically break that model, because the decision arrives through a channel you do not control and the person being recorded did nothing to start it. A published Meta patent application describes glasses that recognize the people in the wearer's line of sight, rank them by relationship, capture clips when something notable happens, and assemble a highlight reel afterwards. It is an application rather than a granted patent, and filing is not shipping, but the hardware is already on people's faces.
Two questions decide whether any of this reads as a service or as a violation: who initiated the recognition, and who gets the benefit. Every item below comes back to those two.
Ten decisions, three phases
Before the event
Decisions that have to exist in writing before anyone travels.
Take a position on attendee-worn recording devices
Three stances are defensible: permitted, permitted with named exceptions, or prohibited in specific spaces. Pick one. Having no position is also a position, and it is the one that ages worst, because the default gets set by whoever arrives with the newest hardware.
Define the spaces where recording is off
Restrooms, prayer and wellness rooms, medical and nursing rooms, private meeting pods, and any session you sold as confidential or under Chatham House Rule. Name the rooms, not the products.
Write the rule about behavior, not about devices
No recording in this room still works in three years. No Ray-Ban Meta glasses is obsolete the moment a competitor ships. Device-specific rules force you to rewrite the policy every hardware cycle, and leave gaps in between.
Put it in the registration terms, not only on the signage
Consent collected at the door is consent collected after somebody has already booked a flight. If attending means accepting a recording policy, say so at the point where attending is decided.
Brief speakers and sponsors separately
They agreed to be in a room. They did not agree to be recognized, clipped, ranked and re-published. A speaker who declined your AV crew has in practice declined an attendee wearable too, and most run-of-show documents do not reflect that yet.
At the event
Making the policy visible and enforceable in the room.
Signage that states the behavior at the door of each space
One line, at the entrance, in the same place every time. Attendees should never have to guess the rule for the room they are walking into, and staff should never have to interpret it.
Give attendees a visible way to opt out
A lanyard color, a badge marker, a wristband. Whatever you choose, decide in advance what it obliges your photography team and your photo platform to do, because an opt-out that only exists on the badge is decoration.
Brief the people who enforce it
Room monitors, AV crew and registration staff need one sentence they can say out loud and one escalation path. A policy nobody on the floor can quote is not in effect.
Your own stack
The part most organizers skip, and the part a member or a works council will ask about first.
Know which of your vendors process biometric data
Photo matching, badge collection with face verification, access control, session analytics, crowd heat-mapping. Storing an image and creating a biometric template are legally different things. Ask which one each vendor does, in writing, rather than assuming.
Know who initiates a match, and how long the data lives
Attendee-initiated matching, where somebody uploads their own photo to find themselves, and organizer-initiated matching, where you run a list against a gallery, are different products with different footing even when the underlying model is identical. Know which mode your event runs, know the retention period for biometric data separately from the retention period for photos, and know both before somebody asks.
Language you can paste today
Starting points, not legal advice. Replace anything in square brackets, and have your own counsel confirm the wording for the jurisdictions your attendees come from.
Registration terms
Add to the terms an attendee accepts at the point of registration.
Recording at this event. Photography and video by the organizer and its appointed suppliers take place throughout the event. Recording by attendees, including with wearable cameras, smart glasses and any device capable of automated capture or facial recognition, is permitted only in general session and networking areas, and is not permitted in [list restricted spaces]. Sessions designated confidential may not be recorded by any party. Attendees who do not wish to appear in organizer photography may request a [opt-out marker] at registration.
Room and session signage
One card at the entrance to every space. Keep the wording identical across the venue.
RECORDING IN THIS ROOM: NOT PERMITTED. This applies to phones, cameras, wearable devices and smart glasses. If you are unsure, ask a member of event staff before you record.
Vendor and supplier clause
For contracts with any supplier whose system may process attendee faces.
Supplier shall not create, store or process biometric identifiers derived from attendee images except as expressly instructed by Organizer, shall scope any such processing to this event only, shall not use attendee images to train or improve models, and shall delete all biometric identifiers within [N] days of the event on an automated schedule, evidenced on request.
Want a copy to send to your legal team?
The ten decisions, the sample registration and signage language, and the seven vendor questions, as a PDF you can forward or paste straight into your registration terms. No sales call attached.
Seven questions for any vendor touching attendee faces
Ask them in writing, before renewal. Every one has a short answer, and a supplier who cannot give it quickly has told you something useful.
| Ask | What a real answer sounds like |
|---|---|
| Does your system create biometric templates, or only store images? | A direct yes or no, plus where the templates live. A vendor who cannot distinguish the two is not equipped to answer the rest of this list. |
| Who initiates a match? | A clear statement of which modes the product supports and which one your event will actually run. Attendee-initiated and organizer-initiated are both legitimate. Conflating them is not. |
| What is the scope of comparison? | Matching runs against the photos of this event only, and never against a cross-event or third-party gallery, unless you specifically asked for that and can justify it. |
| How long is biometric data retained, and is that separate from photo retention? | A stated number of days for each, applied automatically on a schedule rather than on request. Deletion that happens only when somebody remembers to ask is not a retention policy. |
| How does an attendee withdraw and get erased? | A named route, a stated turnaround, and confirmation that erasure covers the biometric template and not only the visible gallery entry. |
| Do you use attendee images to train or improve models? | No, stated in the contract rather than on a sales call. If the answer is yes, you need to know it before your attendees do. |
| Which frameworks have you been deployed under, and can you provide the paperwork? | A data processing agreement you can send to counsel, and specific awareness of GDPR, CCPA and BIPA rather than a logo wall. Illinois and the EU are where this gets expensive. |
How Kampfire answers them
We build a facial recognition product, so these questions apply to us too. Matching is scoped to a single event's photos and never to a cross-event gallery. The face data behind a match lives in a per-event collection that is deleted automatically on a schedule rather than on request. Consent is reported per campaign, so an organizer can evidence it rather than assert it. The agreements and policies behind all of that are on our security and compliance page.
Run facial recognition at your event on purpose.
See how attendee-initiated photo matching works, and what we hand your legal team before you sign.