InRange — Privacy Policy
Last updated 22 October 2026
InRange is a companion to a continuous glucose sensor. It reads glucose values your own sensor app has already recorded, matches them to meals you log, and shows what each meal did. It does not measure glucose itself, does not estimate or predict anything, and gives no medical advice. It is not a medical device.
This policy describes what the app does with your information. The short version: nothing leaves your phone unless you ask for something that needs it: a share, a backup, a dish named from a photograph, a weekly plan, or a packet looked up by its barcode. Each of those is described below. From version 1.1 two more things happen without your asking: the app counts which screens and features are used, and it keeps the record of a subscription. Neither carries anything you log, and both are described below.
Who is responsible
InRange is published by Tugay Demir. Questions about this policy or about your data: privacy@getinrange.app.
What stays on your phone
Your glucose readings, the meals you log, their photographs, activities, insulin doses, notes and every figure derived from them are stored on the device. They are not uploaded unless you share them or back them up, as described below.
Meal photographs are kept in the app's own storage, with iOS file protection on an iPhone and the app's private storage on Android. Deleting a meal deletes its photograph.
What leaves your phone, and only if you ask
Sharing with another person
If you create a share code and someone accepts it, the readings, meals, activities, doses and notes inside the window you chose, with your name and your target range, are copied to InRange's server so that person's phone can read them. They see only that window, enforced by the database rather than by their app. A dietitian or clinician you share with can write a note into your record; it carries their name, and you see it in your own day. Ending the share stops all of this. When the last share ends, or when you use Delete server copy in Settings › Data & privacy, the server copy is removed.
Signing in to share or back up uses Sign in with Apple on an iPhone and Sign in with Google on Android. Your account holds the email address Apple or Google gives InRange (Apple's can be a private relay address), the name you chose, and the target range and sleep hours your figures are read against.
Backup
If you sign in and switch backup on, your record is stored under your account so it survives a lost phone. It is used for nothing else. The same delete removes it.
Meal photographs and recognition
Naming a dish from a photograph is off until you say yes. InRange asks before the first photograph is ever sent, and the answer can be changed at any time in Settings › Data & privacy › Name dishes from photos. If you say no, the photograph stays on your phone and you name the dish yourself; nothing else changes.
If you say yes, each meal photograph passes through InRange's server, which forwards it to Google's Gemini service to name the dish and keeps no copy of it. The answer is a name, never a number — InRange does not estimate carbohydrate from a photograph.
So that a daily limit can be counted without asking you to register, the app creates an anonymous identifier for itself. It is not linked to your Apple ID or Google account, your name or anything you log. The server keeps only how many photographs that identifier sent today, for a week, and removes identifiers that have not been used for a month.
What Google does with a photograph is governed by its own terms, which on the service InRange uses allow Google to use what it is sent to improve its products. We cannot promise on Google's behalf that the picture is used for nothing else, and we will not pretend otherwise. If that matters to you, leave the setting off: typing the dish name gives you exactly the same app.
The weekly plan
A weekly plan is also off until you say yes. InRange asks the first time you ask for one, and the answer can be changed in Settings › Data & privacy › Weekly plans from your dishes. If you say yes, the names of your dishes and the figures measured after them (how far each rose, when it peaked, how long it took to come back) are sent the same way to Google's Gemini service, which arranges them into a week. Nothing else from your record is sent, nothing is kept on our server, and a plan is only ever made when you ask for one.
Barcodes
When you scan a packet, the barcode — and nothing else — is sent to Open Food Facts, a public food database, to look up what the label declares. No account, no identifier and no other data is sent. Products you have scanned are then kept on your phone so the same packet needs no second lookup.
Apple Health
If you choose Apple Health as your source, InRange reads blood glucose, and optionally workouts and insulin, from Health. It never writes to Health. Health data is never used for advertising or data mining and never sold, as Apple's guideline 5.1.3 requires. It reaches a third party in one case only, and only with your permission: the measured rises a weekly plan is arranged from, described above. It also reaches the people you choose to share your record with. You can withdraw access at any time in the Health app.
Health Connect (Android)
On Android, if you choose Health Connect as your source, InRange reads blood glucose, and optionally exercise, steps and active calories, from Health Connect. It never writes to Health Connect. InRange's use of data received from Health Connect adheres to the Health Connect Permissions policy, including its Limited Use requirements: it is used only to show you your own record and the analysis built from it, it is never used for advertising, never sold, and never used to build a profile of you. It reaches a third party in one case only, and only with your permission: the measured rises a weekly plan is arranged from, described above. It also reaches the people you choose to share your record with. You can withdraw access at any time in Health Connect › App permissions › InRange.
LibreLinkUp and Nightscout
If you connect LibreLinkUp, your Abbott credentials are stored in this phone's keychain on an iPhone, or in encrypted storage on Android, and are sent only to Abbott's own servers. If you connect Nightscout, the site address and read token you enter are stored on the phone and sent only to the site you named — which is yours, not ours. InRange only ever reads from either; it never writes.
Notifications
Most of InRange's notices are made on your phone and never touch a server. Two things use one:
- If you are signed in, Apple (on an iPhone) or Google's Firebase Cloud Messaging (on Android) issues this phone a device token, which is stored on InRange's server with the phone's time zone, language and glucose unit. It lets the server ask your phone, silently, to send its latest readings when a person you share with is waiting for them. The token identifies the device, not you, and signing out deletes it.
- If you follow someone and ask to be told when one of their meals is still high two hours later, the server checks their shared readings and sends that notice to your phone, written in your language and unit. It is off unless you turn it on.
Usage counts
From version 1.1, InRange uses Firebase Analytics, a Google service, to count which screens are opened and which features are used: that a meal, a dose or a note was logged, never what was entered; that the subscription screen was opened and how a purchase ended; and where the app stands between its free week and a subscription. The counts are held against an identifier Firebase creates for this installation of the app. It is not your name, your Apple ID or your InRange account, and it is not the advertising identifier. The iPhone app never reads the advertising identifier; the Android app reads it only to measure InRange's own advertising, described below.
One of the things counted says something about you: who the app is for. It is one of three words (the person wearing the sensor, someone following one person, or someone looking after several), and it is sent so we can tell which of those groups the app is working for. No glucose reading, meal, dish name, dose, target, note or name of a person is ever sent to Firebase, and nothing sent to it is used to personalise advertising.
Measuring our own advertising (Android). InRange advertises itself on Google Ads. So that Google can tell which installations came from those ads, the Android app lets Firebase Analytics read the phone's advertising identifier and pass three facts to Google Ads: that the app was opened for the first time, that a free week started, and that a subscription was bought. Nothing you log is ever part of this, and no advertising is personalised from it. If you are in the European Economic Area, the United Kingdom or Switzerland, this is switched off. On any Android phone you can reset or delete the advertising identifier in Settings › Privacy › Ads.
Payments and the subscription
Version 1.0 sells nothing. From version 1.1, InRange is a subscription after one free week. The payment itself is made to Apple, with your Apple Account, or to Google Play, with your Google account; InRange never sees your card or your billing details. To know whether a subscription is active, and to restore it on another phone, the app uses RevenueCat, which receives the store's record of the purchase (the product, the dates, the price and the country of the storefront) against an anonymous identifier it creates for this installation. So that photo recognition and the weekly plan follow the same rule on the server, the app also writes one date to your row on InRange's server: the day your free week or your paid period ends.
On Android, the day your free week started is also kept with Google Block Store, in your Google account's own backup, so that reinstalling the app does not start a second free week. It holds that date and nothing else.
What we do not do
- No advertising inside the app. The iPhone app reads no advertising identifier; the Android app reads it only to measure InRange's own ads, as described above.
- No tracking across other companies' apps and websites, and no marketing tools.
- Your data is never sold, rented, or used to build a profile.
- InRange uses nothing you log to train a model. What Google may do with a meal photograph or a plan request is described above.
Who processes data on our behalf
How long anything is kept
On the phone: until you delete it or delete the app. On the server: only while a share or backup is active, and only within the window you chose. Daily counts for photographs and plans are kept for a week, and failed attempts to enter a share code for a day, so that codes cannot be guessed. Usage counts are kept by Firebase for 14 months, and the record of a subscription by RevenueCat for as long as the app is offered. Deleting the server copy, and deleting the account itself, are both immediate and both offered inside the app, without writing to us.
Your rights
You can export everything the app holds (Settings › Data & privacy › Export) as a spreadsheet or a PDF, delete the server copy from the same screen, delete your account outright (Settings › Account › Delete my account, which removes the account, its backup, every share, and, on an iPhone, this app's access to your Apple ID), and delete everything on the phone by removing the app. If you are in the EU or the UK you also have the rights to access, rectification, erasure, restriction, portability and objection under the GDPR; write to the address above and we will answer within 30 days.
Children
InRange is not directed at children under 13 and we do not knowingly collect their data. A parent watching a child's readings uses their own account, with the child's record shared to it by code.
This website
This section is about the website getinrange.app only. Nothing in it applies to the InRange app, and nothing you log in the app ever reaches the website.
The website uses Google Analytics to count visits and to see which pages people read. It records the pages you open, the links you follow (such as the App Store link or one of our email addresses), the country and city your connection comes from, your browser and type of device, and the page you came from. It never receives anything about your health. Google Analytics stores cookies in your browser so that a second visit is counted as the same visitor. It is never used for advertising, and Google signals and ad personalization are switched off.
If you are in the European Economic Area, the United Kingdom or Switzerland, Google Analytics only starts after you accept it in the cookie notice. Elsewhere it starts when the page opens. You can change your choice at any time with the button below, and if you decline, the cookies it stored are deleted. How Google itself handles this data is described in Google's privacy policy.
Changes
If this policy changes in a way that affects what leaves your phone, the app will say so before the change takes effect. The date at the top always reflects the current version.
Not a medical device
InRange shows information. It does not replace your sensor's own app. Glucose alarms, and every decision about insulin, belong there and with your clinician.