Transparency & control
Privacy Policy
In brief: My Health Bridge is a single-user, personal health synchronization project. Its local application collects body-weight measurements from a Bluetooth scale, stores them on a Raspberry Pi, and—after the account owner authorizes it—sends weight measurements to Google Health. This informational website does not receive health measurements or OAuth credentials.
1. Who operates this project
My Health Bridge is a privately operated, personal-use application, rather than a public health service. It exists to help the owner keep personal body-weight measurements synchronized.
2. Information handled
The local application handles body-weight measurements and their timestamps from a Bluetooth-enabled scale. The local database may also store ingestion and synchronization status information needed to prevent missed or duplicate uploads. To connect to Google Health, the application uses OAuth authorization credentials granted by the Google account owner.
Only health-data permissions needed for the weight synchronization are intended to be requested. The application is not designed to collect Google emails, contacts, advertising profiles, or unrelated Google account information.
3. How the information is used
- To record the owner's weight measurements in a local SQLite database on the owner's Raspberry Pi.
- To send selected weight measurement values and timestamps to the owner's authorized Google Health account using the Google Health API.
- To track synchronization status, troubleshoot errors, and avoid duplicate uploads.
No personal health information is used for advertising, profiling for marketing, lending, resale, or unrelated purposes.
4. Where information is stored and shared
The local weight database and OAuth configuration are maintained on a private Raspberry Pi. Weight data is transmitted to Google Health only when the owner has authorized the connection. Google then processes the uploaded records according to its own applicable privacy terms. There is no sale of data, advertising-data sharing, or transmission of health records to this public website.
The public website is static and does not include health-data forms, web analytics, behavioral tracking scripts, or advertising cookies. Standard hosting infrastructure may process ordinary request information such as IP addresses in accordance with the hosting provider's practices.
5. Security
Access to the Raspberry Pi, local database, and OAuth credentials is controlled by the device owner. Connections to the Google Health API use HTTPS and OAuth authorization. The private dashboard and underlying database are not intentionally exposed by this website. As with any personal system, the owner is responsible for keeping software and access controls up to date.
6. Retention and deletion
Local measurements are retained until the owner removes them from the local database or retires the project. Disconnecting or revoking Google authorization stops further authorized synchronization but does not automatically delete measurements already in the local database or records already sent to Google. The owner can separately delete local records and manage data stored in their Google account using Google's available controls.
7. Google API data use
My Health Bridge will use information received from the Google Health API in accordance with the Google Health API Developer and User Data Policy, including its Limited Use requirements. Google access is used for the health-data synchronization functionality described above, not for advertising or resale.
8. Changes to this policy
This policy may be updated if the application's features or data-handling practices change. The effective date at the top of this page identifies the current version. Any additional Google user-data access would require appropriate disclosure and authorization.
9. Contact
This is a single-user personal project. For privacy or data-management questions, contact the application owner using the support email displayed on the Google OAuth consent screen for My Health Bridge.
This policy describes the intended configuration of the personal integration. The operator must ensure the live implementation matches these statements before publishing.