Effective date: October 27, 2026
App name: Running Pace ("러닝 페이스")
This policy explains what the app processes and where it sends it.
The app has no accounts or sign-in, and the operator runs no server or database that receives the times, distances, or goal names you enter. The app does not request location, camera, microphone, contacts, photos, or SMS permissions, and it does not record distance or routes.
a. Stored on your device (never sent to the operator's server) — last input (distance, finish time or pace, input mode); saved goals (the name you chose, distance, finish time, split style and gap, beat in steps per minute, created time); last beat (steps per minute, sound); settings (unit, beat sound, theme, language, ad-hide expiry time). Stored in on-device storage and removed when you uninstall the app or clear its data. Backup file: when goals or settings change, the app automatically writes a backup file (JSON containing every value the app stores — the above plus items such as the onboarding-seen flag; the install ID and ad/measurement state are not included) to your device's shared Downloads folder; you can also create one in Settings. The file stays on the device and the app does not send it anywhere. Because it is in a shared folder it may remain after uninstall unless you delete it, and apps or file managers with file access can see it. When you restore, the app reads only the one file you pick.
b. Beat playback and notifications. While the beat plays, the app runs a playback (foreground) service, and on Android 13 and later it may ask for notification permission to show a playback notification with a stop button. The beat plays even if you decline. Notification content is created on the device and is not sent to a server. The beat is a sound generated on the device; the app does not listen to or record audio.
c. Sharing (only when you tap). Tapping Share passes a text of the distance, time and pace to the Android share sheet, only to the app you pick.
d. Monitoring and advertising data sent automatically
1. Owl Pulse (our own usage monitoring) → https://api.owlmakers.com/v1/pulse. Sent: app package name, version, language; a random session ID created at each launch; a random install ID created once at installation (not an account or hardware ID — a new value after uninstall); code-style IDs of screens and button taps (e.g. home.save, cadence.start); action outcomes (success / failure / cancel with a category code, and a coarse category of how long a beat played); ad shown / click / failure signals; a signal that the app is open. Not sent: the times, distances, paces, beat values, or goal names you enter. The app holds no location. The server derives only the names of country, region and city from the connecting IP for statistics and does not store the IP address or coordinates. Debug builds send nothing.
2. Google AdMob (ads): advertising ID, IP address, device information, and ad interactions may be processed to show a top banner, native ads under results and between list items, an ad on the exit confirmation screen, a full-screen ad right after you save a goal, and a rewarded ad that hides the banner. The Cadence screen body has no ads while the beat plays. Where consent is required (EEA, UK, etc.) the Google UMP consent form appears first.
3. Google Analytics for Firebase (GA4): anonymous usage statistics (screen views, button-tap codes, outcomes), device model and OS version. The Firebase SDK (Analytics, Messaging) may create a per-installation random identifier (Firebase installation ID); the app sends no push notifications. Entered values and goal names are not sent.
4. App update check: the app can use Google Play's update feature to check for a new version; Google Play services handle this.
Data on your device is deleted when you uninstall the app or clear its data; backup files in Downloads must be deleted by you. Monitoring, analytics, and advertising data are kept under each system's retention policy and then used only as aggregated statistics.
The app does not provide the values or goal names you enter to anyone. Third parties involved: Google LLC (AdMob, Firebase — https://policies.google.com/privacy) and OwlMakers (own Pulse monitoring).
This app uses Google's Firebase Cloud Messaging (FCM) to receive announcements and notices sent by the developer. When you open the app, Google assigns an FCM installation ID (registration token) to this installation; the app does not send or store this value on the developer's servers. The app subscribes to notification topics for the app name and your display language, and Google processes that subscription. A notification goes with the same content to every user of the same app and language and carries no personal data. On Android 13+ the notification permission is requested only when you tap the in-app notice line or the settings row, and you can use every other feature without allowing it. You can turn notifications off at any time in the device's Settings → Apps → Notifications, and you stop receiving them when you uninstall the app.
Delete saved goals one by one (undo is available for 5 seconds), clear app data, or uninstall to remove on-device data; delete backup files in Downloads with a file manager. Turn off notifications in system settings. Where consent is required, change your ad consent under Settings → Ad privacy settings; elsewhere use Google ad settings on your device.
The app is not directed to children. We do not knowingly collect personal information from children under 13.
If this policy changes, the effective date above is updated; material changes are announced in the app or the store listing.
Owlmakers — support@owlmakers.com