WalkUpFire Privacy Policy
Last updated: 2026-04-13
WalkUpFire is built so your data stays with you. Almost to Code doesn’t run servers, and the app doesn’t send your roster, your songs, or your usage anywhere we can see.
Data we collect
None directly. WalkUpFire does not collect personal information from you. There are no accounts, no sign-in, no analytics, no crash reporters, and no advertising SDKs. We do not log what you do in the app.
Where your data is stored
Everything you create in WalkUpFire — teams, players, batting orders, walk-up song settings, trim points, volumes, fades, announcement configuration, soundboard buttons, inning break playlists — is stored locally on your device using Apple’s SwiftData framework.
This data also syncs through CloudKit using your own private iCloud container. That means it moves between your iPhone and iPad through Apple’s iCloud, tied to your Apple ID. It does not pass through us. We cannot read the contents of your private CloudKit database.
Audio files themselves — imported MP3s, generated announcements, and downloaded neural voice models — stay on the device where they were created. They do not sync. If you reinstall the app, local audio files need to be re-imported.
Apple Music and MusicKit
If you sign in to Apple Music inside the app, WalkUpFire uses MusicKit to search the catalog and play tracks you assign to players. The app stores, and syncs across your devices via your iCloud, only the following metadata for each Apple Music track you pick: the track’s catalog ID, title, artist name, ISRC code, duration, and availability status. Actual audio is never stored by the app. Playback is handled by Apple’s system music player using your own active Apple Music subscription.
Your Apple Music listening is governed by Apple’s privacy policy.
RevenueCat (subscription management)
WalkUpFire uses the RevenueCat SDK to manage the yearly subscription and lifetime entitlement. RevenueCat receives an anonymous subscriber ID generated on your device, plus information about your purchase and entitlement status. It does not receive your name, email, Apple ID, or any other personally identifying information from the app.
RevenueCat’s privacy practices are documented at revenuecat.com/privacy.
Purchase transactions are processed by Apple through StoreKit. We never see your payment information.
Third-party SDKs
For completeness, the third-party code shipped with WalkUpFire is:
- RevenueCat — subscription and entitlement management, as described above.
- FluidAudio (Kokoro) — on-device neural text-to-speech. The premium announcer voice runs locally. No audio or text is sent to a remote service.
- Waveform — a rendering library for the audio trim editor. It does not make network requests.
There are no analytics SDKs, no ad networks, no crash reporters, and no remote logging libraries in the app.
Network usage
The app makes network requests only for:
- Apple Music / MusicKit — searching the catalog and streaming tracks you chose, handled by Apple.
- App Store / StoreKit — subscription purchases and restores, handled by Apple.
- RevenueCat — checking your subscription entitlement on launch and after purchases.
- Neural voice download — a one-time download of the Kokoro voice model (~100 MB), cached on your device.
Children
WalkUpFire is used by adults to run music at youth games, but the app itself is not directed at children and does not knowingly collect any information from children under 13.
Changes
If this policy changes, the updated version will be published at this URL with a new “Last updated” date.
Contact
Questions about this policy: [email protected]