Data protection: FitProphet does not store your health data on the phone or on a server. It transfers the data during the analysis operation. The analysis process is completely managed on the phone, where FitProphet uses a background service process to sync and analyze the data. FitProphet maintains a sync log with 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 health data in the sync log is encrypted and can't be read by other apps. The sync log data is stored within the app storage space on your phone and will be removed when you uninstall the app.

For some connected apps, a secure cloud server from fitprohpet.uc.r.appspot.com 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 FitProphet on your phone that new data is available, and FitProphet 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.

FitProphet could require the 'physical activity’ app permission. This permission is required when syncing steps and/or activity data with Google Fit. Google Fit only allows reading or writing steps and activity data when this permission has been given. FitProphet doesn't use this permission for tracking activity or step data itself.

For health and fitness apps that are involved with the sync you need to authorize FitProphet. For each app that you can sync with, we describe the privacy aspects:

Google Fit permissions: FitProphet needs permission to access the Google Fit data when you sync with Google Fit. FitProphet 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, FitProphet will ask some read permissions also. The read permissions are needed when writing data to Google Fit, because FitProphet 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 FitProphet. 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: FitProphet needs permission to access the Samsung Health data when you sync with Samsung Health. FitProphet only asks for the permissions it really needs. Without these permissions, the data can't be synced.

Huawei Health permissions: FitProphet needs permission to access the Huawei Health data when you sync with Huawei Health. FitProphet only asks for the permissions it really needs. Without these permissions, the data can't be synced. FitProphet 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 FitProphet and is never shared with others.

Health Connect permissions: FitProphet needs permission to read or write data to Health Connect on your phone when you want to sync health or fitness data with Health Connect. FitProphet only asks for the permissions it really needs. When writing data to Health Connect, FitProphet requires both a read and write permission because it needs to read data in order to know if data was synced already or needs to be updated in Health Connect.

The use of information received from Health Connect will adhere to the Health Connect Permissions Policy, including the Limited Use requirements.

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

The use of information received from Fitbit APIs and/or Developer Tools will adhere to the Fitbit Platform Developer and User Data Policy, including the Limited Use requirements.

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

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

Withings permissions: FitProphet 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: FitProphet needs permission to access your Suunto health data when you sync with Suunto. Without these permissions, the data can't be synced.

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

Strava permissions: FitProphet 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: FitProphet 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 FitProphet asks for your country when you connect FitProphet with InBody. The country is stored with the private data of FitProphet and is never shared with others.

Smashrun permissions: FitProphet 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: FitProphet 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: FitProphet needs permissions to access your DiabetesM account when you sync to or from DiabetesM. Without these permissions, the data can't be synced.

Under Armour permissions: FitProphet needs permission to access your Under Armour account when you sync with one or more of the Under Armour apps MapMyFitness, MapMyRide, MapMyWalk and MapMyRun. Without this permission, the data can't be synced.

Authorization: FitProphet 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, UnderArmour (the MapMy.. apps) or Garmin. FitProphet 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. FitProphet does not have access to these authorization pages. This safe authorization mechanism is known as OAuth 1 or OAuth 2.

Payment: FitProphet only uses information from your account for the synchronization of the health data. When you purchase FitProphet unlimited usage or subscribe to FitProphet, the financial operation is handled by Google Play Store when you downloaded FitProphet from the Google Play Store. When you installed FitProphet from the Huawei AppGallery, the payment is handled by Huawei. FitProphet 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 FitProphet on your phone and the fitprohpet.uc.r.appspot.com secure server (in the Google Cloud). The log data will be analyzed and then deleted within one week after you send the information. Log data and your email address will never be given to others or published outside the secure systems of fitprohpet.uc.r.appspot.com.

Anonymous crash and log data: When you download FitProphet through the Google Play Store,  anonymous crash data will be sent to a Google server when a crash occurs. Only fitprohpet.uc.r.appspot.com 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 FitProphet privacy policy, you can use the contact page on this site.