Privacy Policy

What we collect across our websites and the Beta Cell Lab Notes app, why, who else handles it, and how to have it deleted.

Last updated October 14, 2026

The short version.

  • We use no advertising or analytics cookies and no tracking pixels. The one cookie we set keeps you signed in to the Education Hub, and your browser deletes it when it closes.
  • We collect personal information only when you give it to us: an Education Hub account, a pin on the Member Map, a trip lottery entry, or a message to us.
  • Some of it can be health information, like what you write in a course reflection. We use it only to provide the thing you asked for. We never sell it or use it for advertising.
  • Donations, newsletter sign-ups and trip tickets happen on Zeffy’s own site, under Zeffy’s policy. We never see your card details.
  • You can delete your Education Hub or Member Map account yourself at any time. For anything else, email us and we’ll delete it.
  • The Beta Cell Lab Notes app sends us nothing at all. See the app section.

Beta Cell Foundation (“BCF,” “we”) is a 501(c)(3) nonprofit, EIN 84-4054715, at 4254 W. 5th Street #7, Los Angeles, CA 90020. This policy covers betacellfoundation.org, T1Ds in the Wild (wild.betacellfoundation.org), the Education Hub (learn.betacellfoundation.org), the Type One Run Member Map (map.betacellfoundation.org), and the Beta Cell Lab Notes app. Washington and Nevada residents: see also our Consumer Health Data Privacy Policy.

What we collect, site by site.

On every site

  • Server logs and traffic counts. Our host, Netlify, logs each request (including your IP address and browser type) to deliver and protect the sites, and gives us traffic reports built from those logs: page views, top pages, referring sites and countries. We see only the totals. No cookies are involved.
  • Fonts and code. Our typefaces and code libraries are served from our own sites, so loading a page doesn’t contact Google or any other font or code service.

betacellfoundation.org

  • Contact form. Your name, email, topic and message. Netlify stores the message and forwards it to us, and screens it for spam, so we can reply.
  • Simulators. They run entirely in your browser. Nothing you enter is sent anywhere or saved.
  • Type One Run page. It shows the Member Map, described below. Its podcast buttons take you to Apple Podcasts or Spotify, under their own policies.

Education Hub (learn.betacellfoundation.org)

Every course can be read without an account. If you create one, we keep:

  • Your email address, to send you sign-in links (there is no password) and to tell your account apart.
  • Your course activity: the courses you join and the sections you finish, so you can pick up where you left off.
  • What you write: your reflection answers and your goals, notes and reflections. These can include health information, such as your insulin-to-carb ratio or how exercise moves your blood sugar. The Hub shows them only to you; our admin tools don’t display them.
  • One sign-in cookie, which keeps you signed in and is deleted when you close your browser. (Browsers set to reopen your last session can restore it.) It is strictly necessary for the sign-in you asked for, so it needs no consent banner.
  • A bot check. The sign-in form uses Cloudflare Turnstile, which looks at your IP address and browser signals to tell people from bots.

While the Hub is in preview it sits behind a site password, and our host may set a strictly necessary cookie to remember that you’ve entered it.

Type One Run Member Map (map.betacellfoundation.org)

Anyone can view the map, and it shows only how many members are in each city. If you add yourself, we keep:

  • Your email address, to send you sign-in links (there is no password) and so the people below can reach you.
  • The city, state or region, and country you type, never a street address. We turn it into that city’s map coordinates using OpenStreetMap’s Nominatim service. The lookup is made from our server, so Nominatim sees the place name but not your IP address or email.

Who sees your email: BCF’s map administrators, and, only if you tick the box for it when you save your city, the Type One Run chapter leader for your area. A chapter leader is a member BCF has appointed to organize local runs, who can see the email and city of members within 80 km (50 miles) of their own pin who have agreed. You can change your answer whenever you save again. Members who joined before we asked (October 2026) stay visible to their chapter leader until they next save. Visitors to the map never see your email.

  • No cookies. Your sign-in is kept in your browser’s storage for that tab only and is gone when you close it.
  • A bot check. The sign-up page uses Cloudflare Turnstile, as above, which loads only once you start entering your email.
  • Map tiles. Your browser loads the map’s background tiles from CARTO, so CARTO receives your IP address.

T1Ds in the Wild (wild.betacellfoundation.org)

  • Browsing needs no account and sets no cookies.
  • Trip lottery entries: your name, email, the trip, what you hope to get out of it, what you want to feel more confident about (which can include health information), and whether you want our newsletter. Netlify stores the entry, and a copy goes to a Google Sheet that only BCF staff can open, so we can draw names and email everyone the result. If you ask for the newsletter, we add you to our list.
  • Ticketed trips register on Zeffy, below.

Donations, newsletter and tickets (Zeffy)

Our Donate, newsletter and Register buttons open Zeffy’s own pages in a new tab; nothing from Zeffy loads on our pages. Zeffy collects what you enter there, including payment details, and sets its own cookies, under Zeffy’s privacy policy. Zeffy passes us your name, email and the details of your gift, sign-up or ticket so we can send receipts, newsletters and trip information. We never receive your card details. Newsletters are sent through Zeffy, and every one has an unsubscribe link.

Email and links elsewhere

Education Hub and Member Map sign-in links are emailed by Supabase, which runs those sites’ databases. When you email us, we keep the conversation so we can help you. Our Facebook group, our store on Bonfire, our Candid profile, the Beta Cell Podcast and Beta Cell Action are run under their own privacy policies.

Cookies and browser storage.

The only cookie BCF sets is the Education Hub sign-in cookie described above. The Member Map keeps its sign-in in your browser’s session storage for the tab. Both are strictly necessary for a sign-in you asked for, so neither needs consent, and neither is used for analytics or advertising. Our websites use no analytics cookies, advertising cookies, tracking pixels or cross-site tracking.

Two services named above can store data in your browser themselves: Cloudflare, on the sign-in pages with a bot check; and Supabase’s network, which may set a short-lived security cookie on supabase.co when you sign in. Sites you go to from ours, like Zeffy and Facebook, set their own.

Do Not Track and Global Privacy Control. We don’t track visitors across other sites, and we don’t sell or share personal information for advertising. Our sites therefore work the same whether or not your browser sends these signals, and we treat Global Privacy Control as an opt-out of any sale or sharing anyway.

Why we use it.

  • To provide what you asked for: your account, your map pin, your lottery entry, a reply to your message. (For EU and UK visitors, the legal basis is performance of our agreement with you.)
  • Health information you choose to give us (your reflections and goals, your lottery answers, and the fact that you’re on a type 1 diabetes map) is used only to provide that service, on the basis of your explicit consent. You can withdraw it at any time by deleting the information or your account.
  • To keep our sites running and secure: server logs, bot checks and spam screening (our legitimate interest in protecting the sites and the people who use them).
  • To send our newsletter, only if you sign up for it (your consent).

We don’t sell personal information, use it for advertising, build profiles of you, or make automated decisions about you.

Who else handles it.

These services store or process information for us, only to provide the parts of our sites described above:

  • Netlify: hosting, server logs, traffic counts, the contact form and lottery entries. Privacy policy.
  • Supabase: the databases and sign-in for the Education Hub and the Member Map, on Amazon Web Services in the United States (Oregon for the Hub, Virginia for the map). Privacy policy.
  • Cloudflare: the Turnstile bot check, and the network in front of Supabase. Privacy policy.
  • Google: the spreadsheet that holds lottery entries. Privacy policy.
  • OpenStreetMap Foundation (Nominatim): turns a typed city into map coordinates, from our server. Privacy policy.
  • CARTO: map tiles. Privacy policy.
  • Zeffy: donations, the newsletter and trip tickets, on its own site.

Otherwise we share personal information only with your chapter leader as described above, when the law requires it, to protect someone’s safety, or with an organization that takes over BCF’s work, in which case we’ll tell you first.

How long we keep it.

  • Education Hub and Member Map accounts: until you delete your account. Deleting it removes everything listed above from our live database immediately. Copies may remain in our providers’ routine backups for a short time, until those backups are replaced.
  • Lottery entries: until the trip is over and we’ve finished following up with entrants, then we delete them.
  • Messages to us: for as long as we need them to help you.
  • Donation and ticket records: for as long as tax and accounting rules require.
  • Server logs: for the period our host keeps them.

Your choices and rights.

  • Delete your Education Hub account from the My Progress page. This removes your email, your course activity, and everything you wrote.
  • Delete your Member Map account by signing in on the map and choosing Delete my account. This removes your email and your pin.
  • Unsubscribe from the newsletter with the link at the bottom of any issue.
  • Anything else (a lottery entry, a message, a copy of what we hold about you): email info@betacellfoundation.org.

Wherever you live, you can ask us to tell you what we hold about you, give you a copy, correct it, delete it, or stop using it. You can also withdraw any consent you’ve given. We’ll confirm the request comes from you, usually by replying to the email address we have, and respond within 30 days. If we turn a request down, we’ll tell you why. You can appeal by replying with “appeal,” and we’ll answer the appeal within 45 days. We will never treat you differently for using these rights.

EU and UK visitors can also object to or restrict our use of their information, and complain to their data protection authority. Our services store information in the United States. Where our providers’ data-processing terms apply, the transfer relies on the European Commission’s Standard Contractual Clauses; otherwise, on its being necessary to provide the service you asked for.

California residents: we don’t sell or share personal information, or disclose it to others for their own direct marketing.

Security, children and changes.

Security. Every site is served over HTTPS. Sign-in uses one-time email links, so there are no passwords to steal. Database rules limit each account to its own information, and only a few BCF staff can reach our databases, to run and fix the services. No system is perfect: if a breach affects your information, we’ll tell you as the law requires.

Children. Our websites aren’t directed to children under 13, and we don’t knowingly collect their personal information. T1Ds in the Wild trips are for adults. If you think a child has given us information, email us and we’ll delete it.

Changes. When this policy changes, we’ll update it here and change the date at the top.

Contact. Questions or requests: info@betacellfoundation.org, or Beta Cell Foundation, 4254 W. 5th Street #7, Los Angeles, CA 90020.

Beta Cell Lab Notes App (iOS & Android)

Effective date: October 14, 2026

This section covers the Beta Cell Lab Notes mobile app specifically, which works differently from our websites above: it runs entirely on your device. See also the Beta Cell Lab Notes Terms of Use.

The short version

Beta Cell Lab Notes is built by the Beta Cell Foundation (a 501(c)(3) nonprofit, EIN 84-4054715). We do not collect, store, transmit, sell, or have any access to your personal or health data. The app runs entirely on your device. Your information stays on your phone (and, if you enable it, in your own Apple or Google cloud account that only you control). We operate no servers and use no analytics, advertising, or tracking.

Who this covers

This section applies to the Beta Cell Lab Notes mobile app on Android and iOS, and its companion Wear OS / Apple Watch app.

Information the app uses, and why

All of the following is processed on your device only:

• Health data you already have. With your permission, the app reads workouts (with their route and elevation, where recorded), heart rate, glucose readings, and food (and, on iOS, insulin) from Health Connect (Android) or Apple Health / HealthKit (iOS) to display them around your workouts. Your CGM (e.g., Dexcom) writes those readings to the health platform; we simply read them.

• Data you log. Insulin, carbohydrates/food, glucose entries, and your written reflections. On iOS these are written back to Apple Health; on Android, insulin and app notes are stored in the app's local database. Glucose brought in from Medtronic CareLink (and its insulin and carbs, if you turn that on) is saved the same way. This is used only to show these items on your charts.

• App settings. Preferences like glucose units and chart height, stored locally.

• LibreLinkUp credentials (optional). If you connect a FreeStyle Libre sensor, your LibreLinkUp email and password are stored encrypted on your device (in the Android Keystore / iOS Keychain) and are transmitted only to Abbott's LibreLinkUp servers to retrieve your own glucose data. We never receive, see, or store them.

• Medtronic CareLink (optional). If you connect CareLink, you sign in on Medtronic’s own page; the app never sees your password. It keeps only a sign-in token, encrypted on your device, used only to fetch your own data from Medtronic’s servers.

• Period days (menstruation), only if you turn on Track Periods. Period tracking is off unless you turn it on, and while it is off the app reads and writes nothing about periods. With it on, the app reads the days marked as a period in Apple Health / Health Connect (menstrual flow; one mark per day, nothing about cycles or predictions) to show them on your Journal calendar and beside that day’s workouts, because insulin sensitivity often changes through the cycle. When you mark a day from its Journal page, the app writes that mark to Apple Health / Health Connect, and it only ever removes marks it made. Period data stays on your device and in your health platform; it is never sent to us.

• Journal. Journal entries are stored on your device, and on iOS in your own iCloud account if iCloud is on.

Where your data is stored

• On your device, in the app's private storage.

• In your own cloud backup, if enabled by you: Android Auto Backup (your Google account) or iCloud (your Apple ID). This backup is controlled entirely by you and your platform provider; the Beta Cell Foundation has no access to it. Your LibreLinkUp and Medtronic CareLink sign-ins are excluded from backup.

What we collect

Nothing. The Beta Cell Foundation does not operate any backend for this app. We have no user accounts, no analytics SDKs, no advertising SDKs, no crash-reporting that sends us your data, and no ability to identify you or access your information.

Third-party services

The app interacts with services you control, each governed by its own privacy policy:

• Health Connect (Google) / Apple Health (Apple) — the on-device health platforms the app reads from and writes to.

• Abbott LibreLinkUp — only if you choose to connect a Libre sensor, and only to fetch your own readings.

• Medtronic CareLink — only if you choose to connect, and only to fetch your own readings.

• Apple iCloud / Google Drive backup — only if you enable device backup, or, on iOS, iCloud for your Journal.

We do not send your data to any third party. Anything you export (a PDF or image of a workout) is created on your device and shared only when and where you choose to send it.

Health Connect data handling (Android)

Our use of Health Connect data adheres to the Health Connect Permissions policy, including its Limited Use requirements. Health data obtained through Health Connect is used only to provide the app's visualization and logging features on your device. It is never used for advertising, never sold, and never transmitted to us or any third party. You can review and revoke the app's Health Connect permissions at any time in the Health Connect settings on your device.

How to control or delete your data

• Revoke health permissions in Health Connect (Android) or Settings → Health (iOS).

• Disconnect LibreLinkUp or Medtronic CareLink in the app's Settings to remove stored credentials.

• Delete individual logged entries in the app.

• Uninstalling the app removes its on-device data. Data you wrote to Apple Health / Health Connect remains there under your control; delete it in that app if you wish. To remove a cloud backup, or the iCloud copy of your Journal, use your Google or Apple account settings.

Data retention

We retain nothing, because we receive nothing. Your data persists on your device (and your own backup) until you delete it.

Children's privacy

This app is not directed to children under 13, and we do not knowingly collect information from children. Because we collect no data at all, no information about any user — child or adult — is transmitted to us. If a minor uses the app, it should be under the supervision of a parent, guardian, and care team.

Medical disclaimer

Beta Cell Lab Notes is an educational and reflection tool. It is not a medical device and does not provide medical advice, diagnosis, treatment, or dosing recommendations. Always consult your healthcare provider for decisions about insulin, food, and exercise.

Changes to this section

We may update this section as the app evolves. Material changes will be reflected here with a new effective date.

Contact

Beta Cell Foundation — info@betacellfoundation.org