Not some of it. None of it. This page explains what that means in practice, and it is short because there is very little to say.
Everything you create in MeloTimer is written to storage on your own device and never leaves it:
On iPhone and iPad, the app and its widget share this data through a private app group on the device, so the widget and the Lock Screen Live Activity can show the routine that is running. On Android, the home-screen widget and the notification of a running routine read it from the app's own storage. Either way, that sharing happens entirely on your device.
Nothing. We have no way to see your routines, your usage or your device. There is no account to create, nothing to sign in to, and no telemetry of any kind. We could not identify a MeloTimer user if we wanted to. The one request the app does make is the version check described in the next section, and it tells us nothing about you either.
MeloTimer makes one kind of network request, and this is it. When the app starts — and again when you come back to it after a while — it fetches a small file from melotimer.com/version.json. The file says which version is current and which is the oldest one still supported. Nothing else. The Android app makes the same request, to the same file.
The request is a plain download of a public file. It carries no account, no identifier, no name, and nothing you have made in the app: not a routine, not a cue, not a single run. There is nothing in it that could be traced back to you, because the app has nothing of that kind to send.
As with any request to any website, our server sees the address your device connects from and the version of the app asking. We do not log it, keep it or look at it, and it is never combined with anything else — there is nothing else for it to be combined with.
If the answer says a newer version exists, the app offers you an update once, and you are free to say no. If it says the installed version is older than we still support, the app asks you to update before carrying on. That exists so a version with a serious fault can be taken out of use rather than left running.
If the request fails — you are offline, the site is down, the answer is nonsense — the app carries on exactly as before. A fault on our side can never leave MeloTimer unusable, and this check is the only thing on our side that can reach the app at all: it cannot switch features on or off, change what the app does, or ask it for anything.
If you ask a step to run a HomeKit scene, the app needs your permission to see the scenes in your home. That permission is granted by you, handled by Apple's HomeKit framework, and used only to run the scene you picked, at the moment you asked for it. Your home, device and scene data stays on your device and with Apple. It is never sent to us: the only request the app makes is the version check described above, and none of this travels with it.
You can withdraw this permission at any time in Settings → Privacy & Security → HomeKit. The rest of the app carries on working; only Home scene cues stop.
HomeKit is on iPhone and iPad only. The Android app has no Home scene cues and asks for no such permission.
On iPhone and iPad, cue sounds are played by the app itself, and by local notifications when your phone is locked. Local notifications are scheduled on your device by your device. On Android, the app plays cue sounds itself for as long as a routine runs, and shows a notification with the current step while it does. No notification is sent from a server, so nothing about them reaches us or anyone else.
If you back up your iPhone or iPad — to iCloud or to a computer — your routines are included in that backup, like any other app's data. That backup belongs to you and is governed by Apple's terms, not ours. MeloTimer itself does not sync your routines anywhere, and there is no iCloud sync between your devices.
On Android, if you use Android's backup, your routines are included in it and stored in your Google account, like any other app's data. That backup belongs to you and is governed by Google's terms, not ours.
MeloTimer is made for families, and a child may well be the person watching the screen. Because the app collects nothing from anyone, it collects nothing from children either. There is no profile, no identifier and no record of a child's use to request, correct or delete — none is ever created.
Deleting a routine in the app removes it. Deleting the app removes everything it stored, including your run history. Because none of it was ever sent anywhere, that is the whole of it — there is no copy for us to delete, and no request you need to make.
If a future version of MeloTimer ever does something that touches your data differently, this page will be updated before that version ships, and the date at the top will change. An app update will never quietly start collecting something this page says it does not.
Questions about this policy, or about the app: milczi@gmail.com.