Privacy policy

Gear Loop is a set of pocket tools for climbers. You can use every tool without an account; everything you enter is then saved only in your browser and nothing is sent to us.

If you sign in

When you sign in with Google or Apple, we receive your name, email address and (from Google) profile picture. We use them only to recognise your account and show who is signed in. We never see your password.

What we store

For a signed-in account: your hangboard training sessions (time, workout, hangs, and the effort, edge, weight and notes you add), your trips and pack lists, your gear in Rack (with its dates, notes and resoles) and racks, saved crags and places, and app preferences such as units and training setup, so they are the same on every device you sign in on.

Photos

You can add photos of your gear in Rack. Before a photo is saved, your device resizes it and re-encodes it, which removes its location (GPS) and camera details. Signed out, photos stay on your device. Signed in, they are stored in your account so they are on every device you sign in on; deleting a photo or the gear deletes the stored file. Your photos are private to your account, and become visible to others only if you share a rack with “Include my photos” turned on; turning that off or stopping sharing removes access. Signing out removes the copies on your device.

Trip crews

When you share a trip with your crew, anyone with its link can see the place, the dates, the gear list and the names people chose to show, plus the stays (addresses, links and notes), everyone’s travel times and flight numbers, and everyone’s route lists; nothing else about you (no email or account details). So don’t put booking codes or door codes you wouldn’t share with the whole link in there. Friends can join as guests with just a name, or signed in. A guest’s device keeps a private key that lets it change their items; we store only a scrambled (hashed) copy of it. The organiser can remove people, make a new link (the old one stops working) or stop sharing, which deletes the crew, the list and the link; anyone can leave a trip, which removes their name, travel and routes from it. When you save a stay’s address, your device asks OpenStreetMap’s Photon service (komoot) where it is, to show the distance to the crag; when you add a beta video, we ask YouTube, Vimeo or TikTok for its title, sending them only the link.

AI gear summary

On a shared trip, the organiser can ask for a “Team gear” summary. Only then, the gear list (item names, amounts and notes) is sent to Google’s Gemini API, with people shown as “person 1”, “person 2” and so on: no names, emails or account details. The summary is stored with the trip and deleted when sharing stops.

Flight details

The travel form suggests airlines and airports from lists that come with the app (airlines © OpenFlights, under the Open Database License; airports from OurAirports), so typing in it sends nothing anywhere. If you use “Fill from booking”, the email text or picture you add is sent to Google’s Gemini API to read out the flights and trains, then thrown away: we don’t store it, and only the flight numbers, places and times come back to the form for you to check. Gemini is asked to leave out booking codes, names, seats and prices, and we check what comes back. Google doesn’t use data sent through the paid API to train its models.

Receipts for Rack

If you use “Fill from a receipt” in Rack, the screenshots, photos or text you add are sent to Google’s Gemini API to read out the climbing gear on them, then thrown away: we don’t store them, and only each item’s make, model, size, quantity, purchase date and shop come back for you to check. Gemini is asked to leave out names, addresses, contact details, order numbers, payment details and prices, and we check what comes back. Signed out, your device keeps a random key so it can be limited to a few reads a day; we see only a scrambled (hashed) copy of it, and only the time of each read is kept. Google doesn’t use data sent through the paid API to train its models.

Route data

Crag stats and the route list you can pick dream routes from come from theCrag (route data © theCrag contributors, shared under CC BY-NC-SA: credit theCrag, non-commercial use, and share alike). The list for a crag is downloaded from Gear Loop when you add a route there; searching it happens on your device and sends nothing anywhere.

Other services the tools use

Weather and conditions come from Open-Meteo: to get a forecast, the coordinates of the crag or town you picked (or your location, if you tap "Use my location") are sent to Open-Meteo. Map links open OpenStreetMap, and route links open theCrag. None of them receive your account details.

What we don’t do

No ads, no selling or sharing of your data, no tracking across other sites. We don’t use your data to train anything.

Where it’s kept

Account data is stored with our backend provider, Convex (in the United States). The site is served by Vercel and Cloudflare. They act on our behalf only to run Gear Loop.

Deleting your data

Email brantscube@gmail.com from the address you signed in with and we’ll delete your account and everything stored with it. Clearing your browser’s site data removes anything stored only on your device.

Beta (news feed)

Beta shows headlines, short excerpts and thumbnails from public climbing news feeds, Reddit and YouTube, and links to the original; opening one takes you to that site, under its own privacy policy. Thumbnails load straight from the sites that publish them. Videos play in YouTube’s privacy-enhanced mode (youtube-nocookie.com), which loads only when you open a video; YouTube then receives your IP address and what you watch, as with any embedded player. Links you save stay on your device and, when you’re signed in, in your account.

Changes

If this policy changes, we’ll update the date above.