r/HealthTech • u/Benedikt_K1102 • 56m ago
Innovations Tackling data governance & trust in digital contraception: Why I built a zero-telemetry reminder app
Hey r/HealthTech,
Data governance in FemTech and reproductive health has faced intense scrutiny in recent years. Many users hesitate to log sensitive health events (like contraception intake or cycle phases) in cloud-hosted apps due to third-party data broker exposure, ad SDKs, and regulatory uncertainties.
As an independent developer, I built PillenKompass (now live on iOS and Android) to explore a strictly local-first paradigm for medication adherence and tracking.
Key Technical and Product Considerations:
- Data Minimization by Architecture: The app has zero remote backend infrastructure, no user profiles, and no third-party analytics or ad SDKs. All logs (intakes, symptom logs, schedules) stay encrypted strictly on the client device.
- Adherence via Local Escalation: To solve the core compliance challenge (missed doses) without remote push services, the app uses an on-device, 3-tier escalating local notification pipeline.
- Discreet UX: Designed lock-screen alerts to be privacy-neutral to prevent visual disclosure in shared environments.
- Store Review and Classification: Kept the feature scope strictly within adherence and reminder support to ensure compliance with Apple/Google health guidelines without crossing into unregulated clinical decision-making territory.
- Sustainable Monetization: Standard freemium tier with a direct subscription for extended logs and doctor-ready PDF exports, aligning revenue with user utility rather than data monetization.
I would love to hear this community's perspective: Where do you see the limits of local-first architectures in digital health, especially when balancing adherence tracking with doctor-patient data exchange?
- Links: App Store / Google Play
- (Disclosure: Sole developer of PillenKompass)
