Lap Counter — Privacy Policy
Last updated: 2026-09-30
This privacy policy applies to the mobile app "Lap Counter" (store listing name "Lap Counter: Multi Stopwatch") on Android and iOS:
- Google Play: package com.simonj.lapcounter, developer "Global Utility App Maker"
- Apple App Store: bundle ID com.simonj.lapcounter, seller "Kyu-Hee Jang"
The app is developed and operated by Kyu-Hee Jang (Google Play developer name: Global Utility App Maker).
Contact: wkdrb2100@gmail.com
OVERVIEW
Lap Counter does not require an account, and we do not sell personal information. It is a hand-timing lap timer: you tap a tile for each athlete every lap, and lap times, totals, statistics, and personal records are calculated on your device from those taps and stored locally. The app also uses Google services and an advertising mediation partner for analytics, crash reporting, remote configuration, and advertising.
NAMES YOU ENTER
You may type names for the athletes you time (up to 24 characters each). Names are optional, are stored on your device, and are not included in analytics events. If you enter other people's names, please do so only where you are allowed to.
VOICE, VIBRATION, SCREEN, AND CLOCK
- Spoken lap times are off by default. When you turn them on in Setup, the athlete name, lap number, and time are read aloud by your device's text-to-speech engine.
- The app can vibrate on each tap; you can turn this off in Setup.
- While a session is running, the app keeps the screen awake.
- To keep elapsed times correct if the app is closed or the device clock changes, the app reads the phone's time-since-start-up clock and a start-up identifier. These values are stored with the session on your device and are not sent to us.
INFORMATION STORED ON YOUR DEVICE
- The current (running or unsaved) session: up to 20 athletes (name, colour, start and finish time), every lap tap with its time and whether it was measured, typed, or estimated, the list of corrections you made (used for undo), goal settings (laps, lap distance and unit, target lap time), the too-short-lap warning time, and the clock information described above.
- Saved sessions: up to 300, with the same content and the name you give them. When the limit is reached, the oldest saved session is removed.
- Your list of people (up to 200 names, each with an internal ID), the last board line-up, and your settings (start mode, spoken lap times, vibration).
The app may also store cached advertising and More Apps configuration.
The developer does not run a server that receives your sessions. The app reads developer-controlled advertising settings and a More Apps list (including app icons loaded from web addresses) from Google Cloud Firestore, but it does not upload your names, laps, or results. When you export a CSV file or share a summary, it goes only where you choose to send it through your device's share sheet.
ANALYTICS, CRASH REPORTING, AND ADS
Google Firebase Analytics may process limited app-usage and technical information, such as app launches, screen views, menu actions (opening the menu, this policy, review, and More Apps), review-prompt results, and ad revenue events, along with app version, device type, and app-instance identifiers. Session events are session_new (number of athletes and start mode), session_start (start mode), session_stop, session_saved (number of athletes), and csv_export. On iOS, an event also records whether the tracking prompt was shown and the current tracking and consent status. These events do not include names, lap times, or results.
Google Firebase Crashlytics may process crash reports and related technical information needed to diagnose app problems.
The app shows banner, interstitial, and app-open ads through Google AdMob, and a native ad in the exit dialog on Android. AdMob may also request ads from the InMobi mediation network. Google and InMobi may process advertising identifiers and device, app, consent, network, and ad-performance information to provide and measure ads, and may use an IP address to estimate an approximate location even though the app has no location permission.
Banner ads are not shown on the Board tab or while a session is running. Full-screen ads are not shown while a session is running or not yet saved: an interstitial ad may appear only right after you save a session (and not if you touched the screen in the meantime), and app-open ads are skipped while a session exists and when you return from the share sheet. The exit-dialog native ad is not shown while a session is running.
PERMISSIONS AND ADVERTISING CHOICES
The only feature permission the app declares is vibration on Android. It does not request location, camera, microphone, contacts, photos, Bluetooth, health data, or notifications.
Where required (for example in the EEA and UK), Google's consent message (UMP) is shown first, and personalized advertising stays off unless your choice allows it. On iOS, the App Tracking Transparency prompt is then shown if you have not answered it yet, unless you already declined personalized ads on Google's consent message. If tracking is not allowed, the IDFA is not available to the app or its ad partners. If the consent message cannot be loaded, personalized advertising stays off for that launch, the app may still request non-personalized ads, and on iOS the tracking prompt may still be shown if you have not answered it yet. The app works whatever you choose.
You can change iOS tracking permission in Settings, and reset or delete the Android advertising ID in your device settings. Where Google requires it, the app menu shows "Privacy choices", which reopens the consent message so you can change your advertising choice. The menu also links to this policy. Analytics and crash reporting are not controlled by these advertising choices.
STORAGE AND YOUR CONTROL
You can discard an unsaved session on the Results tab, delete saved sessions one by one on the History tab, and rename or combine people on the Setup tab. You can also clear the app's data on Android or delete the app. Local data may be included in an Apple, Google, or device backup depending on your backup settings; uninstalling normally removes the active copy but may not remove an older backup.
Because we do not receive your sessions, we cannot delete them for you; the controls above remove the saved sessions from the app's storage. A CSV file you export (with names and lap times) is written to the app's temporary cache before the share sheet opens and is not deleted by the app afterwards, so it can remain on the device (even if you cancel sharing or later delete the session) until the operating system clears the cache, you clear the app's data or cache on Android, or you delete the app. For questions about data processed by Google or InMobi, or to ask us for help with a privacy request, contact us at the address below.
Data processed by third parties is retained according to their service settings and policies. We use these services under their applicable terms, and we ensure that third-party service providers with whom we share user data provide the same or equal protection of that data as stated in this policy.
- Google Privacy Policy: https://policies.google.com/privacy
- Firebase privacy information: https://firebase.google.com/support/privacy
- Google advertising technologies: https://policies.google.com/technologies/ads
- InMobi Privacy Policy: https://www.inmobi.com/privacy-policy
SECURITY
Your saved data is kept in the app's private storage on your device, which the operating system protects from other apps; it is not separately encrypted by the app, so protect your device with a passcode. Apart from the limited analytics events described above, the app does not upload your saved data. Communication between the app and Google services and the ad mediation partner uses encrypted connections (HTTPS/TLS). No method of storage or transmission is completely secure, but we limit what the app collects to what is described in this policy.
IMPORTANT NOTICE
The app is a hand-timing tool: results are only as exact as the moment you tap. It is not an official race timing system and does not detect laps automatically.
CHILDREN
The app is not directed to children under 13, and we do not knowingly collect personal information from children.
CHANGES
We may update this policy if the app or its services change. The date above shows the latest revision.
CONTACT
Kyu-Hee Jang (Google Play developer: Global Utility App Maker)
Email: wkdrb2100@gmail.com