-
-
Notifications
You must be signed in to change notification settings - Fork 20
Privacy Policy
openScale sync is built as an Open Source app, licensed under the GNU General Public License v3 or later. This SERVICE is provided by olie.xdev at no cost and is intended for use as is.
This page informs you about the collection, use, and disclosure of Personal Information if you decide to use this Service.
If you choose to use this Service, then you agree to the handling of information described in this policy. The purpose of any data handling within the app is to enable its core functionality on your device and to synchronize data with the services you choose to connect, including Android's Health Connect platform.
openScale sync is a companion app to the separate openScale app, which records body measurements from a bluetooth scale. openScale sync keeps no measurement database of its own. It reads measurements from openScale on your device and forwards them to the services you enable, and — where you enable it — it brings measurements from those services back into openScale.
I, the developer (olie.xdev), do not collect, receive, or have access to any of your health data, nor to any credentials you enter, nor to the data you read from or write to Health Connect. There is no backend server operated by me, no user account, and no telemetry.
The app stores the following on your device only:
- Your settings, including the addresses, user names, tokens and passwords for the services you configure. These are stored in the app's private storage and are used solely to authenticate against the service you entered them for.
- A synchronization ledger per service, recording for each already-exported measurement its identifier, timestamp, the openScale user it belongs to, and a checksum. It contains no measurement values and exists so the app can tell what still needs to be sent, updated or deleted.
- A retry queue per service, holding measurements that could not be delivered — for example because the network was down — until the next successful attempt, after which they are removed.
If you grant the corresponding permissions, openScale sync exchanges data with Android's Health Connect platform on your device.
Data written to Health Connect (the app's main purpose, so that other health apps can use your measurements): weight, body fat, body water mass, bone mass, lean body mass and basal metabolic rate, each with the date and time of the measurement.
Data read from Health Connect (optional, off by default): weight, body fat, body water mass, bone mass and lean body mass, each with the date and time of the measurement. Reading exists solely to import weigh-ins that other apps recorded, so that a measurement taken elsewhere is not missing from your openScale history. Records written by openScale sync itself are recognised and skipped, so nothing is imported twice.
Reading is tied to a setting you control: each service has a synchronization direction, and for Health Connect the default is Export, under which the app requests no read permissions at all. Read access is requested only after you set the direction to Import or Both. Basal metabolic rate is written but never read, because openScale derives it itself.
Health Connect data is used exclusively to provide the synchronization features described above. It is never used for advertising or marketing, never sold or transferred to data brokers, information resellers or any other third party, and never used to determine credit-worthiness or for lending purposes. It is not used for analytics, and it does not leave your device except to the services you yourself enable and configure.
You can review and revoke the app's Health Connect permissions at any time in the Health Connect settings on your device. Revoking them stops the corresponding synchronization immediately. Data that was already written to Health Connect is managed by Health Connect and can be deleted there.
Data stored in Health Connect is managed by Google and subject to its own privacy controls. For more information, please review the Google Privacy Policy and Google's Health Connect documentation.
When you enable and configure one of the other supported services, the app transmits the measurements you authorize to that service. Which data is transmitted depends on the service and your configuration. The supported services are:
- wger — see the wger Terms of Service.
- Endurain — a self-hosted fitness tracking server; the privacy terms are those of the instance you connect to.
- InfluxDB — a time-series database; the privacy terms are those of the instance you connect to.
- MQTT broker — you choose the broker and are responsible for its privacy policy. This includes brokers you host yourself.
- Generic Webhook — an HTTP endpoint of your choosing; the privacy terms are those of that endpoint.
Most of these are typically self-hosted, in which case the data stays entirely under your own control.
It is your responsibility to review the privacy policies of Health Connect and of any other third-party service you choose to connect with openScale sync. I have no control over and assume no responsibility for the content, privacy policies, or practices of any third-party service.
The app contains no advertising, no analytics, no tracking and no crash-reporting service. It does not include the Google Play Services, Firebase or any comparable library. If you obtained the app through the Google Play Store, the Store itself handles distribution and updates independently of the app; see the Google Play Services Privacy Policy.
The app can optionally write a diagnostic log to your device. This is disabled by default and only takes effect if you switch it on. The log is stored in the app's private storage and is never transmitted automatically. It may contain the device model, the operating system version, the app's configuration, timestamps and error stack traces; credentials, tokens and comparable secrets are redacted before they are written. You may choose to share the log file with me for troubleshooting, which is entirely voluntary and always initiated by you. Switching logging off or uninstalling the app removes it.
All data the app holds lives in its private storage on your device. Uninstalling openScale sync deletes its settings, the synchronization ledger, the retry queue and any log file. This does not delete measurements that were previously written to Health Connect or to another service — those are removed in Health Connect or in the respective service. You can also clear individual services from within the app by disabling them.
I value your trust in providing your Personal Information to the app for local storage and for transmission to services of your choice, including Health Connect. Connections to remote services use transport encryption where the service supports it, and the credentials you enter remain in the app's private storage. Remember that no method of transmission over the internet, and no method of electronic storage, is 100% secure — absolute security cannot be guaranteed. As an open-source project, the code is available for public scrutiny, which helps identify and address security vulnerabilities. You are also responsible for securing the third-party services you connect to and for managing permissions within Health Connect.
Being an open-source application under the GPL, the source code for openScale sync is publicly available at github.com/oliexdev/openScale-sync. This allows for full transparency in how your data is handled within the application itself — including every statement made on this page.
This Service is not directed at children under the age of 13, and I do not knowingly collect any information from anyone, including children.
I may update this Privacy Policy from time to time. You are advised to review this page periodically for any changes. I will notify you of any changes by posting the new Privacy Policy on this page and potentially through the app's release notes or project repository.
This policy is effective as of 12th August 2026
If you have any questions or suggestions about this Privacy Policy, or the app's data handling practices, do not hesitate to contact me at olie.xdev@googlemail.com, or by opening an issue on the project's source code repository.