Cookie Policy
Last updated October 7, 2026. This explains the cookies and browser storage GlucoFlow uses.
Strictly necessary
Always on. GlucoFlow can't work without these.
Sign-in token
Base44 (localStorage)
Keeps you signed in
Lasts: Until you log out or clear storage
glucoflow_consent_v1
GlucoFlow (localStorage)
Remembers your Accept/Reject choice
Lasts: Until you change it or clear storage
Advertising (optional)
Only used if you choose Accept. If you reject, Google Ads never loads.
Google Ads cookies (e.g. _gcl_au, _gcl_aw)
Measures whether ads led to sign-ups or purchases
Lasts: Set by Google; names and duration vary by browser
_aw_signup_fired_…, _aw_paid_fired_…
GlucoFlow (localStorage)
Prevents counting the same conversion twice
Lasts: Until removed on withdrawal or storage is cleared
_aw_checkout_…
GlucoFlow (sessionStorage)
Links a checkout to its conversion
Lasts: Until the browser tab session ends
Health information
We don't put glucose readings, meals, journal entries, or other health records in cookies or browser storage, and we don't send them to Google Ads. Conversion events may include an account or order ID, purchase amount, and currency.
Third-party services
Stripe checkout and Dexcom sign-in open on their own websites. Any cookies they use are set on their domains, not GlucoFlow's, and are covered by their own cookie policies. Exact third-party cookie names and retention vary by provider and browser.
Changing your choice
If you withdraw consent, we stop sending further ad events, remove Google Ads cookies on our domain where the browser allows, and delete our conversion keys. A script that already loaded stays in memory until you reload the page, but it receives no new events.