Privacy

Plain language, and specific. Last updated August 2026.

Limber measures your body. That is about as personal as data gets, so the design answer is to keep it where you put it: your readings, your sessions and your history stay on your phone. We do not have a copy and we cannot get one. Below is the whole of what does leave the app, and who receives it.

There is no account

Limber does not ask you to sign up, and there is nothing to sign in to. You open the app and it works. Because there is no account, there is no server-side profile of you, no email address on file, and no way for us to look up your readings — they are in a database inside the app, on your device.

A sign-in screen exists in Settings for a sync feature that is not built yet. It is not connected to a live service, so it cannot create an account today. If that ever changes, this page changes with it, in the same release.

What stays on your device

• Your test readings — every value you record, with the side (left or right) and the date you recorded it.
• Your Range Score, your datum and your history — all computed on the phone, from those readings.
• Your sessions — what you did, for how long, and when.
• Your settings — reminder times, session length, sound and haptics.

Delete the app and all of it goes with it. See deleting your data.

Apple Health and Health Connect

Health integration is off until you turn it on, and the permission is asked for at the moment you turn it on, not at launch. When it is on, Limber writes your finished sessions to Apple Health (or Health Connect on Android) as workouts.

Limber never reads your health data, and nothing written to Health is ever sent to us or to anyone else — it goes from the app into the operating system's own store and stops there. Turn the toggle off, or revoke the permission in the Health app, and the writing stops.

What the app does send, and to whom

Three third parties, and this is the complete list. None of them receives a reading, a score, a session or anything about your body.

• Firebase Crashlytics (Google) — when the app crashes it sends a diagnostic report: the stack trace, your device model, OS version, app version, and an app-generated identifier for the installation. We use it to find and fix the crash.
• Firebase Analytics (Google) — records that a purchase or a restore happened, alongside the automatic app events Google's SDK collects (an app open, a session, the app version, the device and country). All of it is tied to that same app-installation identifier, not to your name — there is no name to tie it to.
• Firebase Cloud Messaging (Google) — if you allow notifications, a device token is generated so a message could be delivered. Your daily reminder is not one of these: reminders are scheduled by the app on your own phone and need no server at all.
• RevenueCat — handles Limber Pro purchases and tells the app whether Pro is active. It receives an app-generated user id, the purchase and renewal state Apple or Google reports, and the Firebase app-instance id, so a purchase can be matched to the installation that made it. It never sees your card: Apple and Google take the payment, and we never receive your payment details.

The app-instance id is a random identifier Firebase generates for an installation. It is not your device's advertising id, it is not shared for advertising, and reinstalling the app produces a new one.

What we do not do

• We do not sell your data. There is no buyer, because there is nothing to sell.
• We do not run ads, and nothing collected is used to target advertising or shared with an ad network.
• We do not track you across other companies' apps or websites.
• There is no camera in this app, no photo assessment and no video upload.
• There is no AI in this app. Your routine is chosen by deterministic rules running on your phone, and the app will show you the reasons.

What this website measures

Nothing. This site loads no analytics tag, no advertising script, no social pixel and no third-party font — the type, the styles and the images all come off our own server. There are no cookies to consent to, because the site sets none. Your browser will make one request per file on the page and nothing else.

The site is built so that an analytics tag could be switched on from configuration. If it ever is, this paragraph gets rewritten in the same commit, saying exactly what it records — not left to be discovered in a network tab.

In app-store terms

Limber collects no data linked to your identity, because it never learns your identity. What is collected is tied to the installation rather than to you: crash diagnostics, product-interaction and app-usage counts, purchase state, and identifiers (the app-instance id, an app-generated user id, and a push token if you allow notifications). Your health and fitness data is not collected — it stays on the device.

How long it is kept

Your readings live on your phone for as long as you keep the app. Crash reports and usage counts are retained by Firebase on its own rolling schedule — months, not forever — and are not tied to your name. Purchase records are kept as long as the law requires records of a sale to be kept.

Children

Limber is intended for adults. It is not directed at young children, and it asks for no information that would identify one.

Your rights

You can delete everything Limber holds about you at any time, in one step, without asking us: see deleting your data. Because we hold no account, we cannot look up, export or delete anything on your behalf — there is nothing at our end to look up. For anything else, including a question about the third parties above, write to hello@musthaveappscorp.com.

Changes

If this policy changes in a way that matters, we will update this page and the date above.

TODO(launch) Before this page goes live it needs three facts only the publisher can supply: the domain it is served from, the company's registration number and registered address, and confirmation that the app's crash and purchase reporting has been pointed at Limber's own Firebase project rather than the one it inherited from the codebase it was built on. Nothing above has been invented to fill those gaps.