Legal

Privacy Policy

Effective [date] · Betawise is operated by [company legal name] ("Betawise", "we", "us").

The short version

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.

Dexcom connection

If you connect a Dexcom account, you sign in on Dexcom's own website; we never see your Dexcom password. Dexcom gives us a token that lets us fetch your recent glucose readings. That token is stored in a secure, HttpOnly cookie on your device for up to 90 days. When the app refreshes your data, the readings pass through our server on their way to your browser. We do not keep a copy. You can disconnect at any time 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. They are included in requests to the AI coach so it can personalize its answers.

The AI coach

When you generate a weekly insight 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 your coach 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 coach messages.

Technical information

Our hosting provider, Netlify, processes standard request information such as IP addresses to deliver the site and protect it from abuse. Our coach uses 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.

Cookies

Betawise sets cookies only to connect Dexcom: the token cookie described above, and a short-lived cookie that protects the sign-in step. We use no analytics or advertising cookies.

Who we share information with

We never sell, rent or trade your information. We share it only with:

Your choices

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, uses a strict content security policy, and keeps the Dexcom token out of reach of page scripts. No system is perfectly secure, and anyone with access to your unlocked device and browser can see data saved there.

Children

Betawise is not intended for children under 13, and we don't knowingly collect information from them. Teens should use Betawise with a parent or guardian.

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]