Terms of Use and Privacy Policy

Last updated: October 27, 2026

This page has two parts. The Terms of Use set the rules for using Climbing Place and Hike Place: who writes the content, what the maps and the navigation can and cannot do, and what we are not responsible for. The Privacy Policy explains what personal data Good Experience s.r.o. collects, why we collect it, and what rights you have.

Who we are

The controller is Good Experience s.r.o., Heinemannova 2695/6, Dejvice, Praha 6, 160 00, Czechia (the Company, we, us).

Contact: contact@climbing.place, or the contact form.

The supervisory authority in Czechia is the Úřad pro ochranu osobních údajů (Office for Personal Data Protection).

What this page covers

The Service includes:

  • the websites climbing.place and hike.place;
  • the Android apps that open those sites (Trusted Web Activities, packages place.climbing.app and place.hike.app);
  • the Climbing Place watch apps for Garmin, Amazfit (Zepp) and Wear OS;
  • pairing those watches with a climbing.place account and uploading sessions to your logbook.

Using the Service is voluntary. Some features (an account, a public listing, a paired watch, payments) need extra data; you can still browse public content without creating an account.

Terms of Use

By using the Service (described under What this page covers) you agree to these terms. If you do not agree, please do not use the Service. Using the Service is free, except paid guide listings, which have their own terms shown when you set one up.

Content is created by users

Most of what you find on the Service is written, drawn, photographed and kept up to date by its users: climbers, hikers, gym managers, guides and other volunteers. That includes climbing areas, sectors and routes, grades, topos and route lines, approaches and parking, GPX tracks and hike posts, photos, descriptions, opening hours and prices, reviews, condition reports, partner posts and comments. Some data comes from public sources such as OpenStreetMap, and some texts are drafted or translated with the help of AI tools.

  • We do not check it on site. We review some contributions before they are published, but we cannot verify everything, and nobody from us has walked every path or climbed every route. Content can be incomplete, out of date or simply wrong: a route can be closed or rebolted, a grade can be off, a path can be washed away, an access rule or a price can have changed.
  • We are not the author and do not answer for it. The Company is not responsible for the accuracy, completeness, timeliness or legality of content created by users or third parties, nor for any harm that comes from relying on it. Opinions and reviews are those of their authors.
  • When you contribute you confirm that the content is accurate to the best of your knowledge, that you have the right to publish it (your own photo or text, or permission from its author), and that it does not break the law or anyone else's rights. You keep your copyright. You give us a free, non-exclusive, worldwide licence to store, publish, adapt (for example crop, watermark, translate, merge with other contributions or simplify a track) and distribute it on the Service and its apps, and to show it when we present the Service. The licence ends when the content is removed, except for copies already shared by others, backups kept for a short time, and contributions merged into a shared record (such as a corrected route description).
  • We may edit, hide or remove content that is inaccurate, outdated, illegal, infringes someone's rights or breaks these terms, and we may suspend accounts that keep doing so.
  • Something wrong? Use "Suggest changes" on the page, or tell us through the contact form. We act on reports of illegal content without undue delay.

Climbing and hiking are at your own risk

Climbing, bouldering, via ferrata, mountaineering and hiking are dangerous and can lead to serious injury or death. The information on the Service does not replace your own judgement, experience, training, equipment and preparation, a printed guidebook or map, local knowledge, or a qualified mountain guide. Check the rock, the anchors, the weather and the conditions on site and turn back when in doubt. Respect access rules, seasonal closures (for example nesting birds), nature reserves and private land, even when a page does not mention them.

Climbing gyms, guides and other businesses listed on the Service are independent. Any booking, ticket or service is an agreement between you and them.

Maps, routing and navigation

The map, GPX Studio and the Navigate tool help you plan and follow a route. They are aids, not a guarantee that a way exists or is safe.

  • Map data. The base map is made from OpenStreetMap data (© OpenStreetMap contributors, ODbL), which volunteers edit, and contour lines and elevation come from digital elevation models. A path on the map may not exist on the ground, may be overgrown, closed, private or dangerous, and a hut, spring or parking place may be gone.
  • Routing is a suggestion. Routes to a destination are calculated automatically (our BRouter server, and the public OSRM foot router when ours does not answer) from OpenStreetMap data. The router does not know current trail conditions, snow, ice, rockfall, high water, closures or your abilities, and it may lead over terrain that is too hard for you. Always check a calculated route against the terrain, signposts and a map before you follow it.
  • Numbers are estimates. Distance, climb and descent, walking times, arrival times, your personal pace, steep sections, sunset and sunrise times are calculated and can differ from reality.
  • Weather. The forecast along a route comes from Open-Meteo or WeatherAPI.com; the sheet names which one. It is a model forecast for a place and an hour and can be wrong, especially in the mountains. Check an official forecast and the sky.
  • GPS. The position from your phone or watch can be off by tens of metres or lost entirely, in deep valleys, in a forest, under a rock face or when the phone saves battery. Off-route alerts, wrong-way warnings, voice instructions and turn cues can come late, be wrong or not come at all. A browser stops the GPS when the screen locks. Watch the terrain, not only the screen, and never follow the navigation into terrain that looks dangerous.
  • Battery and signal. Navigation uses a lot of battery and routing needs a data connection. Take a charged phone, a power bank and a paper map on longer trips.
  • Offline maps are saved only for a corridor around the route; outside it the map stays blank. They live in your browser or app storage, and the browser or the operating system may delete them, for example when the phone runs low on space.
  • Live location sharing shows your position to anyone with the link until you stop navigating, stop sharing, or 24 hours have passed. Share the link only with people you trust.
  • Shared tracks open for anyone with the link until you stop sharing. When you also share locations, everyone who joins sees the others’ last position, updated every 5 minutes while Navigate is open, for at most 24 hours. Only the latest position is kept, and it is removed when you stop sharing. Sharing your location uses more battery.
  • Emergency screen. It shows your coordinates and rescue numbers. Whether a call or a text gets through depends on your phone and the mobile signal; 112 works across the EU. We do not watch positions and we do not alert rescuers for you.

My tracks

Signed in, you can save a route you planned, a track file you opened, a track drawn in GPX Studio or a walk you recorded to My tracks. Saved tracks are private: only you see them, until you choose to publish one as a hike. You can rename or delete them at any time in the Navigate menu; deleting your account deletes them too. Keep your own copy (Download GPX) of tracks that matter to you; we do not guarantee that stored data will never be lost.

No warranty and limitation of liability

The Service is provided "as is" and "as available", without any warranty as to its accuracy, completeness, availability or fitness for a particular purpose. We may change, limit or end features, and the Service may be unavailable from time to time.

To the extent permitted by law, the Company is not liable for injury, death, loss or damage, direct or indirect, that arises from using the Service; from content created by users or third parties; from map, routing, navigation, weather or GPS errors; or from outages and data loss. Nothing in these terms excludes liability that cannot be excluded by law, such as liability for harm caused intentionally or through gross negligence, or the mandatory rights you have as a consumer.

Your account and fair use

Keep your sign-in details to yourself and tell us if your account has been misused. Do not post spam, fake reviews or someone else's personal data, do not impersonate others, do not upload malware, and do not try to break, overload or copy the Service in bulk (scraping). We may suspend or close accounts that break these rules.

Changes and governing law

We may update these terms; the current version is always on this page, with the date at the top. These terms are governed by Czech law. If you are a consumer, you also keep the protection of the mandatory law of the country where you live. A consumer may also turn to the Czech Trade Inspection Authority (ČOI) for out-of-court dispute resolution.

Privacy Policy

Delete your Climbing Place account

This section is for users of Climbing Place (the website, the Climbing Place Android app, and the Climbing Place watch apps for Wear OS, Garmin and Amazfit), operated by Good Experience s.r.o.

We do not offer in-app one-click deletion. To request that your account be deleted:

  1. E-mail contact@climbing.place from the address on the account, with the subject Delete my Climbing Place account; or
  2. use the contact form and write that you want the account deleted.

We confirm the request and complete it within 30 days.

We delete the account and the personal data we hold for it, including: profile (e-mail, name, photo, preferences), logbook and training entries, saved tracks (My tracks), watch sessions uploaded to climbing.place, pairing-code hashes, chat and booking messages, bookmarks, partner posts, uploaded photos, and similar account content.

We keep only what we must:

  • invoices and tax records for paid guide listings, for the period required by Czech accounting law;
  • a short window of server logs used for security, unless a log is needed longer to investigate abuse;
  • content you asked us to publish as a public contribution (a listing, a topo, a public post), unless you also ask us to remove that.

If you used a watch app without pairing, we have no account data from the watch. Uninstall the app and clear its storage on the watch; nothing was sent to climbing.place.

Personal data we collect

Account and profile

When you register or sign in we may collect:

  • e-mail address and password (stored as a hash);
  • name;
  • optional biography and profile picture;
  • preferences: language, unit system, grade system, whether your profile and logbook are public, e-mail and push notification settings;
  • if you sign in with Google or Facebook: the identifier those providers give us, plus the e-mail and name they share with your consent.

Logbook, contributions and public content

If you use logged-in features we store what you create, for example:

  • outdoor and gym ascents (place, grade, style, date, comments);
  • training log entries;
  • bookmarks;
  • hike posts, photos, notes and GPX tracks;
  • tracks you save to My tracks (name, track points with elevation, distance and climb);
  • route / gym / topo suggestions and uploaded images (including topos);
  • partner-finder posts;
  • chat and direct messages;
  • guide bookings and inquiry messages;
  • watch sessions imported into your logbook (see Watch apps).

Content you mark as public (a public profile, a listing, a contribution, a partner post) can be seen by other users and by search engines. Private logbook items stay on your account unless you make the profile public.

Photos and camera

You may upload photos (routes, hikes, topos, a profile picture, a guide listing). If a photo contains GPS EXIF data, we may read coordinates, altitude and the capture time so we can place it on a map or a street-view walk. The browser or phone camera is used when you scan a watch pairing QR code or take a photo in the app; images are processed only after you choose to upload them.

Location

  • Approximate location: we may look up your IP address in a MaxMind GeoLite2 database on our servers to set a default map view. That lookup stays on our servers.
  • Precise location: only when you use “Near me”, grant geolocation in the browser or Android app, or enable GPS on a watch (typically via ferrata). We use it to show nearby places and, on a watch, to record a track.
  • Photo GPS: as above, from EXIF if present.
  • Last map position: stored in a first-party cookie (lastMapPosition) so the map can reopen where you left it.

We do not track your location in the background on the websites. Watch GPS runs only during a session when that mode and the GPS setting are on.

Hike Place Android app

  • Navigation with the screen locked: when you start navigation or recording a walk, the app runs a foreground service with a visible “Navigation” notification so GPS keeps working while the phone is locked or in your pocket. It stops when you stop navigation. The app does not ask for “allow all the time” background location and does not collect location outside navigation.
  • Where the track goes: a recorded walk stays on your phone until you save it to your tracks or as a hike (then it is uploaded to us like any other track), download it as GPX, or discard it.
  • Notifications: local notifications for navigation alerts (off route, weather), and Firebase Cloud Messaging push for messages you enabled.
  • Crash reports: the app uses Firebase Crashlytics (Google) to send us a report when the app crashes: the stack trace, device model, Android version, app version, free memory/storage and a random installation identifier. It contains no account data, no location and no health data. We use it only to fix bugs; Google keeps crash reports for 90 days.

Health Connect (Android)

If you allow it, the Hike Place app writes each walk you keep (save or download, not discard) to Health Connect on your phone, so it also appears in your fitness apps:

  • an exercise session of type hiking (start and end time, the name of the walk);
  • the exercise route (the GPS points of the walk with time and altitude);
  • distance;
  • elevation gained.

The app only writes these records. It does not read any data from Health Connect, and nothing is sent from Health Connect to us or to anyone else. The records are written on your device; we do not receive a copy through Health Connect.

Access is asked once, after your first finished walk, on Android’s own permission screen. You can refuse, or withdraw access at any time in Settings → Health Connect → App permissions → Hike Place; records already written stay in Health Connect until you delete them there.

The use of information received from Health Connect adheres to the Health Connect Permissions policy, including the Limited Use requirements. We do not use Health Connect data for advertising, do not sell it and do not transfer it to third parties.

Watch apps (Garmin, Amazfit, Wear OS)

The watch app records a climbing session on the device. While a session runs it may read:

  • heart rate;
  • barometric altitude (ascent, indoor route detection);
  • calories reported by the watch;
  • time, laps and grades you enter;
  • GPS track and distance, when GPS is enabled (via ferrata and similar modes);
  • device name / model sent with an upload.

Sessions stay on the watch until you save or discard them. A normal Garmin activity is also written as a FIT file in Garmin Connect; that copy is Garmin’s, not ours.

Pairing is optional. Without a climbing.place account the watch still records; nothing is sent to us. If you pair:

  • you generate a code on the website (My logbook → Watch) or show a QR from the watch;
  • we store only a hash of the code, not the code itself;
  • finished sessions are sent over HTTPS to https://climbing.place/api/watch/session (via Garmin Connect Mobile, the Zepp phone app, or the Wear OS app) with that token;
  • we then store the summary in your logbook: mode, times, duration, ascent/descent, distance, grades, laps, average/max heart rate, calories, device, and an optional GPX track.

Heart rate and related activity metrics are health data (GDPR Article 9). We process them only to provide your logbook, and only if you pair the watch and upload a session — that is your explicit consent. You can stop uploads by clearing the pairing code in the watch/phone settings. You can ask us to delete stored sessions (see Your rights).

We do not sell watch data, use it for advertising, or share heart rate, GPS or session data with advertisers.

Guide listings and payments

If you publish a guide listing we store the listing (display name, photo, bio, services, location text, languages, certifications, website, phone) and billing status. Paid listings go through Stripe. Stripe processes the payment; we store Stripe customer and subscription identifiers and whether the listing is paid. We do not store full card numbers.

Messages we send you

We send e-mail for things you asked for (password reset, contact-form confirmation) and, if you leave e-mail notifications on, for product messages such as chat. Push notifications use the Web Push protocol and a subscription stored against your account; you can turn them off in settings or in the browser.

We do not run SMS or phone marketing. We do not send newsletters beyond those notification settings.

Contact form

Name, e-mail, subject and message. We e-mail a copy to ourselves and a short confirmation to you.

Usage data

Servers automatically log IP address, browser and device type, pages requested, date and time, and similar diagnostic data. This is needed to run and secure the Service.

If you allow tracking cookies, Google Analytics 4 (Google Ireland Limited, measurement ID G-EVMHMZJJX0) measures traffic. You can refuse tracking in Cookie preferences.

Cookies and similar storage

We use first-party cookies and local storage:

  • Strictly necessary: session / login cookies so the site works; cookie-consent choice (cookie_consent_level).
  • Functionality: last map position; colour theme in local storage (bsTheme).
  • Tracking (optional): Google Analytics cookies, only after you accept tracking.
  • Targeting (optional): we do not show third-party ads. This banner category only controls Google’s ads-related consent signals used by Analytics if you grant it. You can leave it off.

You can change this at any time via Cookie preferences in the footer.

How we use the data (legal bases)

  • Contract (GDPR Art. 6(1)(b)): creating and running your account, logbook, uploads, watch pairing and uploads, guide listings, bookings and chat.
  • Consent (Art. 6(1)(a), and Art. 9(2)(a) for health data): analytics cookies; precise geolocation in the browser; uploading heart-rate and GPS sessions from a watch; optional notifications.
  • Legitimate interests (Art. 6(1)(f)): security, abuse prevention, GeoIP map defaults, aggregated statistics, improving the Service. You may object.
  • Legal obligation (Art. 6(1)(c)): accounting records for paid listings, and other duties under Czech or EU law.

Who we share data with

We do not sell personal data. We share it only as follows:

  • Google Ireland Limited — Analytics (if you consent); reCAPTCHA on sign-up, sign-in, password reset and the contact form; Google sign-in if you choose it.
  • Meta Platforms Ireland Limited — Facebook Login if you choose it.
  • Stripe — payments for guide listings.
  • Map tiles — our maps come from our own server (built from OpenStreetMap data). Only if it is unavailable do maps fall back to OpenStreetMap Foundation tiles, which then receive your IP address and the map area you view. The Topo and Satellite layers in GPX Studio load from OpenTopoMap and Esri when you choose them.
  • Routing, elevation and weather — when you ask Navigate or GPX Studio for a route, elevation or a forecast, the coordinates of that route (not your account) go to our own BRouter server, or to the public OSRM foot router run by FOSSGIS (routing.openstreetmap.de) when ours does not answer. Elevation comes from our own terrain model. For a forecast the points of the route go to Open-Meteo straight from your browser, or through our server to WeatherAPI.com.
  • Nominatim (OpenStreetMap) and Photon (Komoot) — reverse geocoding when we turn coordinates into a place name (for example after reading photo GPS).
  • Garmin / Zepp (Amazfit) — if you use their watch and phone apps, those companies process the activity according to their own policies. We receive a session only when you have paired and the phone uploads it to us.
  • Browser push services (for example Google FCM, Mozilla, Apple) — to deliver a push you enabled.
  • Google Firebase Crashlytics — crash reports from the Android app (see Hike Place Android app).
  • CDNs we sometimes load scripts or map extras from (for example cdnjs / Cloudflare, unpkg) — they see your IP the same way any website asset would.
  • Other users — what you publish or send to them (public profile, listings, partner posts, chat, bookings).
  • Authorities — if the law requires it.

reCAPTCHA may collect device and interaction data. It loads on pages that need spam protection (contact, sign-in, sign-up, forgotten password), not on every page.

MaxMind GeoLite2 runs on our servers; we do not send your IP to MaxMind for that lookup.

Where data is processed

We process data in the EU (Czechia). Some processors above are in the EU (Google Ireland, Meta Ireland) or may transfer data to the United States. Where a transfer outside the EEA is needed, it relies on an adequacy decision or Standard Contractual Clauses.

How long we keep data

  • Account, logbook, uploads, saved tracks, watch sessions, chat: for as long as the account exists, then until you ask us to delete them or they are no longer needed.
  • Contact-form messages: as long as needed to answer you and keep a basic record of the request.
  • Payment / listing billing: as required by Czech tax and accounting rules.
  • Server logs: a short period for security and operations, unless a log is needed longer to investigate abuse.
  • Analytics: according to our Google Analytics retention setting; stops for new hits if you withdraw cookie consent.
  • Pairing-code hashes: until you revoke the code or we delete the account.

Usage data used only for security or debugging is kept shorter than account content.

Your rights

You can request access, rectification, erasure, restriction, portability, and object to processing based on legitimate interests. Where we rely on consent, you can withdraw it at any time (cookie banner; watch pairing; notification switches; browser location permission) without affecting earlier processing.

In your account settings you can edit your profile and download a JSON export of core account data (profile, ascents, training log, bookmarks, partner posts, suggestions). That export is not a complete dump of every table; for watch sessions, chat, photos or a full erasure, contact us.

To delete your account, follow Delete your Climbing Place account above.

You may lodge a complaint with the Úřad pro ochranu osobních údajů or with the authority in your EU country of residence.

Children

The Service is not directed at children under 15 (the age of digital consent in Czechia). We do not knowingly collect personal data from anyone under 15. If you believe a child has registered, contact us and we will delete the account.

Security

We use HTTPS, hashed passwords, hashed watch pairing codes, and ordinary access controls. No transmission or storage on the internet is completely secure.

Links to other sites

The Service links to third-party sites (maps, social login, stores, external topos). Their privacy practices are their own. Garmin Connect, Zepp and Google Play have separate policies for their platforms.

Changes

We may update this policy. The new version is posted on this page with a new “Last updated” date. For material changes we will also show a notice on the Service or e-mail account holders when that is reasonable.

Contact