Privacy First

Your health data
is none of our business.

GlucoHome was built by someone who believes that the most sensitive data you produce — what your blood is doing at 3am — should belong entirely to you. Not to a device company. Not to an app. Not to us.

Self-hosting isn't a feature. It's the architecture that makes this privacy guarantee technically possible.

Data flow

Your Dexcom G7
Dexcom API
Dexcom API
Your GlucoHome server
Your GlucoHome server
Your MySQL database
Your browser
Your GlucoHome server(reads only)
kl8techgroup servers are never in this path

Our commitments

Six privacy principles we don't compromise on

We never see your health data

Your glucose readings, ketone logs, event history, and HbA1c trends are stored exclusively in the database you run on your own infrastructure. GlucoHome's servers — run by kl8techgroup — are never in the data path. We serve you the application code. That's it.

No tracking, no analytics, no ads

GlucoHome contains zero third-party analytics scripts, no advertising pixels, no session recording tools, and no behavioural tracking of any kind. We don't know what pages you visit, what features you use, or how long you spend in your dashboard.

Your Dexcom credentials are never touched

The Dexcom OAuth 2.0 connection goes directly between you and Dexcom. GlucoHome never sees your Dexcom username or password. We store only the OAuth access token — in your database — used to fetch your readings from Dexcom's API on your behalf.

Open source — audit everything

GlucoHome is fully open source. Every line of code that runs in your self-hosted instance is publicly available on GitHub. You can inspect exactly how data flows, how OAuth tokens are handled, and what SQL queries run against your database. No black boxes.

You control retention, backups, and deletion

Your data sits in your MySQL database. You decide how long readings are retained. You decide when and how to back it up. You decide what to delete. There is no data deletion request form — you have root access to your own data.

Google sign-in — limited scope

GlucoHome uses Google OAuth for user authentication only. We request the minimum OAuth scopes needed: your name and email address, used to create your account. We do not request access to your Google Drive, Gmail, contacts, or any other Google service.

The bigger picture

Why health data privacy matters more than you think

Your glucose data is some of the most intimate data you generate. It reveals when you eat, how you sleep, how you respond to stress, and whether you're managing a chronic condition. In the wrong hands, it could affect insurance, employment, and financial decisions.

Yet most diabetes tech companies are cloud-first by default — your readings go to their servers, are retained under their policies, and may be shared with third parties for "research", "product improvement", or in response to legal demands.

GlucoHome is a different architecture from the ground up. We're not a cloud company with a privacy policy that limits our liability. We're an open-source application that runs on your hardware — which makes the privacy guarantee technical, not just contractual.

If we can't access your data, we can't breach it, sell it, or hand it over.

Learn what GlucoHome does with your data →

Ready to own your health data?

Set up GlucoHome on your own server and take control of your glucose data for good.