Android - Google Play Store Guidelines

---

Key Permission 1) Foreground Service Health

The SDK uses the FOREGROUND_SERVICE_HEALTH permission.

---

Key Permission 2) Health Connect

The permissions that are declared in the project’s AndroidManifest.xml file must be reviewed.

With every sensor enabled and declared, this might be what is seen in your Play Console:

---

Health Connect App Integration Requirements

To work with Health Connect, apps need to focus on making users' health and fitness better. They have to follow strong rules about privacy and safety from Google Play. This means they should only use health data for allowed reasons, get the right permissions, make sure users agree before sharing their data, and keep the data safe. Apps should also explain in a privacy policy how they handle user data, show users how to control their data, and might need to check their security practices.

To learn more about all the rules and what you need to do to use Health Connect, please refer to the official Health Connect policy requirements .

---

Health Connect by Android Permissions Overview

Health Connect lets apps access health and fitness information, which is very personal. When using Health Connect, apps must follow strict rules to keep this information safe and private. Apps should only ask for access to data if it's really needed to help users track and improve their health and fitness. This includes things like monitoring workouts, sleep, and eating habits, and sharing this data safely with other apps that help with health goals.

To use Health Connect, developers need to make sure they're using the data correctly, such as improving the app's health features and not for things like ads or selling information to others. If an app wants to use Health Connect for research, it must get permission from the people involved. It's also important for apps to be clear about how they use and protect health data, including having a privacy policy that explains everything to users. Developers must also keep this data secure, following best practices to prevent unauthorized access or leaks.

For more detailed rules and how to safely connect an app to Health Connect, please refer to the official guidelines for appropriate access and use of Health Connect .

---

Guidelines for Handling Personal and Sensitive User Data

When your app handles personal and sensitive data, like health information, contacts, or location, it's important to use this data responsibly and safely. Make sure to only collect and use data needed for your app's functions or what users would reasonably expect, securing it with modern methods like HTTPS. Always ask users clearly for their permission before accessing their data, and never sell their information. Be upfront with users about how you're using their data by providing clear in-app disclosures and obtaining their consent in a straightforward manner. Follow these practices to ensure user data is protected and used ethically.

For specific situations or more detailed guidelines, please refer to the official guidelines for personal and sensitive user data .

---

Google Health Connect API Request Form

Once the above guidelines have been read carefully, this request form must be filled out and submitted.

Below is a sample of what a filled-out form may look like, please make sure to read each question carefully and follow its instructions:

---

Health Research Use Case Disclaimer

Please read the following description in it's entirety if you have selected 'Health Research' as a use case for your application:

Applications give users the opportunity to donate their data for health research studies. These studies are typically approved by an Institutional Review Board (IRB) or Ethics Committee (EC) and collect user consent for conducting health research.

Apps conducting health-related human subject research using data obtained through Health Connect must obtain consent from participants or, in the case of minors, their parent or guardian. Such consent must include the (a) nature, purpose, and duration of the research; (b) procedures, risks, and benefits to the participant; (c) information about confidentiality and handling of data (including any sharing with third parties); (d) a point of contact for participant questions; and (e) the withdrawal process. Apps conducting health-related human subject research using data obtained through Health Connect must receive approval from an independent board whose aim is 1) to protect the rights, safety, and well-being of participants and 2) with the authority to scrutinize, modify, and approve human subjects research. Proof of such approval must be provided upon request.

If this description does not fit your application use case, please revise your selected use cases in the previous section

If this description does fit your application use case, please take a moment right now to fill out the Fit & Health Research Form to provide us with the required details to expedite your review

---

READ Access

---

WRITE Access

---

Privacy Policy

---

Review Process Timeline