Data Privacy in Health Apps — What I Chose Not to Collect

The Default Is to Collect Everything When I set up analytics for Lunair , every tutorial and SDK I encountered was designed to maximize data collection. Session recordings, user journeys, demographic profiling, device fingerprinting. The default for modern app development is to hoover up everything and figure out what is useful later. For a mental health app, I decided to go the opposite direction. What Lunair Does Not Collect No personal health data leaves the device. Breathing session history, pattern preferences, and usage frequency stay in local storage. Period. No user accounts. No email, no sign-up, no social login. There is nothing to breach because there is nothing stored server-side. No location data. I have no reason to know where someone is breathing. No third-party analytics SDKs. No Firebase Analytics, no Mixpanel, no Amplitude. Every one of these sends data to third-party servers with their own privacy policies. What I Do Collect (and Why) I use Apple's built-in App Analy