Objectives
The purpose of this guide is to assist ROOK clients in navigating the app submission process for the Apple App Store and Google Play Store, with a focus on permissions related to health data. This guide explains why ROOK extracts specific data points and provides useful resources and detailed instructions.
Useful Links/Resources
Apple App Store Guidelines:
Google Play Store Guidelines:
Health Data Permissions:
Common Challenges
Common Reasons for App Rejections Related to Health Data:
Apple: Missing or inadequate description of permissions.
Google: Insufficient specificity in the description of why permissions are being requested.
Privacy Information:
Apple: Apps must include a privacy information file that Apple reviews.
Google: Apps need to describe individual permissions accurately to protect user privacy and request only the minimal information required.
How to Describe Permissions
Apple
Ensure that the general reason for requesting all health data permissions is well-documented.
Provide a detailed explanation of how this data is used to generate health scores, provide recommendations, or deliver your product or service experience.
Be specific about why each data point is needed.
Example:
ActiveCaloriesBurnedRecord: "We need this to create a summary that will help our users track their caloric expenditure to support body composition goals."
List of Health Data Permissions (See documentation)
By default, we will request the full list of permissions. You can choose to omit the request for certain permissions if you do not plan to use the data.
Required for Health Score
WeightRecord
HeightRecord
ActiveCaloriesBurnedRecord
TotalCaloriesBurnedRecord
StepsCadenceRecord
StepsRecord
ElevationGainedRecord
ExerciseSessionRecord
FloorsClimbedRecord
HeartRateRecord
RestingHeartRateRecord
HeartRateVariabilityRmssdRecord
SleepSessionRecord
Not required for Health Score (optional)
BloodGlucoseRecord
BloodPressureRecord
BodyTemperatureRecord
DistanceRecord
HydrationRecord
MenstruationPeriodRecord
NutritionRecord
OxygenSaturationRecord
PowerRecord
RespiratoryRateRecord
SpeedRecord
Vo2MaxRecord
Example Descriptions for Google Health Connect
Here are sample descriptions for each health data permission:
ActiveCaloriesBurnedRecord:
"We need this to create a summary that will help our users track their caloric expenditure to support body composition goals."
BloodGlucoseRecord:
"We need this to help users monitor their blood glucose levels, essential for managing diabetes and overall metabolic health."
BloodPressureRecord:
"We need this to help users track their blood pressure for cardiovascular health monitoring and to detect potential hypertension."
BodyTemperatureRecord:
"We need this to help users monitor their body temperature, which can indicate infection or other health conditions."
DistanceRecord:
"We need this to track the distance covered by users during their activities, which is crucial for fitness and performance analysis."
ElevationGainedRecord:
"We need this to track elevation gained during physical activities, which helps in understanding the intensity and impact of workouts."
ExerciseSessionRecord:
"We need this to log exercise sessions, helping users track their physical activity patterns and improve their fitness routines."
FloorsClimbedRecord:
"We need this to count the number of floors climbed by users, adding another dimension to their physical activity tracking."
HeartRateRecord:
"We need this to monitor heart rate during various activities, which is vital for assessing cardiovascular fitness and overall health."
HeartRateVariabilityRmssdRecord:
"We need this to measure heart rate variability, which provides insights into autonomic nervous system function and stress levels."
HeightRecord:
"We need this to record user height, which is a fundamental metric for calculating various health and fitness parameters."
HydrationRecord:
"We need this to track hydration levels, helping users maintain optimal hydration for health and performance."
MenstruationPeriodRecord:
"We need this to help users track their menstrual cycles, which is important for reproductive health and understanding hormonal impacts on fitness."
NutritionRecord:
"We need this to log nutritional intake, which supports dietary tracking and helps users meet their nutritional goals."
OxygenSaturationRecord:
"We need this to monitor blood oxygen saturation, which is critical for assessing respiratory health and detecting potential issues."
PowerRecord:
"We need this to measure power output during activities, providing insights into performance and training intensity."
RespiratoryRateRecord:
"We need this to track respiratory rate, which helps in assessing overall respiratory health and fitness."
RestingHeartRateRecord:
"We need this to monitor resting heart rate, an important indicator of cardiovascular health and fitness."
SleepSessionRecord:
"We need this to log sleep sessions, helping users understand their sleep patterns and improve sleep quality."
SpeedRecord:
"We need this to measure the speed of activities, which is essential for performance tracking and fitness improvement."
StepsCadenceRecord:
"We need this to track steps cadence, providing insights into walking/running efficiency and performance."
StepsRecord:
"We need this to count steps taken by users, a fundamental metric for daily activity and fitness tracking."
TotalCaloriesBurnedRecord:
"We need this to calculate total calories burned, helping users manage their energy expenditure and support weight management goals."
Vo2MaxRecord:
"We need this to estimate VO2 Max, a key indicator of cardiovascular fitness and aerobic performance."
WeightRecord:
"We need this to track user weight, a fundamental metric for monitoring body composition and health."