Privacy policy
The robot-md project is run by Craig Merry as the Robot Registry Foundation. This page says what the software and websites collect, where it goes, and how long it stays. It describes the code as it ships today. If the code changes what it collects, this page changes first.
The short version
- The Claude plugin and its MCP server run on your machine. They read your
ROBOT.mdand talk to your robot. They send nothing to us unless a tool or command you approve submits a record to the registry, as listed below. - Registering a robot sends a small, public description of the robot to the registry. That record is published openly under CC0. Don't put anything private in it.
- The websites set no cookies and run no advertising trackers. Only rcan.dev counts page views, with cookieless Cloudflare Web Analytics. Nothing is sold.
What runs locally and stays local
The robot-md plugin for Claude Code and the robot-md mcp server read ROBOT.md, calibration files, camera frames and audit bundles on your machine, and they drive your hardware through robot-md-gateway on 127.0.0.1. None of that is sent to the Robot Registry Foundation. The one exception is the spatial_eval_submit_to_rrf MCP tool, listed in the table below. Your AI client (Claude Code, for example) handles anything the plugin returns to it under that provider's own privacy terms.
What leaves your machine, and when
| When you… | Sent to | What is sent |
|---|---|---|
Run robot-md register or robot-md init --register |
robotregistryfoundation.org | Robot name, manufacturer, model, firmware version, RCAN version, the robot's public signing key and key ID, and optionally a robot URI and an owner ID that you supply. The registry assigns a Robot Registration Number (RRN). |
Run rotate-key, revoke-key, unregister, verify-tier, request-apikey --submit, compliance status, any emit-* command with --submit, or the registry checks in doctor |
robotregistryfoundation.org | The RRN and the signed request for that command, such as a new public key or a compliance packet you chose to submit. |
Approve the spatial_eval_submit_to_rrf MCP tool |
robotregistryfoundation.org | A signed spatial-eval score for one run: the RRN, run ID, timestamp, probe and execute scores, and their signatures and evidence hash. |
| Install or look up an actuator package | robotmd.dev, robotregistryfoundation.org | A request for the public catalog. No robot data. |
| Join a waitlist on robotmd.dev | robotmd.dev (Cloudflare KV) | Your email address, the time, and your browser's user-agent string. |
Each of these requests, like any request on the internet, reveals your IP address to Cloudflare, which hosts the services. The --contact-email option of robot-md init is accepted but not currently transmitted anywhere.
What is public
Registry records are public by design. Anyone can resolve a robot at rcan.dev/r/<rrn>, and registry data is released under CC0. The record contains what you sent at registration, plus keys and compliance attestations you later submit. Don't register personal names or other private details as robot or manufacturer names.
Websites
robotmd.dev, robotregistryfoundation.org and rcan.dev are hosted on Cloudflare. rcan.dev uses Cloudflare Web Analytics, which counts page views without cookies and without fingerprinting individual visitors. robotmd.dev and robotregistryfoundation.org run no analytics scripts. Fonts load from Google Fonts, which receives your IP address when it serves them. The sites set no cookies.
How long data is kept
- Registry records are permanent: the point of an RRN is that it keeps resolving. A key can be revoked, and the revocation is recorded publicly.
- Waitlist entries are kept until the waitlist closes or you ask for removal.
- Rate-limit counters keyed by IP address expire after one hour.
- Cloudflare logs and analytics follow Cloudflare's own retention.
Sharing
We don't sell data or share it with advertisers. Registry data is public, as described above. Otherwise, data is shared only with the infrastructure providers named here (Cloudflare, Google Fonts) or where the law requires it.
Your choices
- Everything the software sends is triggered by a command you run. If you don't register, nothing about your robot leaves your machine.
- To be removed from a waitlist, to correct a registry record, or to ask what we hold about you, email [email protected] or open an issue at github.com/RobotRegistryFoundation/robot-md.
Changes
Changes to this page are tracked in the robot-md repository history, and the effective date above moves with them.