App Store Disclosures
FollowThrough Health App Store Privacy Draft
This draft helps prepare Apple App Privacy and Google Play Data Safety answers for FollowThrough Health. It is not legal advice. Final answers should be reviewed by legal, privacy, security, and clinical advisors before public app-store submission.
Product Positioning
FollowThrough Health is an educational health report explainer and care preparation tool. It does not provide diagnosis, prescription, emergency care, insurance verification, or a replacement for licensed medical judgment.
Data Types Expected
- Account information: email, role, verification state, login sessions, refresh tokens, and password reset or email verification records.
- Health and fitness information: patient profile, conditions, allergies, medication notes, intake answers, goals, diet style, activity level, report text, uploaded report metadata, AI explanation records, care plans, check-ins, and clinician review records.
- User content: files or text the user chooses to upload or paste, support requests, visit briefs, care packets, and local export data.
- Identifiers: backend user ID, patient ID, report IDs, audit IDs, notification device token, and subscription IDs.
- Purchase information: subscription status and checkout records when payment processing is enabled.
- Diagnostics and security records: audit events, consent history, deletion/export requests, and operational events needed to protect the service.
Purposes
- App functionality: account login, protected sync, report upload, educational explanations, saved history, data export, and deletion requests.
- Health education: plain-language report summaries, wellness suggestions, habit planning, and questions to ask licensed professionals.
- Safety and compliance: consent history, audit trail, high-risk review routing, privacy requests, abuse prevention, and account security.
- Communications: password reset, email verification, notifications, and support responses when configured.
- Payments: subscription checkout and subscription state when Stripe or another provider is enabled.
Sharing And Selling
FollowThrough Health should not sell health data. Any sharing with infrastructure, storage, payment, email, AI/OCR, or monitoring providers should be limited to operating the service and governed by appropriate contracts, privacy review, and security review.
Security Controls To Confirm
- Encrypted transport for all production traffic.
- Private report storage with protected download URLs.
- Encrypted sensitive patient fields in the backend database.
- No health data in analytics logs.
- Consent history and audit trail for protected actions.
- Data export and deletion request workflow.
Store Submission Notes
- Do not describe FollowThrough Health as diagnosing, curing, prescribing, or replacing a clinician.
- Explain that report interpretation must be reviewed with licensed healthcare professionals.
- Disclose that uploaded reports may contain sensitive health information.
- Confirm whether OCR, payments, notifications, and email delivery are enabled before final answers.
- Use screenshots and app review notes that show the educational disclaimer clearly.