CarbSnap sends carbohydrate, insulin and override commands to a Nightscout site you run, which forwards them to a Loop app you built. It is a thin, deliberately small piece of plumbing between an AI assistant and software you already operate. This page describes exactly what it keeps.

What CarbSnap stores

Data	Why
Your email address and name, from Google	To know who you are and who took an action
The first name you give the person you are managing	So the interface can say "Liam" rather than an id
Your Nightscout address	To know where to send commands
Your Nightscout API secret and Loop one-time password key	Required to send a command at all. Encrypted with AES-256-GCM before storage.
Your safety limits	To refuse a command that exceeds them
A log of every command attempted, including refusals	So you can see what happened. One-time passwords are redacted from it.
Food descriptions and carbohydrate amounts you log	Your own record, and to eventually learn per-food absorption patterns

What CarbSnap does not store

• Glucose readings. They are read from your Nightscout at the moment a page is displayed and are never copied into our database. Your Nightscout already holds them.
• Photographs of food. Those are handled entirely by Claude or ChatGPT. CarbSnap never receives an image of a meal.
• The QR code from Loop's one-time password screen. That picture is decoded in your browser. Only the key inside it is transmitted.
• Payment details. There is nothing to pay for.
• Anything for advertising, profiling or resale. There is no analytics script, no tracking pixel and no third-party advertising code on any page.

Who else sees your data

Only the services required to make it work, and only what each needs:

Service	What it receives
Cloudflare	Hosting, database and network. All stored data lives here.
WorkOS	Sign-in. Your email address and name.
Google	Confirms who you are when you sign in. Google is told you signed in to CarbSnap; it is not told anything about the person you manage.
Your own Nightscout	The commands you send, which is the entire point.
Resend	Only when email is enabled: your address, to deliver a confirmation link.
USDA FoodData Central and Open Food Facts	The food name you typed, e.g. "pepperoni pizza". No identity, no glucose, no dose.

Your data is never sold, and never shared with anyone else.

Who can see your care circle

Only you, and anyone you explicitly invite. An invited caregiver can log carbs, request a bolus and start an override, and must accept the medical disclaimer themselves — consent is never inherited from whoever set things up. Only the owner can change credentials, limits, or membership. Every action is recorded against the person who took it.

Security, and its honest limits

• Credentials are encrypted at rest with AES-256-GCM, with a separate random initialisation vector per record, and are bound to the field they belong to so a value moved elsewhere fails to decrypt rather than quietly working.
• Sign-in is Google only. CarbSnap never sees, stores or transmits a password.
• All traffic is HTTPS.
• CarbSnap is not a HIPAA-covered entity and its infrastructure is not operated to HIPAA standards. It is a personal do-it-yourself tool, in the same spirit as Loop and Nightscout. Anyone who can read your Nightscout API secret can send commands to that Loop app, which is why the secret is encrypted and never shown again after you enter it.

Deleting your data

Turning off remote commands in settings stops every assistant immediately without deleting anything. To have your account and all associated records removed, email jay.winters@clearjet.com. Deletion removes your stored credentials, care circle, audit log and food log.

Changes

If this page changes in a way that affects what is collected or who receives it, you will be asked to review it before continuing to use CarbSnap.

Back to CarbSnap · Terms