Privacy by construction.
Last updated 28 August 2026
What the public registry stores
RMDY stores the failure title and description you submit, expected behavior, runtime, timestamps, public solver name and profile URL, solver approach, sanitized fixture content, source hashes, public signing keys, signatures, verification results, and bounty proposals.
What should never be submitted
Do not submit raw private traces, prompts containing personal data, credentials, access tokens, private keys, phone numbers, email addresses, or confidential business information. The CLI redacts common sensitive fields locally, and the API rejects several common sensitive patterns, but no automated filter is perfect.
Abuse prevention
For write-rate limiting, the service derives a short-lived one-way bucket from the connecting network address and hourly window. The raw network address is not written to the registry. Platform infrastructure may process standard request logs for security and reliability.
Purpose and sharing
Public records are used to reproduce failures, evaluate fixes, distribute patches, prevent abuse, and keep the bounty ledger transparent. RMDY does not sell registry data. Public submissions are intentionally accessible to anyone.
Retention and removal
Public technical records may be retained to preserve auditability. Material that exposes personal data, secrets, or rights violations may be redacted or removed after a verified request. The official operator contact will be displayed on the homepage before token launch.
Your choices
You can use the CLI locally without submitting a record. Review every generated artifact before uploading it. If you do not want information to become public, do not submit it to the registry.