Skip to content
RoboblackboxRuntime data recorder

Privacy

Last updated September 13, 2026.

This website

We set no cookies and use no advertising or marketing trackers. We do count page views, using Cloudflare Web Analytics: it loads a small script from our host, records the page visited, the page you came from, and coarse details such as country and browser, and it sets no cookie and no identifier that follows you to any other site. Our web host keeps standard server logs (IP address, requested page, time) for up to thirty days for security and capacity; we do not analyse them for marketing. If you email us, we keep your message and reply in our mailbox for as long as the conversation is useful, and we delete it when you ask. We do not sell, rent, or share contact details with anyone.

The recorder, in one paragraph

A Roboblackbox appliance sits at the operator's site and records what the robot fleet publishes on its own network. The raw record stays on the appliance. Three kinds of data leave the site on their own, all agreed at signing: a small heartbeat (about 500 bytes a minute: health, versions, disk, clock); the fingerprint of each sealed record (a hash, not the content), so that we can later show the record was not changed; and, at the close of each period, the findings and summaries the appliance derived from the record (counts, rates, hours of motion, the worst example of each finding with a reference into the record). No raw messages and no positions of people are in those summaries. Nothing else leaves unless the operator asks for it.

What the recorder does not collect

No camera images or video. Cameras are excluded from capture; at most we count how many frames a camera published, never what they showed. No orders, inventory, customers, or business data. No names, badges, or identities of people on the floor. The fleet's own perception may publish where a person was as a position; we record that position as the fleet published it, and our derived findings never link a position to a person. Positions serve safety evidence, never productivity monitoring.

When data leaves the site

Beyond the three streams above, only with the operator's action: an incident window the operator asks us to preserve and upload, or a report the operator exports. Where a site is operated by one company and the robots by another, both must consent. Every export is recorded in the appliance's own record with who requested it and when.

Who can see what

The operator sees everything on its appliance. We see the heartbeat, the fingerprints, the derived findings and summaries, and whatever the operator has uploaded. An insurer or broker sees a document only when the operator shares it. We never provide underwriters with a live view of an operator's fleet, and we never sell or license fleet data to anyone, including for training models.

Retention and return

The appliance keeps seven days of raw records by default and preserves incident windows until the operator releases them. Derived findings and record fingerprints are kept for the life of the service. When a pilot or contract ends, the operator keeps its record and we take the box; uploaded data is returned or deleted at the operator's choice, and our copy of the fingerprints stays so the returned record can still be verified.

Your rights and how to reach us

If you are a person whose position may have been recorded at a site running Roboblackbox, the operator of that site is the controller of that record; we act on its instructions. For questions about this site or about our handling of data: privacy@roboblackbox.com. Roboblackbox, LLC, a Delaware company, Seattle, Washington.