Analytics without your training

We need to know whether the app works. We don't need to know what you climbed. So the app is built so it can't tell us.

By Ben Widdowson · · 5 minute read · Updated

The short answer. Crux's analytics record that things happened, such as the app opening or a climb being logged, never what was in them. There are twenty-five events, all declared in the app's code, and anything else is dropped before it leaves your phone. They never include grades, weights, heart rate, food, notes, photos, locations or anything you typed. They are stored in the EU, and you can switch them off.

Try it: tap an action

The figures at a glance

25events the app can send, and nothing else
0grades, weights, heart rates or meals in any of them
EUwhere analytics are stored
0cookies or tracking scripts on this website

The rule

Analytics describe how the app is used. They never describe how you train. "Someone logged a boulder" helps us see whether logging works. "Someone sent a V5 at 82 kg with a heart rate of 171" is your training, and it stays in your logbook.

Everything the app sends

This is the whole list, with related events grouped. Each event can only carry the details next to it, and each of those is a fixed choice set in the app, never something you typed or measured.

EventWhat it carries
The app was openedNothing else
You logged somethingThe kind: a boulder, a workout, food
You used a coach featureWhich feature
You rated one of Beta's cardsUp or down, and whether you added a note (never the note)
You created an accountWhether a share link brought you
You reached a setup stepWhich step
Beta offered you a review, or showed a card that needs Crux Pro, and whether you tapped itWhich card, and whether it was a free review, Crux Pro or the free reviews used up
You saw the Crux Pro screenWhich part of the app led there
You started, completed or restored a purchase, or started a trialMonthly or yearly, and where you started
You made or opened a share link, or a link brought a new accountProfile, send, reel or invite
You did something after a sessionWhat it was (played Beta, played the reel, shared, posted to a crew) and the kind of session
Crux suggested filming a goWhat prompted it (such as a hard go that didn't send) and where it showed (watch, phone)
You answered that suggestionYes, no, or closed
You saw the short map summary after a sessionHow it opened (after a session, from a notification, on the next open)
You tapped something on itWhat it was (the full reel, the session summary, pinning climbs, sharing, closing it), and for a share whether it was a video, picture, text or link
You opened Beta's take on the mapWhether you watched to the end or closed it, and how many of its screens you reached
You opened a screenThe screen's name only, such as "/climbing-session", never what's on it or the id of anything in it
You opened a help articleWhich article, and from which screen
You added a video to a climbHow it arrived (recorded in Crux, from your camera roll, cut from a recording) and whether the climb was a send (never the video)

How the rule is enforced

The list above is written into the app. Before an event is sent, the app checks it against the list and removes any detail that isn't declared for it. So a mistake in a new feature can't send your training by accident: it gets stripped on the phone. Adding anything to the list means changing the privacy policy first.

Where it goes, and what it's linked to

  • Stored in the EU, with our analytics provider, PostHog.
  • Linked to a random ID, never your name or email address.
  • No location. Your IP address isn't used to work out where you are.
  • No screen recordings, and no events about the app opening, closing or updating beyond "the app was opened".
  • Deleted with your account, along with every event.

Crash reports

Crash reports are separate and can't be switched off, because they are how faults get fixed. They include the error, the screen, the app version and the phone model. They don't include your logbook. The app removes the details from web addresses before they are recorded, because those can carry search terms, and leaves out the app's own log messages. Crash reports are kept for up to 90 days.

This website

cruxlog.app sets no cookies and runs no analytics or advertising scripts. Fonts and images are served from this site. Our host keeps standard server logs, which include IP addresses, for security.

What we do not claim

  • That we collect nothing. The events above are linked to your account's random ID, so we can see that one account logged ten climbs this week. We just can't see what they were.
  • That Crux never sees your training. Your logbook is stored on our servers so it works across your devices, and the coach reads it when you use a coach feature. Analytics is the part we keep training out of.

The privacy policy covers this in its analytics and crash reports section.

Common questions

How do I switch analytics off?

Settings, then Friends and privacy, then turn off "Help improve Crux". It takes effect straight away and stays off.

Is my data deleted if I delete my account?

Yes. Deleting your account also deletes your analytics profile and its events.

Why not just collect everything and keep it private?

Because data that isn't collected can't leak, be misused or be asked for. We only need to know whether the app works, not how you train.

Found an error? Email hello@cruxlog.app. This note is general information, not medical or coaching advice for your situation.

See your own climbing this way

Crux is in beta on iPhone and Apple Watch.

Join the beta