Do not infer a KOKO label from a general security statement
The U.S. Cyber Trust Mark is an FCC voluntary labeling program for eligible wireless consumer Internet of Things products. Homebot One's overview did not provide a KOKO product authorization when checked on October 2, 2026. Ask for evidence for the offered product; that page alone cannot establish whether an authorization exists.
A logo-like image, a reference to NIST, or an FCC equipment authorization should not be treated as evidence of Cyber Trust Mark authorization. Verify the exact offered model and configuration through Homebot One and the applicable program record before relying on the claim.
Understand what the FCC program is designed to show
The FCC's 2024 order established a voluntary program for qualifying consumer IoT products. The adopted structure calls for conformance testing, an application reviewed by a Cybersecurity Label Administrator, and authorization before use of the mark. The label includes a QR code intended to direct consumers to product information in a registry. NIST IR 8425 supplies a consumer IoT cybersecurity baseline that informed the program.
The label concerns defined cybersecurity requirements for the IoT product, which can include the device and necessary components such as an app or backend. It is not a promise that a robot can perform a task, is physically safe in every home, protects every category of personal information under every use, or will remain secure forever. It also does not replace privacy review, safety testing, support terms, or a demonstration of the intended routine.
- Voluntary participation rather than a requirement for every connected product
- Product-level evidence rather than a company-wide reputation statement
- A defined configuration and necessary components rather than an informal product family name
- Authorization for the listed product and support commitments buyers should review
Verify the exact product, version, and registry destination
If a KOKO offer displays or references the mark, request the authorization granted by the issuing Cybersecurity Label Administrator and the product registry link accompanying the label. The FCC adopted a decentralized registry structure, so do not assume every valid entry sits on an FCC-hosted product page. Match the manufacturer, product, model, configuration, and identifiers in the record to the unit or written offer, then save the checked date and any unresolved differences.
A QR code is a link, not evidence by itself. Check the destination before opening it and ask for an accessible non-QR link if needed. Trace claims in reseller listings, screenshots, or search snippets to the manufacturer's product record and issuing administrator. A search typed as Coco or Co Co still needs the same exact product and manufacturer match.
- Exact manufacturer and product name
- Model, hardware version, software version, and product components
- Issuing Cybersecurity Label Administrator, grant, and current authorization status
- Minimum support period and update information shown for the product
- Date checked and person who performed the verification
Keep other FCC, safety, and interoperability claims separate
Connected hardware may have other FCC identifiers or authorizations related to radio-frequency rules. Those records serve a different purpose and should not be described as the Cyber Trust Mark. Likewise, a safety test, accessibility report, privacy notice, smart-home compatibility claim, or industry certification answers a different question. Record each claim under its own source, scope, model, and date.
Ask whether a claimed label covers the physical KOKO unit alone or the IoT product components needed for the offered experience. Check how optional accessories, developer software, third-party integrations, and later updates affect the scope. A verified mark can be a useful input, but it should not be stretched beyond the components and version the record actually names.
Use the mark as one line in a broader decision record
Build a small evidence table with the question, source, exact product, version, checked date, finding, and remaining uncertainty. Add authentication, updates, vulnerability reporting, data protection, secure reset, support lifetime, incident response, and end-of-use steps. These subjects align with NIST's consumer IoT baseline and can be discussed even when a product has no label claim.
If KOKO's program or hardware changes, verify again instead of carrying an older result forward. A pilot unit, research platform, developer build, and later consumer product may have different components and evidence. The decision should say what was verified and avoid converting one label into a general endorsement of Homebot One, KOKO's performance, or a particular household use.
Check current KOKO availability and access paths
Ask what a complete KOKO quote should include
Frequently asked questions
Does this article confirm that KOKO has the U.S. Cyber Trust Mark?
No. It explains how to verify a product claim. Request the issuing administrator's authorization and the label-linked product registry record, then match both to the offered KOKO unit and configuration.
Is the U.S. Cyber Trust Mark mandatory for every home robot?
The FCC established it as a voluntary labeling program for eligible wireless consumer IoT products. Eligibility depends on the rules and product, and a research or developer platform should not be assumed eligible merely because it connects to a network.
Does an FCC equipment identifier prove Cyber Trust Mark authorization?
No. Radio equipment authorization and the voluntary IoT cybersecurity label serve different purposes. Verify each through the appropriate official record.
Does the mark prove that KOKO is safe and private in every home?
No. A verified label addresses the program's cybersecurity requirements for the named IoT product. Physical safety, privacy, task performance, accessibility, and fit still require separate evidence.
Sources & further reading
From Homebot One, the team building KOKO in Fremont, California.
