[FEATURE] Plain-language privacy policy for health data & export/sharing

Description

Write a plain-language privacy policy describing what health data Along With You collects, how it's stored, and how the export/sharing feature works. This needs to ship before the export feature goes live, since export is the first point where journal data can leave the device.

Scope: policy content covering data collection and export/sharing behavior, plus surfacing it in-app (e.g., settings and/or the export screen). Written for the app's audience — people who may be exhausted, anxious, or cognitively overloaded — so plain language over legal jargon. Does not cover the legal sign-off process itself.

Acceptance Criteria

• Policy uses plain language, avoiding legal/technical jargon, appropriate for a stressed or tired reader
• Clearly states what health data is collected (journal entries, etc.) and confirms local-only storage — no cloud sync of medical data
• Clearly explains how export works: what's included (PDF export), how it's generated, and that sharing is manual/user-initiated — no live account access for caregivers or doctors
• Confirms excluded data types are never collected: SSNs, medical portal passwords/secrets, security alarm codes, exact house key/wallet/purse locations
• Reviewed and approved by product owner (Roberta Talmage) before publishing
• Accessible from the app (e.g., settings and/or export screen) before the export feature ships
• The feature/s being implemented are covered by unit tests - If not, create tests for them on this ticket

Additional Info and Resources

Blocks the export feature release — export ships as PDF export only, no live doctor/caregiver account access (per Paul's documented decision). Should reflect current product principles: plain language, reduced cognitive load, and privacy as a requirement rather than a later add-on.

QA

• Have a non-technical reviewer read the policy and confirm it's clear and jargon-free
• Verify the policy accurately matches the actual data handling implementation (local storage only, PDF export, no cloud)
• Confirm the policy is reachable from within the app before export ships

Start by reading the current data-handling implementation and the export entry point, then inspect how settings or the export screen can surface policy content. Draft the policy around local storage, PDF export, manual sharing, and excluded data, and identify any missing unit tests. Done means the policy is reachable before export ships, matches implementation, passes relevant tests, and is approved by Roberta Talmage.