Effective date: June 21, 2026
Ibex (“the app”, “we”, “us”) is a climbing assistant for Android, developed and published by Oliver, an individual developer. This policy explains what data the app collects, why, who we share it with, and the choices you have.
If you have any questions, contact us at support@ibex.fit.
Ibex always signs you in so your data can be saved. There are three options:
You can upgrade an anonymous account to a Google or email account at any time, and you can sign out or switch accounts.
Depending on the method you choose, we store the following account identifiers through Google Firebase Authentication:
Your display name is also attached to the sessions you make public, so other users can see who created a shared session.
When you record a session, Ibex collects precise GPS location (latitude, longitude, altitude, accuracy, bearing, speed and satellite count) at up to once per second. Recording runs in a foreground service so it can continue while the screen is off or the app is in the background during an active session. The app does not request background-location permission and does not track your location when you are not recording a session.
GPS location is used to map your climbs, and it is also sent to third-party services (weather, elevation, time zone, reverse geocoding and the OpenBeta climbing database) so those features can work — see section 4.
For each session you can record and store: the session name, partner name, notes, route/crag names and descriptions, climbing grade, discipline, flags and route markers, gear notes, send outcomes, and similar free-text content you enter.
Saved crag and route locations (name, coordinates, country/region and any description you add) are stored and, like sessions, default to public.
If you add photos or videos to a session, they are uploaded to cloud storage as-is. We do not strip metadata, so any information embedded in the file — including GPS coordinates stored in the photo's EXIF data — is uploaded with it. If a photo is attached to a public session, it can be visible to other users.
To calculate calories, hydration needs and training load, you may enter: sex assigned at birth, age, weight, height, waist, body-fat percentage, resting/max/threshold heart rates, VO₂max, measured resting metabolic rate, and sweat rate. This data is optional and is stored on your device. When you are signed in and cloud sync is enabled, it is also mirrored to your private cloud profile so it follows you across devices. We do not collect your date of birth.
We use Google Firebase Analytics and Google Firebase Crashlytics to understand how the app is used and to diagnose crashes. This includes screen views, basic in-app events (for example when the app is closed), session duration, whether a barometric sensor is present, crash and ANR reports, and standard device/diagnostic information (such as OS version and device model).
This is the most important thing to understand about Ibex.
By default, the sessions, activity logs and crag locations you create are public. A public session — including its GPS track, route details, notes, and any attached photos or videos — is visible to all other signed-in Ibex users, and your display name is shown as its creator.
You control this:
Please consider this before recording sessions at sensitive or private locations, and before adding photos that contain location metadata (see section 2d).
We share data with the following services only to provide the features described. All network connections are encrypted in transit (HTTPS).
Google Firebase (Google LLC) — Authentication, Cloud Firestore (database) and Cloud Storage hold your account identifiers, sessions, locations, sensor data, photos and videos, and your body/fitness profile. Firebase Analytics and Crashlytics receive the usage and crash diagnostics described in section 2g. Firebase App Check / Play Integrity is used to protect the backend.
Weather, elevation, time zone, geocoding and climbing-database providers — to provide weather, altitude and crag information, the app sends your GPS coordinates (and session times) to:
Strava (optional) — if you choose to export a session to Strava, we send the activity name, sport type, start time, duration and elevation gain. We do not send your GPS track or coordinates to Strava.
Ibex link sharing (optional) — if you generate a shareable web link for a
session report, the report's content is uploaded to our own server (r.ibex.fit) so the
link can be viewed in a browser.
Health Connect (optional) — see section 5.
We do not use advertising networks, and we do not sell your personal information.
If you choose to use Health Connect, Ibex can:
Health Connect access is optional, governed by Android's permission screens, and can be revoked at any time in your device settings. Ibex's use of Health Connect data follows Google's Health Connect requirements: the data is used only for the in-app features described and is not used for advertising.
Cloud storage and sync can be turned off in the app's settings, and can be limited to Wi-Fi only. When sync is disabled, your sessions and profile remain on your device and are not uploaded. Note that data already uploaded while sync was enabled remains in the cloud until you delete it or your account.
No method of storage or transmission is completely secure, but we take reasonable measures to protect your data.
Ibex is not directed to children under 13 (or the minimum age required in your country), and we do not knowingly collect personal data from them. If you believe a child has provided us with personal data, contact us and we will delete it.
We may update this policy as the app changes. When we make material changes, we will update the effective date at the top and, where appropriate, notify you in the app or on the Play Store listing.
Questions, requests or concerns:
Oliver — Ibex
Email: support@ibex.fit