ZORYA

A court approved a settlement this year over how Flo handled the most private information its users ever typed into a phone.

If you use Flo and somehow missed the news, here is the short version. The Federal Trade Commission reached an earlier settlement with Flo Health over claims that the app shared sensitive health data, including information about pregnancy and periods, with companies like Facebook and Google, despite telling users that data would stay private. Separately, a class action lawsuit covering past users resulted in a settlement of around 59.5 million dollars, approved by a court this year. Together, the two cases paint a consistent picture: an app marketed as private was, for a meaningful stretch of time, sending detailed health signals to advertising platforms without the kind of clear consent most users assumed they had given.

What actually changed, and what did not

A settlement is not the same as a rebuild. It resolves a legal claim and, in cases like this, compensates past users for what already happened. It does not retroactively make the original data sharing disappear, and it does not automatically mean the underlying business model has changed in a fundamental way going forward. Settlements like this are often the end of a legal process, not necessarily the start of a different one.

If you have used Flo at any point over the past several years, it is worth checking whether you fall within the class covered by the settlement, since compensation has been part of the resolution. But the more useful question, longer term, is what you want happening to the information you are logging right now, today, in whatever app sits on your home screen.

It is also worth being honest about how these cases usually unfold from the outside. A settlement announcement generates a wave of news coverage, a short window of public attention, and then, for most users, nothing changes about their daily habits at all. People keep the app installed because switching feels like effort, because their logging history lives there, or because they simply have not connected the legal news to their own account in any concrete way. That gap, between what gets reported and what actually changes in practice, is exactly why the pattern keeps repeating across this category of app.

The pattern behind the headline

This is not really a story about one company having a bad year. It is a pattern that shows up across the femtech space: an app collects detailed, sensitive data, monetizes that data through advertising partnerships or data sharing agreements, and eventually faces regulatory or legal consequences once the practice becomes public. Glow had a well documented data breach in 2016 that exposed millions of user records. Ovia Health drew scrutiny in 2019 over pregnancy data being shared with employers through corporate wellness programs. Flo settled with the FTC and, now, with a class of its own users.

The common thread is not that any one of these companies is uniquely careless. It is that the business model, free app, funded by data, creates a structural incentive to collect more than users realize and to monetize it in ways that are disclosed in language few people actually read. Settlements happen after the fact. They do not change the incentive that caused the problem in the first place, because the app is usually still free, still funded by something, and still subject to the same pressure to find new revenue the next time growth slows.

A different starting point

Zorya was built with a different premise from the start: if there is no backend, there is nothing to share, sell, or eventually have to settle a lawsuit over. Every entry you log, from kicks to symptoms to weight, stays in local storage on your own device. There is no account to create, no server receiving your data, and no third party integration quietly riding along in the background. The app earns money through an optional one time tip, not through a pipeline that depends on your information being valuable to someone else.

This is not a claim that needs a settlement to prove itself years from now, because there is no mechanism in place for the thing a settlement like this addresses. You cannot settle a lawsuit over data sharing when the data never left the phone.

If you are weighing whether to keep using Flo, switch to something else, or simply want a clearer picture of what any pregnancy app does with your information, the Flo settlement is a useful reminder to actually read what you agreed to, wherever you are logging. And if a symptom or question comes up along the way, that conversation still belongs with your midwife or care team, not with any app on your phone.

It is also worth remembering that switching apps mid-pregnancy is a far smaller task than it feels like in the moment. Most of what matters, your weekly milestones, your own memory of how you have been feeling, your appointment schedule, lives in your head and in your records with your care provider, not inside any single app. A tracker is a convenience for noticing patterns and holding notes, not the record of your pregnancy itself. If the way a company handles your data has made you uneasy enough to consider leaving, that unease is reasonable information in its own right, worth acting on rather than talking yourself out of because the switch feels inconvenient.