Privacy by architecture
Your account records sync to our servers so you can review them across devices. Core analysis uses your own records. Optional AI processing and sharing have separate disclosures below.
Notebook sharing is your choice
Notebook entries sync through your account. Only entries you explicitly select for visits and reports appear in reports and live sharing links. Deselecting an entry changes future reports and live links; it cannot recall downloaded or emailed copies.
Minimal activity records help us improve the app
We record the local days you visit, save entries, or create a report, and the time of your first saved entry that day. These account records contain no health values or note text. A reminder link sets an account-scoped cookie for 24 hours so we can count whether it led to a saved entry. These records are deleted when you erase your data or delete your account.
Public counts never point back to you
The totals on our How we count page are counted as anonymous events: a kind, a time, and a keyed hash that cannot be traced to your account. The day after an appointment you made a report for, we may email one question about whether it was used, unless that appointment's reminder is set to none. Your answer, and anything you choose to write about the visit, is stored with your account and deleted when you erase your data. We quote what you wrote only if you said we may, and only after a person has read it.
Analysis runs in the app, not in a data lake
Your insights, your weekly briefing, your note tags, your readings in range: core patterns are computed by plain functions inside the app, on your data alone. There is no ad-network pixel, no advertising cookie tracker, optional AI features are disclosed separately. Our hosting platform counts page visits in aggregate (cookieless and anonymized, never your readings) so we can tell which pages help. Turning a reading into meaning never requires sending it anywhere.
Your readings stay private to your account
SteadyRange keeps your glucose and BMI history in a database scoped to your account, not pooled into a shared dataset mined across users. Every query that touches a reading is filtered to your user ID, so one account can never see another's data.
We do not sell your health data or share it with advertisers
Your health data is not a product. We don't sell it, we don't hand it to advertisers, and we don't use it to train models. The report you generate for your doctor is built on the fly and handed to you, not retained for anyone else.
You can take it or erase it, anytime
Export a full backup from Settings whenever you like; child accounts can download their Family readings from Family. Main-account backups cover their own records, not independently owned family records. Download managed child readings separately from Family. Erase health data removes your logged health records and revokes report, calendar, and caregiver links while keeping your account, care-team records, care messages, settings, subscription, and Family memberships. It also removes records in child profiles you manage; it does not erase independently owned family records. Leave or remove a Family membership to stop record sharing. Delete account also removes your sign-ins, passkeys, caregiver access, and care messages, and cancels active subscriptions. Deleting a main Family account also deletes its managed child profiles and ends Family sharing and sponsored access; independent members keep their accounts and records. Backups are not erased immediately and their expiry window has not been verified. Security audit records and payment-provider transaction records remain; optional AI processors have separate deletion limits. Copies you or recipients have already downloaded or received by email cannot be recalled.
The one exception, stated plainly
The optional AI features are the exception: when you use one (scanning a lab photo or a meal, asking the assistant a question, importing an unrecognized file, or turning on AI summaries in Settings), the photo or the relevant summary of your readings is sent to an AI service to produce that one answer, with provider-dependent retention. SteadyRange doesn't store the images. Every one of these is something you invoke or switch on yourself; account records sync to our servers; optional AI requests are separate.
Optional AI and retention
When you invoke an AI feature or enable AI summaries, photos, questions, transcripts, file contents or a relevant health-record summary can be sent through our server to the configured processor. SteadyRange does not store uploaded scan images, but provider deletion is separate. Review the provider terms before submitting sensitive information.
OpenAI
API data is not used for training by default. Abuse-monitoring retention is generally up to 30 days, with exceptions and endpoint-specific storage. No approved zero-retention configuration is claimed here.
Provider data policyxAI
Optional voice parsing can send a transcript when rule-based parsing fails. API retention depends on account configuration; zero retention has not been verified.
Provider data policy- Live health records
- Erase health data removes logged health records from the live database and revokes report, calendar, and caregiver links. Account settings, care-team records, care messages, and subscriptions remain. Account deletion also removes sign-ins, care messages, and caregiver access and cancels subscriptions.
- Database backups
- Provider-dependent expiry. The deployed backup window has not been verified; deletion does not immediately erase provider backups.
- Security audit records
- Retained after deletion. The operator has not yet published a verified retention period.
- Payment records
- Stripe retains transaction records under its legal and contractual obligations; deleting SteadyRange does not delete those records.
- Optional AI requests
- Provider-dependent retention and deletion limits. No zero-retention configuration is claimed. Generated answers may be saved in your account.
- Recipient copies
- Previously downloaded reports, screenshots and delivered email cannot be recalled.
Disclosure updated September 30, 2026. Production processor contracts and retention settings still require operator verification.
How we measure product use
We use Vercel Analytics for page counts and events such as completing setup, saving a first entry, returning within seven days, preparing a report, and upgrading. Event properties contain fixed page or source labels, not readings, doses, names, email addresses, or account identifiers. Query strings are removed and private report, care, verification, and clinic pages are excluded.
For new users, this browser keeps a small account-scoped progress marker to avoid repeating milestone events and remember which free tool led to signup. The marker stays on your device; it is not an advertising cookie. Clearing browser storage resets it. Blocking analytics does not affect tracking your health.
Promises are the easy half. The" "security page" " is the checkable half: where the data runs, which companies touch it, what a deletion removes, and who to email when something is wrong.
Open-source credits
The exercise picker uses names, muscles and instructions from the exercises-dataset by Hasan Emir Yıldırım, and the muscle map draws its body silhouette from MuscleMap by Melih Colpan. Both are MIT licensed; the full notices live in the project's third-party notices file. No exercise images or animations are used.
This page describes how the product is built; it isn't legal or medical advice. Learn the terms behind your numbers in the" "glossary.
A calmer, more private way to track
Glucose and BMI in one quiet log, with insights that stay on your side. Start free. Export or erase anytime.
Responsible operator
The responsible operator's legal name has not yet been published.
Contract jurisdiction has not yet been published; legal review is pending.
For privacy rights, deletion questions, billing or business contact: hello@steadyrange.com.