Privacy Policy
28 September 2026
zeroPlayer has no accounts. It never asks for a name, an email address or a phone number, and there is no sign-in screen. This page describes what does travel, despite that.
Stays on your device
All of the following is stored on your iPhone or iPad and never sent to a server. Deleting the app deletes it too.
- Presets — name, icon, the station attached to it, timer length
- Favourites
- Listening history — what you played, when, for how long, and which preset started it
- Your position in a podcast episode
- Settings such as the default timer
The reordering that adapts recommendations to your history is computed on the device as well, so there is no reason for what you listen to to leave it. You can erase the history at any time from the Settings tab.
Sent to the server
Station and podcast lists come from a server run by the developer
(ai.zerolive.co.kr). These are the only values that travel with a request.
- An install identifier — a random UUID created the first time you open the app. It is not a device identifier and has nothing to do with your Apple account; reinstalling produces a new one. It is used only for alarm registration and abuse limits.
- The app version and the query you made (country, genre, search term and the like)
- The id of a station that failed to play, so dead stations can be removed from the list
- The ids of stations you removed with "Stop playing this" — on iOS 25 and earlier only. On those versions the server decides what an alarm plays, so keeping the list on the device alone means a station you removed still wakes you. Only the ids travel, never whether you listened to them. iOS 26 and later never sends them, because the app itself decides, and granting alarm permission also deletes the copy held on the server.
- The connecting IP address that comes with any internet request; the edge (Cloudflare) logs it briefly
What you listened to, for how long, and which presets you use are not sent.
When alarms are on
How an alarm reaches you depends on the iOS version, and so does what the server keeps.
- iOS 26 and later — the device schedules the alarm itself, so the server has no part in it. The moment you grant alarm permission the app deletes the push token it had stored on the server, and nothing is sent to the server at alarm time.
- iOS 25 and earlier — the device token issued by Apple Push Notification service is kept on the server so a notification can be delivered at the time you set. Turning all alarms off, or deleting the app, stops it being used. The notification carries only what to play (a station name), never anything about who is listening.
Permission is requested only when you first turn an alarm on. The melody and volume you choose for an alarm stay on the device.
Stream playback
When you play a station the app connects to that station's own server. Audio does not pass through the developer's server. The station therefore records ordinary access information such as your IP address. That log belongs to the station and the developer cannot see it.
Advertising
Google AdMob banners appear on the list and history screens. There are no ads on the playback screen, the mini player, or the screen an alarm opens, and no feature is locked behind watching an ad.
AdMob may use the device advertising identifier and coarse (country-level) location to select ads and measure them. iOS asks for your permission before an app uses the tracking identifier, and declining leaves every feature of the app working — the ads are simply less targeted. See Google's partner sites policy for details.
Children
This app is not directed at children under 14. It does not ask for an age and does not knowingly collect information from children.
Changes
If this page changes, the date at the top is updated, and significant changes are announced inside the app.
Contact
Questions, or a request to delete something, go to zerolive7@gmail.com.