Data Collection Policy

Last Updated: June 26, 2026

This Data Collection Policy provides a detailed breakdown of all data collected by the GetFit mobile application operated by KeyZen.


1. Categories of Data Collected

1.1 Data You Provide

Category Specific Data When Collected Required
Identity Name Onboarding Yes
Contact Phone number Phone OTP registration Only if chosen
Contact Email address Email registration or profile Only if chosen
Credentials Password (stored as bcrypt hash) Email/password registration Only if chosen
Social Identity Google account ID, email, name, avatar Google Sign-In Only if chosen
Social Identity Apple account ID, email, name Apple Sign-In Only if chosen
Profile Profile photo (base64 or URL) Photo upload No
Country Country (selected in onboarding) Onboarding No
Health Profile Height (cm), weight (kg), age, gender Onboarding Yes
Fitness Goals Goal (lose/gain/maintain), target weight, timeline Onboarding Yes
Preferences Activity level, diet preference (veg/non-veg), fitness level Onboarding Yes
Nutrition Logs Food items, quantities, meal type, calories, protein, carbs, fat Manual food logging User-initiated
Water Intake Liters consumed per day Streak updates User-initiated
Chat Messages Text messages to AI Trainer AI chat sessions User-initiated
Feedback Thumbs up/down on AI responses AI interaction User-initiated
Health Questionnaire Allergies, health conditions, cuisine, cooking time, budget AI diet generation User-initiated
Exercise Videos Video URLs submitted for AI analysis Video analysis User-initiated

1.2 Data Collected Automatically

Category Specific Data Source Purpose
Health Data Step count Apple HealthKit / Health Connect / Pedometer Fitness tracking
Health Data Active energy burned (kcal) Apple HealthKit / Health Connect Calorie tracking
Health Data Walking/running distance Apple HealthKit / Health Connect Distance tracking
Health Data Exercise sessions Health Connect (Android) Workout tracking
Device Data Device type, OS version Firebase Analytics App performance
Usage Data Feature usage events Firebase Analytics Service improvement
Crash Data Error stack traces, device state Firebase Crashlytics, Sentry Bug fixing
Network Data IP address Server access logs Security

1.3 Data Generated by the App

Category Specific Data How Generated
Computed Health Metrics BMI, body type (ectomorph/mesomorph/endomorph) Calculated from height and weight
Computed Nutrition Targets Maintenance calories, goal calories, daily protein target Mifflin-St Jeor equation + goal adjustment
Nutrition Streaks Daily completion scores, streak qualification Computed from food logs vs. targets
AI Memories Personal facts (injuries, goals, preferences, body stats) AI extraction from chat conversations
AI User State Energy, recovery, fatigue, motivation, adherence, injury risk AI computation from usage signals
AI Learning Profile Communication preferences, response patterns AI analysis of interactions
Subscription Status Plan tier, expiry date, payment status Payment verification

1.4 Camera and Image Data

Data When Collected Processing Storage
Barcode images When scanning products Processed on-device for barcode decoding Not stored
Food photos When using food recognition Sent as base64 to AI service for identification Not permanently stored on server
Profile photos When uploading profile picture Stored as base64 or URL in user profile Stored until account deletion

2. Data We Do NOT Collect


3. Why We Collect Each Data Type

Purpose Data Used
Account authentication Phone number, email, password, Google/Apple IDs
Profile personalization Name, avatar, country
Fitness calculations Height, weight, age, gender, activity level, fitness goal
Calorie and nutrition tracking Food logs, water intake, nutrition streaks
Step and activity tracking HealthKit/Health Connect step count, calories, distance
AI coaching Chat messages, AI memories, user state, health profile
AI diet generation Health profile, allergies, health conditions, preferences
AI food recognition Camera food photos
Subscription management Payment transaction IDs, plan selection
Analytics and improvement Device info, usage events, crash reports
Security IP addresses, authentication tokens

4. Permissions and Their Justification

Permission Platform Why Required
Camera iOS & Android Barcode scanning for packaged food products; food photo recognition for AI-powered nutritional analysis
HealthKit (Read) iOS Reading step count and active energy burned to display accurate fitness data without manual entry
Health Connect (Read) Android Reading step count, active calories, distance, and exercise data for fitness tracking
Activity Recognition Android Detecting physical activity for accurate step counting via the device pedometer
Internet Both All API communication with our backend for authentication, data sync, AI features, and payment processing
Photo Library Both Selecting profile photos from your gallery

5. Data Minimization

We follow the principle of data minimization:


6. Contact

For questions about data collection:


This Data Collection Policy is effective as of June 26, 2026.