Bouldering Log: Climb Tracker — Privacy Policy
Last updated: 2026-09-26
This privacy policy applies to the mobile app "Bouldering Log: Climb Tracker"
(shown on your device as "Climb Log") on Android and iOS:
- Google Play: package com.simonj.climblog, developer "Global Utility App Maker"
- Apple App Store: bundle ID com.simonj.climblog, seller "Kyu-Hee Jang"
The app is developed and operated by Kyu-Hee Jang (Google Play developer name:
Global Utility App Maker), referred to as "we" or "us".
Contact: wkdrb2100@gmail.com
OVERVIEW
Climb Log is a manual logbook for bouldering sessions. You start a session, add
the problems you try with a V grade and an optional name, count attempts and
mark sends. Totals, the grade pyramid and progress views are calculated on your
device from what you enter. 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:
- Climbing log: each session's start and end time and the gym name you type
(up to 40 characters); for each problem, its V grade (V0-V17), the name you
give it (up to 60 characters), attempt count (1-999), whether and when it was
sent, and when it was added (up to 300 problems per session).
- Up to 5 recently used gym names, offered when you start a new session.
- If stored log data cannot be read, a copy of it is kept on the device under a
separate backup entry so it is not silently lost.
- If you used an earlier version of the app, your earlier log (problem names,
grades, grading system, times and send state) is imported into History once.
The original copy is kept unchanged on the device as a backup; deleting
sessions in the app does not remove that earlier copy.
- App state such as cached advertising configuration and a cached list of our
other apps.
Your log is not uploaded to a server operated by us. The app does not use GPS or
ask for location permission.
THIRD-PARTY SERVICES
- Google Firebase Analytics: app usage events (for example app launch, tab and
menu opens, session started, problem added, send logged, session saved, and
the App Tracking Transparency answer), ad revenue events, device and technical
information and an app-instance identifier, used to understand how the app is
used. Some events include the V grade of a problem, its attempt count, or the
number of problems and sends in a saved session. Gym names and problem names
are not sent as event data.
- 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 log.
- Google AdMob: 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), plus consent
signals and SDK diagnostics described in Google's disclosures, used to show
and measure ads, prevent fraud and diagnose ad delivery.
- Ad mediation partners: the app includes the InMobi and Liftoff Monetize
(Vungle) adapters for Google AdMob mediation. When AdMob selects one of them to
serve an ad, that partner may receive similar ad-request data (advertising
identifier where permitted, device, network and IP information, and consent
signals) to show and measure that ad.
Apart from device backups, the app sends data automatically only to the services
above, for the purposes above. 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. See:
https://policies.google.com/privacy
https://firebase.google.com/support/privacy
https://policies.google.com/technologies/ads
https://www.inmobi.com/privacy-policy
https://liftoff.io/privacy-policy/
ADS CONSENT & TRACKING
Where required (for example in the EEA and UK), the app first uses Google's User
Messaging Platform (UMP) to ask for your advertising consent. Ads are requested
only when that step reports that ads may be requested; in those regions they
are non-personalized unless your choice allows personalized ads. If the consent
step fails, the app does not request ads during that launch.
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 partners.
Where Google requires it, the app menu shows "Privacy choices", which reopens
the consent message so you can change your choice. The menu also shows a short
privacy summary.
Analytics and crash reporting are not controlled by these ad choices.
PERMISSIONS
The app does not ask for location, camera, microphone, contacts, photo library
or notification permissions. It uses internet access for ads, analytics and app
configuration, and vibration for button feedback. On iOS it may ask for tracking
permission as described above.
DATA RETENTION & DELETION
- Local data: you can delete a problem during a session, edit attempts and send
state on the History screen, and delete a whole session there. Ending a
session with no problems discards it. Backup copies described above are not
removed by these controls.
Uninstalling the app removes its local data from this device; existing device
or cloud backups are handled separately (see below).
- Data processed by Google Firebase, AdMob and mediation partners 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
Your log is kept in the app's private storage area, which the operating system
protects from other apps; it is not separately encrypted by the app, so protect
your device with a passcode. Data sent to Google Firebase and AdMob is
transmitted over encrypted (HTTPS/TLS) connections. No method of transmission
or storage is completely secure.
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: Kyu-Hee Jang (Google Play: Global Utility App Maker)
Email: wkdrb2100@gmail.com