--- title: "Hardware that does not report on you" url: "https://kyberdeck.com/blog/hardware-that-does-not-report-on-you" description: "Most connected devices report on their owners by design: telemetry, accounts, cloud processing. This is what hardware looks like when there is nothing to report." --- # Hardware that does not report on you October 8, 2026·3 min read·Editorial team Close-up of a card computer with its mute slider switched off and a metal shutter over the microphone, a detached antenna beside it You press the mute button on the speaker in your kitchen and a ring turns red. Is the microphone off? The red ring is drawn by the same software that decides when to listen, so the honest answer is: it is off if that software says so. Meanwhile your television sends a list of what you watched to an analytics service, your phone uploads “diagnostics” every night, and your car reports where it parked. You agreed to all of it, once, on a screen you scrolled past. None of these devices is spying in the cinematic sense. They report, routinely, because reporting is part of how they were paid for. ## The real cause: the business model needs the report A device sold below cost, or sold once and supported for years, has to earn somewhere. When the earning happens through advertising, analytics or data partnerships, every design decision leans towards collecting. The controls that would stop the flow are built as settings, inside software the vendor updates — so the vendor keeps the last word over a switch you thought was yours. ## How devices report on you **Telemetry by default.** Usage analytics and diagnostics are on out of the box, and turning them off is a hunt through menus that an update can quietly reset. **The mute that is a setting.** A software toggle and a software-drawn light. You cannot tell it apart from a real cut, and neither can anyone auditing the device from the outside. **An account as the price of entry.** The device does nothing until you sign in, which ties everything it sees to one identity in one company’s records. **Cloud processing for everything.** Every word goes to a server because that is where the model lives — and once it is there, retention is a policy, not a property. **Updates that change the deal.** The device you bought is not the device you own a year later; terms and data flows move with the firmware. **Firmware nobody can read.** Closed code on a closed board means every promise is unverifiable by design. ## Built so there is nothing to report KyberDeck starts from the opposite end: the safest data is data that was never sent, and the most trustworthy switch is one that software cannot override. **A circuit, not a setting.** `kyber mute --hard` describes a physical switch that cuts the microphones and the camera. The indicator is wired to the same line, so when it is dark, the microphone has no power. The Card has a hardware mute; the Band has a slider that makes it deaf. **No KyberDeck account.** There is no account holding your recordings and no advertising business to feed. Your identity is the one your KyberBot acts under, held on your own devices. [Your data is not the product](https://kyberbot.com/blog/your-data-is-not-the-product) sets out what that means for the assistant. **On the device first.** `kyber listen` captures and transcribes on the device. Nothing leaves it unless a policy you can read says it may, and the [home node](https://kyberdeck.com/blog/the-home-node) takes what is too big for a pocket without anything leaving the house. **When it has to leave, it leaves unlinked.** Some work genuinely needs more compute. Then it goes, encrypted, to KyberFusion, a cloud designed so that a node can do the work without learning who asked. Anonymity is the goal that cloud is built for, not a claim we can make before launch; [what a cloud node knows about you](https://kyberfusion.com/blog/what-a-node-knows-about-you) is honest about where that line sits. **Readable all the way down.** Published schematics, documented parts and an open system: KyberLinux, with verified boot and atomic updates, so that an update cannot quietly change what the device does. [One system from the wrist to the rack](https://kyberlinux.com/blog/one-system-from-wrist-to-rack) explains why the same rules hold on every form. We cannot prove any of this to you yet. There are no units, and these are design commitments rather than test results. What we can do is publish the schematics, both SDKs and the OS image together, so the claims can be checked instead of trusted. That plan is on [the homepage](https://kyberdeck.com/), and the forms it covers are in [the five forms of KyberDeck](https://kyberdeck.com/blog/five-forms-of-kyberdeck). ## A test you can run today Two checks. Neither needs more than ten minutes of your attention. **The wake-word test.** Mute a voice assistant with its own button, then say its wake word clearly. If anything happens — a light, a chime, a “the microphone is off” — something was still listening closely enough to hear its name. If nothing happens, that proves nothing either way, which is exactly the problem with a mute you cannot see. **The night-time test.** Open your router’s list of connected devices, or run a DNS logger such as Pi-hole on a spare board, and leave it overnight. In the morning, count how many different domains your television, your speaker and your phone contacted while you were asleep. Every one of them is a report you did not write. - privacy - telemetry - hardware mute - KyberDeck ## Keep reading - [A robot is a deck with wheels](https://kyberdeck.com/blog/a-robot-is-a-deck-with-wheels) - [Build your own cyberdeck on KyberLinux in a weekend](https://kyberdeck.com/blog/build-your-own-cyberdeck)