Privacy policy
What Crux collects when you use the app and this website, why, who it is shared with, and the choices you have. Crux is built and run by one independent developer in the UK.
In short
Your logbook is private unless you share it. We keep what you log, what your phone and watch measure with your permission, and a little technical data, to run Crux (2,3). Beta, the coach, sends what a feature needs to Anthropic, without your name or email, and it isn't used to train their models (4). Friends, crews, followers and gyms see only what each feature says, and you can switch every sharing feature off (5). We don't sell your data or use it for advertising (6). Analytics count how the app is used, never how you train, stay in the EU and can be switched off (7). This website sets no cookies (8). Download everything, or delete your account and everything in it at once (9). We reply to requests within one month (11). Crux is for people 16 and over. There is a plain summary at Your data.
1. Who we are
Crux is developed and operated by Benjamin Widdowson, trading as Crux, a sole trader based in the United Kingdom. Under UK and EU data protection law, Benjamin Widdowson is the data controller for the personal data described here. This policy covers the Crux apps for iPhone, Apple Watch and Android, their backend services, and cruxlog.app. It does not cover the App Store, Google Play or Apple Health, which have their own policies.
2. Your account and the app
- What: email address and password, an optional username, display name, photo and profile details (date of birth, gender, height, activity level, units, goals, training locations, availability, reminders), your push token and notification setting, the date you last opened Crux and on which platform and version, support messages, messages you send to friends in Crux (end-to-end encrypted, so we can't read them) and when you read them, and subscription records.
- Why: to run your account, do calculations such as calorie targets and BMI, send the notifications you allow, answer support, and know what to unlock.
- Who sees it: you, and Crux staff for support. Your password is never stored in readable form. It is hashed by our authentication provider, Supabase.
- How long: while your account exists; deleted with it.
Sign-up, Instagram and your phone number
- A sign-up check by Cloudflare Turnstile, which confirms a real person is creating the account.
- Instagram handle, if you add one to your profile. Only your friends and people who follow you on Crux can see it. It is not shown on public pages or share links, and it is not sent to Beta. Remove it at any time from your profile.
- Your phone number, if you choose to share it with a friend. You pick each friend one at a time, and only those friends can see it, with a button to message you on WhatsApp or by text. It is never shown to anyone else, on public pages or share links, and it is not sent to Beta. Stop sharing with a friend at any time, or remove the number and every share stops.
Imported workouts, how you train and taking a break
- Workouts you import. If you import a file of past workouts (a CSV from another app or a spreadsheet), the file is read on your phone. Only the sessions you choose to import are saved, with your account, in the same way as workouts you log in Crux, and they're marked as imported. The file itself isn't uploaded or kept. You can undo an import, which deletes every session it brought in.
- How you train, and taking a break. If you answer "How do you usually train?" in setup or Settings, we keep the answer so Crux can suggest the right things. If you switch on "Taking a break from climbing", we keep the date you switched it on; while it's on, Crux pauses your climbing plan and doesn't send climbing notifications such as new sets or grade questions. Neither is shown to friends, crews or gyms. Switch either off, or change your answer, in Settings.
Notifications, emails and which app you use
- Whether you've allowed notifications, turned them off, haven't been asked yet, or (on iPhone) get them quietly in Notification Centre, so we can tell a problem in Crux from a choice you made. On iPhone, until you answer, Crux may send notifications quietly to Notification Centre; the first one lets you keep them or turn them off.
- Emails about what you've missed. If your phone can't receive Crux notifications, we may email you, at most every three days, to say how many friend requests, Psych, tags and other updates are waiting. The email says only how many of each, never who or what. Turn it off with "Email me what I've missed" in Settings, or with the unsubscribe link in the email.
- The date you last opened the app, and whether it was on iOS or Android and which version. The date is used to decide whether to send one reminder after a long break. The platform and version are counted, as totals only, to see how many people use Crux on each and to plan updates.
Support
- Messages you send through Help and support, any screenshot you attach, and the app version, phone model and system version at the time. They are stored with your account, read by Crux staff, and deleted with your account.
- To help read, look into and answer support messages, Crux may use an AI assistant (Claude, made by Anthropic). It sees the message, any screenshot and the device details, but not your email address. Under Anthropic's terms for API customers, this is not used to train their models.
- Some replies may be written with the assistant's help, using our help articles. A reply sent without a person reading it first says so. A person at Crux reads every conversation, and answers anything about your account, billing, deleting your data, or an injury or health worry. You can ask for a person at any point.
- The assistant may also read a message to suggest which idea for Crux it asks for, so we can count how many people want each one. A person checks every suggestion, and nothing is linked until they do. Messages about your account or billing aren't read for this. The assistant doesn't see your email address.
- Crux staff may start a support conversation with you, for example to welcome you to the beta or ask how Crux is going. It appears in Help and support as a message from Crux, and works like any other support conversation. You don't have to reply, and you can ask us to stop.
While Crux is in beta
If you signed up to test Crux, the small team running Crux sees a weekly summary of how each tester is using the app, with your display name and username, so we can talk to you in person about what's working. It covers counts like how many climbs and sessions you've logged, which features you've used and whether notifications are on. It never includes your email address, notes, photos, videos, health data or where you've been. It's kept on our own computer, not shared with anyone, and stops when the beta ends. People who aren't on the beta only ever appear as an anonymous code.
Subscriptions
Crux Pro is bought through the App Store or Google Play and managed through RevenueCat. We never see or store your card details. We receive your subscription status, so the app knows what to unlock, and a record of each subscription event (a purchase, renewal, cancellation, billing problem, refund or expiry) with the product, price, currency and the store's country. We keep those records to understand how many people subscribe and stay. They are deleted with your account.
3. Health and fitness data
- What: climbs (grades, terrain, holds, attempts, notes, photos and videos), workouts, hangboard sessions and finger tests, nutrition, body weight, measurements and progress photos, Beta's reviews and plans, your training plan, and what your watch, Apple Health or Health Connect measure.
- Why: this is the core of Crux: to log, track and review your training. Health data is a special category under UK and EU law and needs your explicit consent. You give it by creating an account and choosing to log this information.
- Who sees it: only you, unless you share something (section 5).
- How long: while your account exists; deleted with it, or when you delete the entry.
An injury you tell your plan about
If you say you're ill or injured and choose an area, such as a shoulder, Crux keeps it so it can leave moves that load it out of your plan until you say it's fine. You can also tell us this when you first set up Crux. Only you can see it: it isn't shown to friends, crews or gyms, and it isn't sent to Beta.
Apple Watch
During a climbing session the watch app uses the altimeter, motion sensors, step counter and heart rate sensor to detect attempts, height, falls and rest. The results are saved with your climbs: for each attempt, how high you got, whether it ended in a fall, how long you rested, your peak heart rate, and how much your movement was sideways and how high your arm was held. They are stored only in your account. The watch also saves the session as a workout in Apple Health. Strength, Hybrid and guided hangboard sessions started on the iPhone start a watch workout too, which records heart rate and active energy, saves to Apple Health, and isn't imported twice. For hangboard reps, Crux saves how long the watch saw you hanging and when that started, alongside the rep itself, so we can make hang detection more accurate. It's stored only in your account.
Apple Health
If you connect Apple Health, Crux can read steps, heart rate, resting heart rate, active energy, sleep, heart rate variability, heart rate recovery, time in daylight, VO₂ max, weight, workouts and their effort scores, including the route of a walk, run or ride so it can be drawn on that workout's summary. Routes from Apple Health are read on your phone each time and are never stored by Crux or sent to our servers. It can write a weight you log, the workouts you record with Crux, and the effort you give a workout that is linked to an Apple Health workout. Withdraw permission in iOS Settings, under Privacy and Security, then Health. Apple Health data is never sent to our analytics or crash reporting providers, and is never used for advertising.
Health Connect (Android)
Crux can read the same kinds of data from Health Connect, including an exercise session's route when you allow it, read on your phone to play it in its reel and never stored. If you choose to import your history, Crux can also read data recorded before you connected it. Crux only reads; it writes nothing to Health Connect, and it reads only while the app is open, never in the background. You choose each type in Health Connect's own permission screen and can withdraw it there at any time.
Crux uses Health Connect data only to show your training, health trends and workout summaries and to give you Crux's training and nutrition guidance. It is never sold, never used for advertising, never used to decide anyone's eligibility for credit, insurance or anything similar, and never sent to our analytics or crash reporting providers. It is shared only with the providers that run Crux for you (section 6), and people at Crux read it only when you ask for support, for security, or where the law requires. Crux's use of information received from Health Connect follows the Health Connect Permissions policy, including its Limited Use requirements.
Siri and Shortcuts (iPhone)
So Siri can answer questions like "what's my next session", Crux keeps a small summary on your phone: your personal bests, your next planned session, your last session and your training load. It stays on the device and is replaced each time you open Crux. If you log water or weight through Siri, the request waits in the app for you to confirm it before anything is saved.
Location
With your permission, Crux uses your location to match a session to a saved gym and to show a small map on the session summary. When you open the Climbing tab, Crux checks whether you're at one of your saved gyms so it can offer that gym's wall map; this check stays on your phone and isn't saved. On Apple Watch, Crux checks your location once when you start a session, and saves where the session took place for that map. Location is optional. Crux only uses it while the app is open, with one exception: when you start recording a run, walk or ride, Crux uses your location with the app in the background or the phone locked, until you finish. Your phone shows that it's in use the whole time. Crux doesn't use your location in the background at any other time.
Recorded runs, walks and rides
The route is stored with your account: points along the way, each with how long you'd been moving and your height, so Crux can draw it and show your quicker stretches, climbs and best times. While you're recording, the points are kept on your phone so nothing is lost if the signal drops, and that copy is deleted once you save or discard. Your route is private: only you can see it unless you share it, and Beta gets your distance, pace, splits and height gained, never your route or where you were. Crux also stores your best times over set distances, as distances and seconds with no location. For a watch-recorded session, the route is read from Apple Health or Health Connect for the reel; the route itself still isn't stored.
If you share a session as a link or a reel, you choose whether it shows your route on a map or only its shape as a plain line. Either way the first and last 200 m are left off, because a run usually starts at home. A map is a picture made on your phone when you share and stored with the link; anyone with the link can see it, and it stops showing if you delete the link. A crew post can lead with the route on a map, with the first and last 200 m left off. Only active members of that crew see it, and only while the post is up. Your route and best times are included when you download your data, and they're deleted with that session or with your account.
Photos, videos, camera and microphone
- Media you attach is stored privately in your account. The camera is used for photos, barcodes, meal scans and filming your climbs. Crux records video without sound: it does not record audio. If you dictate a note, speech is turned into text by your device's own dictation.
- Finding a session's videos. Crux looks at when photos and videos in your library were taken, on your phone, to suggest which climb each belongs to. Nothing from your library leaves your phone unless you choose to attach it to a climb. Crux never asks for library access by itself: only when you tap to look.
- Filming from your watch. Your watch can start and stop the phone's recording, and Crux cuts it into a clip per go; you choose which to keep and the rest are deleted from your phone. While your watch's camera page is open, your phone sends it small, low-resolution pictures of what the camera sees, straight from the phone to the watch, so you can line up the shot. They aren't saved on either device or sent anywhere else, and they stop when you leave that page.
- Several videos of a climb. One of them is the climb's video, the one used when you share the climb or switch on "Show on the map"; the others are only seen by you and your friends, never by followers or anyone with a share link. Each counts toward your storage.
- Space. "Free up space" re-encodes older videos smaller on your phone and replaces the stored copy. It never touches a video you've shared as beta or one on your current project.
- Only videos of you. Videos you add to a climb, and beta you share, must be of you climbing. Before a video is shared publicly as beta, Crux asks you to confirm it's you. Don't add or share videos of other people climbing; if you see one, report it from the video and we'll take it down.
- Choosing the best part of a clip. To open a video on your best go, your phone looks at where a person is in the frame, on the phone itself (on Android this uses an open-source model built into Crux, not a Google service). Nothing about this leaves your phone, and it isn't used to recognise who anyone is. The same applies when Crux checks whether a hold photo has someone in it, and when it reads your video of a climb.
Bluetooth and force sensors
- If you connect a force sensor (such as a Tindeq Progressor) to measure your finger strength, Crux uses Bluetooth to find it and read its force readings while a test or session is running. The readings are saved with that test in your account, like any test you type in, including a small copy of the force over time so the chart can be redrawn.
- Crux keeps which sensor your phone used last on your phone only, so it can reconnect; it doesn't send the sensor's identity to Crux. Crux sends nothing to the sensor's maker, and stores nothing on the sensor, so a sensor you borrow keeps none of your readings.
- While a watch workout runs, the sensor's live reading is shown on your watch too. Bluetooth is also how your Garmin watch sends climbs. You can turn Bluetooth access off for Crux in your phone's settings at any time.
- Sharing a grip test. If you share a grip test (a peak pull, pinch or a lift from the floor) to a crew, the post shows each hand's result in kilograms or as a share of your body weight, never both, so your body weight can't be worked out from it, and never the force recording itself.
4. Beta, the AI coach
- What: the data a feature needs, sent from our backend to Anthropic, the company behind the Claude models: for example recent sessions, effort, goals, your plan, body weight, nutrition totals, and recent sleep, resting heart rate and heart rate variability.
- Why: so Beta can write reviews, plans, workouts and nutrition guidance. A request is only made when you use a coach feature. Beta does not give medical advice.
- Who sees it: Anthropic processes it. Under Anthropic's terms for API customers, this data is not used to train their models. Your account name and email address are not included in these requests.
- How long: Beta's reviews and plans are kept in your account and deleted with it.
What each feature sends
- Your training plan: its tracks, block and week, and why a session was missed, but never an injury.
- A meal photo scan sends the photo, and so does a photo of your own training spreadsheet you ask Beta to read.
- If you ask Beta to read a workout file you're importing, the column names and the first 20 rows are sent so Beta can say what each column holds; nothing else in the file is sent, and Beta's answer isn't stored.
- If you ask Crux to read your video of a climb, your phone works out how you moved from the video itself. The video and your body's movement stay on your phone; only which hand and foot used which numbered hold, when, and your height if you've set it, are sent to Beta.
- Planning with Beta sends what you type with your goals, your available training times and a count of your recent sessions.
- If you ask Beta a question, your question is sent with a summary of your logged climbing and training; Crux does not store the question or the answer, and the last few are kept only on your phone.
- With Crux Pro, when Beta reviews a climbing session or plans your next one, it reads the replies and notes on your climbs and on the problems you're working, with their time in the video and what was drawn. Beta never sees the video itself or who wrote a note.
- Listening to a review uses your device's built-in text to speech, and nothing is sent anywhere for that.
Ratings and plays
If you rate one of Beta's cards, the rating and any note you add are stored with that card in your account, so we can fix what Beta gets wrong. They are deleted with your account, and the note is never sent to our analytics. When you play Beta's review, or its first line, we record the date and time with that review. It is deleted with your account.
5. Friends, crews, gyms and sharing
- What: what you choose to share, and the links between you and others (friends, follows, crews, tags, challenges, replies).
- Why: so you can climb and train with other people.
- Who sees it: by default, nothing you log is visible to anyone else. These features change that, and each is your choice. Each part below says exactly who sees what. You can block a person and report a crew or a reply; reports are reviewed by Crux staff, who may remove a reported reply.
- How long: until you remove it, stop sharing, leave, or delete your account.
Finding you, invites and your QR
- Once you pick a username, other signed-in climbers can find you by it and see your username, display name and profile photo. You choose whether they can also find you by your name, see you as someone who climbs at the same gyms, or find you from their contacts. All three are on by default for new accounts. On 11 November 2026 we switched them on for existing accounts that had never saved a choice; if you had saved a choice, it hasn't changed. Existing accounts are told about this in the app. You can turn each one off at any time in Settings, under Friends and privacy, then How people find you.
- If you turn on being shown at your gyms, other climbers at those gyms can see you there and add you as a friend or follow you, and Crux may tell them, by name, that you've joined Crux. If you climb at the same gym at the same time as someone, Crux may ask them afterwards whether they were climbing with you. It shows your name, username, photo and the gym, never your climbs. If you're shown at your gyms, Crux may also suggest you to climbers who were at the same gym at the same time as you, or who usually climb there in the same part of the week as you (for example weekday evenings), in the last 60 days. It says only that: the gym, and a time of week the other climber climbs in themselves. It never shows when you climb, your climbs, or which days you were there. Turning off being shown at your gyms stops it. If you can be found by name or at your gyms, Crux may also suggest you to people who share two or more friends with you, saying which of their friends know you.
- Checking your contacts. Your phone scrambles (hashes) each email address and phone number before anything is sent. We compare them with climbers who allowed contact matching, return any matches, and discard them straight away. We keep only a count of how many checks you made that day. Crux never contacts anyone in your address book.
- Being found from contacts. We store a scrambled copy of your account email, and of your phone number if you add it. Turning it off deletes both.
- Invites. An invite link opens a web page and image showing your name, username and your profile photo, if you have one. You send invites yourself, from your phone.
- Your session QR. Showing it means you agree to be friends with anyone who scans it and taps Join in the next 12 hours, without a request to accept. They choose, with a tick for each, whether to become your friend, join the crew you picked and tag you both in that day's session. You're told when someone joins, and can stop the QR at any time. Don't post your QR publicly.
- People who aren't on Crux. You can add someone you climbed with by their first name only. We keep that first name on your account and nowhere else: nobody else can see it, it isn't shared with your friends, crews or gyms, and it is never sent to Beta or any other service.
- Who invited you. If you open someone's share link, or follow their link to the beta form and then make an account with the same email, or name them as who sent you, we record that they brought you. For 30 days after you join, we tell you whose link it was so you can add them as a friend, and we tell them you joined so they can add you. Nothing else is shown about it, it isn't shown to anyone else, and either of you can simply ignore it. It's removed if either account is deleted.
Friends, followers, messages and hellos
- Friends. Friendship needs both of you to agree. A friend can see your sends with their grade, date and gym, your climbing days, your badges and crews, and a score and grade history worked out from those sends. They can give Psych, and you are told who did. If you choose a current project, friends can see its grade, gym, tape colour and wall pin, and for each climb on it the date, result, goes, height and any photos or videos. Choosing a different project, or none, takes them away straight away. Friends can also watch the videos of your climbs: every go you've kept a video of, each marked with its go number, whether it sent and how high it got. Apart from those and your current project, friends never see your photos or videos. They never see notes, heart rate, effort, rests, time on the wall, weight or where you came off a climb.
- Your home gym. Your friends see it on your profile, with Member if you've said so and left Show on my profile on. Other gyms you climb at aren't shown to anyone else.
- Your plan. With "Show on my profile" on, friends, and followers if your profile is public, can see your plan's shape. Never your weights, your sessions or anything you've told the plan about an injury.
- Saving a friend's climb. Crux tells that friend you saved it, and later if you send or flash it. They're never told about goes that didn't send, and nothing is sent to people who aren't your friends.
- Following. Anyone signed in can follow you, unless you turn on "Private account" (off by default); then you approve each request, and until you approve someone they see only your name and photo. A follower sees your public beta videos, and, if "Public profile" is on, your name, photo and grades; your sends reach followers only if you also turn on "Show my sends to followers". Followers never see your sessions, the gym, notes, other photos or videos, heart rate or weight: those are for friends. Only you see your followers list. Removing someone stops them following you; they aren't told. Changing any switch takes effect straight away.
- Messages. Friends can message each other in Crux. Messages are end-to-end encrypted: they're locked on the sender's phone with keys that only the two of you have, so nobody else can read them, including Crux. Your messages key is made on your phone and its private part never leaves it. If you make a recovery key, a copy of your messages key is stored with your account, locked with that recovery key, which only you have; Crux can't open it. Without a recovery key, messages can't be read on a new phone. Crux still stores who you message and when, when messages are read, emoji reactions, and which message replies to which, but not what you wrote or shared. If you report a message, your phone sends us that message and the 10 before it (or, if you report the whole conversation, its last 50), as your phone shows them, and we keep that copy with the report so we can act on it. Messages are never given to Beta, never used for analytics, and never shown anywhere else in Crux. You can unsend your own messages at any time, which removes them for both of you. If either of you blocks the other or you stop being friends, neither of you can send new messages. We keep messages until they're unsent or an account is deleted; deleting your account deletes the messages you sent and the conversations you were in. On iPhone, notifications show the sender's name and the start of the message, unlocked on your phone, unless you turn previews off, mute the conversation or turn off friends and crews notifications; on Android they say who sent it.
- Notes on friend requests. When you ask someone to be your friend you can add a short note, encrypted like a message. They see it with the request; if they accept, it becomes the first message in your conversation.
- Hellos. One short message (up to 140 characters) to someone Crux already connects you with, or who chose to be found; never across a block, never if they switched hellos off. Messages are replacing them: once the app has messages you can't send new hellos, hellos between people who are friends move into their conversation, and hellos from people who aren't friends stay in your hello list. They are not sent to Beta, and they are deleted when either account is deleted.
Crews
- Sharing a session to a crew. The crew sees a snapshot: the title, date, gym, one highlight and up to four figures, and if you choose, a workout's exercises or a climbing session's climbs (grade, tape, result, goes, wall pin and kept videos; on by default, with a switch). It never includes your notes, heart rate, effort, rests, time on the wall, weight or where you came off a climb. Only active members of that crew can see it, and only while the post is up: remove the post, or leave the crew, and it stops showing straight away.
- Sharing automatically. On by default for every crew you're in. Posts lead with one of that session's own videos if it has one, otherwise one of its photos, otherwise the gym on a map, otherwise figures only; choose something else for each crew. Turn it off per crew and per kind of session, and turn off "Share to new crews". Imported sessions from Apple Health, Health Connect or a file are never shared automatically. Crewmates can't download your video through Crux, but anyone can screenshot or record what's on their screen, so only share what you're happy for that crew to see.
- Sharing a strength test. The card shows either the weight you added or your result as a share of body weight, whichever you choose, never both, so your body weight can't be worked out from it. It goes only to the crew you pick, never to a public link.
- Crew photos. Members, and people invited to the crew, can see them; if the crew is listed, any signed-in climber can. Owners and admins change them. Closing a crew deletes them.
- Crew board and awards. If you opt in, crew members see your sent grades, climbing days and flashes for the week. Sunday awards are worked out only from members who opted in, and only each award's winner is shown.
- A crew's regular session counts nights on which two or more members climbed. It never names who didn't climb.
- Crew projects show each member's goes and sends on that problem that week, from climbs shared with the crew or the crew board. Your go shares your result and any line with the person you pass to, and tells you if they send it.
- A crew's week reel is made only from sessions members shared with the crew that week. Only members can watch it, and it's never a public link.
- Tagging. If someone tags you in a session, nothing is linked until you accept. A shared reel can then show your climbs' grade, colour, terrain, attempts and outcome that day. It never shows notes, photos, heart rate or location.
- Belaying. A friend can add themselves as the belayer on a sport route you log, and you're told when they do. Who belayed a climb (their name and photo) is shown to anyone signed in to Crux who can see that climb. You can take a belayer off your climb, and they can take themselves off. Blocks hide it both ways.
- Board sessions. Friends, crewmates and people tagged together that day see each other's board sends: the problem's name, grade, angle, board and the time, with who sent it. Never tries, notes, heart rate or effort. A problem set on the board shows to linked people at that gym for 20 minutes.
Gyms
- Adding a gym. It becomes a shared gym page anyone signed in can see. We record that you added it, but that record isn't shown to anyone. From Apple Maps we store only its Apple Maps ID and name. Its map position is only saved from you: where you tap on the map, or your phone's location if you tap "I'm at the gym now". Nobody is told where you were.
- Setting up a gym. What you set is shown on the gym page, labelled "Set up by climbers" until it has been checked. Other climbers' checks are counted but not shown with names. Your username may be shown as one of the people who set it up only if "Show my name on problems I tag" is on. A photo of the gym's grade board, if you choose to take one, is sent to Anthropic so Beta can read the colours from it; it isn't kept after that, and you check and edit every colour before anything is saved.
- Public gym pages at cruxlog.app/g/ show the gym's name, area, grading, facilities and challenges. It never shows who climbs there, how many people do, or anything about you.
- Gym invite links show the gym's name and area, how it grades, some of what it has and, if you have a username, that you invited them. It doesn't show anything from your logbook, how many people climb there, or who else is on Crux.
- Gym memberships. Stored with your account and shown on your profile unless you hide it. A gym's page never shows who is a member or how many. Crux may tell a gym how many of its members use Crux, only when there are at least five, and never who they are.
- Gym statistics. Off by default. If you opt in, your sessions, and your climbs on the gym's map, count toward anonymous totals the gym's team can see. Totals are shown only when at least five climbers are included. Gyms never see an individual's data.
- How much Crux is used at each gym. We count, as totals per gym, climbs, workouts and people logging there. These totals stay inside Crux. A gym is only ever told the totals described above, and only when there are at least five.
- Setters' names. A setter with a Crux account is only named once they agree, and can ask to be taken off at any time. Setters see only anonymous totals from at least three climbers.
- Gym reset calendars. Crux reads gyms' public posts about reset dates, and Beta may read a post's image to find walls and dates. We never copy a gym's photos onto its Crux page unless the gym connects its account and agrees.
The wall map, problems and beta videos
- Tagging a problem. Its pin, tape colour, wall type, holds, moves and any photo you take of it are visible to everyone signed in to Crux, and on the problem's share page. Photograph the holds, not people. Your name is shown as the person who tagged it unless you turn off "Show my name on problems I tag". A problem's hold map can be seen and edited by anyone signed in. The climber who first mapped it is named on it unless they turn off "Show my name on problems I tag"; who changed it later isn't shown.
- Scanning a wall. If you scan a section of wall, the photo and the holds Crux finds on it are visible to everyone signed in to Crux, and are used for every problem on that wall until it's reset. Holds are found on your phone; the photo isn't sent anywhere else to do it. Crux checks the photo on your phone and won't use one with a person in it, so photograph the wall, not people. Your name is shown as the person who scanned it unless you turn off "Show my name on problems I tag". Anyone signed in can correct a scan, and who corrected it isn't shown. If the gym scans the wall itself, its scan replaces yours and can't be changed by climbers. Scans and corrections may be used to improve Crux's own hold finder, which runs on phones; they are photos of walls, never of people, and aren't shared with anyone else to do this. A scan is kept until the wall is reset, then kept with that set's problems.
- Map totals. Totals are shown only once at least three climbers are included, and never with names. If nobody has added a problem's wall type, holds and moves, they can come from the first climber who logged it with an answer, without a name, until three climbers have given one. Turn off "Count my climbs in map totals" in Settings and your climbs are left out of every total.
- How climbs feel. Your answer on its own is never shown; a problem shows the most common answer only once three climbers have answered. Crux may suggest problems friends and crewmates sent, naming them; it never shows their goes that didn't send.
- Beta videos. If you switch on "Show on the map" for a climb's video, it becomes public, with your name, photo and a link to your profile, on that problem and the wall map and its share link, even if your account is private. We count how many people watched it (each person once, never you) and any Psych it gets; we don't show you who watched. Turning it off removes it everywhere straight away. Nothing is shared this way unless you switch it on for that video.
- Skeleton beta. If you switch on "Share as skeleton beta" for a go, the movement Crux read from your video, as a stick figure on the problem's photo, is shown to anyone signed in to Crux on that problem's page, grouped with others who climbed it the same way. It shows your height band (for example 170–185 cm), never your name or the video. It's off until you switch it on for that go, and switching it off removes it straight away.
- Featuring your climb. We only ever ask about a video you've already made public on the map, we only use it if you say yes to that video, and we credit you by your username unless you ask us not to. Saying no, or ignoring it, changes nothing.
- Challenges. Other people in a challenge see your username, display name, photo and your progress on that challenge. They don't see anything else from your logbook. In a challenge run by a gym, you choose whether your name is shown; if not, you're shown as "A climber" and the gym sees the same. Results are kept for the people who took part and aren't shown on your profile or anywhere public. Leave at any time.
Replies and notes
- A reply shows your username, name and photo. On a crew post, the crew's members see it. On a climb, the climber and their friends see it, and so does anyone signed in to Crux once the climber shows that climb's video on the map. On a problem, anyone signed in to Crux sees it. People who have blocked each other don't see each other's replies.
- Replies are kept until you delete them, the person whose post, climb or problem it is deletes them, or the post, climb or problem is deleted; deleting your account deletes your replies.
- You can tag friends, crewmates and people on the thread who can see it, and crews you're in (a hidden crew only on its own posts). Blocking stops tags both ways. Beta never sees who was tagged.
- Anyone who can see a reply can see who reacted and with which emoji, and the author is told who reacted.
Share links, coach links and Psych from a link
- Share links. A send, reel, invite or profile makes a web page and image anyone with the link can open. We count how many times each page is opened, and how many times a chat app fetched its preview. To count different people, we make a code from the opener's internet address, the kind of browser and the day. The code can't be turned back into the address, is different for each link and each day, and is deleted after two days. We do not record who opened it.
- A climb's video on a send or reel shows only if you include it for that share; anyone with the link can watch it until you stop sharing it on the climb's page. Stopping sharing on the climb's page ends its send links and takes the video off any reel.
- The picture on a shared problem. Your own photo or video still, else the problem's wall map photo, else none, plus a drawing of the wall. Sharing the problem is what makes the picture public. The picture never shows your name, and nothing else about your climbs is added to the page.
- The map on shared session reels. It shows the gym's map and the problems you climbed that day, in order, with tape, grade and result. It never shows a GPS track, the time of each climb, notes, heart rate, or the people you climbed with. Turn off "Show the map on shared reels" in Settings, or when you share.
- Coach links. Unlike other share links it shows the whole session. It's made only when you choose it, works for 30 days, can be stopped from the session's Share menu at any time, and is never shown to search engines. We count how often it's opened, as with other share links, but not who opened it.
- Psych from a shared link. Someone with a Crux account can sign in on the page to send you Psych. You're told who sent it; the page itself only shows how many people have. The sign-in is kept only while the page is open, and nothing is saved in the browser. Blocked people can't send you Psych.
Climbers we contact
Sometimes we message climbers directly, for example on Instagram after they've posted a climb publicly at a gym. We keep their public handle, where we found them, the dates we messaged them and they replied, our own notes, and the link we sent them. Only Crux staff can see this, and nothing else from a Crux account is added to it. Ask us to remove you and we delete it. Ask us not to contact you again and we keep only your handle, so nobody messages you again.
6. How we use it, and who we share it with
We use a small number of service providers. Each receives only what it needs.
| Provider | What it does |
|---|---|
| Supabase | Database, sign-in and file storage |
| Anthropic | Produces the coach's responses, and helps us read support messages |
| RevenueCat | Subscription status |
| Apple and Google | App distribution, payments, maps and, if connected, Apple Health or Health Connect |
| Expo | Delivers push notifications and app updates |
| Resend | Sends emails: sign-up codes, beta next steps and what you've missed, from the EU |
| PostHog | Product analytics, hosted in the EU |
| Sentry | Crash and error reports |
| Cloudflare | Sign-up check, website hosting and email routing |
| Open Food Facts and USDA FoodData Central | Food databases. Only the search term or barcode is sent. |
We do not share your data with data brokers or advertisers. We would only disclose data beyond this list if the law required it, or to protect the safety of Crux, its users or the public.
7. Analytics and crash reports
- What: analytics describes how the app is used. It never describes how you train. Crash reports include the error, the screen, the app version and the device model.
- Why: to understand how Crux is used and fix faults.
- Who sees it: PostHog and Sentry, linked to your account's internal ID, a random string, and never to your name or email address. Analytics data is stored in the EU.
- How long: analytics is deleted with your account. Crash reports keep an ID that no longer matches anyone, and expire under Sentry's retention period.
Exactly what analytics records
- Events record that the app was opened, that you created an account, which setup step you reached, that you logged a type of activity, such as "climbing" or "nutrition", that you used a coach feature, that Beta offered you a review or showed a card that needs Crux Pro and whether you tapped it, whether you gave one of Beta's cards a thumbs up or down (never the note), that you did something straight after a session (played Beta's review, played the reel, sent a share link or posted to a crew) and what kind of session it was, that you saw the Crux Pro screen and which part of the app led you there, that you started or completed a purchase or a trial, and that you made or opened a share link, and that you saw the short map summary after a session and what you tapped on it.
- Which screens of the app you open, by the screen's name only, such as "/climbing-session", never what's on it and never the id of a climb, session or person in it. And which help article you opened, and from which screen. We use these to see which parts of Crux are used, so the most used are easiest to reach.
- We don't use your IP address to work out where you are, and the app doesn't send events about opening, closing or updating it beyond "the app was opened".
- They never include grades, weights, heart rate, food, notes, photos, locations or anything you typed. The app only sends event types declared in advance and drops anything else before it leaves your phone.
- For a sample of sessions crash reports also record how long some actions took, to find slow screens. A copy of each error is kept in our own database with your account, and is deleted with your account.
- You can switch analytics off in Settings, under Friends and privacy, with "Help improve Crux".
- Crash reports cannot be switched off, because they are how faults get fixed. They do not include the contents of your logbook.
8. This website
- This website sets no cookies and runs no analytics or advertising scripts.
- Fonts and images are served from this site, not from a third party. Our host, Cloudflare, keeps standard server logs, which include IP addresses, for security. If you email us, we keep your message and address so we can reply.
The beta form
If you join the beta, we keep your name, your email address and your answers: your phone and watch (make and model), the apps you use for climbing, climbing training, other workouts and nutrition, your home gym, how you heard about Crux, and who sent you, if you give us their Crux username. We also keep where the page saw you come from: the tags on the link you followed, the name of the website that sent you (not the full address), or the Crux share or social link you used. We use them to invite you and, counted as totals, to decide which phones and watches to support and where to find climbers. We don't keep your IP address. To stop abuse we keep a code made from it and the day, which can't be turned back into the address. Ask us to delete your answers at any time.
The ideas board
cruxlog.app/ideas lists ideas for Crux in our own words, with how many people asked for or voted for each, shown only from five people up. It never shows what you wrote to us, or who asked or voted. To vote you sign in with your Crux account there; the sign-in is kept in that browser tab's memory and nothing is saved in your browser, so closing the tab signs you out. The sign-in form loads Cloudflare Turnstile. Your votes are stored with your account; only you can see which ideas you voted for, and we see totals. Deleting your account deletes your votes and your links to ideas.
9. Keeping and deleting
We keep your data while your account is active. You can delete your account and everything in it fromSettings, then Delete account. This happens at once and cannot be undone. You can get a copy of everything first: in the app, go to Settings, then Your data, then Download my data.
- Your analytics profile and its events are deleted at the same time.
- Share and invite links stop working, and the images made for them are deleted.
- Your contact-matching settings, and the scrambled email and phone number stored for them, are deleted.
- Backups are cycled out within 30 days.
- Edits you suggested to a gym, gyms you asked us to add, crews you reported, and changes you made to a gym page you ran are kept, with your name removed, as long as the gym or crew is on Crux.
If you cannot open the app, email privacy@cruxlog.app from your account's address and we will delete it within 30 days. Delete your account lists what is deleted and what is kept.
10. Legal basis
- Consent for health and fitness data, and for optional features such as Apple Health, Health Connect, location, camera, contacts, notifications, gym statistics. You can withdraw consent by switching the feature off, removing the permission, or deleting your account.
- Contract for account and subscription data, which we need to provide the service.
- Legitimate interests for analytics and crash reporting, which keep the app working. You can object by switching analytics off.
- Legitimate interests for the ways of being found (by name, at your gyms and from contacts), which help the people you climb with find you. They start switched on, and you can object by switching each one off in Settings.
11. Your rights
If you are in the UK or EU, you can access, correct and erase your data, restrict or object to some processing, move it to another service, and withdraw consent. Download my data makes one file with everything Crux stores about your account, in a standard format (JSON) you can open without Crux, with links to your photos and videos that work for seven days.
To use any of these rights, email privacy@cruxlog.app. We reply within one month. If you are not satisfied, you can complain to theInformation Commissioner's Office, or to your local authority in the EU. If you live in California, you have similar rights under the CCPA. We do not sell personal data, so there is nothing to opt out of.
12. International transfers
Some providers, including Anthropic and Sentry, process data outside the UK and EU, including in the United States. Where this happens we rely on that provider's safeguards, such as Standard Contractual Clauses, to protect your data to UK and EU standards. Analytics data stays in the EU.
13. Children
Crux is not intended for anyone under 16. We do not knowingly collect data from children. If you believe a child has given us personal data, contact us and we will delete it.
14. Security
Connections are encrypted. Access rules mean your data can only be read by your own account, except where you have chosen to share it. Photos and videos are stored privately. No system is completely secure, but we work to keep Crux's practices sound for an app of its size.
15. Changes
We update this policy as Crux changes, and we change the date and version at the top when we do. If a change is significant, we will tell you in the app. Every version is listed onthe change log.
16. Contact
Benjamin Widdowson, trading as Crux
privacy@cruxlog.app