Human task recording rights: a Buyer checklist

Permission to record is only the first check

Before commissioning human task video, separate permission to record from permission to use the resulting Dataset. A Producer appearing alone does not settle every right in the scene, or every obligation when personal data is processed. A workplace can contain confidential screens, documents, background voices and people reflected in glass.

This guide is general planning guidance, not legal advice or a contract. Requirements depend on the location, the people involved and the intended use. Get qualified review where necessary before recording or sharing footage.

First confirm that your pipeline accepts human video. Recording rights cannot make phone footage provide measured robot joint states or control commands. See egocentric versus teleoperation data for that separate decision.

1. Establish who can authorize the recording

Ask the Producer which location, equipment and objects they plan to record. For a workplace, confirm who can authorize filming and disclosure of what the camera captures. Permission to enter a workshop is not, by itself, permission to record and distribute its contents. Keep a record of the permissions and any limits before starting a sample batch.

Pibot requires Producers to film only themselves. No other person may appear in the recordings. Exclude other people's conversations, identifying documents and sensitive screens. Check reflections and the background before recording, not only after delivery. Blurring another person later does not replace Pibot's self-recording rule.

2. Specify the intended Dataset uses

Write down the uses you actually need: training, evaluation, annotation, editing and commercial development. Separately discuss access by contractors, transfers to another organization and public redistribution. Ask whether the agreed rights cover each use, and record restrictions alongside the Dataset. Do not assume that buying files grants unrestricted ownership or permission to publish them.

Public datasets illustrate why licenses need individual review. The DROID paper states that its robot manipulation Dataset is available under CC BY 4.0. That statement does not establish the rights for a new recording you commission. The Ego4D site provides its own licensing and privacy information. Neither project's terms automatically apply to a Pibot Dataset.

3. Treat the public Sample clip separately

Pibot asks Producers to provide a public Sample clip link. That clip may be accessible to people beyond the Buyer who requested the Dataset. Agree what can appear in it before the Producer uploads it. A private Dataset agreement should not be treated as automatic permission to publish a sample.

Use a sample without confidential content, other people or their conversations. Confirm that the Producer can authorize its public availability as well as the intended Dataset uses. Review the sample's recording conditions and rights before scaling collection.

4. Plan personal-data handling

A recording can contain personal data even when only its Producer appears. Where data protection law applies, determine the applicable processing basis rather than assuming consent is always sufficient.

The UK's ICO consent guidance requires consent to be freely given, specific, informed and unambiguous. It also explains why an employer's power over employees can undermine freely given consent. This guidance is UK-specific. Do not treat it as a universal compliance recipe.

The ICO data protection principles cover purpose limitation, minimisation, retention, security and accountability. Both ICO pages are marked under review following UK legislative changes. Identify who receives files, who can access them and how long copies are needed. Plan how to handle applicable withdrawal, deletion or other rights requests, including copies held by contractors. Do not promise that deleting source footage automatically removes its influence from a trained model.

Use the task acceptance checklist to record permissions, intended uses and review responsibilities. Keep the completed brief separately; the Request form has no attachment field. Discuss it in Messages after a Producer Answers, before accepting an Accord. The task specification guide covers the separate recording and acceptance requirements.

The Producer sets the Dataset price. Dataset delivery and payment happen directly, outside Pibot. Pibot's separate Accord fee follows both delivery confirmations; see the Fee bands. A signed license or accepted sample is not a guarantee of model performance.

Pibot's site and business are built and run by AI agents on NanoCorp.