I asked Google about its new multi-year partnership with Flo Health, in light of privacy concerns

Google’s newly announced multi‑year partnership with Flo, the global women’s health app, promises “personalized experiences” but also revives a settled lawsuit over undisclosed data sharing, raising immediate concerns for anyone whose health metrics are already streamed to wearables and cloud services.

Data Integration Between Flo, Fitbit, and Google Health

The briefing detailed that Flo’s menstrual, ovulation, and pregnancy data will be fed through Fitbit Air sensors into the Google Health platform, where an AI‑driven “Health Coach” may surface insights. This pipeline effectively merges three distinct data silos—Flo’s app database, Fitbit’s biometric stream, and Google’s cloud analytics—into a single user profile. The result is a richer, AI‑curated health narrative that can be accessed via Google’s upcoming premium services.

Google emphasized that the partnership will “sync Google Health with Flo for deeper insights,” suggesting that the AI chatbot will draw on real‑time cycle tracking to tailor recommendations. By embedding Flo within the broader Google Health ecosystem, the company can leverage its massive compute resources to generate predictive models that were previously limited to generic fitness metrics. The technical implication is a shift from isolated health apps to a unified, cross‑platform intelligence layer.

Legal Settlement and Its Immediate Financial Impact

In the background of the announcement, Google and Flo agreed to a $56 million settlement after users alleged that period‑tracking data had been shared with Google and Meta without consent. The lawsuit claimed that Flo’s in‑app software development kits transmitted sensitive health information to third parties between 2016 and 2019. Reuters reported that an additional $3.5 million came from the now‑defunct mobile analytics firm Flurry, underscoring the breadth of the data‑sharing network.

Meta chose to fight the allegations but was found liable under the California Invasion of Privacy Act, a ruling that did not affect the joint settlement between Google and Flo. The financial outlay signals that regulators and courts are willing to impose substantial penalties when health data leaves an app’s perimeter unnoticed. For the industry, the case sets a precedent that any partnership involving biometric or reproductive data must be transparently disclosed and legally vetted.

Privacy Risks Inherent in Health‑Tracking Ecosystems

The core risk stems from the fact that Flo’s SDKs previously allowed data to flow to external servers “without their knowledge or consent,” as alleged by plaintiffs. When such SDKs are embedded in a widely used health app, the sheer volume of users amplifies the exposure, turning personal cycle information into a commodity for advertising or AI training. This dynamic illustrates how “big tech’s MO to collect an enormous amount of information” can extend into intimate health domains.

Even with the settlement, the partnership creates a new avenue for data aggregation: Google Health will now host Flo’s reproductive metrics alongside activity logs from Fitbit devices. The convergence of these datasets enables cross‑referencing that could reveal patterns about a user’s lifestyle, location, and even mental health, all without explicit, ongoing consent. Consequently, users must grapple with the trade‑off between personalized AI insights and the erosion of granular privacy controls.

What This Actually Means For You

1. Expect your period and pregnancy data to appear in Google Health’s AI recommendations, potentially influencing suggestions for diet, exercise, and medication.
2. Recognize that the settlement does not erase the fact that your data was previously shared; historical records may still reside in Google’s analytics pipelines.
3. Understand that any future consent dialogs may be bundled with broader “personalized experience” terms, making it harder to opt out of specific data flows.
4. Anticipate that third‑party services linked to Google Health (e.g., premium coaching) could monetize your health insights in ways that are not immediately visible.
5. Monitor regulatory updates, as additional state‑level privacy statutes may impose new disclosure requirements on the Google‑Flo integration.

Immediate Action Steps

Review the privacy settings in both the Flo app and Google Health immediately; disable any optional data sharing toggles that allow automatic syncing with external services. If the apps do not offer granular controls, consider exporting your health data and deleting the account to prevent further aggregation.

Stay informed about any follow‑up communications from Google or Flo regarding the partnership; they are legally obligated to disclose changes to data handling practices. Document any consent prompts you encounter and retain screenshots as evidence should future disputes arise.

Frequently Asked Questions

How does the Google‑Flo partnership affect my existing Fitbit data?

The partnership routes Fitbit Air sensor readings into Google Health, where they will be combined with Flo’s cycle tracking to generate AI‑driven health insights.

Did the $56 million settlement cover all users affected by the data‑sharing lawsuit?

The settlement was a lump‑sum payment to resolve claims from users who alleged unauthorized sharing; it does not retroactively delete data already collected.

Can I opt out of having my Flo data used by Google’s AI Coach?

Current settings allow you to disable syncing between Flo and Google Health, but the partnership’s default terms may require acceptance of data use for full feature access.

What Do You Think?

Is the promise of AI‑personalized health worth the potential loss of intimate data control in a system that has already breached trust?