Privacy and consent for on-site robotics capture
On-site capture needs clear consent, minimization, and transfer controls, not afterthoughts.
On-site robotics capture needs clear consent, data minimization, and transfer controls agreed before cameras roll, not after the first shift. Identifiable imagery, retention windows, and on-device masking belong in the same workshop where you define sensors and volumes. Operant scopes those controls as part of robotics data collection, especially in public, retail, home, and clinical spaces.
A capture plan that ignores people in frame will stall when legal reviews the first batch. Treat privacy as a capture constraint, like lighting or safety, so the dataset you intended is the dataset you can keep.
Where consent is the binding constraint
- Public sidewalk and campus programs under delivery robotics data collection.
- Clinical corridor work under hospital robotics data collection.
- Training-OR and phantom programs under surgical robotics data collection, which stay off live-patient capture unless a separate approved path exists.
- Homes and stores, where residents and shoppers can appear in RGB.
Align with legal on identifiable faces, audio, retention, and who may receive transfers. Our privacy and consent FAQ is the short version of the same rule.
Book a discovery call to put consent and minimization in the statement of work with the sensor list.
Scope your capture program
Book a discovery call to align on your stack and data requirements.