Privacy Policy for ClimbLogger

Last updated: September 29, 2026

The short version

Your climbing sessions, health data and statistics live on your device — we cannot see them. Our server (hosted in the EU) stores only three things: community contributions you actively submit, a temporary relay of Garmin watch sessions (deleted automatically), and the shared climbing-location database. The app uses Meta's SDK to measure our advertising. Details below.

1. Data stored on your device only

This data is never uploaded to our server. It syncs between your iPhone and Apple Watch via Apple's WatchConnectivity framework, and you can delete it per session or entirely in the app.

1b. Backup and transfer to a new phone

2. Data processed on our server

ClimbLogger has a backend server (api.happygolucky.no) hosted by Hetzner in Falkenstein, Germany (EU). It stores:

DataWhenRetention
Community submissions — new locations, corrections and feedback you send in, an optional photo, and an anonymous per-device identifier (Apple identifierForVendor) used for abuse preventionOnly when you actively submitUntil reviewed; the identifier is used solely for spam triage
Garmin session relay — if you connect a Garmin watch, finished sessions (including heart-rate measurements) pass through the server so your iPhone can fetch them. Protected by a random per-install token.Only if you use Garmin syncDeleted automatically: 30 days after your phone has imported them, 90 days at most. You can request immediate deletion at any time (see Contact).
The climbing-location database — crags, gyms, shops, routes and topos. Public, shared content; not personal data——

Uploaded photos are stripped of EXIF metadata (including location) both on your device and again on the server. We keep no user accounts and no profiles.

3. Advertising measurement (Meta / SKAdNetwork)

The app includes the Meta (Facebook) SDK to measure the effectiveness of our own ads for ClimbLogger. It sends app-activity events (such as install and app launches, with device model, OS version, language and IP address) to Meta. It has no access to your climbing or health data. Attribution also uses Apple's privacy-preserving SKAdNetwork, which reports aggregate campaign numbers without identifying you.

4. Location photos (Google)

Photos of climbing locations shown in the app are fetched by our server from Google Places on your behalf — your identity and IP address are not sent to Google by us.

5. Strava integration

When you connect Strava, activities are created on your Strava profile only when you explicitly sync a session, including statistics, an infographic image, and heart-rate summary if available. You can disconnect Strava at any time in Settings and delete synced activities on Strava.

5b. Notion integration

If you connect Notion (Settings → Export → Send to Notion), ClimbLogger writes your sessions and climbs into the Notion page you choose — normally a copy of our ClimbLogger Logbook template — when you tap Sync. The data goes directly from your phone to Notion. Heart-rate summaries are included only if you turn that option on, and location coordinates are never sent. To connect, Notion sends a one-time login code through our server (api.happygolucky.no), which exchanges it for an access token and passes the token straight back to your phone; we do not store the code, the token or any of your Notion data. You can disconnect in the app at any time and remove the ClimbLogger connection in Notion under Settings → Connections.

5c. Exporting your data

Settings → Export → Export data creates a JSON or CSV file on your phone with your sessions and climbs. The file is shared only where you choose in the iOS share sheet and is deleted from the app's temporary storage afterwards. Heart-rate data and coordinates are included only if you turn them on; coordinates of places you created yourself are never exported.

6. Data sharing

We do not sell, rent or trade your personal information. Data leaves the systems described above only when you explicitly sync to Strava or Notion, export a file yourself, or as described for Meta (section 3) and Google (section 4).

7. Your rights (GDPR)

8. Children's privacy

ClimbLogger is not intended for children under 13, and we do not knowingly collect data from children under 13.

9. Changes to this policy

We update this page when the app's data handling changes, and note significant changes in release notes.

10. Contact

Email: marius.arnesen@gmail.com
Website: https://happygolucky.no/climblogger/


Personvernserklæring for ClimbLogger

Sist oppdatert: 19. september 2026

Kortversjonen: Klatreøktene, helsedataene og statistikken din lagres lokalt på enheten din — vi kan ikke se dem. Serveren vår (i EU, Tyskland) lagrer kun: bidrag du selv sender inn (nye steder, rettelser, tilbakemeldinger — med en anonym enhets-ID mot misbruk), en midlertidig mellomlagring av Garmin-økter inkl. puls (slettes automatisk etter 30–90 dager, og på forespørsel), og den delte klatrestedsdatabasen. Opplastede bilder renses for EXIF/posisjonsdata. Appen bruker Metas SDK til å måle annonsene våre (app-hendelser som installasjon og oppstart sendes til Meta), samt Apples anonyme SKAdNetwork. Stedsbilder hentes fra Google via serveren vår, uten at din identitet deles. Valgfri sikkerhetskopi lagres i din egen private iCloud (hos Apple), og «Overfør til ny telefon» sender en fil direkte mellom enhetene dine — ingen av delene går via serveren vår. Vi selger aldri data. Spørsmål, innsyn eller sletting: marius.arnesen@gmail.com.