Privacy

What we collect

• Your account: email address and a password. Passwords are hashed by our authentication provider; we never see or store the plain text. If you sign in with Apple or Google instead, we receive the email address they pass us (Apple may give a private relay address) and, the first time, your name. Nothing is ever posted back to that account.
• Your profile: display name, and optionally a photo, the disciplines you climb, your grade system and current grades, your home gym or crag, and — because they change what the app shows you — gender, birth year, the year you started climbing, height and wingspan. All of it is optional and editable.
• What you log: sessions and ascents (date, indoor or outdoor, the place, duration, how it felt, your focus, notes, any injuries you record, boulder tallies, named climbs and grades), strength workouts and their sets, training plans, phases, trips, pyramids and assessments. If you use a force sensor, the pulls it measures: the peak and average force, how long you held, which hand, how you were pulling, and the force-over-time curve itself. If you log a climb on a training board (a Kilter, Tension or MoonBoard), we keep which board it was, which climb, and the angle. The climb itself, its grade and its setter's public username come from a public dataset, today BoardSesh's, and are not about you. Climb Kaizen is not affiliated with or endorsed by Kilter, Tension, Moon, Aurora, Tindeq or any other company named here.
• Body measurements, if you switch them on: weight, sleep, steps, resting heart rate, heart-rate variability, blood pressure, waist, hydration, calories, and one-to-five ratings for soreness, stress and motivation. Everything is off until you turn it on, and each one is separate.
• Cycle tracking, if you switch it on: the days you record, an optional flow level, and any symptoms you tag. Off by default, kept in its own place, and deletable on its own.
• Your settings, such as units, colour theme, timer preferences, which metrics you switched on, and whether you said yes to analytics.
• Payment, if you subscribe: whether you are in your free days, subscribed or comped, which plan you chose, the dates, and any code you used. We never see your card. The card form appears on our page, but it is served by Stripe and your details go straight to them — we cannot reach inside it. Outside the United States Stripe is also the seller and handles the tax. We keep the identifiers Stripe gives us so we know which subscription is yours. If you subscribe through Apple on an iPhone or iPad, Apple takes the payment and we never see how you paid. We keep the identifier Apple gives the subscription, which plan it is and Apple’s word for where it stands, and no Apple price, currency or App Store country. If a plan moves from one of your accounts to another, because the same Apple account restored it there, we keep a record of the move. On Apple’s US App Store we also keep the renewal sentence you were shown and when you tapped to subscribe.
• Anything you report to us: what you wrote in the feedback sheet, and a screenshot or recording if you attached one. A screenshot or recording shows what was on your screen when you made it, which can include a check-in or your cycle. You can hide parts of a screenshot before it sends. Your email address is joined on when we read the report so we can reply; it is not stored on the report itself. We add nothing from your check-ins or your cycle: there is no field it could sit in.
• Ordinary technical records: our hosting and database providers keep standard server logs, including IP address, to run and secure the service. Our database provider’s logs also note the rough location an IP address points to, down to a city and postcode. They record which account made each request and what it asked for, including the words typed into a search, and the provider keeps them for up to seven days. Our host keeps its logs for up to 30 days. When the phone app checks for an update, it sends Expo, which delivers our updates, an ID it made when it was installed, with the platform and the app version. The phone keeps that ID, and it isn’t linked to your account. Our analytics provider keeps none of this; see below. Signing in sets cookies that keep you signed in. Each sign-in also leaves a record in our database, with an IP address and the browser or device it was used from. The record stays until you sign out on that device or delete your account. Opening the demo on our website signs you in as its made-up climber. That visit’s record is cleared within two days of your last use.
• Which way you signed in, remembered on that device. So the sign-in screen can show you the door you used last, your browser or phone keeps one word — Google, say. It names a method, never you; it is never sent anywhere; and signing out removes it.

Health and body data

Body measurements and cycle tracking are the most personal things here, so they get their own rules:

• Everything is off by default, and you agree once. The first body measurement you switch on, and cycle tracking, each ask you to agree in a sentence we keep in your own record. The daily check-in only ever asks for what you switched on.
• Nothing about your cycle tells you how to train. The app does not prescribe a session, a load or a rest because of where you are in your cycle. If that ever changes it will be described here first and it will be something you switch on yourself — never on by default, never quietly, and never folded into another setting. It may show you what your own history looks like alongside your cycle, including patterns and trends in it, because that is your record rather than our advice.
• Your phone’s health app is read-only today, and only if you connect it. That is Apple Health on an iPhone and Health Connect on an Android phone. If you connect one, the app reads only the metrics you have switched on, and only while the app is open. It writes nothing back at present; if that changes it will be something you switch on, it will be described here first, and your phone will ask you separately. You can change what it shares, or revoke it entirely, in that app at any time. Connecting is per-device.
• You can delete them separately, without deleting your account, in Preferences.

Washington and Nevada law asks for a separate policy on health data. Ours is at /health-data-privacy, and it applies to everyone.

Location

When you are picking a gym or crag, the app can offer places near you. If you allow it, your device's location is read at that moment only, and your exact location never leaves your device. The app rounds it to a square a few kilometres across, asks for the places around that square, and works out on your device which of them are nearest. Then it forgets the location. Nothing about it is saved to your account, and there is no background or continuous location tracking. The request that fetches the places carries that rough square, so like every request it stays in our database provider’s logs for up to seven days. Declining costs you nothing; you can still find any place by typing its name.

The website also sees which country you are connecting from. Our web host, Vercel, works it out from your IP address and passes it to us with each page. We use it to show prices in dollars or euros, and on the subscription page to choose your checkout, because outside the United States you buy from Stripe rather than from us. It is also how we tell whether we can sell in your country. Where we cannot, the website opens no new account. It is not saved to your account. If you subscribe, the country is sent to Stripe with the checkout and kept with your subscription there.

Our analytics provider gets no location from your device or from your IP address. If you said yes to analytics, it does hold your time zone and the region of the home gym or crag you chose, such as a town and state.

Bluetooth devices

Today the app can connect to one kind of Bluetooth device: a finger-strength sensor, such as a Tindeq Progressor, to show your pull as you make it. It looks for one only when you press Connect — never when the app starts, and never in the background. It connects to the one sensor you pick and reads force from it; it sends the sensor nothing except the commands that start and stop a measurement.

Android calls the permission this needs Nearby devices, which sounds broader than it is. We declare the scan as never being used to work out where you are, and the app does not ask for location in order to use a sensor. On iPhone it is the ordinary Bluetooth permission.

A pull you save is training data, kept with your workouts and tests. It is not written to your phone's health app, it is not part of the body measurements or cycle data described above, and nothing about it reaches our analytics provider.

Analytics

We use PostHog to understand whether the app is being used and whether it is working — only if you say so. It is deliberately narrow:

• You choose. Signup ends with one question, and the box starts unticked. You can change your answer any time in Preferences, under Help improve Climb Kaizen. Off, nothing about you reaches PostHog.
• Nothing is kept on your device for it, whatever you answer. No cookie, no stored identifier. PostHog is not contacted until you say yes, except to fetch our project settings or to send a crash report, neither of which carries an identifier.
• Events are a fixed list we wrote by hand — things like "a session was logged" or "this screen was opened" — and the code refuses to build if an event carries a property that is not on the list.
• The analytics software adds a few facts of its own to each event: your device’s make and model, its operating system, the app version, your language setting, your time zone and your screen size. On the website it adds your browser, the page you were on and the site you came from.
• The content of what you write never leaves: no notes, no place names, no climb names, no cycle or body values.
• No recording of your screen, and no capture of what you click or type. A recording is made only if you press Record in the feedback sheet. One thing we do note: if you tap the same spot several times quickly, we record which screen you were on, because that usually means something is stuck.
• Once you have said yes, you are identified by your account's internal ID, never your email address. Signing out, or saying no, disconnects it.
• If the app crashes, a crash report is sent so we can fix it. It carries what went wrong in the code and which screen you were on, never anything you wrote, and no identifier unless you have said yes to analytics. Native crashes on iPhone go to Apple, under the choice you made when you set up the phone.
• Your IP address is discarded, not stored. PostHog receives it the way any server does, then drops it at the door — so no location is derived from it and none is kept.
• Events are kept for up to seven years, the period PostHog sets for every paid account. Deleting your account deletes the ones linked to you.

Tracking across websites

We run no advertising code, and nothing on Climb Kaizen follows you to other websites. Our analytics, which runs only if you say yes, sees only what you do here and keeps nothing on your device.

One provider sees more. On the subscription page, Stripe’s payment code collects details about the device you are using, to stop fraud. Stripe may use them across the businesses that use it, under its own privacy policy.

Do Not Track. Your browser may send a Do Not Track signal. There is no agreed standard for what a website should do with one, and ours does not change anything when it gets one. Nothing here tracks you across other websites, and analytics stays off until you say yes.

Global Privacy Control. This signal asks a website not to sell or share your personal information. We don’t sell or share it, so the signal has nothing to switch off.

Emails we send

Emails about your account and your plan go to everyone who has an account, because they are part of the service: confirming your address, resetting your password, receipts, letters about your subscription, and notice that our terms changed.

Now and then we may also email news about Climb Kaizen, such as something new in the app. Every one of those has an unsubscribe link. Unsubscribing stops them, and it does not stop the account emails. If the law where you live says we must ask before sending them, we ask first.

Who can see your data

Nobody else who uses Climb Kaizen can see what you log, unless you choose to share it.

If you add a real gym, crag or route that our shared list is missing, we may add it to that list for everyone. Only the place or the climb goes, as a name and its facts. Your name, your notes and your log never go with it.

If a government or court asks for your data

We wrote down, before anyone asked, what we do when a government, a court, or anyone else demands your data. The short version:

• Only valid legal process, served on us. Not a phone call, an email, or a badge. For anything you recorded, including body measurements and cycle days, only a search warrant from a court.
• The narrowest reading, and a fight where there is one. We produce only what is specifically named, ask for anything broad to be narrowed, and for health data we take legal advice and challenge the demand wherever the law gives us a way to.
• California's shield laws. We are a California business. California forbids businesses here from assisting out-of-state investigations into reproductive or gender-affirming care that is legal in California, and we treat your cycle data as covered by that.
• We tell you. Before we hand anything over, we email you a copy of the demand so you can object yourself, unless a court order forbids it. When such an order lapses, we tell you then.
• Nothing voluntary. The one exception is a genuine emergency involving danger to someone's life, where the law allows disclosure without delay. Even then we give the minimum, write down why, and tell you afterwards.
• If you are in the EU or UK, a foreign court's order alone is not a reason for us to disclose anything. The law requires an international agreement, and we hold to it.
• The strongest protection is data we never have. Keep your body measurements or your cycle on your phone, in Preferences, and there is nothing on our side to demand.

As of 21 October 2026, we have never received a demand for anyone's data. If that changes, this page will say so, unless a court order forbids it. For the full policy, write to privacy@climbkaizen.com.

What we don't do

• We never sell or rent your data, and there are no outside advertisers here.
• Nothing is ever shared back to your Apple or Google account if you sign in with one.
• Nothing you log goes to another app or site unless you choose to send it, by pressing share or by switching on sending to a service you use. It never starts on its own.
• No background location tracking.
• No selling or sharing of anything with data brokers.

Why we are allowed to use it

European data protection law lets a company use personal data only on one of a few grounds, and asks it to say which. These are ours. Legitimate interests means we have a reason of our own, we have weighed it against yours, and you can object to it (see Your data is yours, below).

Who processes it

We use a small number of providers purely to run the service, and they process data only on our instructions, except where a line below says a provider acts for itself:

• Supabase: database, authentication and file storage (hosted in the United States).
• Vercel: web hosting. Vercel also keeps usage data its service generates, which can include records of requests to our website, and uses it to run and improve its service. For that data, it acts for itself.
• Stripe: payments and subscriptions. Outside the United States Stripe is the seller of record, which means it handles the sale and the tax rather than us. For the payment itself, fraud checks and improving its own services, Stripe acts for itself, under its own privacy policy.
• PostHog: product analytics and error reporting (United States). It also holds a screen recording, if you make one in the feedback sheet.
• Expo: building the mobile app and delivering its updates.
• Apple: the App Store, test versions through TestFlight, and the subscription when you buy it on an iPhone or iPad. Apple runs these for itself, under its own privacy policy. We receive the subscription’s identifier and status, never how you paid.
• Resend: sending email, such as confirming your address, resetting your password, letters about your plan, and any news about the app. It also carries the notice we get when you send a report from the feedback sheet. Resend keeps its own record of whom we email, which it uses to run its service and catch abuse. For that record, it acts for itself.
• Google Workspace: our email inbox, so it holds anything you write to us.

Your data is stored in the United States, wherever you live. We are a US company, and our database is there too.

If you are in the EU, the UK or Switzerland, that means your data leaves Europe. Because we offer the app there, European data protection law applies to us directly, and you have the rights described below. When we pass your data to Supabase, Vercel, Stripe, PostHog, Resend, Expo or Google Workspace, at least one of two safeguards applies, and for most of them both do. One is the European Commission’s standard contractual clauses, a contract the Commission wrote for exactly this, which the provider has agreed with us. The other is the provider’s certification under the EU–US Data Privacy Framework, which the Commission recognises as protecting your data adequately. The UK and Switzerland have their own versions of each, and every one of those providers is covered by one of them. To find out which applies to whom, or for a copy, write to privacy@climbkaizen.com.

Everything your phone or browser sends to our servers travels encrypted, and our database encrypts what it stores.

On top of that, every row is locked to its owner at the database itself, so one person’s account cannot read another’s even if our own code asks it to.

Your data is yours

Your logs belong to you. In Preferences you can export everything as CSV or JSON at any time, and delete your body measurements or your cycle data on their own. You can delete your account and everything in it yourself, from Preferences, on the web or on your phone — see deleting your account. To correct anything you cannot edit in the app, email privacy@climbkaizen.com.

How long we keep it. We keep what you log until you delete your account. A session, a workout or another entry you delete on its own leaves the app at once, and is erased for good with the account. Body measurements and cycle data are different: deleting those removes them from our database straight away. An email you send us is kept for up to two years after your last message. Our email provider keeps a copy of each email we send you for up to 30 days. If you joined the waitlist, we keep your address until you unsubscribe, or for a year after the app launches if you never sign up. A report you send from the feedback sheet is kept for up to two years after you send it, or less if you ask us to delete it, at privacy@climbkaizen.com. A screen recording you attach to one is kept for 30 days.

Some of that stays when you delete your account. An email you sent us stays for its two years. A report from the feedback sheet stays for its two years too, because it may describe a fault we are still fixing. With the account gone, nothing on it points to you except the words and any picture or recording you chose to send. The copy our email provider holds of an email we sent you runs out after its 30 days. And if you subscribed, California law requires us to keep the record that you agreed to auto-renewal for three years, held apart from everything else and without your name.

You can also ask us to restrict your data, which means we keep it but stop using it for a while: while we check something you told us is wrong, for instance, or while we consider an objection.

You can object to anything the table above rests on legitimate interests. Write to privacy@climbkaizen.com and we will stop, unless we have a compelling reason that outweighs yours, in which case we will tell you what it is. Asking us to leave your logs out of any study of climbing always works, and so does unsubscribing from news or objecting to it.

Where we rely on your consent, you can take it back at any time, with the switch you used to give it or by writing to us. That stops what happens next; it does not undo what was lawful before.

If you are unhappy with how we handle your data, tell us first if you can, at privacy@climbkaizen.com. You can also complain to a data protection regulator. In the EU, that is the authority in the country where you live or work, or where you think the problem happened; the European Data Protection Board lists them. In the UK, it is the Information Commissioner’s Office. In Switzerland, it is the Federal Data Protection and Information Commissioner.

California and other US states

California’s privacy law, the CCPA, gives people who live there the rights below. We give them to everyone in the United States, whatever state you live in.

• To know what we collect about you, where it comes from, what we use it for and who we give it to. This page is the general answer. For your own data, export it in Preferences, or ask us.
• To delete it. Delete your account in Preferences, or ask us. What stays afterwards, and why, is under Your data is yours.
• To correct it. Edit it in the app, or ask us.
• To stop us selling or sharing it. We don’t sell or share anybody’s personal information, in the sense California’s law gives those words, including anyone under 16. We have not in the last 12 months either.
• To limit how we use sensitive information. Your sign-in details are sensitive information under the law, and so is anything about your health, such as body measurements, cycle days or an injury you record. We use it only in the ways the law allows without offering a way to limit it: to give you the app and the features you switch on, to keep the service secure, and to make it better.
• Not to be treated differently for using any of these rights. We offer no discount or reward in exchange for your data.

How to ask. Use the app, or write to privacy@climbkaizen.com. We reply within 10 business days to say we have your request, and answer it within 45 days. If we need longer, up to 45 days more, we tell you why. To protect your account, we act on a request that comes from the email address on the account, or once we have confirmed it is you some other way. Someone you authorize can ask for you. We will ask for your signed permission, and we may check with you. If we turn a request down, we tell you why, and you can ask us to look again by replying; we answer that within 45 days too. If you are still unhappy, you can complain to your state’s attorney general.

In the words California’s law uses, these are the kinds of personal information we have collected in the last 12 months. Each comes from you, from your device, or from a provider named on this page. We use each only for the purposes in the table above and keep it for as long as How long we keep it says. We give it only to the providers under Who processes it, and to nobody else unless the law makes us.

• Identifiers: your name, email address, account ID and IP address, the ID the phone app makes for its update checks, and the identifiers Stripe or Apple give your subscription.
• Personal information in California’s customer records law: your name, your height and wingspan, and health details you record, such as an injury.
• Characteristics of protected classifications: your birth year, and your gender if you give it.
• Commercial information: your plan, its dates, and any code you used.
• Biometric information, which the law defines to include sleep, health and exercise data that identify you: what you log, the body measurements you switch on, and force-sensor pulls.
• Internet or other electronic network activity: server logs, and analytics events if you said yes.
• Geolocation data, approximate only: the country you connect from, and the rough square described under Location. Never your exact location.
• Audio, electronic or visual information: a screenshot or screen recording you attach to a report.
• Inferences: the numbers the app works out from your log, such as V-points and personal records.
• Sensitive personal information: your sign-in details, and the health information above.

California’s law also lets you ask whether we gave your personal information to other companies for their own marketing. We don’t.

Children

Climb Kaizen is not directed at children, and our Terms of Service require you to be at least 18 to hold an account — signup asks for a birth month and year and refuses anyone younger. We do not knowingly collect information from anyone under 18. If we find that a child has given us information, we will delete it. If you believe one has, email privacy@climbkaizen.com.

On a phone, signup may also ask Apple or Google for your age range, because the law in some places requires apps to. Where such a law covers you, they share it without asking you. Elsewhere you can choose not to. If your age range puts you under 18, signup refuses you. We use it for nothing else, and we don’t keep it or send it anywhere.

Who holds your data, and how to reach us

Climb Kaizen LLC, a California limited liability company, at 440 N Barranca Ave #9839, Covina, CA 91723. That is the company deciding what happens to your data, and "we" throughout this page means it.

If you are in the EU, the European Economic Area, the UK or Switzerland, our representative there is Data Protection Representative Limited (trading as DataRep). You can raise anything about your data with them instead of with us, from your own country: email datarequest@datarep.com with “Climb Kaizen LLC” in the subject line, use their form, or write to DataRep at the address for your country below. Address a letter to DataRep, not to us, or it may not reach them. For anything about the app itself, write to us at privacy@climbkaizen.com.

If the company changes. Climb Kaizen is a personal project, and we don't plan to sell it. But a company sometimes has to change shape, and ours may move to another state one day. If a different company ever takes over the service, your account and your data go with it. Whoever takes over must keep the promises on this page, and we will email you before your data moves, with time to export it or delete your account. That is the service moving with its company, not your data being sold.

If this policy changes in a way that affects you, we will update the date above and tell you before the change takes effect, by email or in the app. A new feature that you have to switch on is described here when it arrives, and until you switch it on it changes nothing about your data. Questions, requests, or concerns: privacy@climbkaizen.com.