Dexcom’s Data Policy Update — What Actually Happened & Why Everyone Is Furious

Dexcom rolled out a new data policy update to G7 users — and they did it in the worst possible way. Mid-sensor. Mid-day. A message blocking access to blood sugar readings with two options: accept a policy update that most people will never read, or delete the app. No warning. No window to prepare. Just a screen standing between a diabetic and their numbers. Graham and I break down what we know about what actually happened, what the policy likely contains, and why the outrage isn’t really about Dexcom taking data — it’s about how they did it and what they won’t clearly say about where that data is going. 🔑 Key Takeaways What Dexcom’s data policy rollout actually looked like — and why it was handled so badly. Why the real problem isn’t the data collection — it’s the messaging and the lack of transparency. What Dexcom is likely trying to build with aggregated CGM data — and why that’s actually interesting. Graham’s theory on AI supplementing inaccurate CGM readings in real time. Why Ken thinks Dexcom is working toward photo-based carb tracking inside the app. The GlucoseSense app — what it does and why Ken uses it every day. The darker possibility — individual medical avatars built from aggregated data and what that could mean for insurance coverage. Why the G7 accuracy decline has been the real story all along — and why nobody made this much noise about it. #Type1Diabetes #Dexcom #DexcomG7 #CGM #DiabetesTech #DataPrivacy #T1D #ContinuousGlucoseMonitor #DiabetesManagement #HealthyDiabetic