Privacy policy
Your music
never leaves
your phone.
Run2Beat is designed around a simple promise: the music files you provide stay on your device. Listening history and equalizer presets can copy to your iCloud account when you are signed in — they are not sent to Run2Beat.
Last updated: October 2026
Run2Beat (“we”, “our”, or “us”) respects your privacy. This Privacy Policy describes how we handle information when you use the Run2Beat iPhone and Apple Watch app (“the App”) and, separately, when you visit Run2Beat.com (the website).
1. The App — information we collect
The App does not collect, store, or transmit any personal data to external servers operated by us. Music files, BPM lists, playlists and most settings stay on your device. If you are signed in with your Apple ID, listening history and equalizer presets are also copied to your personal iCloud account, as described below.
2. Music Files
Music files you import into Run2Beat are stored in the App’s private sandbox on your device. They are not shared with third parties, uploaded to any server, or accessed outside the App.
3. Apple Watch Sync
When you sync BPM lists, playlists or Favourites to your Apple Watch, audio files are transferred directly from your iPhone to your paired Apple Watch using Apple’s WatchConnectivity framework. No data passes through our servers.
4. Health and Bluetooth on Apple Watch
The Apple Watch app can read two kinds of data from the watch, and only to show them back to you on the wrist:
- Health. Today’s activity summary drives the Move-goal ticks on the watch home screen and the Move and Exercise cards on the session page. Run2Beat only reads; it never writes anything to Health.
- Bluetooth. The battery level of connected headphones, read while the session page is open, so the watch can show how much charge is left. Headphones that publish the standard Bluetooth Battery Service are read from that service. AirPods and Beats do not publish it; their level is read from the battery field in the accessory’s public Bluetooth advertisement.
Both are optional. watchOS asks before Run2Beat gets access, and you can decline it or withdraw it later in Settings — the music keeps playing either way and those rows simply stay empty. Neither kind of data is sent to Run2Beat, copied to iCloud, or passed on to your iPhone. It stays on the watch.
5. iCloud
When you are signed in with your Apple ID, Run2Beat uses Apple’s iCloud Key-Value Store to keep a copy of your listening history and equalizer presets. Audio files never leave the phone. There is no Run2Beat account and no sync button. A change is saved about a second later, and again when you open the app. Settings shows Saved in iCloud and the time of the latest save when the iCloud card is open.
The copy is private to your Apple ID and is not sent to Run2Beat. Clearing all listen counts also clears the iCloud copy. Deleting the app does not. If iCloud is off for Run2Beat, the data stays on this phone only.
6. App analytics and tracking
The App does not use any analytics, tracking, or advertising frameworks. We do not track your usage or collect crash reports beyond what Apple may collect through its standard iOS crash reporting.
7. Third-party services in the App
The App does not integrate with social networks or advertising platforms. Optional Shazam identification during import (when you enable it) sends audio signatures to Apple’s ShazamKit for metadata lookup; that is the only outbound network call related to your music, and you can leave it off.
8. This website (Run2Beat.com)
The marketing website uses Google Analytics (Google tag / gtag.js, measurement ID G-TS1EQ35CVJ) to understand aggregate traffic — for example page views and approximate geography. Google may process technical data such as IP address, device/browser type, and pages visited, according to Google’s own policies. This applies only to the website, not to the App.
You can limit Analytics via browser settings, privacy extensions, or Google’s tools where available. We do not use the website Analytics to identify you inside the App, and we do not sell personal data.
9. Children’s Privacy
The App and website are not directed at children under the age of 13 and we do not knowingly collect data from children.
10. Changes to This Policy
We may update this Privacy Policy from time to time. The latest version is always available on this website and within the App.
11. Contact
If you have questions about this Privacy Policy, please contact us at hello@run2beat.com