Short answer
Before licensing workplace video for AI training, establish who appears in it, what each group was told or agreed to when it was recorded, whether that covers model training and transfer to you, and how withdrawal is handled. Employees, contractors, customers and bystanders need separate answers. Blurring or anonymization lowers identifiability but does not supply permission that was never given. This is diligence, not legal advice.
This is not legal advice. Use the questions below to brief counsel.
Why the people in the frame come first
Most rights questions about workplace video concern things: a vendor's course, a client's goods, an equipment maker's manual. People are different. The worker whose face, hands and voice fill a clip has interests the business holding the file may not be able to license, and those interests travel with the footage.
Robot-learning data makes this sharper: you buy demonstration video because it shows a body doing the work, so training value and identifiability sit in the same pixels. Purpose matters too. Footage made to train staff, check quality or secure a site was recorded under a notice describing that purpose, and licensing it to an outside company for model training adds a new use and a new recipient. The wider license-or-record choice is covered in existing footage vs commissioned recording.
Who appears, and what to establish for each
| Who | Relationship to the recording | What to establish | Common gap |
|---|---|---|---|
| Employees filmed as demonstrators | Subject of the clip | Exact notice or release wording; whether taking part was optional | Covers staff training, not model training or transfer |
| Co-workers in frame | Captured incidentally | Whether the workplace notice reached them | No individual agreement |
| Agency and contract staff | Employed by another organization | Who gave notice; whether agency terms mention recording | The site's policy never reached them |
| Customers, patients, guests | On the premises, sometimes close up | Any notice beyond signage | Nothing covering AI use; no way to contact them |
| Former employees | Left before AI use was considered | Whether any contact route remains | Re-notice is often impractical |
| Minors | Occasionally present in retail, hospitality or care | Whether they appear at all | Usually grounds to exclude the clip |
Signed releases for every demonstrator say nothing about the customer standing behind them.
What the notice or consent must cover
Read the actual text, with version dates, against your planned uses:
- Purpose. "Recordings may be used for training purposes" in a staff handbook most likely meant training people. Look for wording that names AI or model development.
- Recipients. Internal use only, or licensing to third parties and their contractors, such as annotation vendors?
- Data types. Video, audio and what will be derived from them, such as hand pose, body pose and gaze. Derived body data can raise its own questions; see biometric privacy laws and workplace video.
- Retention and withdrawal. How long recordings may be kept, and how a withdrawal request reaches a licensee.
- Freedom to decline. Whether staff could refuse to be filmed without any effect on their job.
The employment setting matters: agreement given to an employer can be weighed differently from agreement given to a stranger. In the EU, the GDPR lets Member States set more specific rules for employees' personal data, by law or collective agreement, under Article 88(1) (European Parliament and Council of the EU, 2016). European regulators have issued guidelines on video devices (European Data Protection Board, 2020), and the UK ICO's guidance on monitoring workers recommends a data protection impact assessment where monitoring is likely to result in a high risk to workers (Information Commissioner's Office, 2023). See EU AI Act and GDPR considerations for the wider EU picture.
In the US, much depends on the state where recording happened. Illinois's Biometric Information Privacy Act defines biometric identifiers to include a scan of hand or face geometry (Illinois General Assembly); ask counsel whether hand or face data you plan to derive from footage falls within it. California's Penal Code section 632 makes it an offense to intentionally record a confidential communication without the consent of all parties (California Legislature), so audio needs its own check.
Who can grant what
A business can license footage it made, but not permissions it never obtained from the people in it; a broad grant clause does not create them. Its representations about people should match records it can produce: notices, releases, a register and a description of who else is in frame.
Recordings made at customer sites can also involve the premises owner's terms; see body-worn camera footage from field technicians. Screens, documents and branded goods in frame are covered in third-party content in workplace recordings.
What redaction and pseudonymization change
Redaction makes a delivered clip less identifiable. It does not turn footage recorded without adequate notice into footage people agreed to, and hands, tattoos, voice, gait and uniforms often still identify someone. Purpose-built corpora pair the two; Ego4D reports working with consenting participants and applying de-identification procedures (Grauman et al., 2021). See face and bystander redaction for methods and their cost to training value.
Robotics programs also need to know which clips came from which person, which argues against full anonymization. A pseudonymous operator ID lets a withdrawal reach every clip and derived file, and lets you hold out evaluation data by operator. The supplier should keep the key under access control, and the license should prohibit re-identification.
Designing consent into commissioned recording
Commissioned collection is the one route where consent can be written for the intended use from the start; CaptainCook4D, for example, recorded under IRB approval with written consent (Peddi et al., 2023). For workplace demonstrators, the agreement should name AI and robot model training, licensing to the buyer and its contractors, every stream recorded, derived pose data, retention, and what withdrawal reaches once a model is trained. Participation should be voluntary, and anyone else likely to be in frame needs their own agreement or must be kept out of the capture zone. See recruiting demonstrators for commissioned collection; the SourceX site describes a separate physical-world path for new recordings of hands-on work coordinated with businesses.
Illustrative consent register extract
A register is the working form of consent management for a video archive: one row per person, linked to clips by pseudonymous ID.
# Illustrative only — synthetic IDs and fields; not a legal template or a SourceX document
register: site_014_demonstrations_v3
operators:
- operator_id: op_B07 # pseudonymous; name key held by supplier
relationship: employee
document: demo_release_v2 (signed 2026-03-02)
scope: {model_training: yes, third_party_license: yes, audio: no, derived_pose: yes}
withdrawn: no
clips: 142
- operator_id: op_B11
relationship: agency_staff (agency_A3)
document: demo_release_v2 (signed 2026-03-09)
scope: {model_training: yes, third_party_license: yes, audio: no, derived_pose: no}
withdrawn: 2026-07-18 # clips and derived files deleted per license schedule C
clips: 0
incidental_people:
coworkers: site notice N-4 covers internal training only -> identifiable clips excluded
customers: kept out of capture zone; clips showing customers excluded
minors: excluded
audio: not delivered
License terms that reflect the people in the data
The full clause list is in licensing terms for robotics training data. For people specifically, look for:
- A representation that notices and consents cover the licensed uses and recipients, with the register or a supplier attestation attached.
- A withdrawal procedure that finds affected clips by operator ID and states a position on models already trained.
- A ban on re-identification and on publishing identifiable frames without review.
- Retention limits that match the consent; see retention, deletion and audit rights.
Limitations
- Documents show that notice was given. Whether it was adequate or freely given is a judgment for counsel in the relevant jurisdiction.
- Fresh consent for an existing archive is often impractical, so some technically good footage will not be usable.
- Opt-in and exclusion skew coverage: if only experienced, willing staff remain, operator diversity and per-operator holdouts suffer.
- Rules follow where people were recorded and where data is processed. Suppliers are US businesses, but buyers can be anywhere, so more than one regime may apply.
Questions to ask suppliers
- Who appears in the footage: employees, agency or contract staff, customers, patients, members of the public, minors?
- What notice, policy or release covered each group when recording happened, and can you share the text with version dates?
- Does that wording cover model training by an outside company and its contractors, or only internal staff training?
- Could workers decline to be filmed, and how was a refusal recorded?
- Are people linked to clips by a pseudonymous ID, so a withdrawal can be traced to every clip and derived file?
- How many people in the archive have since left, and can any of them be reached?
- In which states or countries was each recording made, and was audio captured?
- Is any of the workforce covered by a collective agreement that addresses recording?
- Were any recordings made on customer premises, and what do those contracts say about filming?
Discuss your requirements
When you submit a request through the SourceX buyers page, the form asks for licensing and de-identification requirements; use them to state the consent scope, recipients and redaction you need. SourceX checks the data and the supplier's licensing permissions, agrees allowed uses in a license, and follows up about potential sources; a request does not guarantee a match. The procurement hub and humanoid training data guide cover the rest of the buying sequence.
Explore sourcing and licensing options with SourceX
Sources
- Regulation (EU) 2016/679 (General Data Protection Regulation) — Member State rules for employee data.
- Guidelines 3/2019 on processing of personal data through video devices (Version 2.0) — EDPB guidance on video devices.
- Employment practices and data protection: monitoring workers — UK ICO guidance on monitoring workers.
- Biometric Information Privacy Act (740 ILCS 14) — definition of biometric identifiers, including hand and face geometry.
- California Penal Code Section 632 (eavesdropping on or recording confidential communications) — all-party consent for recording confidential communications.
- Ego4D: Around the World in 3,000 Hours of Egocentric Video — consent paired with de-identification.
- CaptainCook4D: A Dataset for Understanding Errors in Procedural Activities — recording under IRB approval with written consent.