No cameras. No microphones.
Presence, proven.

Modern phones, watches, earbuds, and trackers constantly emit short radio announcements (Wi-Fi probe requests and Bluetooth Low Energy advertisements) as part of normal operation, whether or not they're being used. The hub passively listens to these broadcasts; the penny-sized nodes don't scan at all, they just sense motion and wake the hub. Nothing is connected to, nothing is intercepted, and no communication content is ever visible to the system. Only the public identifiers, signal strength, and timing are logged.

It weakens single-identifier tracking rather than eliminating it: a rotating address is a poor long-term handle, but rotation runs on very different clocks, and a freshly logged identifier often stays live for hours or days. Digital Tripwire treats that honestly on three horizons. In real time, confidence comes from the device cluster: phone, smartwatch, earbuds, tracker, fob, most of which emit consistent identifiers, matched with temporal correlation and scored on every event. In the near term, a logged identifier inside its rotation window can be reacquired in the field as an investigative lead. And in the long term, identifiers become matchable after a lawful seizure through stored per-network MACs and IRK resolution, covered in the attribution section and the next question down.

Three properties working together. Authentication: each record is created automatically by a documented process at capture, on the node. Integrity: SHA-256 hashing with each record embedding the previous record's hash makes the log a tamper-evident chain, where any alteration is arithmetically visible. Custody: records upload immediately over cellular to encrypted storage, and export in a documented format with the full chain intact so any expert, including opposing counsel's, can verify it independently.

No, and not by settings: by hardware. There is no camera, no microphone, and no GPS in the node. It cannot see, hear, or follow anyone. It records device presence: which radio identifiers were near it, at what signal band, and when. The privacy section above walks through everything deliberately absent from the hardware.

Nodes run for years on a coin cell because they do exactly one job: sense motion, send a trigger. The hub monitors its paired nodes and the app shows each node's status and battery, with a health notification well before one needs attention. Home lives on USB-C power, so there's nothing to charge; Mobile recharges like a phone. Beyond that there is no routine maintenance: no cleaning, no recalibration, nothing to babysit.

Removal is itself evidence. Moving the node is exactly what a node detects, so the act of grabbing it fires the trigger: the hub wakes, scans the room, seals the record, and uploads it while the app alerts you in real time. And because records never live on the node in the first place (they're created on the hub and pushed off-site) destroying the node destroys nothing. In practice, the removal event plus the moments before it is often the most incriminating sequence in the whole log.

Yes. The hub uploads over an integrated cellular connection, independent of your Wi-Fi and your router, so cutting the internet (a classic pre-theft move against camera systems) changes nothing. Home runs on USB-C power with its internal battery carrying it through an outage; Mobile is battery-powered by nature. The nodes themselves run on their own coin cells and don't depend on building power at all.

Not by itself, and that's by design. The system logs device signatures, not identities, and the signatures are stored as salted hashes. Attribution to a person happens through context: an institution matching against a watch list it lawfully holds, or a post-incident comparison against the devices of the people known to have had access. The system's job is to document presence beyond dispute. Establishing identity remains with people and institutions using their existing lawful processes, which is exactly where a civil society should keep it.

Then it has no one to talk to, and we'd rather tell you that than pretend otherwise. Nodes speak short-range encrypted Bluetooth to hubs; a node that moves beyond every hub's range can't report until a hub is in range again. In practice that's a placement question: Home covers the rooms around it, and Mobile extends coverage to wherever you are, your car, your hotel room, your bag. Any hub on your account can hear any node on your account, so protection travels with your hardware, not with a single fixed box.

Often, yes, once a device is lawfully seized and forensically examined. Two mechanisms make this work. First, phones store the randomized Wi-Fi MAC they generate for each network and reuse it for that network, and those stored per-network MACs are recoverable in a standard forensic extraction. Second, rotating Bluetooth addresses are generated from the device's Identity Resolving Key (IRK); with the IRK extracted from the seized device, every past rotating address it broadcast becomes mathematically resolvable, including ones the hub logged weeks earlier. This is why the system retains every event, even low-confidence single-identifier detections: an identifier that meant nothing at capture can become the corroborating link after seizure, and the hash chain proves the record existed before anyone knew which device to look for.