Privacy Policy Health Sync

Data protection: Health Sync does not store your health data on the phone or on a server. It transfers the data during the sync operation. The sync process is completely managed on the phone, where Health Sync uses a background service process to sync the data. Health Sync shows a notification when the sync is running. Health Sync maintains a sync log with technical information about the sync operation. Personal data is not part of the sync log. The log only contains information about the sync process of the last two days. Older log data is deleted automatically. The log data contains some health data information that has been synced, but no identifying information such as personal data or location data. The log data is stored within the app storage space on your phone and will be removed when you uninstall the app. The data can't be accessed by other apps unless your phone has been rooted.

For some connected apps, a secure cloud server from appyhapps.nl is used for the synchronization logistics: the server receives messages when new data is available from the connected app (for example Garmin Connect). The server will inform Health Sync on your phone that new data is available and Health Sync will retrieve and process the data on the phone. The server does not receive or process your health and fitness data and does not have the authorization data to access your account.

 

Health Sync uses sensitive permissions on your phone to collect information. The following sensitive permissions may be required depending on the sync options you choose in the app:

 

Physical activity: This permission is required when syncing steps and/or activity data with Google Fit. Google Fit only allows to read or write steps and activity data when this permission has been given. Health Sync doesn't use this permission for tracking activity or steps data itself.

 

Google Fit permissions: Health Sync needs permission to access the Google Fit data when you sync with Google Fit. Health Sync only asks for the permissions it really needs. Without these permissions, the data can't be synced. Read permissions are required for reading data from Google Fit. Write permissions are required for writing data to Google Fit. When you sync to Google Fit, Health Sync will ask some read permissions also. The read permissions are needed when writing data to Google Fit, because Health Sync will check if there is other data in Google Fit that could cause sync conflicts.

Access to your Google profile is required to show the Google account that is used for Google Fit in the Google Fit Authorization page in Health Sync. Only the account name is stored. Other profile information is not used or stored. Your Google account name is stored in the private storage space of the app and not on an external server.

The use of information received from Google Fit will adhere to the Google Fit Developer and User Data Policy, including the Limited Use requirements.

 

Samsung Health permissions: Health Sync needs permission to access the Samsung Health data when you sync with Samsung Health. Health Sync only asks for the permissions it really needs. Without these permissions, the data can't be synced.

 

Huawei Health permissions: Health Sync needs permission to access the Huawei Health data when you sync with Huawei Health. Health Sync only asks for the permissions it really needs. Without these permissions, the data can't be synced. Health Sync asks for the country where you live, because the Huawei Health integration doesn't work in all countries. The country is stored with the private data of Health Sync and is never shared with others.

 

Fitbit permissions: Health Sync needs permission to access your Fitbit data when you sync with Fitbit. Without these permissions, the data can't be synced.

 

Polar permissions: Health Sync needs permission to access your Polar data when you sync with Polar. Without these permissions, the data can't be synced.

 

Garmin permissions: Health Sync needs permission to access your Garmin Connect data when you sync with Garmin. Without these permissions, the data can't be synced.

 

Withings permissions: Health Sync needs permission to access your Withings (Health Mate) health data when you sync with Withings. Without these permissions, the data can't be synced.

 

Suunto permissions: Health Sync needs permission to access your Suunto health data when you sync with Suunto. Without these permissions, the data can't be synced.

 

Oura permissions: Health Sync needs permission to access your Oura health data when you sync with Oura. Without these permissions, the data can't be synced.

 

Strava permissions: Health Sync needs permission to store activity and weight data to Strava when you sync with Strava. Without these permissions, the data can't be synced.

 

InBody permissions: Health Sync needs permission to access your InBody health data when you sync with InBody. Without these permissions, the data can't be synced.
Integration with InBody varies by country. This is why Health Sync asks for your country when you connect Health Sync with InBody. The country is stored with the private data of Health Sync and is never shared with others.

 

Smashrun permissions: Health Sync needs permissions to write weight and activity data to your Smashrun account when you sync with Smashrun. Without these permissions, the data can't be synced.

 

Runalyze permissions: Health Sync needs permission to write data to your Runalyze account when you sync with Runalyze. Without these permissions, the data can't be synced.

 

DiabetesM permissions: Health Sync needs permissions to access your DiabetesM account when you sync to or from DiabetesM. Without these permissions, the data can't be synced.

 

Authorization: Health Sync does not receive the account password of the accounts you use for Google Fit, Samsung Health, Huawei Health, Strava, Fitbit, InBody, Polar, Withings, Suunto, Oura, Smashrun, Runalyze, DiabetesM or Garmin. Health Sync uses the secure mechanisms of the fitness apps and platforms to get authorization for the connection. When you need to give your account credentials, you only do this on a secure site of the fitness app/platform. Health Sync does not have access to these authorization pages. This safe authorization mechanism is known as OAuth 1 or OAuth 2.

 

Payment: Health Sync only uses information from your account for the synchronization of the health data. When you purchase Health Sync unlimited usage or subscribe to Health Sync, the financial operation is handled by Google Play Store when you downloaded Health Sync from the Google Play Store. When you installed Health Sync from the Huawei AppGallery, the payment is handled by Huawei. Health Sync does not receive information from Google or from Huawei about your bank account, credit card, or other payment method you may use.

 

Log data protection: When you choose the option in the Help Center to 'Report another problem', the log data is sent to the app developer together with the email address you provided when sending the report. This email address and the log data is only used for support reasons and can only be accessed by the app developer. The log data is sent to a secure server that can't be accessed by others than the app developer, using a secure connection between Health Sync on your phone and the appyhapps.nl secure server (in the Google Cloud). The log data will be analyzed and then deleted, within two weeks after you sent the information. Log data and your email address will never be given to others or published outside the secure systems of appyhapps.nl.

 

Anonymous crash and log data: When you use the app and with some crashes, anonymous usage information and crash data will be sent to a Google server. Only appyhapps.nl has access to this anonymous usage and crash data. This data doesn't contain any information about personal data or about the synced data.

 

If you have questions about the Health Sync privacy policy, you can use the contact page on this site.