Legal
Privacy Policy
Effective [date] · Betawise is operated by [company legal name] ("Betawise", "we", "us").
Glucose readings and related information are health data. Our Consumer Health Data Privacy Policy describes how we handle them under laws such as Washington's My Health My Data Act, and applies alongside this policy.
The short version
- Files you import are analyzed in your browser and saved in your browser's storage. They are not uploaded to our servers. There is no Betawise account.
- If you connect Nightscout, our server requests your readings from your Nightscout site and passes them to your browser without keeping a copy.
- AI explanations are off until you turn them on. If you consent, summary statistics, logged-meal summaries, optional details from Settings and your chat messages are sent to our AI provider. Raw readings and their timestamps are not sent. Anything you type in a message is sent as written.
- No ads, no selling, no tracking. We don't sell or rent your information, show ads, or use third-party analytics or advertising trackers. We keep anonymous counts of how features are used, with no cookies or IDs.
- Email is optional. If you sign up for check-ins, we keep only your email address, separate from any glucose data.
- You can delete everything with one button in Settings.
What we handle, and where it goes
Glucose data you upload
When you upload a CGM export (for example from Dexcom Clarity or LibreView), the file is read and analyzed in your browser. Its readings, and any carbs or insulin entries it contains, are saved in your browser's local storage on that device so the app works when you come back. They are not sent to our servers.
Sleep data you import
If you import a sleep export from Oura or WHOOP (or another file with sleep start and end times), it is read in your browser and the sleep start and end times, time asleep and naps are saved in your browser's storage. Betawise uses them to show when you were asleep on your charts and to compare glucose on different nights. Sleep data is not uploaded to our servers and is not sent to the AI provider. You can remove it in Settings.
Nightscout connection
If you connect your own Nightscout site, your browser saves its address and the read-only access token you provide. When you load or refresh data, your browser sends them to our server, which requests your recent glucose readings and logged carbs and insulin from your Nightscout site and passes them straight back to your browser. We do not keep a copy, and we never ask for your Nightscout API secret. You can disconnect in Settings.
Information you type in
Settings lets you add optional details such as your diabetes type, therapy and goals. These are stored in your browser. If AI explanations are on, they are included in AI requests so answers can reflect them.
AI explanations
AI explanations are off until you agree to share information with our AI provider; Betawise asks the first time you use them, separately from accepting the Terms. Once you agree, when you generate an AI summary or send a message, your browser sends our server: summary statistics (such as time in range, averages and detected patterns), a summary of logged meals, the optional details from Settings, and the messages in your current conversation. We forward this to our AI provider, Anthropic, to generate a reply. We do not store AI conversations on our servers. Under its commercial terms, Anthropic does not use this information to train its models, and may retain it for a limited time to operate and secure its service.
Please don't include your name or other identifying details in messages. If you withdraw consent, future sharing stops; information already sent is not automatically removed from the provider.
Technical information
Our hosting provider, Netlify, processes standard request information such as IP addresses to deliver the site and protect it from abuse. Our AI and Nightscout functions use IP addresses briefly, in memory, to limit how many requests one visitor can make. Fonts and all other site files are served from betawise.org itself.
Anonymous usage counts
To learn which features help, Betawise counts events such as "a page was viewed", "a sample member was opened", "data was loaded" or "a pattern was tracked". We store only daily totals. Once a week, the app also reports how many weeks it has been since that device first used Betawise, so we can see whether people come back. Your browser keeps the date of its first visit on your device; it is never sent, only the week number.
These counts contain no glucose data, no messages, and nothing that identifies you or your device: no cookies, no IDs, and no stored IP addresses. If your browser sends a Global Privacy Control or Do Not Track signal, Betawise sends no usage counts at all.
Cookies
Betawise sets no cookies.
Email updates
If you sign up for the two-week check-in, we collect only the email address you enter. Netlify, our hosting provider, receives and stores the sign-up for us. We use your address only to send Betawise check-ins and product news, and we never sell or share it for advertising. Every email has an unsubscribe link, and you can ask us to delete your address at any time. Signing up is separate from the app: your glucose data is never linked to your email address.
Calendar reminders
If you add a weekly reminder, Betawise creates a calendar file on your device. You add it to your calendar yourself; we never see your calendar.
Who we share information with
We never sell, rent or trade your information. We share it only with:
- Netlify, which hosts the site, runs our server functions and stores email sign-ups.
- Anthropic, which generates AI explanations from the information described above, if you turn them on.
- Your own Nightscout site, only if you connect it; we request your data from it using the token you provide.
- Authorities, if the law requires it, and then only what is required.
Your choices
- Delete: Settings → "Delete data saved in this browser" removes the readings, settings and history Betawise saved in this browser. It does not delete files you downloaded or information already sent to the AI provider.
- Export: Settings → "Export my data" downloads a copy of your data as a file you control.
- Don't use AI explanations, or turn them off: Settings → "Turn off AI explanations" stops future sharing. Imported files are analyzed without sending your health data to our servers.
Because your data lives on your device, clearing your browser's site data also deletes it. If you have questions or want to exercise rights under laws such as Washington's My Health My Data Act or the California Consumer Privacy Act, contact us at [contact email].
Security
The site is served only over HTTPS, and uses a strict content security policy so the pages can only load code and data from betawise.org. No system is perfectly secure, and anyone with access to your unlocked device and browser can see data saved there.
Children
Betawise is for adults 18 and older using their own data. It is not designed for reviewing children's data, and we don't knowingly collect personal information from children. If you believe a child has sent us information, contact us and we'll delete anything we hold.
Changes
If we change this policy, we'll update the date above. If we make a significant change to how we handle data, we'll say so in the app.
Contact
[company legal name] · [mailing address] · [contact email]