I built Zorya because I searched for a pregnancy app that did not send my data anywhere, and I could not find one I trusted. Most apps sync to the cloud, require an account, and have privacy policies that run to 8,000 words. Zorya stores everything locally using your phone's own database. No backend. No account. No cloud. One-time purchase. When you delete the app, everything is gone. I ran a survey with 53 mothers before building. 96% had used an app with documented privacy violations. 70% said local-only storage was extremely important to them. Somehow no iOS app was doing this well. Zorya is a solo build. I designed it. It ships with a contraction timer, kick counter, pregnancy journal, symptom tracking, and weekly milestones from week 4 to 40. It handles pregnancy loss with care. It is available in English and Croatian. Happy to answer anything.

Forum Threads

p/zorya-pregnancy-tracker

•

4mo ago

What do you think about data privacy when building or using health apps?

Before building the app I ran a small survey with 53 mothers. Almost all of them, 96 percent, had used a pregnancy or health app that had a documented privacy violation at some point. That number stuck with me because it looks like It is not a niche problem.

So I am curious how other founders and builders here think about this. Do you treat privacy as a feature you add later, or as something that shapes the architecture from day one? And for anyone who has used health apps as a user, has a privacy issue ever changed which app you trust or which one you deleted?

View all

Zorya - Pregnancy Tracker

Private pregnancy tracker. No cloud, no accounts.

Private pregnancy tracker. No cloud, no accounts.

Forum Threads

What do you think about data privacy when building or using health apps?

Forum Threads

What do you think about data privacy when building or using health apps?