Humanoid Robot Procurement: The 12 Contractual Protections Every Enterprise Must Secure for Data Ownership, AI Training and Cybersecurity

Physical AI Journal | Research report | Humanoid robot procurement
Physical AI Journal Research Team — Independent analysis by Sekason Research Limited, United KingdomAs of 13 November 2026
Scope and Disclaimer
This report provides market and adoption intelligence only. It gives no engineering, safety-certification or technical-conformity opinion on any robot, deployment or manufacturer, and no legal, financial or investment advice. Security findings are attributed to the researchers and outlets that reported them. The 12 protections are an editorial framework, and sample positions are negotiation starting points for counsel review. The report does not evaluate, certify or endorse the cybersecurity or safety of any product.
Evidence labels carry specific meanings. Verified means stated in an official, regulator, customer-issued or Tier 1 to 2 source, and for security items it attaches to the existence of the disclosure, not to the researcher's technical claim. Company-claimed means originating with the vendor and not independently audited. Secondary-reported means reported by a trade, aggregator or law-firm source whose primary document was not opened. Researcher arithmetic and editorial inference are the Research Team's own calculations and judgements. This report is as of 13 November 2026, and specifications, prices, deployment status and regulation change quickly.
Research was AI-assisted with editorial oversight under the Editorial Standards → Editorial Standards page. To report an error, use the Corrections → Contact page; see also the Disclaimer → Disclaimer page.

1. Executive Intelligence Synthesis: Five Signals Procurement Must Price In
Direct answer.
Enterprises should secure six of 12 contractual protections before any humanoid robot pilot data flows and the other six before a multi-site term. No public contract text on data ownership, AI-training rights, retention, teleoperation access or patch terms was found for any named commercial humanoid deployment, including Agility Robotics' Digit v5 at about $8,500 a month under Robots-as-a-Service (RaaS) plus a $25,000 deployment fee (secondary-reported). The 12 protections span six control points: ownership and use, shared-model training, sensor and remote access, cloud versus local processing, cyber accountability, and exit. They are an editorial framework (editorial inference).
This report helps Automation and Procurement Buyers decide which protections to secure before approving a vendor, signing a RaaS agreement or expanding a pilot into a multi-site deployment. The central question is whether an enterprise can deploy a humanoid robot without surrendering control of its operational data, intellectual property, facility information or future automation capability. The evidence says the answer turns on contract terms that vendors do not publish. The Digit v5 price is public, but no data terms accompany it.
"I don't believe the entire industry has figured out who owns the data."
Nizar Trigui, Chief Technology Officer, GXO, Economist Enterprise Physical AI and Robotics Summit panel, London, 13 October 2026 (secondary-reported; TechJournal, 23 October 2026)
Signal 1: no data terms are public for named deployments.
No vendor–customer terms were found for any named humanoid deployment. The only published vendor sale terms found, for Boston Dynamics' non-humanoid Spot product, allow open-ended retention of site-observed data (company-claimed; clause text to be re-checked).
Signal 2: the contest is over training and derived assets, not title alone.
Panellists from GXO and BMW Group said in October 2026 that data ownership remains unsettled (secondary-reported). Thomas Stapp of GreyOrange, a warehouse-automation vendor, distinguishes data that can be returned from learning merged into a shared model (vendor-affiliated opinion). CMS reads EU Data Act Art. 4(13) as requiring a contract before a data holder uses non-personal data (secondary-reported).
Signal 3: reported training data comes from outside customer sites.
Figure AI reports paying public creators $15M to record tasks (company-claimed), and Tesla employees at Grünheide are reported to wear cameras for Optimus training (secondary-reported). Vendors therefore hold alternatives, which shapes what a buyer can reasonably refuse. Silence about customer-site capture is not evidence that it does not happen.
Signal 4: researchers have disclosed vulnerabilities in one vendor's products, and regulators are moving.
Every documented finding concerns Unitree and is a researcher disclosure; no confirmed in-the-wild compromise of a deployed humanoid was found. The US FCC added foreign-produced advanced robotic devices to its Covered List on 28 July 2026 (verified per the cyber notes; to be checked against the primary PDF), and EU CRA manufacturer reporting duties have applied since 11 September 2026 (verified).
Signal 5: outcome and continuity evidence is thin.
Only two deployments have quantified outcomes, and both originate with the vendor. Agility reported 2025 net sales of $1.8M against a $2.5B SPAC valuation (secondary-reported), so insolvency and exit terms need contractual cover.
# | Protection | Control point | Priority tier | Owner role |
1 | Data title and licence scope | A. Ownership and use | Before any pilot data flows | Chief Data Officer, Legal Counsel |
2 | Derived assets and customer-specific IP | A. Ownership and use | Before a multi-site term | Legal Counsel, Operations Leader |
3 | AI-training opt-in and exclusion | B. Shared-model training | Before any pilot data flows | Chief Data Officer, Legal Counsel |
4 | Sensor, camera, microphone and facility-map limits | C. Sensor and remote access | Before any pilot data flows | CISO, Operations Leader |
5 | Remote-access and teleoperation controls | C. Sensor and remote access | Before any pilot data flows | CISO, Operations Leader |
6 | Data location, telemetry and subprocessor controls | D. Cloud versus local | Before any pilot data flows | CIO, CISO |
7 | Security baseline and patch obligations | E. Cyber accountability | Before a multi-site term | CISO |
8 | Vulnerability and incident notification to the buyer | E. Cyber accountability | Before any pilot data flows | CISO, Legal Counsel |
9 | Liability, indemnity, insurance and responsibility allocation (data and cyber only) | E. Cyber accountability | Before a multi-site term | Legal Counsel, Procurement |
10 | Retention, deletion and return on exit | F. Portability and exit | Before a multi-site term | Chief Data Officer, Legal Counsel |
11 | Exit licence, transition assistance and continuity | F. Portability and exit | Before a multi-site term | Procurement, Legal Counsel |
12 | Change-in-law and regulatory-status continuity | F. Portability and exit | Before a multi-site term | Legal Counsel, Procurement |
2. Platform and Market Landscape: Where Buyer Control Is Won or Lost
Direct answer.
An enterprise deploying a humanoid robot hands over sensor data, facility maps, operational logs and task data, and grants the vendor access through cloud or fleet platforms and possible teleoperation. Contract control attaches at six points: ownership versus use rights, shared-model training, sensor and remote access, cloud versus local processing, cybersecurity accountability, and exit. Purchase, lease and RaaS change who holds the hardware, not automatically who holds the data rights (editorial inference).
2.1 Market snapshot, labelled by source
Shipment volume is Chinese, and procurement-relevant Western supply is pre-volume. About 19,100 humanoid robots shipped globally in H1 2026, against about 5,100 in H1 2025, with Chinese makers above 97% share (secondary-reported; attributed to Counterpoint Research via TechNode, 11 August 2026, though TechNode credits the outlet IT Home and names no research firm).
AgiBot accounts for about 8,400 in the article body, while a Humanoid.guide headline gives 8,600; this report uses 8,400 and flags the conflict.
Agility, Tesla, Figure, Apptronik and Boston Dynamics have no independently verified volume. Reported pilots concentrate in warehousing and automotive manufacturing, and no healthcare humanoid deployment evidence was found. Definitions also conflict: Interact Analysis says only about 10% of robots produced in 2025 were deployed in real-world operations (analyst finding), while the TechNode report puts industrial and commercial use above 70% of H1 2026 shipments (secondary-reported). Treat the gap as a measurement problem, not as an adoption level.
Market and capital snapshot.
Every row carries its source date and evidence label. As of 13 November 2026.
Data point | Value | Source and date | Label |
H1 2026 global humanoid shipments | About 19,100 (H1 2025: about 5,100); Chinese makers above 97% | TechNode, 11 August 2026 | (secondary-reported) |
AgiBot H1 2026 shipments | About 8,400 (article body) against 8,600 (headline elsewhere); unreconciled | TechNode; Humanoid.guide | (secondary-reported) |
Unitree H1 2026 shipments | About 5,900 | TechNode, 11 August 2026 | (secondary-reported) |
Global 2025 shipments | About 15,000 (Omdia) | ClickOrlando, 29 July 2026 | (secondary-reported) |
Agility Digit v5, RaaS | About $8,500 a month plus a $25,000 deployment fee | The Robot Report, 7 September 2026, reporting the S-4 | (secondary-reported) |
Agility Digit v5, ownership | About $200,000 upfront, a $20,000 deployment fee, about $36,000 a year | The Robot Report, 7 September 2026 | (secondary-reported) |
Tesla Optimus price | No announced price at 22 October 2026; long-running target of $20,000 to $30,000 at full scale | AI Business, 22 October 2026 | (company-claimed) |
Other platforms' prices | No verified price found for Unitree, UBTech, AgiBot, 1X, Figure, Apptronik or Atlas | Research gap | Not available |
Figure Series C | Over $1B committed at $39B post-money, 16 September 2025 | The Robot Report, September 2025 (dated) | (company-claimed) |
Agility SPAC (Churchill Capital Corp. XI) | $2.5B valuation; over $620M expected gross proceeds; close expected Q4 2026 | The Robot Report, 7 September 2026 | (secondary-reported) |
Unitree IPO | Priced 6 August 2026; 6.1B yuan raised; valuation about 61B yuan | The Standard (Hong Kong), August 2026 | (secondary-reported) |
Humanoid (London) Series A | $152M at $1.35B post-money, 22 July 2026 | Robotics 24/7, 22 July 2026 | (company-claimed) |
2.2 What a buyer hands over: the data path and six control points
Data leaves the facility along a path that contracts can interrupt at six places. Sensors and onboard compute capture the environment. A vendor cloud or fleet platform, such as Agility's Arc or Boston Dynamics' Orbit, delivers updates and is likely to receive telemetry (editorial inference). Shared models learn from some of that data. Human operators and subprocessors may view or handle it. Agility describes Arc as a cloud-based platform and cites "years of data from real world customer deployments" (company-claimed), but states nothing on what is collected, retained or used for training. What Arc or Orbit holds, and for how long, is undocumented (editorial inference).
The six control points, defined once in the buyer's terms, organise the 12 protections in Section 8:
• A. Ownership and use. Who holds title to data, and who may use it for what purpose. The EU Data Act gives access and use rules rather than an ownership right (CMS reading, secondary-reported).
• B. Shared-model training. Whether the vendor may use customer data to train or improve models that serve other customers.
• C. Sensor and remote access. What cameras, microphones and sensors capture, and who, including remote operators, can view or control the robot.
• D. Cloud versus local processing. Where data is processed and stored, and which telemetry endpoints and subprocessors receive it.
• E. Cyber accountability. Which party, among customer, manufacturer and integrator, owns configuration, access control, updates and incident response.
• F. Portability and exit. Retention, deletion, return and continuity if the relationship ends or the vendor fails.
Each control point maps to protections in Section 8: A to Protections 1 and 2; B to Protection 3; C to Protections 4 and 5; D to Protection 6; E to Protections 7, 8 and 9; and F to Protections 10, 11 and 12.
"Hardware depreciates. Learning compounds."
Thomas Stapp, executive leadership team (strategy and corporate development), GreyOrange, essay in Automation World, 7 October 2026 (secondary-reported; vendor-affiliated opinion)
Data path and control points: sensors, cameras, microphones and onboard compute (Protection 4); vendor cloud or fleet platform (Protections 6, 7, 8); shared models and vendor training pools (Protections 2, 3); exit, return, deletion and continuity (Protections 10, 11, 12). Human operators, remote sessions and subprocessors: Protections 5 and 6. Across all data: Protections 1 and 9.
3. Deployment Evidence: What Has Been Reported Versus What Has Been Announced
Direct answer.
Reported outcomes exist for two humanoid robot deployments, Figure 02 at BMW Spartanburg and Agility Digit at GXO, and both originate with the vendor (company-claimed). No independently audited uptime, intervention or payback figure was found for any deployment, and none of the deployments reviewed discloses its data terms. Buyers should treat every outcome as a vendor claim until the customer or an auditor confirms it, and should discount any announcement that has not produced operating data.
Quantified outcomes exist for two cases only. Figure reports 11 months of deployment at BMW, 90,000+ parts loaded and 1,250+ runtime hours (company-claimed). BMW, as reported by eWeek on 29 June 2026, cited 10 months, 90,000+ components and about 1,250 hours (secondary-reported), so the two accounts differ by a month. Digit has moved over 100,000 totes at GXO's Flowery Branch site (company-claimed, November 2025, dated), with no duration, robot count or uptime given.
"Runtime", "intervention" and "contributed to" are undefined in every source. Intervention counts and remote-operator hours, which determine how much human access a deployment creates, are unreported.
Ask any vendor to define these terms in writing before accepting outcome data as a basis for a contract, and request intervention and remote-operator hours as contract reporting items.
Test any deployment claim a vendor cites on four points: who reported the outcome, whether the vendor or the customer; over what period and with how many robots; under what definition of runtime and intervention; and what data left the site during the deployment. The BMW case answers the first point only in part, because BMW's own 2024 release reports no metrics and the 2026 figures reach this report through trade press. The GXO case answers none of the others. A vendor unable to answer all four has supplied a marketing claim, not decision evidence.
The evidence ladder places each deployment by what is actually documented. Schaeffler's Digit agreement is an announcement, Apptronik's work is exploration, Hyundai's Atlas is a plan (company-claimed), Tesla's Optimus has a production start claimed in a company letter (company-claimed), and UBTech's orders rest on company statements alone (company-claimed). Data-term disclosure is "none found" in every case.
Evidence ladder
Deployment Data-Governance Tracker (extract).
Source classes shown inline. Last checked 13 November 2026.
Deployment | Ladder status | Outcome claims and source class | Data terms disclosed |
Figure 02, BMW Spartanburg | Pilot completed; vendor-claimed outcomes | 11 months, 90,000+ parts, 1,250+ hours (company-claimed); BMW as reported: 10 months (secondary-reported) | None found |
Agility Digit, GXO Flowery Branch | Operating RaaS; vendor-claimed volume | 100,000+ totes, no duration, robot count or uptime (company-claimed, November 2025, dated) | None found |
Agility Digit, Schaeffler | Announcement only | None; operating status unconfirmed (company-claimed, 13 November 2024, dated) | None found |
Atlas, Hyundai Metaplant America | Plan stated (2028 start) | None; owner-issued plan (company-claimed) | None found; same-group data strategy only |
UBTech Walker S2 | Orders and deliveries claimed by the company only | Orders above RMB 800M since early 2025 (company-claimed, 17 November 2025) | None found |
Apptronik Apollo | Exploration and testing | None; no sustained performance data (secondary-reported) | None found; terms not searched |
Tesla Optimus | Production start claimed | None; no deployment outcome (secondary-reported of a company letter) | None found; Tesla filings not opened |
4. Economics and ROI: What Contract Control Costs, and What Losing It Costs
Direct answer.
Agility's reported terms, the only published benchmark, put five-year cost at about $535,000 under RaaS against about $400,000 under ownership (researcher arithmetic from secondary-reported terms), excluding other costs. No verified payback exists for any humanoid deployment. A vendor price offset for a data-rights concession is worth accepting only where it exceeds the buyer's own estimate of what that concession costs (editorial inference), using the worksheet below.
4.1 Published terms
Agility's Digit v5 is reported at about $8,500 a month, about $102,000 a year, covering robot, software and maintenance, plus a $25,000 deployment fee under RaaS. Ownership is reported at about $200,000 upfront, a $20,000 deployment fee and about $36,000 a year for software and maintenance. All figures are secondary-reported from The Robot Report of 7 September 2026, which reports the S-4; the researchers did not open the S-4. Five-year totals are about $535,000 under RaaS ($510,000 plus $25,000) and about $400,000 under ownership ($200,000 plus $20,000 plus 5 × $36,000) (researcher arithmetic), excluding other costs. Agility's own five-year revenue-per-robot assumptions are about $535,000 and about $400,000 (company-claimed assumptions). The gap of about $135,000 between the two routes (researcher arithmetic) reflects the vendor retaining the hardware and carrying the service obligation (editorial inference); it is not a measure of what data rights are worth. These are buyer costs, not buyer returns.
Five-year cost comparison for Agility Digit v5.
Inputs are secondary-reported; totals are researcher arithmetic; other costs excluded. As of 13 November 2026.
Cost line | RaaS | Ownership |
Robot price | Included in monthly fee | About $200,000 upfront (secondary-reported) |
Deployment fee | $25,000 (secondary-reported) | $20,000 (secondary-reported) |
Annual service | About $102,000, or about $8,500 a month, covering robot, software and maintenance (secondary-reported) | About $36,000 for software and maintenance (secondary-reported) |
Five-year total | About $535,000 = $510,000 + $25,000 (researcher arithmetic) | About $400,000 = $200,000 + $20,000 + 5 × $36,000 (researcher arithmetic) |
4.2 No audited payback
No verified payback exists for any humanoid deployment. A trade-blog payback claim traces to no primary source and is excluded here. Treat every vendor ROI model as a company-claimed input, and ask for the intervention and uptime definitions behind it (Section 3).
4.3 Cost-of-control worksheet
Procurement can price control with inputs that only the buyer holds. The worksheet contains no pre-filled values. The decision rule is an editorial inference: accept a training concession only where the quoted price offset exceeds the buyer's own estimate of what the concession costs, and only with opt-in, revocation and exclusion terms (Protection 3).
Run the worksheet twice, once for the pilot and once for the multi-site term, because exposure scales with fleet size and term length. Take the breach-cost inputs from the buyer's own incident history and insurer, not from vendor material, and require the vendor to state any price offset in writing before it is compared with the concession cost.
Cost-of-control worksheet.
Buyer inputs only; no values supplied by this report.
Input | Who supplies it | Buyer entry |
Contract term and fleet size | Operations Leader | ________ |
Value of site data (sensitivity rating) | Chief Data Officer | ________ |
Price offset quoted for any training concession | Vendor quote | ________ |
Switching cost: re-integration, re-teaching tasks, downtime, data re-collection, exit assistance fees | Operations Leader, vendor | ________ |
Breach-cost inputs from own incident history and insurer | CISO, insurer | ________ |
Concession cost estimate (sum of the above exposures attributable to the concession) | Finance, with Legal Counsel | ________ |
Decision: accept only if the quoted offset exceeds the concession cost estimate | Procurement | ________ |
4.4 Counterparty and continuity
Agility reported 2025 net sales of $1.8M, an operating loss of $140M and cash burn of about $100M, against a $2.5B SPAC valuation, about 1,400 times 2025 revenue (researcher arithmetic), with closing expected in Q4 2026 (secondary-reported; the S-4 was not opened). Reported multi-year orders of over $300M from one customer were later described by Agility as potential value subject to milestones, not revenue (secondary-reported; company-claimed). These indicators do not predict failure. They show why insolvency, change-of-control and exit protections (Protection 11) carry cost weight in any multi-year RaaS term.
Counterparty indicators for Agility Robotics.
All figures secondary-reported from The Robot Report, 7 September 2026, unless stated. As of 13 November 2026.
Indicator | Value | Label |
2025 net sales | $1.8M | (secondary-reported) |
2025 operating loss | $140M | (secondary-reported) |
Cash burn | About $100M | (secondary-reported) |
SPAC valuation | $2.5B, with over $620M expected gross proceeds (about $420M trust, $200M PIPE led by Foxconn) | (secondary-reported) |
Valuation as a multiple of 2025 revenue | About 1,400x = $2.5B / $1.8M | (researcher arithmetic) |
Reported multi-year orders of over $300M | Later described by Agility as potential value subject to milestones, 2 November 2026 | (secondary-reported; company-claimed) |
4.5 RaaS versus purchase for data rights
Under RaaS the vendor keeps the hardware; under ownership the buyer holds it. Data and training rights follow the contract in both cases, not title to the robot (editorial inference). A buyer who leases should therefore secure Protections 1 to 3 as firmly as a buyer who purchases, and should add Protection 11 for hardware return and site restoration.
5. Named Deployment Case Studies: What Each Reveals About Data Terms
Direct answer.
None of the five humanoid deployments reviewed has disclosed its data terms. Each disclosed a platform, a scope and, in some cases, outcome claims; none published contract text on data ownership, retention, AI-training use or teleoperation access, although GXO's chief technology officer states that customers own their data (company-claimed, via press). Two have vendor-claimed outcomes, one is an owner-issued plan, one rests on company-only order claims and one is exploration. Announced is not operating, and none of these cases offers contract text that a buyer can use as a benchmark.
5.1 Figure 02 and BMW Spartanburg.
Figure AI's Figure 02 was trialled in the body shop of BMW Group Plant Spartanburg. BMW's 6 August 2024 release (verified, dated) describes a several-week trial, states that no Figure robots were at the plant and no timetable existed, and reports no metrics. Figure's later post of 19 November 2025 (company-claimed) reports 11 months, 10-hour weekday shifts, 90,000+ parts and 1,250+ runtime hours, and says every intervention was logged and run data informed the Figure 03 design. Whether BMW consented to, or owns, that data is not stated. Protections informed: 1 and 3.
"data capturing and training capabilities"
BMW Group, corporate statement on continuing work with Figure, BMW Group Newsroom, 6 August 2024 (verified; dated)
5.2 Agility Digit and GXO, Flowery Branch.
GXO announced a multi-year RaaS agreement with Agility on 27 June 2024 (verified for the announcement), after a late-2023 proof of concept. Digit moves totes from cobots to conveyors, and the fleet is managed through the Agility Arc cloud platform. More than 100,000 totes have moved (company-claimed, November 2025, dated); duration, robot count, uptime and labour-hour savings are not given. An expansion to Statesville and Lebanon from early 2027, starting with Digit 4, is announced (company-claimed), with robot counts undisclosed. GXO's release makes no statement on data. GXO's chief technology officer says customers own their data under GXO's current contracts (company-claimed, via press), but the contract text is not public. Protections informed: 1 and 6.
5.3 Boston Dynamics Atlas and Hyundai Metaplant.
Hyundai Motor Group's plan of 6 January 2026 (company-claimed) starts Atlas at its Metaplant America in Savannah, Georgia in 2028 on parts sequencing, with component assembly by 2030. It is a plan, not an operating deployment, and syndicated pages asserting an earlier operating start contradict Hyundai's own timeline and are not relied on. Hyundai's stated data strategy (company-claimed) is explicit but captive: operational data feeds retraining and remote monitoring within one corporate group, which says nothing about third-party customer terms. Protections informed: 3 and 10.
"a cycle of continuous retraining"
Hyundai Motor Group, corporate statement on its Physical AI plan, 6 January 2026 (company-claimed)
5.4 UBTech Walker S2.
UBTech's claims come from the company alone. It reports orders above RMB 800M since early 2025 and customers including BYD, Geely and Foxconn (company-claimed, 17 November 2025, borderline dated), with capacity targets of 5,000 units in 2026 and 10,000 in 2027 (company-claimed targets). No customer statement, per-customer unit count, hours or throughput exists, no independent delivery count exists, and no HKEX filing was retrieved. One order, worth RMB 159M, is for a "data collection center", which shows that robot data collection can be a purchase purpose in itself. Protections informed: 3 and 4.
5.5 Apptronik Apollo with Mercedes-Benz, GXO and Jabil.
A Startup Fortune article of 25 June 2026 corrected an earlier claim that Apptronik's Apollo was working factory shifts at Mercedes-Benz and GXO. The corrected record is that Mercedes announced in March 2024 it was exploring Apollo, Jabil agreed in February 2025 to test it, no reliable current source confirms a GXO deployment, and no sustained performance data is published (secondary-reported). Apptronik's data terms were not searched. The case matters because a correction was needed at all: announcement language was read as operation. Apply the announced-versus-operating test to every vendor claim, and add Protection 12 where regulatory status changes the product a buyer receives.
Case study map.
What was disclosed on data, and which protections each case informs. As of 13 November 2026.
Case | Status | Disclosed on data | Protections informed |
Figure 02, BMW Spartanburg | Pilot completed | Intervention logging stated; consent and ownership not stated | 1, 3 |
Agility Digit, GXO | Operating RaaS; expansion announced | Arc cloud platform named; contract text not public | 1, 6 |
Atlas, Hyundai Metaplant America | Plan (2028) | Captive same-group retraining only | 3, 10 |
UBTech Walker S2 | Company-only claims | A data collection centre order; no customer terms | 3, 4 |
Apptronik Apollo | Exploration | Terms not searched | 12 |
6. Friction, Risk and Unresolved Issues: Security, Regulation, Ownership and Evidence
Direct answer.
Four unresolved risks matter most in humanoid robot procurement: undisclosed data and training terms, security findings concentrated in one vendor with disputed patch status, an unsettled US import regime, and thin outcome evidence. Nothing in this section is an engineering or conformity opinion, and security findings are attributed to the researchers who reported them. The regulatory dates below set when Protections 8 and 12 take effect, and several rest on law-firm secondary sources.
6.1 Security evidence: all Unitree, all researcher-reported
Every documented humanoid or legged-robot security finding in the research concerns Unitree and originates with researchers. Researchers reported CVE-2025-2894, a hidden remote-access backdoor in the Go1, in March 2025, and the fix was reported as silently patched. For CVE-2025-35027 ("UniPwn"), researchers report hardcoded Bluetooth keys and an authentication bypass; Unitree stated on 29 September 2025 that "most of the fixes" were complete (company-claimed, reported by IEEE Spectrum), and later secondary reporting documents no public firmware patch. An arXiv preprint on the G1 reports a shared hardcoded key, disabled TLS verification in a web client and telemetry to two China-based endpoints every 300 seconds; the authors did not confirm that audio, video or spatial data was exfiltrated. CVE-2026-76639 and CVE-2026-76640, affecting the G1 EDU, were published on 27 to 29 August 2026, with fixed firmware unverified. No confirmed in-the-wild compromise of a deployed humanoid was found (Recorded Future, 5 May 2026; company-claimed security-vendor research). The findings are researcher disclosures, not observed exploitation. These findings do not generalise to other vendors, and absence of research on other vendors is not evidence of security. The actionable step is to require a firmware-to-CVE fix history from any vendor (Protection 7).
Security findings table.
All rows concern Unitree products and are researcher disclosures. As of 13 November 2026.
Finding | Date | What the source reports | Vendor response | Source class |
CVE-2025-2894, Go1 remote-access backdoor | CVE 27 March 2025 | Hidden functionality allowing remote control through a third-party service; CVSS 6.1 (tentative) against 6.6, and one outlet calls it critical | Reported silently patched within days; Unitree says newer models unaffected (company-claimed) | (verified disclosure; severity conflict unresolved) |
CVE-2025-35027, UniPwn | NVD 26 September 2025 | Hardcoded Bluetooth keys, authentication bypass, root-level injection; researchers say wormable in radio range | Company statement on 29 September 2025 that most fixes were complete (company-claimed); patch not confirmed | (verified, IEEE Spectrum; aggregator rows secondary-reported) |
G1 security and telemetry analysis | September 2025 | Shared hardcoded key, unencrypted DDS, disabled TLS verification, telemetry to two China-based endpoints every 300 seconds; exfiltration of audio, video or spatial data not confirmed by the authors | Not found | (verified preprint exists; authors' claims; not peer-reviewed) |
"Skynet Starter Kit" conference talk | 28 December 2025 | Abstract claims radio and Wi-Fi hijack, prompt injection and cloud takeover on G1 | Not found | (researcher claims, not independently confirmed) |
CVE-2026-76639 and CVE-2026-76640, G1 EDU | Published 27 to 29 August 2026 | Two root-level chains reported; wormability tested on two robots only | Ownership check added; $5,000 bounty paid 6 August 2026; fixed firmware unverified (company-claimed, as reported) | (verified disclosure; secondary summaries) |
6.2 Regulatory and FCC uncertainty
The FCC added "foreign-produced advanced robotic devices" to its Covered List by Public Notice DA 26-786 on 28 July 2026, following a National Security Determination dated 27 July 2026 (verified; to be checked against the primary PDF). Skadden and Sidley read the action as covering humanoids, quadrupeds and autonomous mobile robots, leaving previously authorised models unaffected and not restricting federal purchasing (secondary-reported). The Hacker News reports a waiver for vulnerability-patching software and firmware changes through at least 1 January 2029, and Conditional Approval applications due by 1 January 2028 (secondary-reported). Two points remain open. The Register reports that foreign-owned manufacturers producing in the US, such as Hyundai-owned Boston Dynamics, are exempt, while Skadden and Sidley describe a product-origin "domestic end product" test. The sources also do not address the legal effect on units already deployed or on continued support, parts and updates. The GUARD Act (3 June 2026) and a Cotton–Schumer federal-funds bill (about 26 March 2026) are introduced, with no later action found.
6.3 Ownership, training and notification clocks
Ownership and training use remain unsettled (Section 1). The EU Data Act applies from 12 September 2025, with the Art. 3 "access by design" requirement applying to products placed on the market from 12 September 2026 (secondary-reported; CMS, 20 July 2026). CRA manufacturer reporting has applied since 11 September 2026: early warning within 24 hours, notification within 72 hours and a final report within 14 days of a corrective measure for vulnerabilities (verified; European Commission and ENISA pages). Those duties run from manufacturer to authorities, so the buyer's own notice right must be contracted. CRA main obligations apply from 11 December 2027 (verified; European Commission, 11 September 2026). The EU AI Omnibus (Regulation (EU) 2026/1744) moved product-embedded high-risk obligations to 2 August 2028 (secondary-reported), and India's DPDP Rules place breach reporting and security safeguards at 18 months, about May 2027 (secondary-reported).
6.4 Evidence and vendor friction
Tesla's October 2025 language put production start "toward the end of next year", against an October 2026 "Early Ramp" and a 20,000-per-week rate expected around end 2027 (company-claimed; secondary-reported). Outcome terms are undefined (Section 3). Analyst forecasts for 2035 diverge roughly ninefold, from above 700,000 units (Interact Analysis, analyst finding) to about 6.5M (Goldman Sachs, secondary-reported), and Humanoid.guide notes that neither Goldman report identifies confirmed customer orders near those volumes. Some pages in the evidence base are AI-assisted or syndicated and contradict primary sources; they are excluded. Do not let a forecast, a funding round or a syndicated deployment claim substitute for contract terms.
Regulatory trigger map.
Each row marks its basis as official page or law-firm secondary. As of 13 November 2026.
Instrument | Date or status | Basis | Protections affected |
FCC Covered List, DA 26-786 | Notice 28 July 2026; firmware waiver to at least 1 January 2029; Conditional Approval applications by 1 January 2028 | Official page cited by the cyber research (to be checked); scope detail is law-firm secondary | 7, 12 |
EU CRA, manufacturer reporting | Applies from 11 September 2026 | Official page (European Commission; ENISA) | 8 |
EU CRA, main obligations | Apply from 11 December 2027 | Official page (European Commission news, 11 September 2026) | 7, 12 |
EU CRA, article-level detail | Five-year update support; users informed; SBOM from 11 December 2027 | Law-firm secondary (CMS) | 7, 8 |
EU Data Act | Applies from 12 September 2025; Art. 3 for products placed on the market from 12 September 2026 | Law-firm secondary (CMS) | 1, 6 |
EU AI Act as amended by Regulation (EU) 2026/1744 | In force 27 July 2026; product-embedded high-risk obligations 2 August 2028 | Law-firm secondary (White & Case; EUROGIP) | 12 |
UK Cyber Security and Resilience Bill | Lords Report Stage concluded 26 October 2026; not law at the latest source | Official page plus trade secondary (GOV.UK; ISACA) | 8, 9 |
UK PSTI regime | In effect since 29 April 2024; consumer products; business scope not stated | Official page (GOV.UK) | 7 |
India DPDP Rules | 18-month clock to about May 2027; Board report within 72 hours of a breach | Law-firm secondary (Saga Legal) | 6, 8 |
7. Platform Comparison: What Each Vendor Publishes About Data, Training and Security
Direct answer.
Published data and security terms are sparse across humanoid robot vendors. Boston Dynamics, through its non-humanoid Spot and Orbit documents, is the only vendor with published retention language found, and most others are silent or publish consumer-oriented policies. Figure's privacy policy covers website and app services, not deployments. Tesla, Apptronik and Nvidia terms were not searched. This comparison is not a ranking of capability, price or security quality.
The scorecard records only what each vendor's own documents say, or the absence of such a document. It does not rank capability, price or security quality, and a blank cell is not a finding of poor practice. Read it as a question list: each "No public disclosure found" is a document to request before signing.
Vendor disclosure scorecard.
Not a ranking. Cells read "No public disclosure found" or "Not searched" exactly as in the research. As of 13 November 2026.
Vendor | Public terms found | Training-use statement | Remote-access disclosure | Cloud or fleet dependency | Retention and deletion | Security disclosure and patch record | Source class |
Agility (Arc) | Privacy and terms pages not retrieved | No public disclosure found (Arc page) | No public disclosure found | Arc described as a cloud-based automation platform | No public disclosure found | No researcher findings located; vendor security documentation not searched | (company-claimed) |
Figure | Privacy policy effective 21 January 2026 covers website and app services; Terms and Conditions not retrieved | Aggregated de-identified data may be used to improve the Services; no mention of robots or model training | No public disclosure found | No public disclosure found | No retention periods stated | No researcher findings located | (company-claimed) |
Boston Dynamics (Spot and Orbit, non-humanoid proxy) | Spot and Orbit terms of sale | Data may be used to improve products; the word "train" does not appear; clause text to be re-checked | No public disclosure found | Orbit is a vendor-supplied fleet platform | Spot: vendor may retain site-observed data indefinitely; no deletion clause found | Software updates for high-severity bugs; no committed patch timeline as summarised | (company-claimed) |
Tesla | Not searched (10-K and 10-Q risk factors not opened) | No public disclosure found | Data-collection operators reported in the US | No public disclosure found | No public disclosure found | No researcher findings located | (secondary-reported) |
Apptronik | Not searched | Not searched | Not searched | Not searched | Not searched | Not searched | Not available |
Unitree | Go app privacy policy, effective 14 July 2023 (consumer product, not a humanoid enterprise product) | No mention of model training | Live camera feed and operation logs collected | Policy states both that control data is not uploaded and that information will be stored in China | No public disclosure found | Five researcher disclosures (Section 6.1) | (company-claimed; findings researcher-reported) |
UBTech | Not searched | Not searched | Not searched | Not searched | Not searched | No researcher findings located | Not available |
1X | 1X's own terms not retrieved | Its CEO reportedly said the company cannot improve the product without customer data | Employees with VR headsets reportedly able to view the home | No public disclosure found | No public disclosure found | No researcher findings located | (secondary-reported; home robot; dated) |
Google DeepMind (model provider) | Gemini Robotics On-Device 2 model card, 30 July 2026 | Trained on images, text, robot sensor and action data | No public disclosure found | Designed for local-device operation | No privacy section; nothing on what is sent to Google | No public disclosure found | (company-claimed) |
Nvidia (GR00T and Isaac) | Not searched | Not searched | Not searched | Not searched | Not searched | Not searched | Not available |
The scorecard shows three patterns. Retention language exists only for non-humanoid products. The privacy documents that do exist, from Figure and Unitree, were written for consumer apps and websites and say nothing about workplace deployments. The only documented security records concern Unitree and originate with researchers, not the vendor. Where a vendor answers by pointing to a consumer privacy policy, record that the policy does not govern the deployment and ask for the enterprise terms in writing.
The terms exist or will be written, and they are being set without public benchmarks (editorial inference). For each vendor, request the data processing schedule, the telemetry endpoint and subprocessor lists, the remote-access role list, the patch and fix history, and the deletion and return terms. Because the table is not a ranking, a vendor that publishes more is not thereby a vendor that offers better terms.
8. Strategic Recommendations: The 12 Contractual Protections
Direct answer.
Six pilot-gating protections apply before a humanoid robot pilot expands to multiple sites: data title and licence scope
(1), AI-training opt-in and exclusion (3), sensor and facility-map limits (4), remote-access controls (5), data location and subprocessor controls (6), and incident notification (8). The other six apply before a multi-site or multi-year term: derived assets (2), security baseline (7), liability (9), retention and deletion (10), exit continuity (11) and change-in-law (12). The tiering is an editorial framework.
How to use the cards.
Each card follows a fixed template. Evidence anchors are labelled so a reader can see how much weight each carries. Starting positions are negotiation starting points for counsel review, not legal advice, and no card states or implies that any vendor currently offers the protection. Protection 9 covers data and cyber liability only; physical-safety liability is outside this report.
Protection 1: Data title and licence scope
Control point A, ownership and use · Before any pilot data flows
What to secure. Title to raw operational data, logs, audio, video and outputs sits with the customer. The vendor's licence is limited to serving this customer, with no sale, disclosure or commercialisation.
Evidence anchor. GXO's chief technology officer said on 13 October 2026 that the industry has not settled ownership, and also that customers own their data under GXO's current contracts (secondary-reported; company-claimed via press). CMS's reading of EU Data Act Art. 4(13) is that a data holder needs a contract before using non-personal data (secondary-reported). Boston Dynamics' non-humanoid Spot terms allow indefinite retention of site-observed data (company-claimed; re-check clause text).
Buyer decision test. Can the vendor use any customer data beyond serving this customer without a separate written grant?
Starting position (editorial framework). The buyer proposes that title to all customer-site data and outputs vests in the customer and that the vendor receives a revocable, purpose-limited licence to serve this customer only.
Fallback (editorial inference). Accept a service-delivery and security licence, with commercial reuse excluded and defined data classes carved out.
Evidence to request. Data inventory by class; draft data schedule; existing customer data terms.
Owner. Chief Data Officer, with Legal Counsel.
Protection 2: Derived assets and customer-specific IP
Control point A, ownership and use · Before a multi-site term
What to secure. Ownership, or a perpetual licence, of configurations, task definitions, site maps, workflows and customer-specific model weights, with a stated split between customer-specific work and base-model improvements.
Evidence anchor. Thomas Stapp of GreyOrange says no commercially accepted method exists to measure what a shared model gains from a site (vendor-affiliated opinion; secondary-reported). Hyundai describes operational data feeding continuous retraining within its own group (company-claimed; captive arrangement).
Buyer decision test. If you leave, can you keep running or re-create what your site built?
Starting position (editorial framework). The buyer proposes that the customer owns all configurations, maps and workflows created for its sites and holds a perpetual licence to customer-specific model weights, with base-model improvements remaining with the vendor.
Fallback (editorial inference). Accept a term licence to customer-specific weights with documented export formats and a transition period, trading exclusivity for price.
Evidence to request. Artefact inventory; export format documentation; model-lineage description.
Owner. Legal Counsel, with Operations Leader and Chief Data Officer.
Protection 3: AI-training opt-in and exclusion
Control point B, shared-model training · Before any pilot data flows
What to secure. Default no training on customer data. Separate written consent by data class, a defined meaning of "improve", exclusion zones, protection against feeding competitors' models, and revocation.
Evidence anchor. Patrick Lanners, Innovation and AI Lead at BMW Group, said at the 13 October 2026 panel that BMW would effectively train competitors' models if it did not protect its data (paraphrase; secondary-reported). Figure says BMW run data informed the Figure 03 design (company-claimed). Boston Dynamics' non-humanoid Spot terms permit using data to improve products without saying whether that includes machine-learning training (company-claimed; re-check).
Buyer decision test. Does the contract define "improve" and exclude machine-learning training unless the customer opts in?
Starting position (editorial framework). The buyer proposes that no customer data is used to train, fine-tune or evaluate any model shared with other customers unless the customer gives separate written consent for a named data class, revocable on notice.
Fallback (editorial inference). Allow opt-in, aggregated, time-limited training on named data classes against a price offset.
Evidence to request. Definition of "improve"; training data-flow diagram; list of models fed by customer data.
Owner. Chief Data Officer, with Legal Counsel.
Protection 4: Sensor, camera, microphone and facility-map limits
Control point C, sensor and remote access · Before any pilot data flows
What to secure. A list of enabled sensors and their purposes, no-go zones and hours, audio off unless required, limits on retention and export of facility maps, and handling rules for worker and visitor data.
Evidence anchor. Figure's privacy policy, effective 21 January 2026 and written for its website and app services, lists "Sensory Data" including photos, videos and recordings of a person's environment (company-claimed). Tesla employees at Grünheide are reported to wear cameras for Optimus training (secondary-reported).
Buyer decision test. Can you list what the robot captures, where it goes, and disable capture by zone?
Starting position (editorial framework). The buyer proposes that the vendor captures only the sensor data listed in a schedule, respects customer-defined no-go zones and hours, and may not retain or export facility maps without written approval.
Fallback (editorial inference). Allow the listed sensors with audio disabled by default and facility-map retention limited to the term.
Evidence to request. Sensor and purpose schedule; capture-control documentation; worker-data handling terms.
Owner. CISO, with Operations Leader and Legal Counsel.
Protection 5: Remote-access and teleoperation controls
Control point C, sensor and remote access · Before any pilot data flows
What to secure. Named roles for any vendor or subcontractor access, customer approval and visibility of sessions, customer-accessible session logs, location limits, subcontractor flow-down terms and credential standards.
Evidence anchor. 1X early buyers were reportedly required to accept a contract allowing employees wearing VR headsets to view the home through the robot's cameras, with app time windows, face blurring and no-go zones (secondary-reported; home robot; dated). Tesla is reported to use "Data Collection Operators" in the US (secondary-reported). Agility Arc and Boston Dynamics Orbit are vendor-run fleet platforms, implying vendor-side visibility of telemetry (editorial inference; extent undocumented). No source gives enterprise remote-operator hours.
Buyer decision test. Who at the vendor or its subcontractors can see your site, from where, and can you see the log?
Starting position (editorial framework). The buyer proposes that vendor access to live sensor feeds or robot control requires per-session customer approval, named roles and locations, and customer-readable logs retained for the term.
Fallback (editorial inference). Allow pre-approved support windows for named roles, with logs delivered on a fixed schedule.
Evidence to request. Remote-access role list; location list; sample session log; subcontractor list.
Owner. CISO, with Operations Leader.
Protection 6: Data location, telemetry and subprocessor controls
Control point D, cloud versus local processing · Before any pilot data flows
What to secure. A stated processing architecture (edge, customer tenancy or vendor cloud), a list of telemetry endpoints, the ability to disable or localise telemetry, a subprocessor list with change notice, and a stated transfer mechanism.
Evidence anchor. Researchers analysing the Unitree G1 reported periodic telemetry to two China-based endpoints every 300 seconds; the authors did not confirm that audio, video or spatial data left the robot (researcher-reported). Unitree's consumer Go app policy says control data is not uploaded, yet also that information will be stored in China (company-claimed; internally inconsistent).
Buyer decision test. Do you hold a current list of where data goes, and the right to refuse a new subprocessor?
Starting position (editorial framework). The buyer proposes that the vendor lists every telemetry endpoint and subprocessor, gives prior written notice of changes, and disables or localises telemetry on request.
Fallback (editorial inference). Accept vendor-cloud processing in a named region with a subprocessor list and an objection right, trading full localisation for price.
Evidence to request. Data-flow diagram; telemetry endpoint list; subprocessor list.
Owner. CIO, with CISO.
Protection 7: Security baseline and patch obligations
Control point E, cyber accountability · Before a multi-site term
What to secure. Per-device credentials, no shared fleet keys, verified TLS, a software bill of materials (SBOM), a vulnerability-disclosure policy, patch commitments mapped to CVEs and firmware versions, and a minimum update-support period.
Evidence anchor. Researchers report a shared hardcoded key and disabled TLS verification in a Unitree G1 web client (arXiv preprint; authors' claims). The Go1 backdoor was reported as patched silently, and the patch status of UniPwn is disputed (researcher-reported; IEEE Spectrum). CMS reports a CRA five-year minimum update-support period and SBOM requirements from 11 December 2027 (secondary-reported).
Buyer decision test. Can the vendor show which firmware version fixes which CVE?
Starting position (editorial framework). The buyer proposes that the vendor maintains per-device credentials, publishes a firmware-to-CVE fix history and supports security updates for a stated minimum period no shorter than the contract term.
Fallback (editorial inference). Accept vendor-defined patch targets by severity, with fix history disclosed on request and remedies for missed targets.
Evidence to request. Vulnerability-disclosure policy; SBOM; patch history; update-support statement.
Owner. CISO.
Protection 8: Vulnerability and incident notification to the buyer
Control point E, cyber accountability · Before any pilot data flows
What to secure. Notice to the buyer within defined hours of the vendor learning of a vulnerability or incident affecting the buyer's deployment, with cooperation, forensic logs, and alignment to the buyer's own reporting clocks.
Evidence anchor. The CRA reporting duties in Section 6.3 (verified; European Commission and ENISA pages) run to authorities, not buyers. Boston Dynamics' non-humanoid Spot terms contain no incident-notice clause that the researchers found (company-claimed; re-check).
Buyer decision test. Does the buyer learn of an incident in time to meet its own reporting clock?
Starting position (editorial framework). The buyer proposes that the vendor notifies the buyer within hours of becoming aware of a vulnerability or incident affecting the deployment and supplies forensic logs on request.
Fallback (editorial inference). Accept a longer window for non-critical vulnerabilities, keeping the shortest window for incidents involving customer data.
Evidence to request. Incident-response plan; notification template; named reporting contact.
Owner. CISO, with Legal Counsel.
Protection 9: Liability, indemnity, insurance and responsibility allocation (data and cyber only)
Control point E, cyber accountability · Before a multi-site term
What to secure. A named owner for configuration, access control, updates and incident response across customer, manufacturer and integrator; data and security breaches outside liability caps; indemnity for data-protection non-compliance; and evidence of insurance. Physical-safety liability is out of scope.
Evidence anchor. Morgan Lewis (18 June 2026) raises hacking responsibility, warranty and exit rights as questions for warehouse robot agreements, but does not address incident notice or audit (secondary-reported). Boston Dynamics' non-humanoid Spot terms state that the §10.3 liability caps do not apply to §11 breaches (company-claimed; re-check).
Buyer decision test. Is there a responsibility matrix, and are data and security breaches outside the liability cap?
Starting position (editorial framework). The buyer proposes that data and security breaches sit outside any liability cap, that each duty in a responsibility matrix has a named owner, and that the vendor indemnifies data-protection non-compliance it causes.
Fallback (editorial inference). Accept a higher dedicated cap for data and security breaches in place of unlimited liability.
Evidence to request. Draft responsibility matrix; insurance certificates; current liability terms.
Owner. Legal Counsel, with Procurement.
Protection 10: Retention, deletion and return on exit
Control point F, portability and exit · Before a multi-site term
What to secure. Retention limits by data class, deletion on request and at termination with a certificate covering backups and subprocessors, return in a documented machine-readable format, and deletion of facility maps.
Evidence anchor. Boston Dynamics' non-humanoid Spot terms allow indefinite retention of site-observed data, and the researchers found no deletion clause (company-claimed; re-check). Morgan Lewis raises post-termination data as a question (secondary-reported). Stapp distinguishes severable data from learning merged into a shared model (vendor-affiliated opinion).
Buyer decision test. Can you obtain a deletion certificate that covers subprocessors and backups?
Starting position (editorial framework). The buyer proposes that the vendor deletes customer data at termination or on request, certifies deletion including backups and subprocessors, and returns raw data in a documented machine-readable format.
Fallback (editorial inference). Accept deletion within a stated period after a transition window, with certification on request.
Evidence to request. Retention schedule; deletion certificate template; export format specification.
Owner. Chief Data Officer, with Legal Counsel.
Protection 11: Exit licence, transition assistance and continuity
Control point F, portability and exit · Before a multi-site term
What to secure. A licence to keep running customer-specific artefacts, transition services and documentation, continuity on vendor insolvency or change of control, termination rights for performance failure or insolvency, hardware return and site restoration, and step-in or escrow arrangements. Escrow is an ask, not an evidenced norm.
Evidence anchor. Agility reported 2025 net sales of $1.8M, an operating loss of $140M and a $2.5B SPAC valuation (secondary-reported). No public robot contract example was found for escrow or audit rights, and Morgan Lewis raises exit rights as a question (secondary-reported).
Buyer decision test. If the vendor fails or you leave, what keeps your operation running?
Starting position (editorial framework). The buyer proposes termination rights on vendor insolvency or change of control, a transition-services period, and a licence to continue running customer-specific artefacts after exit.
Fallback (editorial inference). Replace escrow with a documented continuity plan and an extended support period, trading escrow for price.
Evidence to request. Continuity plan; financial statements; transition-services description; hardware return terms.
Owner. Procurement, with Legal Counsel and Operations Leader.
Protection 12: Change-in-law and regulatory-status continuity
Control point F, portability and exit · Before a multi-site term
What to secure. A vendor warranty and duty to notify on regulatory status (FCC authorisation of the model, CRA reporting), update-continuity commitments, replacement or termination rights if status is lost, cooperation on Data Act, CRA and AI Act duties, and a stated allocation of cost.
Evidence anchor. FCC Public Notice DA 26-786 of 28 July 2026 (verified; to be checked against the primary PDF). Skadden and Sidley read previously authorised models as unaffected, and Skadden sees the action as capable of supporting change-in-law claims (secondary-reported). Whether foreign-owned US manufacturers are exempt is unresolved.
Buyer decision test. If the model's US or EU status changes, who bears the cost, and do updates continue?
Starting position (editorial framework). The buyer proposes that the vendor warrants the regulatory status of supplied models, notifies the buyer of any change, continues security updates, and bears replacement or termination costs where status is lost through the vendor's own supply decisions.
Fallback (editorial inference). Share cost by cause, with update continuity guaranteed and termination rights if status is lost.
Evidence to request. FCC authorisation identifiers for each model; vendor regulatory-status statement; notification procedure.
Owner. Legal Counsel, with Procurement.
8.13 Negotiation sequence
Pilot terms tend to become the default for expansion (editorial inference), so the negotiation should be sequenced by exposure. Before any pilot data flows, secure Protections 1, 3, 4, 5, 6 and 8. Before a multi-site or multi-year term, secure Protections 2, 7, 9, 10, 11 and 12. State in the pilot agreement that its terms are provisional and set no precedent, and agree a master schedule containing the multi-site protections before any expansion order. Trade only the items in V14: the scope of training consent against a price offset, exclusivity of customer-specific weights, and escrow. Walk away when a vendor will not define "improve", will not list telemetry endpoints or remote-access roles, or offers no deletion or exit return. No public contract shows what vendors accept on any of these points, so treat each position as a test to run in negotiation, not a settled ask.
Responsibility allocation matrix for Protection 9.
Illustrative allocation to be negotiated (editorial framework; not a sourced allocation). L = leads, S = supports, I = informed.
Duty | Customer | Manufacturer | Integrator |
Configuration and site settings | L | S | S |
Access control and credentials | L | S | S |
Firmware and security updates | I | L | S |
Vulnerability disclosure and fix history | I | L | S |
Incident notification to the customer | I | L | S |
Incident response inside the customer's network | L | S | S |
Data return and deletion at exit | S | L | S |
Regulatory-status notices | I | L | S |
Priority tiers, tradeable items and walk-away signals (editorial inference).
Tier | Protections or signals | Note |
Secure before any pilot data flows | 1, 3, 4, 5, 6, 8 | Pilot terms tend to become the expansion default |
Secure before a multi-site or multi-year term | 2, 7, 9, 10, 11, 12 | Agree in a master schedule before expansion |
Tradeable against a price offset | Scope of 3 (opt-in, aggregated, time-limited); exclusivity in 2; escrow in 11 | Apply the worksheet decision rule (V7) |
Walk-away signals | Vendor will not define "improve"; will not list telemetry endpoints or remote-access roles; offers no deletion or exit return | Each leaves a control point unpriceable |
Pilot agreement versus multi-site master agreement (editorial framework).
Protection | Pilot agreement | Multi-site master agreement |
1 Data title and licence scope | Required in full | Carried over and extended to all sites |
2 Derived assets | Record artefacts created | Ownership or licence terms |
3 Training opt-in | Required: default no training | Named opt-ins and revocation |
4 Sensor limits | Sensor schedule and no-go zones | Site-by-site schedules |
5 Remote access | Named roles and session logs | Subcontractor flow-down |
6 Data location | Endpoint and subprocessor lists | Change-notice and objection rights |
7 Security baseline | Request patch history | Binding baseline and patch commitments |
8 Incident notice | Required: notice within defined hours | Aligned to all applicable reporting clocks |
9 Liability | Named owners for pilot duties | Caps, indemnity and insurance |
10 Retention and deletion | Deletion at pilot end | Retention schedule and certification |
11 Exit and continuity | Hardware return | Insolvency, change of control, transition, escrow ask |
12 Change in law | Notice of status change | Cost allocation and termination rights |
9. Executive FAQ
Direct answer.
Six areas cover the questions to put to a humanoid robot vendor about data: the scope of ownership and use rights, whether customer data trains shared models, who can access cameras and sensors remotely, where data is processed and stored, what patch and incident evidence the vendor can show, and what is returned or deleted at exit. The answers below summarise the evidence and point to the relevant protections in Section 8, each labelled by evidence class.
Who owns the data a humanoid robot collects in my facility?
Ownership is whatever the contract says, and no contract text for a named humanoid deployment is public. GXO's chief technology officer said on 13 October 2026 that the industry has not figured it out (secondary-reported), and CMS reads the EU Data Act as giving access and use rules, not an ownership right (secondary-reported). Write title and use rights down. See Protection 1.
Can a humanoid robot vendor train its AI on my operational data?
Only if the contract allows it, so the contract should say so explicitly. Boston Dynamics' non-humanoid Spot terms permit use of site data to improve products without saying whether that includes machine-learning training (company-claimed; clause text to be re-checked). Vendors also source training data elsewhere, such as Figure's paid creators (company-claimed), so a default no-training position may cost them less than it appears. See Protection 3.
What happens to my data and customer-specific model if I switch humanoid robot vendors?
It depends on exit terms that no public humanoid contract shows. Thomas Stapp of GreyOrange distinguishes data that can be returned from learning merged into a shared model (vendor-affiliated opinion), so secure return of raw data, a licence to keep running customer-specific artefacts, and a deletion certificate. Ask also whether anything learned from your site can be removed from shared models. See Protections 2, 10 and 11.
Can vendor staff or remote operators see through a humanoid robot's cameras in my plant?
Not enough is public to say. Reported teleoperation examples involve home robots, such as 1X's reported VR-headset access (secondary-reported, dated), and no source gives enterprise remote-operator hours or intervention counts. Require named roles, locations, customer-visible session logs and subcontractor flow-down, and ask whether camera feeds leave the site and who stores them. See Protections 4 and 5.
What cybersecurity and patching obligations can I require from a humanoid robot vendor?
Require a published security baseline, a firmware-to-CVE fix history and a minimum update-support period. Researcher findings on Unitree show that patch status can be hard to verify (researcher-reported), and CRA reporting duties run from manufacturers to authorities, not to buyers (verified), so buyer notice must be contracted. Ask the vendor to confirm in writing which CVEs affect the supplied firmware. See Protections 7 and 8.
Does the FCC ban on foreign-made robots change my humanoid robot contract or software updates?
It can, depending on the model and its origin. DA 26-786 of 28 July 2026 stops new FCC authorisations for covered equipment, previously authorised models are unaffected, and a waiver for vulnerability-patching firmware changes runs to at least 1 January 2029 (secondary-reported). Whether foreign-owned US manufacturers are exempt is unresolved, so add change-in-law and update-continuity terms. See Protection 12.
Is a robots-as-a-service agreement different from buying a humanoid robot when it comes to data rights?
Hardware title differs, but data rights follow the contract under both models. Agility's reported terms are about $8,500 a month under RaaS or about $200,000 upfront for ownership (secondary-reported), and RaaS adds vendor-continuity risk because the vendor keeps the hardware. Secure Protections 1 and 11 under either model, and check return terms closely under RaaS because the hardware leaves with the vendor.
11. References and Strategic Sources
Direct answer.
Sources are ranked by tier: company filings, official regulator and government pages and vendor documents first, then IEEE Spectrum, the International Federation of Robotics and analyst research, then law-firm analysis and trade press, which are used to verify reported events rather than for analysis. Each source carries a classification of verified, company-claimed or secondary-reported. No company filing was opened, so all filing-derived numbers are secondary-reported, and the primary documents still to be checked are noted in the table. The limits are stated in the Scope and Disclaimer section.
• FCC: Public Notice DA 26-786, foreign-produced advanced robotic devices added to Covered List (28 Jul 2026). https://docs.fcc.gov/public/attachments/DA-26-786A1.pdf [Verified (Tier 1; to be verified against the primary document)]
• European Commission: CRA reporting page (Updated 11 Sep 2026). https://digital-strategy.ec.europa.eu/en/policies/cra-reporting [Verified (Tier 1)]
• ENISA: Cyber Resilience Act / Single Reporting Platform page (11 Sep 2026; SRP v1.3 noted 4 Nov 2026). https://www.enisa.europa.eu/topics/product-security-and-certification/cyber-resilience-act [Verified (Tier 1)]
• GOV.UK: Cyber Security and Resilience Bill collection (Page shows 18 Nov 2025 (metadata shows Nov 2026)). https://www.gov.uk/government/collections/cyber-security-and-resilience-bill [Verified (Tier 1)]
• GOV.UK: Regulations: consumer connectable product security (Published 8 Jan 2024; updated 17 Mar 2025). https://www.gov.uk/guidance/regulations-consumer-connectable-product-security [Verified (Tier 1)]
• ISO: ISO 25785-1 catalogue page (stage 30.20) (Undated). https://www.iso.org/standard/91469.html [Verified (Tier 1)]
• House Select Committee on the CCP: Letter to Secretaries Hegseth, Lutnick and Chairman Carr (6 May 2025). https://chinaselectcommittee.house.gov/media/letters/letter-to-secretary-hegseth-secretary-lutnick-and-chairman-carr [Verified (Tier 1)]
• House Select Committee on the CCP: Moolenaar, Obernolte, McClellan introduce GUARD Act (3 Jun 2026). https://chinaselectcommittee.house.gov/media/press-releases/moolenaar-obernolte-mcclellan-introduce-legislation-to-ban-dangerous-chinese-robots [Verified (Tier 1)]
• BMW Group Newsroom: Successful test of humanoid robots at BMW Group Plant Spartanburg (6 Aug 2024). https://newsroom.bmwgroup.com/global/successful-test-of-humanoid-robots-at-bmw-group-plant-spartanburg [Verified (Tier 1)]
• GXO Investor Relations: GXO signs industry-first multi-year agreement with Agility Robotics (27 Jun 2024). https://investors.gxo.com/news-releases/news-release-details/gxo-signs-industry-first-multi-year-agreement-agility-robotics [Verified (announcement only; commercial claims company-claimed) (Tier 1)]
• Hyundai Motor Group: CES 2026 Atlas / Physical AI plan (6 Jan 2026). https://www.hyundaimotorgroup.com/en/news/CONT0000000000198146 [Company-claimed (Tier 1)]
• Figure AI: F.02 Contributed to the Production of 30,000 Cars at BMW (19 Nov 2025). https://figure.ai/news/production-at-bmw [Company-claimed (Tier 1)]
• Figure AI: Introducing Index (25 Aug 2026). https://figure.ai/news/introducing-index [Company-claimed (Tier 1)]
• Figure AI: Privacy Policy (Effective 21 Jan 2026). https://figure.ai/privacy-policy [Company-claimed (Tier 1)]
• Agility Robotics: Strategic investment and agreement with Schaeffler Group (13 Nov 2024). https://www.agilityrobotics.com/content/agility-robotics-announces-strategic-investment-and-agreement-with-motion-technology-company-schaeffler-group [Company-claimed (Tier 1)]
• Agility Robotics: Agility Arc product page (Undated). https://agilityrobotics.com/solution/arc [Company-claimed (Tier 1)]
• Apptronik: Apptronik closes over $935 million Series A (11 Feb 2026). https://www.apptronik.com/news-collection/apptronik-closes-over-935-million-series-a [Company-claimed (Tier 1)]
• Boston Dynamics: Spot Terms and Conditions of Sale (SpotTCS 1.24) ("12-11-25" as printed). https://www.bostondynamics.com/wp-content/uploads/2020/05/spot-terms-and-conditions-of-sale.pdf [Company-claimed (Tier 1; clause text to be re-checked against the PDF)]
• Boston Dynamics: Orbit Terms and Conditions of Sale (ORBIT TCS 1.5) ("08-19-26" as printed). https://bostondynamics.com/wp-content/uploads/2024/03/orbit-terms-and-conditions-of-sale.pdf [Company-claimed (Tier 1; clause text to be re-checked against the PDF)]
• Unitree: Privacy Policy, Go app (Effective 14 Jul 2023). https://marketing.unitree.com/go2En/docPrivacy.html [Company-claimed (Tier 1)]
• Google DeepMind: Gemini Robotics On-Device 2 model card (30 Jul 2026). https://deepmind.google/models/model-cards/gemini-robotics-on-device-2/ [Company-claimed (Tier 1)]
• UBTech (via Kyodo News PR Wire): UBTech Walker S2 release (17 Nov 2025). https://kyodonewsprwire.jp/release/202511179261 [Company-claimed (Tier 1)]
• IEEE Spectrum: Unitree robot exploit (UniPwn) (25 Sep 2025; updated 24 Nov 2025). https://spectrum.ieee.org/unitree-robot-exploit [Verified (Tier 2)]
• IFR: New IFR position paper on humanoid robots (About Aug 2025). https://ifr.org/news/new-ifr-position-paper-on-humanoid-robots-published/ [Verified (Tier 2)]
• Interact Analysis: Humanoid robot revenue to reach $15bn by 2035 (release) (21 May 2026). https://interact-analysis.prezly.com/humanoid-robot-revenue-to-reach-15bn-by-2035.json [Analyst finding (Tier 3)]
• Counterpoint Research: Global humanoid robot shipments soar nearly 300% YoY in H1 2026 (headline only) (19-20 Aug 2026). https://counterpointresearch.com/en/insights/global-humanoid-robot-shipments-soar-nearly-300-percent-yoy-in-h1-2026 [Analyst finding (Tier 3)]
• Goldman Sachs: The global market for robots could reach $38 billion by 2035 (earlier forecast; not opened) (Undated). https://www.goldmansachs.com/intelligence/pages/the-global-market-for-robots-could-reach-38-billion-by-2035.html [Secondary-reported (Tier 3; not opened)]
• Skadden: FCC updates Covered List to include foreign-produced advanced robotic devices (5 Aug 2026). https://www.skadden.com/insights/publications/2026/08/fcc-updates-covered-list-to-include-foreign-produced-advanced-robotic-devices [Secondary-reported (Tier 3)]
• Sidley Austin: FCC adds all foreign-produced advanced robotic devices to Covered List (7 Aug 2026). https://www.sidley.com/en/insights/newsupdates/2026/08/fcc-adds-all-foreign-produced-advanced-robotic-devices-to-the-covered-list [Secondary-reported (Tier 3)]
• Cleary Gottlieb: Trade Watch: FCC adds robotics, House NDAA targets humanoids (not opened) (Aug 2026). https://www.clearytradewatch.com/2026/08/fcc-adds-foreign-produced-robotics-power-inverters-to-covered-list-house-ndaa-targets-foreign-adversary-humanoid-robots/ [Secondary-reported (Tier 3; not opened)]
• Steptoe: FCC adds advanced robotic devices to Covered List (not opened) (Aug 2026 (date not stated)). https://www.steptoe.com/en/news-publications/global-trade-and-investment-law-blog/fcc-adds-advanced-robotic-devices-to-the-covered-list.html [Secondary-reported (Tier 3; not opened)]
• White & Case: FCC prohibits new foreign-made power inverters and robots (not opened) (Aug 2026 (date not stated)). https://www.whitecase.com/insight-alert/us-federal-communications-commission-prohibits-new-foreign-made-power-inverters-and [Secondary-reported (Tier 3; not opened)]
• White & Case: EU AI Omnibus enters into force, amending the AI Act (4 Aug 2026). https://www.whitecase.com/insight-alert/eu-ai-omnibus-enters-force-amending-ai-act [Secondary-reported (Tier 3)]
• Gibson Dunn: EU AI Act Omnibus agreement (27 May 2026). https://www.gibsondunn.com/eu-ai-act-omnibus-agreement-postponed-high-risk-deadlines-and-other-key-changes/ [Secondary-reported (Tier 3)]
• EUROGIP: Machinery Regulation 2023/1230: what the Digital Omnibus on AI changes (6 Aug 2026 (modified 8 Sep 2026)). https://eurogip.fr/en/machinery-regulation-2023-1230-what-the-digital-omnibus-on-ai-changes/ [Secondary-reported (Tier 3)]
• CMS Germany: Data Act and Physical AI: who owns the data from connected robots (20 Jul 2026). https://cms.law/en/deu/legal-updates/data-act-and-physical-ai-who-owns-the-data-from-connected-robots [Secondary-reported (Tier 3)]
• CMS Germany: Cyber Resilience Act: new obligations for robot manufacturers (14 Sep 2026). https://cms.law/en/deu/legal-updates/cyber-resilience-act-new-obligations-for-robot-manufacturers [Secondary-reported (Tier 3)]
• Morgan Lewis: Top considerations of robotic use in warehouse agreements (18 Jun 2026). https://www.morganlewis.com/zh-cn/blogs/sourcingatmorganlewis/2026/06/top-considerations-of-robotic-use-in-warehouse-agreements [Secondary-reported (Tier 3)]
• DLA Piper: UK commencement of the data protection provisions in the DUAA (6 Feb 2026). https://privacymatters.dlapiper.com/2026/02/uk-commencement-of-the-data-protection-provisions-in-the-data-use-and-access-act/ [Secondary-reported (Tier 3)]
• Kennedys: DUAA 2025: commencement dates and planned guidance for 2026 (Undated (pre-Feb 2026); superseded). https://www.kennedyslaw.com/en/thought-leadership/article/2026/the-data-use-and-access-act-2025-commencement-dates-and-planned-guidance-for-2026 [Secondary-reported (Tier 3)]
• ISACA: UK Cyber Security and Resilience Bill: Lords Report Stage takeaways (Oct/Nov 2026). https://www.isaca.org/resources/news-and-trends/isaca-now-blog/2026/the-uks-cyber-security-and-resilience-nis-bill-five-key-takeaways-from-lords-report-stage [Secondary-reported (Tier 3)]
• Saga Legal via Legal 500: The privacy timer starts now: DPDP Rules and the 18-month countdown (About Nov 2025). https://www.legal500.com/firms/237811-saga-legal/c-india/news-and-developments/the-privacy-timer-starts-now-analysing-the-dpdp-rules-and-its-18-month-countdown [Secondary-reported (Tier 3)]
• Storyboard18 / AZB & Partners: DPDP Rules coverage (not opened) (Nov 2025 (AZB: 19 Nov 2025)). https://www.storyboard18.com/amp/digital/breaking-govt-notifies-final-dpdp-rules-sets-staggered-rollout-with-key-obligations-for-data-fiduciaries-84201.htmhttps://www.azbpartners.com/bank/update-indias-digital-personal-data-protection-framework-comes-into-effect/ [Secondary-reported (Tier 3; not opened)]
• FDD: As Chinese robotics industry surges, Senate considers limited federal procurement ban (27 Mar 2026). https://www.fdd.org/analysis/2026/03/27/as-chinese-robotics-industry-surges-senate-considers-limited-federal-procurement-ban/ [Secondary-reported (Tier 3)]
• Recorded Future (Insikt Group): Hacking Embodied AI (5 May 2026). https://www.recordedfuture.com/research/hacking-embodied-ai [Company-claimed (Tier 3)]
• arXiv (Mayoral-Vilches, Makris, Finisterre): The cybersecurity of a humanoid robot / G1 analysis, 2509.14139v3 (Sep 2025). https://arxiv.org/pdf/2509.14139v3 [Verified (preprint exists; authors' claims) (Tier 3)]
• arXiv: 2509.14096 companion paper (title only) (Sep 2025). https://arxiv.org/html/2509.14096v1 [Secondary-reported (not opened) (Tier 3; not opened)]
• Alias Robotics: Case study, humanoid robot G1 (Undated). https://aliasrobotics.com/case-study-humanoid-robot-g1.php [Company-claimed (Tier 3)]
• media.ccc.de (39C3): Skynet Starter Kit: from embodied AI jailbreak to remote takeover of humanoid robots (28 Dec 2025). https://media.ccc.de/v/39c3-skynet-starter-kit-from-embodied-ai-jailbreak-to-remote-takeover-of-humanoid-robots [Secondary-reported (researcher claims) (Tier 3)]
• TakeOnMe: CVE-2025-2894 page (CVE 27 Mar 2025). https://takeonme.org/cves/cve-2025-2894 [Secondary-reported (Tier 4)]
• SentinelOne: Vulnerability database, CVE-2025-35027 (NVD 26 Sep 2025). https://www.sentinelone.com/vulnerability-database/cve-2025-35027/ [Secondary-reported (Tier 4)]
• Axios: Chinese robotics manufacturer left backdoor in product (1 Apr 2025). https://www.axios.com/2025/04/01/threat-spotlight-backdoor-in-chinese-robots-future-of-cybersecurity [Secondary-reported (Tier 4)]
• Help Net Security: Unitree G1 humanoid robot vulnerability (16 Oct 2025). https://www.helpnetsecurity.com/2025/10/16/unitree-g1-humanoid-robot-vulnerability/ [Secondary-reported (Tier 4)]
• Security Affairs: Hack one robot, reach the next: Unitree G1 security flaws (29 Aug 2026). https://securityaffairs.com/198085/hacking/hack-one-robot-reach-the-next-unitree-g1-security-flaws.html [Secondary-reported (Tier 4)]
• The Hacker News: FCC blocks new foreign-produced robots (28 Jul 2026). https://thehackernews.com/2026/07/fcc-blocks-new-foreign-produced-robots.html?m=1 [Secondary-reported (Tier 4)]
• The Hacker News: Humanoid tag page (G1 EDU summary, 28 Aug 2026) (28 Aug 2026). https://thehackernews.com/search/label/Humanoid [Secondary-reported (Tier 4)]
• The Register: FCC robot ban coverage (29 Jul 2026). https://www.theregister.com/a/5280145 [Secondary-reported (Tier 4)]
• Humanoid.guide: Unitree patch-status piece (summarising Tech Times) (Sep 2026). https://humanoid.guide/?p=17802 [Secondary-reported (Tier 4)]
• unwire.hk: UK police Chinese robot dogs security risks (3 Sep 2025). https://unwire.hk/2025/09/03/uk-police-chinese-robot-dogs-security-risks [Secondary-reported (Tier 4)]
• DigitalToday: Unitree survives US-China tech robot curbs (10 Aug 2026). https://www.digitaltoday.co.kr/en/view/91186/unitree-survives-us-china-tech-robot-curbs-existing-six-models-can-still-be-sold [Secondary-reported (Tier 4)]
• The Robot Report: Industry reacts to FCC ban (29 Jul 2026). https://www.therobotreport.com/industry-reacts-fcc-ban-u-s-imports-new-humanoid-quadruped-robots/ [Secondary-reported (Tier 4)]
• The Robot Report: Agility Robotics reports $1.8M revenue ahead of humanoid SPAC (title inferred from URL) (7 Sep 2026). https://www.therobotreport.com/agility-robotics-reports-18m-revenue-ahead-of-humanoid-spac/ [Secondary-reported (Tier 4; to be verified against the primary document; S-4 to be obtained)]
• The Robot Report: Figure AI raises $1B Series C (Sep 2025). https://www.therobotreport.com/figure-ai-raises-1b-in-series-c-funding-toward-humanoid-robot-development/ [Secondary-reported (Tier 4)]
• ClickOrlando (AP-style): US bans foreign-made humanoid robots (29 Jul 2026). https://www.clickorlando.com/business/2026/07/29/us-bans-foreign-made-humanoid-robots-targeting-china-over-national-security/ [Secondary-reported (Tier 4)]
• Washington Times: Lawmakers propose bill to block sale of China-built robots (headline only) (4 Jun 2026). https://m.washingtontimes.com/news/2026/jun/4/lawmakers-propose-bill-block-sale-robots-built-china/ [Secondary-reported (Tier 4)]
• eWeek: US Chinese robots federal security bill (not opened) (Jun 2026). https://www.eweek.com/news/us-chinese-robots-federal-security-bill/ [Secondary-reported (Tier 4; not opened)]
• TechNode: Chinese makers accounted for more than 97% of global humanoid shipments in H1 2026 (11 Aug 2026). https://technode.com/2026/08/11/chinese-makers-accounted-for-more-than-97-of-global-humanoid-robot-shipments-in-h1-2026/ [Secondary-reported (Tier 4)]
• Humanoid.guide: AgiBot leads H1 2026 humanoid shipments with 8,600 units (headline only) (Not stated). https://humanoid.guide/agibot-leads-h1-2026-humanoid-shipments-with-8600-units/ [Secondary-reported (Tier 4)]
• Humanoid.guide: Goldman raises 2035 humanoid robot forecast to 6.5 million (15 Sep 2026 (modified 21 Sep)). https://humanoid.guide/goldman-raises-2035-humanoid-robot-forecast-to-6-5-million/ [Secondary-reported (Tier 4)]
• 24/7 Wall St.: Robots everywhere: Goldman Sachs now sees 6.5 million humanoid robots by 2035 (13 Sep 2026). https://247wallst.com/investing/2026/09/13/robots-everywhere-goldman-sachs-now-sees-6-5-million-humanoid-robots-by-2035/ [Secondary-reported (Tier 4)]
• SCMP / Humanoid.guide: Morgan Stanley raises China humanoid shipment forecast to 50,000 (headlines only) (About 24 Jun 2026). https://www.scmp.com/tech/article/3358210/morgan-stanley-raises-china-humanoid-robot-shipment-forecast-50000-unitshttps://humanoid.guide/morgan-stanley-doubles-china-humanoid-robot-forecast/ [Secondary-reported (Tier 4; not relied on; not opened)]
• Robotics 24/7: Report: humanoid robot revenue to reach $15 billion by 2035 (23 May 2026). https://www.robotics247.com/article/report-humanoid-robot-revenue-to-reach-15-billion-by-2035 [Secondary-reported (Tier 4)]
• Robotics 24/7: Humanoid raises $152M at $1.35 billion post-money valuation (22 Jul 2026). https://www.robotics247.com/article/humanoid-raises-152m-at-1.35-billion-post-money-valuation [Secondary-reported (Tier 4)]
• Robotics 24/7: Agility announces agreement to deploy Digit at Toyota Motor Manufacturing Canada (headline only) (Not stated). https://www.robotics247.com/article/agility-robotics-announces-agreement-to-deploy-digit-humanoid-at-toyota-motor-manufacturing-canada/Agility_Robotics [Secondary-reported (Tier 4; not opened)]
• Automation.com: Humanoid robots: vision and reality (date source for IFR paper) (Aug 2025). https://www.automation.com/en-us/articles/august-2025/humanoid-robots-vision-reality-position-paper [Secondary-reported (Tier 4)]
• Automation World (T. Stapp): Who owns what robots learn: the next industrial automation contract fight (7 Oct 2026). https://www.automationworld.com/factory/robotics/article/55410053/who-owns-what-robots-learn-the-next-industrial-automation-contract-fight [Secondary-reported (Tier 4)]
• TechJournal UK: Who owns robot training data becomes... (Economist panel report) (23 Oct 2026). https://www.techjournal.uk/p/who-owns-robot-training-data-becomes [Secondary-reported (Tier 4)]
• Runtime Wire: Figure Index human-video robot training data (25 Aug 2026). https://runtimewire.com/article/figure-index-human-video-robot-training-data [Secondary-reported (Tier 4)]
• RuntimeWire: GXO / Agility Digit two new warehouse sites (26 Oct 2026). https://runtimewire.com/article/gxo-agility-digit-two-new-warehouse-sites [Secondary-reported (Tier 4)]
• Robotics & Automation News: Agility Robotics says more than 30 companies considering Digit (2 Nov 2026). https://roboticsandautomationnews.com/2026/11/02/agility-robotics-says-more-than-30-companies-considering-digit-humanoid-robot/106595/ [Secondary-reported (Tier 4)]
• Assembly Magazine: Humanoid robot Digit moves 100,000 totes (24 Nov 2025). https://www.assemblymag.com/articles/99671-humanoid-robot-digit-moves-100-000-totes-at-distribution-center [Secondary-reported (Tier 4)]
• Automotive World: Humanoid robots scale up at GXO with Agility expansion (press release reproduction) (Undated). https://www.automotiveworld.com/news-releases/humanoid-robots-scale-up-at-gxo-with-agility-expansion/ [Secondary-reported (Tier 4)]
• AI Business: Tesla Optimus production starts, Q3 2026 results (22 Oct 2026). https://aibusiness.vc/robots/tesla-optimus-production-starts-q3-2026-results-when-you-can-buy-one [Secondary-reported (Tier 4)]
• TechCrunch: Tesla starts Optimus robot production in California as profit falls 43% (21 Oct 2026). https://techcrunch.com/2026/10/21/tesla-stars-optimus-robot-production-in-california-as-profit-falls-43/ [Secondary-reported (Tier 4)]
• Nasdaq / Motley Fool: Tesla Optimus: key takeaways from Q3 earnings call (25 Oct 2025). https://www.nasdaq.com/articles/tesla-optimus-humanoid-robot-key-takeaways-q3-earnings-call [Secondary-reported (Tier 4)]
• Bloomberg: Airbus humanoid order sends Chinese robot maker's shares surging (19 Jan 2026). https://www.bloomberg.com/news/articles/2026-01-19/airbus-humanoid-order-sends-chinese-robot-maker-s-shares-surging [Secondary-reported (Tier 4)]
• eWeek: BMW factory AI robots (29 Jun 2026). https://www.eweek.com/news/bmw-factory-ai-robots/ [Secondary-reported (Tier 4)]
• eWeek: Hyundai Atlas humanoid robots factories (21 May 2026). https://eweek.com/news/hyundai-atlas-humanoid-robots-factories [Secondary-reported (Tier 4)]
• eWeek: China deploys humanoid robots, UBTech Walker (not opened) (Nov 2025). https://www.eweek.com/news/china-deploys-humanoid-robots-ubtech-walker/ [Secondary-reported (Tier 4; not opened)]
• Korea Herald: Humanoid robot to enter production lines at Hyundai's Georgia Metaplant in 2028 (title only) (Jan 2026). https://www.koreaherald.com/article/10649929 [Secondary-reported (Tier 4; not opened)]
• Boerse Express: UBTech Robotics article (AI-assisted; ad-box date anomaly) (23 Jul 2026). https://www.boerse-express.com/news/articles/ubtech-robotics-aktie-1000-walker-s2-ausgeliefert-siemens-partnerschaft-931458 [Secondary-reported (Tier 4; not relied on)]
• The Standard (Hong Kong): Chinese humanoid robot maker Unitree prices IPO at 61 billion yuan valuation (About 6-10 Aug 2026). https://www.thestandard.com.hk/finance/article/339267/Chinese-humanoid-robot-maker-Unitree-prices-IPO-at-61-billion-yuan-valuation [Secondary-reported (Tier 4)]
• Startup Fortune: Apptronik's Apollo robot has left the lab (self-corrected) (25 Jun 2026). https://startupfortune.com/apptroniks-apollo-robot-has-left-the-lab-and-is-now-working-factory-shifts-at-mercedes-benz/ [Secondary-reported (Tier 4)]
• Trending Topics: Apptronik raises $520 million, valuation about $5 billion (headline only) (Feb 2026). https://www.trendingtopics.eu/apptronik-raises-520-million-for-humanoid-robots-valuation-climbs-to-around-5-billion/ [Secondary-reported (Tier 4)]
• Ynet News: 1X NEO early-buyer contract and remote operation (31 Oct 2025). https://www.ynetnews.com/tech-and-digital/article/hkq6sazkzl [Secondary-reported (Tier 4)]
• electrive.com: My colleague, the robot: Optimus learns from Tesla employees in Grünheide (22 Jul 2026). https://electrive.com/2026/07/22/my-colleague-the-robot-optimus-learns-from-tesla-employees-in-grunheide [Secondary-reported (Tier 4)]
• IIoT World: Physical AI deployment ROI, humanoid robots (not relied on) (13 Apr 2026). https://www.iiot-world.com/artificial-intelligence-ml/robotics/physical-ai-deployment-roi-humanoid-robots [Secondary-reported (Tier 4; not relied on)]
• Unite.ai: Figure introduces Helix 2.5, tested zero-shot in 30 unseen homes (Not verified). https://unite.ai/figure-introduces-helix-2-5-tested-zero-shot-in-30-unseen-homes [Secondary-reported (Tier 4)]
• Mammothtimes (AI-syndicated): AI-syndicated page on Atlas at Hyundai's Georgia Metaplant (contradicted by Hyundai's 2028 plan) (16 Jan 2026). https://business.mammothtimes.com/mammothtimes/article/tokenring-2026-1-16-beyond-the-lab-boston-dynamics-electric-atlas-begins-autonomous-shift-at-hyundais-georgia-metaplant [Secondary-reported (Tier 4; not relied on)]
• MIT Technology Review; TechCrunch (XDOF): Gig workers training humanoids (1 Apr 2026); collecting robot training data (17 Jun 2026) (1 Apr 2026; 17 Jun 2026). https://www.technologyreview.com/2026/04/01/1134863/humanoid-data-training-gig-economy-2026-breakthrough-technology/https://techcrunch.com/2026/06/17/collecting-robot-training-data-is-dirty-unglamorous-work-some-ai-labs-are-already-paying-xdof-to-do-it/ [Secondary-reported (Tier 4; not opened)]
• Mondaq / Loeb & Loeb: AI in robotics: key contract and legal risks (Dec 2025) (surfaced, not read) (Various). https://www.mondaq.com/unitedstates/new-technology/1716602/ai-in-robotics-key-contract-and-legal-risks [Secondary-reported (not read)]
• Stephens Scown: Robotics and robot-as-a-service: structuring for growth and risk management (surfaced, not read) (Various). https://www.stephens-scown.co.uk/specialist-sectors/technology/robotics-and-robot-as-a-service-structuring-for-growth-and-risk-management/ [Secondary-reported (not read)]
• Seyfarth: The AI-driven evolution of robotics (surfaced, not read) (Various). https://www.seyfarth.com/news-insights/the-ai-driven-evolution-of-robotics.html [Secondary-reported (not read)]
• ABA Business Law Today: AI Services Addendum for Procurement Contracts (Aug 2024) (surfaced, not read) (Various). https://businesslawtoday.org/wp-content/uploads/2024/08/AI-Services-Addendum-for-Procurement-Contracts-Aug.-2024.docx [Secondary-reported (not read)]
• Pillsbury: CISA AI-in-OT framework (surfaced, not read) (Various). https://www.pillsburylaw.com/en/news-and-insights/cisa-ai-ot-framework.html [Secondary-reported (not read)]
• Mayer Brown: Multi-agency guidance on securing agentic AI systems (2026) (surfaced, not read) (Various). https://www.mayerbrown.com/ja/insights/publications/2026/06/multi-agency-guidance-on-securing-agentic-ai-systems [Secondary-reported (not read)]
• ASD ACSC: Secure by Demand: priority considerations for OT owners and operators (14 Jan 2025; fetch blocked) (surfaced, not read) (Various). https://www.cyber.gov.au/resources-business-and-government/governance-and-user-education/secure-by-design/secure-demand-priority-considerations-operational-technology-owners-and-operators-when-selecting-digital-products [Secondary-reported (not read)]
• European Commission: Safer and more secure digital products (CRA application dates: reporting 11 September 2026; main obligations 11 December 2027) (11 Sep 2026). https://commission.europa.eu/news-and-media/news/safer-and-more-secure-digital-products-2026-09-11_en [Verified (Tier 1; official page)]
Decision for the Automation and Procurement Buyer: request in writing, from every shortlisted vendor, the evidence listed on Protections 1, 3, 4, 5, 6 and 8, and do not release pilot data to a vendor that supplies none of it.
This report is backed by authoritative research, independent verification, and structured analytical methodology.
© 2026 Physical AI Journal, a publication of Sekason Research Limited (UK Company No. 14339910). All rights reserved. Market and adoption intelligence only; not legal, engineering or safety advice.



