PPP Mobile App — Store Declarations (Data Safety + Health)
Purpose: The approved, ready-to-transcribe answers for the Google Play Data Safety form + Health apps declaration, and the Apple App Store Connect App Privacy equivalents. Transcribe these verbatim into the consoles when the app record is ready.
Status: Approved, ready to transcribe. Content sign-off complete (see Decision trail). Submission itself remains gated on the Play app record (#8034). This document delivers the approved declarations only — it does not submit them.
Scope: Google Play "App content" items 4 (Data safety) and 6 (Health apps) from the parent checklist #7933. The other seven items (advertising ID, location, foreground service, photo/video, app access, target audience, content rating) are mechanical and tracked on #7933.
Source of truth:
mobile/ppp/app.config.js+mobile/ppp/lib/services/*+api/backend-pppimage service, re-verified againstHEADon 2026-07-16. Where a code re-verification corrected the originally-drafted matrix, the change is flagged in Corrections vs the originally-drafted matrix — Matt-approved content is never silently altered.Last updated: 2026-07-16
1. Health apps declaration
PPP is not a regulated medical device. It is a professional record-keeping and wellness-tracking tool for doctors (CPD logging, surgical logbook, wellbeing check-ins). It does not diagnose, treat, cure, mitigate, or prevent a disease or condition. Every data point it processes describes the doctor's own professional activity, training, or personal wellbeing — not a patient's diagnosis or treatment.
Health features present in the app (declare these under Google Play "Health apps"):
- Wellness / readiness tracking — reads fitness & vitals data (heart rate, HRV, sleep, SpO2, steps, respiratory rate) from Apple HealthKit / Android Health Connect and computes a personal wellness readiness score.
- Mental wellbeing check-ins — WHO-5 Wellbeing Index questionnaire.
- Professional record-keeping — CPD activity logging and surgical logbook (clinician's own case records).
Console answer: Declare as a general health & fitness / professional record-keeping app. When asked "Is your app a medical device regulated by a governing body?", answer No.
2. Data Safety declaration (Google Play) / App Privacy label (Apple)
Every row below is encrypted in transit (HTTPS / TLS 1.2+). Nothing is sold, and nothing is used for advertising or cross-app tracking.
| Data type | Collected | Linked to identity | Shared with third parties | Purpose | Notes |
|---|---|---|---|---|---|
| Account info — name, email, medical registration number | Yes | Yes | No | Account creation, authentication, professional-registration verification | Auth via AWS Cognito |
| Health & fitness — HealthKit / Health Connect vitals (HR, HRV, sleep, SpO2, steps, respiratory rate); WHO-5 check-ins | Yes | Yes | No | Wellness readiness scoring, coaching prompts | Fitness/vitals only — no clinical HealthKit record types read (see Corrections) |
| Location — foreground + background | Yes | Yes | No | Auto-timesheet on hospital geofence entry/exit | Coordinates used on-device for proximity; not persisted server-side |
| Photos — camera captures | Yes | Yes | Yes — Microsoft Azure OpenAI Service (OCR text extraction only) | Medical-sticker OCR, document upload, profile picture | OCR provider is Azure OpenAI, not Google Gemini (see Corrections) |
| App activity / diagnostics — crash reports, stack traces | Yes | Device/session-linked | Yes — Sentry | Crash and error reporting | |
| App activity / diagnostics — usage telemetry (geofence entry/exit events) | Yes | Device/session-linked | Yes — Microsoft Azure Application Insights | Product telemetry and reliability | Scalar-only: hospital ID + event type. No coordinates transmitted |
| Financial info — payment reference only (no card data) | Yes | Yes | Yes — Stripe (payment processing) | Subscription billing | Billing runs in the WebView; no card data touches the device |
| Device identifiers — push notification token | Yes | Device-linked | Yes — Expo push service | Delivering in-app / push notifications |
On-device only (declare as "not collected / not shared" where the console distinguishes on-device storage):
- Session credential — stored in
expo-secure-store(biometric-gated), never leaves the device except as a bearer token on API calls. - MMKV / AsyncStorage local cache — app state persisted on-device (AES-256 encrypted MMKV).
Advertising & tracking:
- Sold or used for advertising: No.
- Advertising ID (AAID / IDFA): Not used. No ad SDKs, no analytics SDKs beyond crash/telemetry above, no cross-app or cross-site tracking.
Encryption in transit: Yes — HTTPS / TLS for all network traffic. Do not claim certificate pinning: the withCertificatePinning config hook is currently a functional no-op (pins commented out, tracked #5110). Declaring "encrypted in transit (TLS)" is accurate; declaring pinning would not be.
Data deletion:
- Route: By email request to the support contact declared in the store listing — not a self-service in-app delete button. This lets us properly off-board a doctor and retain only anonymised insights, never their identifiable data.
- Google/Apple require a named deletion route. Use the support/deletion contact email published in the store listing (see the transcription-time note in Open items).
3. Transcription checklist — exact console answers
Google Play → App content → Data safety
| Console question | Answer to enter |
|---|---|
| Does your app collect or share any of the required user data types? | Yes |
| Is all of the user data encrypted in transit? | Yes |
| Do you provide a way for users to request that their data is deleted? | Yes — by email request (name the store-listing support email) |
| Personal info — Name, Email address | Collected + shared? Collected, not shared. Linked to user. Purpose: App functionality, Account management |
| Personal info — Other info (medical registration number) | Collected, not shared. Linked. Purpose: Account management |
| Financial info — Purchase history / payment info | Collected, shared (Stripe). Linked. Purpose: App functionality |
| Location — Approximate + Precise | Collected, not shared. Linked. Purpose: App functionality (auto-timesheet) |
| Photos and videos — Photos | Collected, shared (Azure OpenAI, OCR). Linked. Purpose: App functionality |
| Health and fitness — Health info, Fitness info | Collected, not shared. Linked. Purpose: App functionality |
| App activity / App info and performance — Crash logs, Diagnostics | Collected, shared (Sentry, Azure Application Insights). Purpose: Analytics, App functionality |
| Device or other IDs | Collected, shared (Expo push). Purpose: App functionality (notifications) |
| Is any data used for advertising or marketing? | No |
| Does the app use an advertising ID? | No |
Google Play → App content → Health apps
| Console question | Answer to enter |
|---|---|
| Does your app access, collect, or use health data? | Yes |
| Health features used | Fitness / vitals tracking, mental wellbeing check-ins, professional record-keeping |
| Is your app a medical device regulated by a governing body? | No |
| Does the app provide health-condition diagnosis, treatment, or monitoring? | No |
Apple App Store Connect → App Privacy
| Category | Answer |
|---|---|
| Contact Info (Name, Email) | Collected, linked, not used for tracking. Purpose: App Functionality |
| Health & Fitness | Collected, linked, not used for tracking. Purpose: App Functionality |
| Location (Precise) | Collected, linked, not used for tracking. Purpose: App Functionality |
| User Content (Photos) | Collected, linked. Shared with Azure OpenAI for OCR. Purpose: App Functionality |
| Financial Info (Payment) | Collected, linked. Shared with Stripe. Purpose: App Functionality |
| Diagnostics (Crash / Performance) | Collected. Shared with Sentry / Azure Application Insights. Purpose: App Functionality, Analytics |
| Identifiers (Push token) | Collected. Purpose: App Functionality |
| Data used to track you | None |
| Data deletion | Contact-based (support email in listing) |
Corrections vs the originally-drafted matrix
These are the points where a fresh code re-verification (2026-07-16, against HEAD) corrected the matrix as originally drafted in the issue's engineering notes. Matt's content sign-off stands — these are accuracy corrections to declared facts, flagged here so they are visible rather than silently changed. Each carries file evidence.
| # | Originally drafted | Corrected to | Evidence |
|---|---|---|---|
| 1 | OCR provider = Google Gemini | Microsoft Azure OpenAI Service (GPT-4o-mini Vision). Flow: device camera → Azure Blob → backend → Azure OpenAI | Migrated in #4633; api/backend-ppp/src/services/image/imageService/index.ts |
| 2 | Certificate pinning (encryption-in-transit claim) | TLS only — withCertificatePinning is a functional no-op (pins commented out) | Tracked #5110; mobile/ppp/app.config.js |
| 3 | HealthKit isClinicalDataEnabled: true → clinical records read | false — fitness/vitals only, no clinical HealthKit record types requested | mobile/ppp/app.config.js (react-native-health plugin config) |
| 4 | Third parties: Sentry only | Sentry + Azure Application Insights + Stripe + Expo — telemetry (hospital ID + event type, no coordinates), payment reference, push token added | mobile/ppp/app.config.js; backend telemetry; verified against mobile/ppp/lib/services/* |
Additionally confirmed safe to declare (no correction, but verified): no ad SDKs, no advertising ID, no third-party analytics SDKs beyond crash/telemetry; Stripe billing runs in the WebView so no card data is stored on-device.
Note on the sibling
data-collection.mddoc: that inventory (last updated 2026-03-03) still names "Google Gemini" and "AWS S3" for the OCR flow — it predates the #4633 Azure migration and is stale on the same point corrected in row 1 above. It is not updated by this change (out of scope — this issue delivers the store declarations, not a rewrite of the collection inventory). The reconciled current picture lives inprivacy-policy.md(v1.1, 2026-07-12) and this document. Refreshingdata-collection.mdshould be a separate follow-up.
Decision trail
- 2026-06-03 — Matt: medical-device question = Option A ("not a medical device — record-keeping & wellness only"); Data Safety matrix accurate ("Yes; nothing missing"); leaned toward email-based deletion to properly off-board and retain anonymised insights. (
matt-ppp, issue #8234) - 2026-07-13 / 2026-07-15 — Matt confirmed the pasted plain-English declarations read as accurate.
- 2026-07-16 — Rob: final decision on the deletion route = Option A, email-based deletion request (proper off-boarding + anonymised-insight retention; compliant as long as honoured). ("I decide A", issue #8234)
Open items to confirm at transcription time
- Concrete deletion-request email address. The route is decided (email-based); the specific address should be the support/deletion contact published in the store listing.
privacy-policy.mdusessupport@professionalperformanceportfolio.com— confirm this is the address to name in the Play Console / App Store Connect data-deletion field at transcription time. - Submission gate. Do not submit until the Play app record (#8034) exists.