Health Data
Govern sensitive cycle, symptom, prediction, and wearable information without exposing more data than support needs.
No synthetic metrics
This page is an operational guide only. It does not display counts, rates, statuses, or health-data values unless those values are returned by a backend admin endpoint.
What admins should review
guide- Use the user detail page for account status, onboarding state, cycle-record counts, daily-log counts, AI-thread counts, wearable type, and subscription state.
- Use Predictions to review generated cycle phase snapshots, confidence, warning flags, model versions, and source metadata.
- Use Wearables to confirm connection type, latest sync time, and metric volume when investigating sync issues.
- Avoid exposing raw symptom notes or intimate health entries in general support workflows unless a verified data request requires it.
Controls still needed
guide- Add a dedicated subject-access export action with audit logging before exposing downloadable health data.
- Add a deletion workflow that separates account suspension from irreversible health-data erasure.
- Add role-based permissions so support staff can triage accounts without reading sensitive health details.
- Add consent-state visibility for AI, wearable import, notifications, analytics, and email communication.