Privacy Policy

Last updated: June 24, 2026

RunningBuds is built to be private by design: no account, no tracking, and your conversations travel directly between you and your running partner. This policy explains what the app accesses and why.

RunningBuds is provided by Codelous, LLC ("we," "us"). Questions: support@runningbuds.app.

The short version

• No account, no sign-up. We don't ask for your email, phone number, or login.
• No servers storing your data. We don't operate a backend that collects or stores your personal information.
• Your voice goes straight to your buddy, encrypted end-to-end. We never receive, record, or store your calls.
• No analytics, no ads, no trackers, no data sales.

What the app accesses on your device

• Microphone — to send your voice to your running partner during a call. Audio is processed on your device and transmitted, encrypted, directly to your partner. It is not recorded, stored, or sent to us.
• Camera — only to scan your partner's pairing QR code. Scanning happens on your device; no photos or video are saved or transmitted.
• Display name — the name you optionally enter is stored on your device and shared with your partner during a call so they know who they're talking to.
• Settings & relay usage count — your in-app preferences and a running total of relayed call time are stored locally on your device (the relay total is kept in the iOS Keychain). This stays on your device and is not sent to us.

Connecting a call

• To connect two phones, RunningBuds uses standard real-time communication technology (WebRTC). Establishing a connection requires sharing your device's network addresses (IP addresses) with your partner's device and with connectivity servers (STUN/TURN). This is inherent to how direct device-to-device calling works.
• Pairing information (the QR code or link) is exchanged directly between you and your partner. It is not sent to our servers.
• When a direct connection isn't possible, the call is routed through a third-party relay service (Cloudflare TURN). The relay forwards your call between the two devices. Because the audio is end-to-end encrypted (DTLS-SRTP), the relay carries only encrypted data and cannot listen to your call, and we do not receive or store call content. Cloudflare may process connection metadata (such as IP addresses and bandwidth) to provide the relay; see Cloudflare's privacy documentation. To obtain short-lived relay credentials, the app contacts our credential service, which does not receive your call content or personal information.

Subscriptions

• Subscriptions are sold and processed by Apple through in-app purchase. We do not receive or store your payment details. Your subscription status is determined on your device using Apple's StoreKit.
• We do not maintain subscriber accounts or profiles.

What we don't do

No advertising, no analytics or usage tracking, no cross-app or cross-site tracking, no selling or sharing of personal data, no user profiling.

Children

RunningBuds is not directed to children under 13 (or the minimum age required in your region), and we do not knowingly collect personal information from them.

Your choices and rights

Because we don't collect or store your personal data on servers, there's very little for us to access, correct, or delete. Information held on your device (your name, settings, and relay count) is removed when you delete the app. To cancel a subscription, use your Apple ID Account Settings. For any privacy questions or requests, contact support@runningbuds.app.

Third-party services

• Apple — in-app purchases and subscription processing (see Apple's Privacy Policy).
• Cloudflare — TURN relay connectivity when a direct connection isn't available (see Cloudflare's Privacy Policy).

Changes to this policy

We may update this policy from time to time; the "Last updated" date above will reflect any changes. Material changes will be reflected in the app or on this page.

Contact

Codelous, LLC — support@runningbuds.app