How to stop Clue training AI on your data
What the policy itself says, plan by plan. Where Clue 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 Clue Plus)
The AI features are opt-in on explicit consent under Article 6(1)(a), and the policy is unusually careful about where the data does not go: "No data is shared with the operators of other Foundation models or the provider of the LLM", and "No data is transferred to Anthropic". That is better than most of this category manages. The gap is in the quoted sentence. Clue operates its own Foundation Model "trained by Clue" and never says what it was trained on. For an app holding cycle dates, symptoms and sexual activity, the difference between processing that data and learning from it is the question, and consent to the first is not consent to the second. Two passages come close enough to be worth naming. Records of AI interactions — "user queries, contextual information used to generate responses, evidence packets and generated outputs" — are retained and used to "operate, maintain, secure and improve AI functionality, identify failure modes, evaluate answer quality and develop future AI-supported functionality". And where information derived from those interactions "is used to improve predictions, develop new algorithms or create more valuable features", the policy routes it into its health analytics purpose, whose consent text reads: "I agree to the health data I track in the app being processed for analytics purposes so Clue can improve my predictions, develop new algorithms and create more valuable features with personalized insights." That processing is de-identified, kept on EU servers, and happens only "if you have toggled this on in your privacy settings". Developing algorithms from health data you opted into is not nothing — but it is not a statement that your data trains the Foundation Model, which is the question this entry is unclear about, and Clue's own careful drafting elsewhere shows it can say so plainly when it means to.
Did a step here not work, or does Clue offer a control this page doesn't mention? Tell us and we'll correct it.