Kick Counter — Privacy Policy
Last updated: 2026-09-26
This privacy policy applies to the mobile app "Kick Counter" on Android and iOS
(listed as "Kick Counter: Tap Event Logger" on Google Play and "Kick Counter:
Event Logger" on the App Store):
- Google Play: package com.moon.kickcounter, developer "janey-moon"
- Apple App Store: bundle ID com.moon.kickcounter, seller "Heekyung Moon"
The app is developed and operated by Heekyung Moon (Google Play developer name:
janey-moon), referred to as "we" or "us".
Contact: ansgml2100@gmail.com
OVERVIEW
Kick Counter is a manual tap log. You tap once per event, and the app records
the time of each tap in a session of up to ten taps within two hours, then
keeps finished sessions in a History list. The app does not require an account,
and we do not sell personal data. It uses Google services for analytics, crash
reporting, app configuration and advertising, as described below.
LOCAL DATA
The following are stored in the app's storage on your device:
- The current session and up to 200 saved sessions. Each session holds its
start time, the time of each tap (up to ten), the times of any Undo or Stop
actions, and when it ended.
- A list of up to 500 internal IDs of sessions you deleted, so a deleted session
is not saved again by mistake. Each ID includes that session's start time.
- A short summary of the last finished session (its date, number of taps and
whether it reached ten or was stopped).
- If saved history cannot be read, a copy of the unreadable data is kept on the
device so it is not silently lost. Any sessions saved by an earlier version
of the app are carried over, and that older copy is left in place.
- App state such as an app-open counter, whether the review prompt was shown,
and cached ad and "more apps" configuration.
Taps are entered only by you; the app does not use sensors to detect anything.
Your sessions are not uploaded to our servers. If you tap Share on a session in
History, a text summary (date, times, number of taps, result and gaps) is passed
to the app you choose in the system share sheet.
THIRD-PARTY SERVICES
- Google Firebase Analytics: app usage events (for example app launch, app-open
count, screen and tab opens, menu use, review prompts, when a session reaches
ten taps, and the number of taps when you stop a session early), the tracking
permission result on iOS, launch-ad and ad revenue events, device and
technical information and an app-instance identifier, used to understand how
the app is used. Tap times and other History details are not sent as event
data; only the tap count and outcome noted above are.
- Google Firebase Crashlytics: crash reports and technical diagnostics, used to
keep the app stable.
- Google Firebase Firestore: the app downloads app configuration (such as ad
settings and a list of our other apps). It does not upload your data. When
you open "Developer's other apps", the icons in that list are loaded from the
web addresses it contains, and those hosts may see your IP address.
- Google AdMob: banner, interstitial, app-open and native ads. AdMob may process
the advertising identifier (Android Advertising ID or iOS IDFA, where
permitted), device and network information, ad interaction data and IP address
(which may be used to estimate approximate location, even though the app has
no location permission), used to show and measure ads, prevent fraud and
diagnose ad delivery. The app does not include adapters for other ad
networks (mediation).
Apart from sharing you start yourself, the icon downloads above and device
backups, the app sends data automatically only to the services above, for the
purposes above. We use these services under Google's 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. See:
https://policies.google.com/privacy
https://firebase.google.com/support/privacy
https://policies.google.com/technologies/ads
ADS CONSENT & TRACKING
When the app starts, it first uses Google's User Messaging Platform (UMP) to
check whether a consent message is required (for example in the EEA and UK) and
shows it if so. Personalized ads are used only where consent is not required or
your choice allows them; otherwise any ads are non-personalized.
On iOS, only after that step and only when personalized ads are allowed, the app
requests App Tracking Transparency (ATT) permission. If tracking is not allowed,
the IDFA is not available to the app or its ad partner, and ads are
non-personalized.
If the consent check fails, the app does not show the tracking prompt and may
still show non-personalized ads.
Where Google requires it, the app menu shows "Privacy choices", which reopens
the consent message so you can change your advertising choice.
Analytics and crash reporting are not controlled by these ad choices.
PERMISSIONS
The app does not ask for location, camera, microphone, contacts, photos,
Bluetooth, health data or notification permissions. On iOS, the only permission
prompt is App Tracking Transparency, described above. It uses internet and
network state access for ads, analytics and app configuration, vibration for tap
feedback, and on Android the advertising ID and other permissions used by the
Google SDKs. The Android package also declares legacy storage (Android 12 and
earlier) and overlay permissions; the app does not use them and does not ask
you to grant them.
DATA RETENTION & DELETION
- Local data: you can delete any finished session from History after a
confirmation. When more than 200 sessions are saved, the oldest are removed.
Deleting a session does not remove it from the recovery or earlier-version
copies described above or from an existing backup. Other local data stays
until it is overwritten, you clear the app's data (Android) or you uninstall
the app.
- Data processed by Google Firebase and AdMob is kept according to those
services' retention settings and policies. Uninstalling the app does not
delete data that was already sent to them.
- To request deletion of data associated with your use of the app, email us at
the address below. Because we do not ask for your name, email or account, we
may only be able to act on data we can link to you from the information you
provide, and we will explain any limits in our reply.
STORAGE & CONTROL
- Android: if device backup is enabled, app data may be included in your Google
backup and restored on reinstall.
- iOS: app data may be included in your iCloud or device backups according to
your device settings.
- Android: you can reset or delete your Advertising ID in Settings > Google (or
Privacy) > Ads.
- iOS: you can change tracking permission in Settings > Privacy & Security >
Tracking.
SECURITY
Data sent to Google Firebase and AdMob is transmitted over encrypted (HTTPS/TLS)
connections. Local data is kept in the app's private storage area and is
protected by your device's operating system; it is not separately encrypted by
the app, so protect your device with a passcode. No method of transmission or
storage is completely secure.
IMPORTANT NOTICE
Kick Counter only records what you tap. It is not a medical device and does not
detect, monitor, assess or interpret anything. The ten-tap and two-hour limits
only structure a session, and a session result has no health meaning. For any
health question or concern, contact a qualified healthcare professional; in an
emergency, contact your local emergency services.
CHILDREN
This app is not directed to children under 13 and we do not knowingly collect
personal information from children.
CHANGES
We may update this policy. The "Last updated" date above will change
accordingly.
CONTACT
Developer: Heekyung Moon (Google Play: janey-moon)
Email: ansgml2100@gmail.com