Privacy policy

What the app reads and writes

Apple Health data, only for the types you switch on and only after you allow them in the Health access sheet. With Backfill, also older records for the range you pick. When you delete a record in Apple Health, the next sync reports its uuid so your server can remove it too. The app writes nothing: it only asks Apple Health for read access.

Permissions

Apple Health, read only, for the types you switch on. Camera, only while the pairing scanner is open: frames are decoded on the iPhone and are never stored or sent. Local Network, to reach a webhook server or MQTT broker on your home network. Notifications, for failed syncs and payloads that were dropped; they are shown on the iPhone and sent nowhere.

Where it goes

Only to the destinations you enter or pair. The app contacts no other server. Besides the types you switch on, each payload carries the app version, and each record carries the name of the app or device that wrote it. On an iPhone that name often includes your own name.

MQTT is unencrypted unless you switch on TLS. States are published retained, so the broker keeps the latest value of each sensor even after you switch MQTT off in the app: clear the topics on the broker if you stop using it.

What the developer can receive

The app itself sends nothing to the developer. Apple shares some things with the developer through App Store Connect, under Apple's privacy policy: in the TestFlight beta, crash reports and any feedback you send through TestFlight with the screenshot you attach; once the app is on the App Store, sales and usage reports. None of this carries your health data, your settings or the addresses you send to.

What stays on the iPhone

Your settings, with secrets in the iOS Keychain. Sync progress, so a sync sends only what is new; a backfill, or a delivery that iOS cut off, can send a record again with the same uuid. A log of the last 100 deliveries, which you can clear.

Payloads that could not be delivered yet, at most 700: when the queue is full, the oldest one makes way. Otherwise each one stays until it arrives, or until it is older than 7 days and a server answers it with an error. Without a connection, nothing is dropped for its age. With MQTT on, the latest value of each sensor; switching MQTT off removes them at the next sync. With a data resolution set, the samples of a window that is still filling.

Your settings and the sync progress are part of your iPhone backup, like other app data. The log, the undelivered payloads, the sensor values and the held samples are not. Deleting the app removes all of it, but iOS can keep the secrets in the Keychain: clear them in the app first if you want them gone. A settings export without secrets still contains your webhook URLs, which can work as a password, so share it with care.

Your control

Everything is opt-in and reversible: which types are read, where they go and how often. Turning off access in the Health app stops the matching reads immediately. The developer holds no copy of your health data or settings, so there is nothing of that to request or delete on the developer's side. For crash reports or feedback that Apple passed on, email the address below.

Changes, controller and contact

A change to this policy is published on this page with a new date, and in the app's changelog.

Owen Vogelaar, trading as oVog Enterprise, registered with the Dutch Chamber of Commerce (KvK) under number 81085583, is responsible for this app and this policy. Email owen282000@hotmail.com. You can also ask privacy questions in Discussions.