Bit Run handles two sensitive things: your fitness data (including heart-rate and GPS routes) and real Bitcoin. We take protecting both seriously. This page explains, in plain language, the measures we have in place. For the data we collect and your rights, see our Privacy Policy.
All traffic between your device and Bit Run is encrypted in transit over TLS (HTTPS). Access tokens and any sensitive credentials are encrypted at rest. We use authorization tokens (OAuth) for connected services rather than your passwords — we never see or store them.
The app ships with security headers (Content-Security-Policy, HSTS, clickjacking and MIME-sniffing protections), validates input on the server, and limits outbound requests to known, trusted destinations. We do not run third-party advertising or behavioral-tracking scripts.
Rewards are paid to a Lightning Address you control — we do not custody your withdrawn funds. Withdrawals run through server-side, idempotent checks to prevent duplicate or unauthorized payouts, and a balance can only be moved by the account that owns it.
We collect only what we need to verify runs and pay rewards, and we never sell your data or use it to train external AI models. See the Privacy Policy for the full list and your choices, including deletion.
No system is perfectly secure. If a breach affects your data, we will notify affected users and the appropriate authorities as required by law.
Found a vulnerability? Please report it privately to hwikyeong.kim@bitrun.run before disclosing it publicly, and give us a reasonable window to fix it. We appreciate good-faith security research and will not pursue researchers who follow this policy.
Bit Run is in active beta. We run regular internal security reviews and keep dependencies patched, but this is not a substitute for a formal third-party audit, which we will pursue as we scale. Use of the service is subject to our Terms of Service.