Standards
This page is written to be forwarded to your legal and ML teams. Plain, specific, no fluff. If something here is missing what they need, tell us and we'll add it rather than answer it once by email.
Consent and rights
We are filming identifiable people in their own homes and workplaces, which needs a higher standard of consent than annotation work does. Our intended structure records consent at three levels, because they can differ: the person in frame, the premises, and the individual session.
Being straight with you: the written release is still with our lawyers, and we would rather say that than claim a form we can't yet show you. It will cover downstream model training, redistribution and your ability to sublicense, because a release that doesn't is worthless to you. Email hello@021motion.com and we'll send it to your legal team for review the moment it's final — before you commit to anything.
Bystanders
We film in controlled spaces so incidental people are the exception rather than the rule, and we blur bystanders on request.
Quality control
Every clip is checked before it's counted. These are the gates — published, so you can hold us to them rather than take our word for it.
- Framing
- Hands and the worked object are in frame for the whole action.
- Task completed
- The attempt reaches its end state, or is explicitly flagged as a failed attempt.
- Lighting
- Exposure holds through the action; no blown highlights on the hands.
- Second review
- Anything rejected on the first pass is looked at again by a different reviewer.
- Metadata completeness
- Every required field in the episode JSON is populated, not null.
- Format validation
- The file opens and decodes in the target packaging before it leaves us.
We report the acceptance rate on every delivery, with a reason code against each rejected clip. On a pilot, score the first sample batch against your own rubric, not ours — if the gates above don't match how you actually grade data, we would rather find that out on 20 clips than on 2,000.
Formats and delivery
MP4/H.265 by default, or your spec. One JSON per episode. Delivered straight into a bucket you control. LeRobot or RLDS packaging on request.
What ships with every delivery
- Footage
- Episodes in the agreed codec and container.
- Episode metadata
- One JSON per episode: task, scene, device, duration, outcome.
- QA report
- Per-delivery acceptance rate, plus the reason code on every rejected clip.
- Consent records
- A consent and location-permission record for every person and premises in the delivery.
Data security
Encrypted in transit. Access limited to named staff on your project, not shared accounts. Local copies deleted once you confirm delivery.
We don't hold SOC 2 or ISO 27001 today. We're not going to imply otherwise with a badge row — if your security review needs a specific control evidenced, ask and we'll answer it directly.
Data protection and jurisdiction
You contract with
021motion2106 House Ave, Ste 383
Cheyenne, WY 82001
United States
Data is collected in
Tirana, Albania — under Law 124/2024, which is aligned with GDPR. Consent is collected there, under that law.
Data processing agreements are available on request.
Subprocessors
Third parties that touch data submitted through this website.
| Processor | Purpose | Region |
|---|---|---|
| Cloudflare | Site hosting and the /api/pilot endpoint | Global edge |
| Cloudflare D1 | Stores pilot request form submissions | Global edge |
| Cloudflare Turnstile | Bot protection on the pilot form | Global edge |
| Cloudflare Email | Delivers pilot request notifications to us | Global edge |
Captured footage is delivered into storage you control and does not pass through a third-party processor of ours on the way.
Security FAQ
- Where is the footage stored before it reaches us?
- On managed machines in Tirana, under named-staff access only, and deleted once you confirm the delivery landed. We do not keep a working copy after that unless your contract asks us to.
- Who can see the raw footage?
- The filming team and the reviewers assigned to your project. Access is by named individual, not a shared account, and it is removed when someone leaves the project.
- How is it transferred?
- Encrypted in transit, delivered directly into a bucket you control — your S3, GCS or Azure. We never publish a download link.
- Can a contributor withdraw after filming?
- Yes. The consent record names the route, and we will pull the affected episodes from any delivery that has not yet left us and tell you which IDs are affected in one that has.
- Do you train models on our data?
- No. Footage shot for you is delivered to you; we do not retain it to build a dataset of our own.
Questions from your legal or ML team?
Send them straight to us at hello@021motion.com, or get them on a call with us directly. We'd rather answer the hard questions before a pilot than after.
Request a pilot