Climb Companion — processing of personal data
The data controller is Alessandro Sposito — [email protected]. Climb Companion has no legal department or Data Protection Officer (DPO): one isn't required for processing at this scale, but you can still write to this address with any question about this policy.
Climb Companion has no server of its own: your profile, projects, photos, training history, Challenges, and all other information you enter stay exclusively on your device, in a local database (SwiftData) that the app creates and manages by itself. No data is ever sent to a developer's server: there is no developer server to send it to.
If you take a photo of a route or a boulder, the image is saved only in the app's local database, never in the system photo library or anywhere else. If you choose an existing photo instead, the app uses iOS's system picker (PhotosPicker): it only receives the photo you choose, without ever requesting or gaining access to the rest of your photo library.
Videos you record in the app, or attach to attempts from your library, stay saved exclusively on this device, in an area of the app that other apps can't access. They're never uploaded to any server, never analyzed, and aren't included in the manual export or the automatic iCloud backup: if you change device or uninstall the app, your videos are lost. The individual frames you choose to pin to holds are saved together with your projects and are included in backups, because they're part of your beta. The audio track is removed at import. A video only leaves your device if you explicitly choose to share it, and in that case it goes wherever you send it (Instagram, TikTok, Messages...), under that service's rules, not ours. When you record a video in the app, iOS also records audio: Climb Companion deletes it immediately after recording and never keeps or transmits it.
Challenge reminders and, if you start a Climb Companion Plus free trial, the single alert shortly before it expires, are local notifications, scheduled and managed entirely by your device: they never pass through any server, developer's or third party's (unlike push notifications, which would require a server). In both cases the app requests permission only when it's actually needed, not at launch.
Purchases and subscriptions are handled entirely by Apple through StoreKit: payment, card details, and billing never pass through the developer, who receives from Apple only confirmation that the purchase is valid, not your payment data. For information on the data Apple collects during purchase, see Apple's own privacy policy.
Climb Companion doesn't integrate any analytics, advertising, or tracking tools of any kind, whether its own or third-party (no Facebook SDK, Google Analytics, ad framework, or similar). We don't learn how you use the app, how often you open it, or what you do inside it: that data stays only on your device and we never see it.
Sometimes, after a positive moment (a route sent, a training card finished, a Challenge completed), the system popup asking you to rate the app may appear. It's Apple's native mechanism (SKStoreReviewController), managed entirely by iOS: the app only decides when to suggest it, never shows it directly, and never receives any outcome. We don't know whether you left a rating, how many stars you gave, or whether you simply closed the popup — Apple doesn't share this information with the developer. If you've turned on "Share With App Developers" in iOS Settings ▸ Privacy & Security ▸ Analytics & Improvements, Apple can provide us, through App Store Connect, some aggregated and anonymous usage metrics: even in that case it's a channel managed and aggregated by Apple, not tracking implemented by this app.
From Settings ▸ Data & Backup you can export all your data to a file that you choose where to save (Files, iCloud Drive, AirDrop...): it's entirely under your control, not an automatic upload. The same file can be re-imported to restore data on another device or after reinstalling the app. The developer never has access to this file unless you choose to share it yourself.
Your data stays on the device until you uninstall the app or delete it yourself from the individual screens (e.g. deleting a project or an attempt). Uninstalling the app permanently erases everything, unless you saved a manual backup beforehand: that's why a periodic export is recommended before switching devices.
From Settings ▸ iCloud Backup you can turn on, if you want, the automatic saving of a copy of your data (the same format as the manual export) to your private iCloud Drive: it's off by default, only you can turn it on. Your data stays in your own personal Apple account, under your private iCloud — the developer has no access to that backup, nor to any server of its own. This is not real-time sync between devices (that would require CloudKit, not yet introduced): it's a backup copy written periodically, useful so you don't lose your history when switching devices.
Climb Companion is not specifically directed at children under 16 and doesn't require account registration, so it doesn't knowingly collect identifying data from minors. If you're a parent and believe your child used the app and entered personal data, you can delete it at any time by removing the app or the individual content from the settings.
Because your data stays on your device, you already have full direct control: you can view, edit, or delete it at any time from the app's screens, with no need to request it from the developer. If you'd still prefer to formally exercise the rights granted by the GDPR (access, rectification, erasure, portability, objection) by writing to the controller, you can do so at the address given above.
If this policy changes in a material way (for example with the introduction of real-time sync via CloudKit), the updated version will always be published at this same address, with the last-updated date shown at the bottom of the page.
For any question about this policy or the processing of your data, write to [email protected].
Last updated: September 8, 2026
Climb Companion