App Privacy Details
Effective Date: March 8, 2026
1. Introduction
This page provides a detailed breakdown of the data collected, used, and shared by the Pinnacle Pulse mobile application (iOS and Android). It is structured to align with Apple App Store “App Privacy” (Nutrition Label) and Google Play “Data Safety” disclosure requirements.
This page supplements our Privacy Policy and Terms of Service. Use it as a public reference and as a checklist when completing App Store Connect and Google Play Console privacy questionnaires.
Operator: elephantmilk asia LLC
App bundle ID: com.pinnaclepulse
Platforms: iOS, Android
2. Apple App Store — App Privacy Details
The table below maps data types to Apple’s official App Privacy categories. “Linked to You” means data is tied to your account or identity. “Used to Track You” means data is linked with third-party data for advertising or shared with a data broker.
| Data Category | Data Type | Linked to You | Used to Track You | Purpose |
|---|---|---|---|---|
| Contact Info | Email address | Yes | No | Account creation, authentication, service communications |
| Name | Yes | No | Profile display, personalization | |
| Health & Fitness | Heart rate variability (HRV) | Yes | No | Recovery tracking, daily check-in, AI forecasting |
| Resting heart rate | Yes | No | Recovery tracking, wearable sync | |
| Sleep data (duration, quality, score) | Yes | No | Recovery tracking, daily check-in | |
| Step count & active calories | Yes | No | Activity tracking via Health Connect / Apple Health | |
| Blood oxygen (SpO₂) | Yes | No | Recovery and wellness metrics | |
| Body measurements (height, weight, body fat %, circumferences) | Yes | No | Progress tracking, 3D avatar, body scan | |
| Peptide dosage, injection site, protocol data | Yes | No | Peptide tracking, protocol management, on-device AI predictions | |
| Blood biomarker results (Pro tier) | Yes | No | Health score, organ grades, trend analysis | |
| Photos or Videos | Body scan photos (multi-angle captures) | Yes | No | 3D body reconstruction, progress visualization |
| AR capture images | Yes | No | Progress tracking, 3D visualization | |
| Profile avatar photo | Yes | No | User profile display | |
| User Content | Peptide logs & notes | Yes | No | Tracking, journaling, AI forecasting |
| Stack protocols & templates | Yes | No | Protocol management | |
| Subjective wellness inputs (energy, mood, soreness, focus) | Yes | No | Daily check-in, recovery insights | |
| Identifiers | User ID (Firebase account ID) | Yes | No | Account management, data sync, authentication |
Data Not Collected
The Pinnacle Pulse app does not collect the following data types:
- Location — No GPS or location data is collected (despite a legacy iOS permission string, no location SDK is active)
- Financial Info — No payment or purchase data is processed in-app (subscriptions will be handled via App Store / Google Play when launched)
- Contacts — No access to your contact list
- Browsing History / Search History — Not collected
- Usage Data — No analytics SDK is integrated; no usage or diagnostic data is sent to third parties
- Diagnostics — No crash reporting SDK (e.g., Crashlytics, Sentry) is integrated
- Sensitive Info (beyond health data above) — No racial, political, or religious data
3. Google Play — Data Safety
The table below maps data types to Google Play Data Safety categories. “Shared” means data is transferred to a third party. “Optional” means the user can use the app without providing this data.
| Data Category | Data Type | Collected | Shared | Optional | Purpose |
|---|---|---|---|---|---|
| Personal info | Name | Yes | No | Yes | Profile, personalization |
| Email address | Yes | No | No (required for account) | Authentication, communications | |
| User IDs | Yes | No | No | Account management, data sync | |
| Health and fitness | Heart rate & HRV | Yes | No | Yes | Recovery tracking, check-in |
| Sleep data | Yes | No | Yes | Recovery tracking | |
| Steps & active calories | Yes | No | Yes | Activity tracking | |
| Blood oxygen (SpO₂) | Yes | No | Yes | Wellness metrics | |
| Body measurements | Yes | Yes (fal.ai for 3D scan) | Yes | Progress tracking, 3D avatar | |
| Peptide & dosage data | Yes | No | Yes | Peptide tracking, AI forecasting | |
| Blood biomarker results | Yes | No | Yes | Health score, trend analysis | |
| Photos and videos | Body scan photos | Yes | Yes (fal.ai for 3D reconstruction) | Yes | 3D body visualization |
| AR capture images | Yes | No | Yes | Progress tracking | |
| Profile avatar | Yes | No | Yes | Profile display | |
| App activity | App interactions (peptide logs, check-ins) | Yes | No | Yes | Core app functionality |
| Other user-generated content (notes, protocols) | Yes | No | Yes | Tracking, journaling | |
| Device or other IDs | Firebase User ID | Yes | No | No | Authentication, data sync |
Security Practices (Google Play)
- Data is encrypted in transit (HTTPS/TLS)
- Cloud-stored data is encrypted at rest (Firebase)
- Users can request deletion of their account and associated data
- Health data from wearables is accessed only with explicit user permission via Apple Health / Health Connect
4. Feature-by-Feature Data Breakdown
4.1 Account & Authentication
- Methods: Email/password, Google Sign-In, anonymous guest access
- Data collected: Email address, display name, Firebase User ID
- Storage: Firebase Authentication (Google Cloud)
- Google Sign-In: Receives email, name, and profile picture from your Google account via OAuth
4.2 Health & Wearable Sync
- Integration: Apple Health (iOS) / Health Connect (Android) via the
healthpackage - Supported wearables: WHOOP, Oura, Apple Watch, Garmin, Xiaomi Smart Band, HUAWEI Band — data flows through the health platform, not direct SDK connections
- Data synced: HRV, resting heart rate, sleep score/duration, step count, SpO₂, active calories, workouts
- Permission: Explicit user consent required via HealthKit / Health Connect permission dialogs
- Storage: Local (Hive) and cloud (Firestore) when account sync is active
4.3 Body Scan & 3D Avatar
- Camera: Multi-angle body photos captured via device camera
- On-device processing: Google ML Kit pose detection runs locally; no images sent for pose analysis
- Cloud processing: Body photos are uploaded to fal.ai for 3D body reconstruction (SAM-3 model). This is the most sensitive data transfer in the app.
- Results stored: 3D GLB models, body measurements (shoulders, chest, waist, hips, arms, thighs), scan history — in Firebase Storage and Firestore
- On-device AI: EvoEngine predictions (TensorFlow Lite) run entirely on your device; no health data sent to servers for forecasting
4.4 Peptide Tracking
- Data logged: Peptide name/ID, dosage, unit (mcg/mg/IU), injection site, timestamp, notes, subjective metrics (energy, mood, soreness, focus)
- Biometric context: HRV score, soreness level, sleep hours at time of log
- AI predictions: On-device EvoEngine generates 7-day forecasts from your logs — processed locally
- Storage: Local (Hive) and cloud (Firestore:
peptide_logs,protocols,stack_protocols)
4.5 Blood Panels (Pro Tier)
- Data: Biomarker results (testosterone, IGF-1, HGH, cortisol, and related markers), reference/optimal ranges, health score, organ grades
- Lab integration: Currently manual entry; partner lab API is planned but not yet active
- Storage: Local (Hive) and cloud (Firestore:
blood_panels)
4.6 Local vs. Cloud Storage
- On-device (Hive + SharedPreferences): Profile, daily metrics, peptide logs, baseline data, blood panels, protocols, onboarding flags, streaks, disclaimers
- Cloud (Firebase Firestore + Storage): Account-linked sync of all user data when logged in; scan images, GLB models, AR captures in Firebase Storage
- On-device only (never sent to servers): EvoEngine AI predictions (TensorFlow Lite), ML Kit pose detection results
5. Device Permissions
5.1 iOS Permissions
| Permission | Usage Description | Why It’s Needed |
|---|---|---|
| Camera | “Pinnacle Pulse needs camera access to capture progress photos for 3D visualizations.” | Body scan, AR capture |
| Photo Library | “Pinnacle Pulse needs photo library access to save AR scan images.” | Save scan results, avatar selection |
| Health (Read) | “Pinnacle Pulse reads heart rate, HRV, and sleep data from Health to auto-fill your daily check-in and track recovery.” | Wearable sync, daily check-in |
| Health (Write) | “Pinnacle Pulse may save workout or wellness data to Health when you log activities.” | Write-back of logged activities |
| Microphone | “Pinnacle Pulse may use the microphone for video recording or voice features when you use the camera.” | Camera video capture (if audio enabled) |
Not requested: Location, Contacts, Face ID, Bluetooth, Motion, App Tracking Transparency (ATT)
5.2 Android Permissions
| Permission | Why It’s Needed |
|---|---|
| CAMERA | Body scan, AR capture |
| READ_MEDIA_IMAGES / READ_EXTERNAL_STORAGE | Gallery access for avatar and scan images |
| POST_NOTIFICATIONS | Local reminder notifications (peptide doses, check-ins) |
| ACTIVITY_RECOGNITION | Step count and activity data via Health Connect |
| BODY_SENSORS | Heart rate and sensor data from wearables |
| Health Connect: READ_STEPS, READ_HEART_RATE, READ_SLEEP, READ_ACTIVE_CALORIES_BURNED, READ_HEART_RATE_VARIABILITY, READ_BLOOD_OXYGEN | Wearable health data sync |
Not requested: Location, Bluetooth, Contacts, Record Audio, Fine Location
6. Third-Party Data Sharing
We do not sell your personal information. The following third parties receive data as part of providing the Service:
| Third Party | Data Shared | Purpose | Sensitivity |
|---|---|---|---|
| Google Firebase (Auth, Firestore, Storage) | Account credentials, all user-generated content, scan images, 3D models | Backend infrastructure, authentication, cloud sync | Standard — contractual data protection (Google Cloud) |
| Google Sign-In | OAuth token exchange; receives email, name, profile picture from Google | Authentication | Standard — OAuth 2.0 |
| fal.ai | Body scan photos (multi-angle captures) | 3D body reconstruction (SAM-3 AI model) | High — body photos leave your device and are processed on fal.ai servers |
| Google ML Kit | None (on-device processing only) | Pose detection for body scan alignment | None — all processing is local |
| Apple Health / Health Connect | Read/write health metrics per user permission | Wearable data bridge | Platform-managed — user controls permissions |
| Google Fonts | IP address, requested font files | Typography rendering | Low — standard web font delivery |
7. No Tracking, No Advertising
Pinnacle Pulse does not use your data for tracking purposes. Specifically:
- No App Tracking Transparency (ATT) prompt — we do not access IDFA or use cross-app tracking
- No analytics SDKs integrated (no Firebase Analytics, Mixpanel, Amplitude, PostHog, or similar)
- No crash reporting SDKs (no Crashlytics, Sentry, or similar)
- No advertising SDKs or ad networks
- No data sharing with data brokers
- No use of data for targeted advertising or marketing profiling
8. Data Retention & Deletion
- Account data: Retained while your account is active. You may request account deletion, which removes your Firebase Auth record and associated Firestore/Storage data.
- On-device data: Stored locally in Hive and SharedPreferences. Uninstalling the app removes local data. Cloud-synced data persists until account deletion.
- Body scan photos on fal.ai: Processed for 3D reconstruction; retention on fal.ai servers is governed by their privacy policy. We recommend reviewing fal.ai’s data handling practices.
- Health data: Read from Apple Health / Health Connect per your permission settings. Revoking permission stops future sync; previously synced data remains until you delete it.
To request deletion of your account and all associated data, contact us using the details in Section 9.
9. Contact & Related Documents
For questions about this App Privacy disclosure or to exercise your privacy rights:
elephantmilk asia LLC
Pinnacle Pulse
[Contact email or address to be inserted]
Related documents:
- Privacy Policy — full privacy policy covering website and app
- Terms of Service — terms of use, subscription plans, and user responsibilities
- Disclaimer — medical and AI liability disclaimer