How to stop Flo training AI on your data
What the policy itself says, plan by plan. Where Flo publishes the steps, they're here in its own words, read from an archived copy of the page that gives them. Where it doesn't, this page says so instead of inventing a menu path.
All accounts (free and Premium)
This is menstrual and reproductive health data, about as sensitive as consumer data gets, and the policy is specific about where it goes. A named sub-processor, Tecton, Inc., described as a "Machine Learning Development Platform", receives "Personal data relating to cycle dates, goals, symptoms" for cycle predictions, retention forecasting and content. The word "train" isn't in the policy's 46,000 characters. The Privacy Portal FAQ asks the question in its own heading, whether your personal data is used to train Flo's AI, and answers about third parties: "Your personal data is not used to train third party AI models." Of Flo's own cycle-prediction models it says nothing. One Flo document does. A newsroom post from March 2021, republished from the AWS Startup Blog, quotes Flo's CTO on training models "on Flo's large user population" from the period dates, symptoms and metadata people log. Those are the company's own words, five years old, and no later document repeats or withdraws them. No opt-out is stated anywhere. As with Replit, the entry stays UNCLEAR while Flo is asked whether the 2021 statement still describes the app.
Did a step here not work, or does Flo offer a control this page doesn't mention? Tell us and we'll correct it.