Jump Timer — Privacy Policy

Lucid Studios LLC · Effective 25 July 2026

The short version

Every line here is a plain-English restatement of a section below — nothing extra, nothing softened.

Who this is about

Jump Timer is an interval timer for jump-rope workouts, published for iPhone by Lucid Studios LLC. This policy covers the Jump Timer app and its two pages on this site — this policy and the support page. Questions go to developer@lucidstudios.io.

Jump Timer has no account and no sign-in. We do not know who you are.

What Jump Timer keeps on your iPhone

Everything the app records lives in its own storage on your iPhone — one local database plus the app's own files. There is no CloudKit or iCloud sync, no copy on a Jump Timer server, and no backup we can read. Rather than list every field, here is the whole picture by category:

Your streak is not kept as its own record — it is worked out from your finished sessions each time it is shown. Its current value is copied into the widget snapshot above, so the widget can draw it while the app is closed.

Apple Health

If you grant permission, Jump Timer reads exactly three things from Apple Health: your body mass, your date of birth, and your biological sex. Those raw values are never stored by Jump Timer — they are read when needed and kept only in memory.

Numbers worked out from them are stored. Your calorie estimate for a finished workout (which prefers your Health values over anything you typed by hand) is saved with that session on this device, written back to Apple Health, and — if you have linked Strava — sent to Strava with the workout. Your age from Health also seeds your heart-rate zone boundaries, which are saved in the app's preferences on this device.

If you grant permission, Jump Timer writes exactly three things to Apple Health: the workout itself, the active energy burned, and your heart rate. Health data belongs to Apple Health, not to Jump Timer — you manage or delete it in the Health app, and you can withdraw either permission there at any time.

Bluetooth heart-rate monitors

Jump Timer connects to standard Bluetooth heart-rate straps and uses the heart-rate service only (Bluetooth service 0x180D, characteristic 0x2A37). It reads your heart rate. While you are choosing a strap it also reads the name the strap broadcasts and its Bluetooth identifier, so you can recognise it in the list and it can reconnect later — nothing else about the strap, and nothing at all about you.

The paired strap's identifier is saved on your iPhone so it can reconnect automatically. It never leaves the device.

Strava (only if you link it)

Linking Strava is optional and off until you do it. Nothing is sent to Strava unless you link.

What Jump Timer sends to Strava

An upload contains your workout: start time, duration, calories, and the heart-rate trail recorded during the run. It also carries the workout title you typed — that is free text you control, so treat it as public to your Strava audience — and an identifier for the session, used so the same workout is never uploaded twice. No location or GPS data is sent, because Jump Timer never collects any.

What Jump Timer reads from Strava

Nothing. Jump Timer only writes workouts to your Strava account; it never reads your activities, your profile, or your friends. The permission Jump Timer requests during linking is literally activity:read_all,activity:write, and we name that read half openly rather than hide it. It is there because Strava requires it, not because the app wants your data: after the upload, Jump Timer makes one more call to set the activity's type to a jump-rope workout, and Strava rejects that call with a 404 unless the same token may also read your activities. So the app must ask for read access — and still reads nothing. No code in Jump Timer fetches your activities, your profile, or your friends.

How your Strava data is used

Your Strava data is never sold, and it is never used for advertising. It is used solely to put your finished workout in your own Strava account.

Feedback you send from the app

Settings › Send Feedback posts exactly six things: which app it is, whether it is a bug or a feature request, your description, an optional reply email address, the app version, and your iOS version. No advertising identifier, no device identifier, no device model, no language or region.

That post passes straight through our small relay service and becomes an issue in our private GitHub repository for Jump Timer. GitHub stores and holds the issue on our behalf — so your description and, if you gave one, your email address rest with GitHub. The relay keeps nothing itself.

A reply email address is optional; leave it blank and we simply have no way to write back. When you do give one, we use it to reply about your report and nothing else.

The relay writes operational logs that are deleted after 14 days. Those logs contain no feedback content — not your description, not your email address — and automated tests enforce exactly that on every build. They carry no IP address either; nothing in the relay ever writes one to a log, though that rests on how the relay is built rather than on a test.

We never store your IP address. To stop abuse of the feedback endpoint, a one-way, salted hash of it is counted for a few minutes, then deleted. It is not linked to your feedback and cannot be reversed to an address.

Notifications, widgets, and the Live Activity

The streak reminder is a local notification your iPhone schedules for itself, and the home-screen widgets read a snapshot file on the device. The Live Activity is different: it is drawn by the running app itself, which hands the current segment straight to iOS, so it never touches that file. None of this involves a push service, and none of it sends anything off your iPhone.

What Jump Timer never does

Deleting your data

Deleting the app removes everything Jump Timer stored on the device: your workouts and sessions, your preferences, the paired strap's identifier, any queued uploads, the widget snapshot, and the cached voice audio all go with it. The Strava link goes too, with one detail worth stating plainly — iOS leaves Keychain items behind when an app is deleted, so Jump Timer clears its own stored Strava tokens on the first launch after any reinstall. A reinstalled Jump Timer is never already linked.

Two things deliberately survive, because they are not ours to delete. Jump Timer's authorization in your Strava account stays live until you revoke it in Strava's own settings under "My Apps". Activities already uploaded remain in your Strava account until you delete them in Strava.

Workouts Jump Timer wrote to Apple Health belong to Health, not to Jump Timer — manage or delete them in the Health app.

Feedback you already sent lives in our private GitHub issue tracker. Ask us at developer@lucidstudios.io and we will delete the issue, including any reply address you gave.

Changes to this policy

If the app's data practices change, this page changes with them and the effective date at the top moves. The current version is always the one you are reading.

Contact

Lucid Studios LLC — developer@lucidstudios.io