What CrimpDex does — and doesn't — do with your data

Data we collect

CrimpDex is a training logbook for a Tindeq Progressor finger-strength sensor. The data you enter or capture through it — peak force and critical force readings, bodyweight, training session logs, and app preferences such as your default edge size and unit system — is written to a local database stored only on your device.

We do not collect this data. "Collect," in the sense that matters for a privacy policy, means data leaving your device — and nothing here does. CrimpDex has no server, no account system, and no INTERNET permission declared anywhere in the app, which means Android itself will not allow it to open a network connection under any circumstance.

Bluetooth and location permissions

CrimpDex requests BLUETOOTH_SCAN and BLUETOOTH_CONNECT (and, on Android versions older than 12, BLUETOOTH, BLUETOOTH_ADMIN, and ACCESS_FINE_LOCATION) for exactly one purpose: finding and connecting to your Tindeq Progressor over Bluetooth Low Energy so it can read live force measurements.

Android requires apps to hold a location permission before they are allowed to scan for Bluetooth LE devices on older OS versions, purely because BLE scan results can theoretically reveal nearby beacons' locations. CrimpDex does not read, store, or use your device's location in any way — the permission is a side effect of Android's Bluetooth API, not a feature we use. On Android 12 and later, CrimpDex requests BLUETOOTH_SCAN with the neverForLocation flag, which tells Android explicitly that this app does not use Bluetooth scanning to derive location.

Where your data lives

All of it — every force reading, every session, every setting — lives in a single local database file inside CrimpDex's private app storage on your phone. CrimpDex itself never transmits that file anywhere. The app declares no internet permission at all, so Android will not let it open a network connection under any circumstance. If you uninstall CrimpDex, the database is deleted along with it. We have no copy, because we never received one.

One exception is worth stating plainly, because it is Android doing it rather than CrimpDex. Android's built-in Auto Backup is left switched on for this app, so your phone may copy CrimpDex's database into your own Google Drive, encrypted with your device passcode. That copy belongs to your Google account, not to us — we cannot see it, ask for it, or restore from it. It is there so your training history survives a lost or replaced phone. If you would rather it did not exist, you can turn backup off for CrimpDex, or for every app, under Settings › Google › Backup on your device.

Paying for CrimpDex

CrimpDex is free to use for seven days. After that it needs unlocking once, with a single payment and no subscription. An unlock code, if you were given one, is checked on your own phone and involves no one else.

Payment is handled entirely by Google Play. CrimpDex never sees or stores your card details, your name, or your email address, and it still has no internet permission of its own — the Play Store app on your phone does the talking. Google gives us an order record for the sale, which is the same information any Play developer receives, and we use it only to answer questions about a purchase or issue a refund. Google’s handling of that payment is covered by their own privacy policy, not this one.

Third parties

CrimpDex includes no analytics libraries, no advertising networks, no crash-reporting services, and no other third-party SDKs that collect or transmit data. The only external library the app depends on for its Bluetooth functionality (Nordic Semiconductor's Android BLE library) runs entirely on your device and has no network access of its own.

Children's privacy

CrimpDex is not directed at children and is not designed to appeal to them. Since the app collects no data of any kind off-device, there is no data of any user, child or otherwise, for us to handle.

Changes to this policy

If CrimpDex ever changes in a way that affects this policy — for instance, if a future version added cloud sync — this page will be updated first, with a new effective date above, before that change ships.