"Private" is a word robotics companies use loosely. We define it in engineering terms, not marketing terms, because that's the only version that survives a skeptical buyer, or a journalist, asking follow-up questions.
What we will never claim
- That a part or design is "100% private" without naming exactly what stays local and what doesn't.
- That any third-party software bundled into a build (Home Assistant, a cloud LLM, a mobile app) is private by default, most consumer smart-home and AI stacks phone home unless deliberately configured not to.
- Unverified safety or security claims about parts we didn't design from scratch.
Third-party exposure builders should know about
| Component | What happens by default | What to check |
|---|---|---|
| Home Assistant | Optional analytics, optional cloud remote access (Nabu Casa) | Disable analytics; use local-only remote access if you need it |
| Cloud AI/LLM services | Prompts and sometimes audio/video leave the device | Prefer on-device or self-hosted inference for anything voice- or camera-driven |
| Companion mobile apps | Often include third-party analytics SDKs | Check the app's own privacy disclosures before installing |
Our position
We sell files and prints, not a managed cloud service, there is no CyberFab account required to use a part you buy from us, and nothing we ship phones home. What you build around the part (network gear, AI compute, companion apps) is your architecture and your choice; we tell you where the real exposure points are instead of pretending they don't exist.