Privacy policy
Last updated: 2026-10-15
GlucoBeat processes health data. That's why this policy is clear and specific: which data, what for, on what legal basis, with whom, for how long and how to exercise your rights.
1. Data controller
Diego Manuel Béjar Santiago · Tax ID 10880184B · C/ Cardenal Benlloch, 74, esc. izq., 1-1, 46920 Mislata (Valencia), España · glucobeat@wandary.com. Data Protection Officer: Diego Manuel Béjar Santiago · glucobeat@wandary.com.
2. What data we process and why
| Data | Purpose | Legal basis |
|---|---|---|
| Email, name (optional), language, sessions and devices | Create your account, give you access and keep it secure | Performance of a contract (art. 6.1.b GDPR) |
| Which days you use the app: only the date, with no detail of what you do in it or of your health data | Know how many people use the app each day. That record is deleted after 90 days and afterwards only totals with no personal data are kept | Legitimate interest in understanding how the service is used (art. 6.1.f GDPR) |
| Profile photo (optional): the one you upload or, only if you choose it, a copy of your Google photo | Show it to you and to the people you share your data with | Your consent (art. 6.1.a GDPR) |
| Health data: glucose, meals, exercise, insulin, medication, sleep, notes, diabetes type, treatment and targets | Store it, show it to you and compute statistics for you | Explicit consent (art. 9.2.a GDPR) |
| Pseudonymised summary of your data for the chosen period | AI analysis and “How would this affect me?”, only when you ask | Specific explicit consent (art. 9.2.a) |
| Birth year, sex, height and weight (optional) | Give context to statistics and analyses, always as ranges | Specific explicit consent (art. 9.2.a) |
| LibreLinkUp credentials (encrypted) | Sync your readings automatically (beta) | Specific explicit consent (art. 9.2.a) |
| Access permissions to your Dexcom account (tokens, encrypted; never your Dexcom password) | Bring in your glucose readings through the official Dexcom connection | Explicit consent (art. 9.2.a GDPR), which you give when you authorise the connection at Dexcom |
| Email of the people you invite and log of their access | Share your data in read-only mode | Your consent (arts. 6.1.a and 9.2.a) |
| Technical and security logs (pseudonymised IP, account actions) | Security, abuse prevention and proof of compliance | Legitimate interest (art. 6.1.f) and legal obligation (art. 6.1.c) |
| Email for news (optional) | Send you news at most once a month | Consent (art. 6.1.a) |
| Subscription and billing data (plan, period, payment status, amount and any tax details you give when paying) | Charging your subscription, issuing the invoice and keeping our books. We never see or store your card | Performance of the contract (art. 6.1.b) and legal obligation (art. 6.1.c) |
| Public pages you visit, with two random identifiers from your browser, the country you connect from and the site (its domain only) or campaign you come from (our own audience measurement; never in the app) | Know how many people visit the site, which pages are read and where visitors come from, in aggregate figures | Legitimate interest (art. 6.1.f GDPR), exempt from consent (art. 22.2 LSSI). See Audience measurement |
The campaign or ad you arrived from stored with your account (utm_* or click identifier, e.g. gclid), only for accounts created before 14 October 2026 that came in through a campaign link |
It was recorded to learn which campaigns brought sign-ups. Since that date no campaign is linked to any account, and what was recorded is not used or disclosed to anyone. The campaign of a visit is only counted in the audience measurement, in aggregate figures and unrelated to any account | Legitimate interest (art. 6.1.f) |
We don't make automated decisions with legal effects on you. AI analyses are informational and are not medical advice.
Audience measurement
To know how many people visit GlucoBeat, which pages are read and where visitors come from, the site counts visits itself, without Google Analytics or any other third-party tool. Only on the public pages (home, information pages, blog, doctor profiles, our story, glossary, methodology, contact, legal texts and the log-in page) and never in the app, where your health data lives. Each time you open one of those pages, your browser sends us its address (without parameters) and two random identifiers. When you arrive, it also tells us which site you come from, only its domain (for example, google.es) and never the full address of the page, and, if the link you followed carries one, the campaign it is tagged with (the utm_* parameters). Ad click identifiers (such as gclid or fbclid) are not stored. We add the date and time and the country you connect from, which is derived from the connection. Your IP address is not stored.
The two identifiers are random numbers generated by your browser; they don't contain or reveal your name, your email or your account:
- The visit one is kept in your browser's session storage (
gb-visita, in sessionStorage) and is deleted when you close the tab. It is used to count visits. - The browser one is kept in its local storage (
gb-navegador, in localStorage) together with the date it was created. It is used to count how many different people visit us and how many come back. It expires 13 months after it is created and is not renewed by visits: after that a new one is created, unrelated to the previous one.
This measurement is used solely to produce aggregate audience statistics for the site: it is not combined with any other data (not with your account, if you have one, nor with your health data), it is not used for advertising or any other purpose, and it is not disclosed to third parties. The data collected is deleted after 25 months.
Because it meets these conditions, this measurement is exempt from consent under article 22.2 of Spanish Law 34/2002 on information society services (LSSI), as set out in the Spanish Data Protection Agency (AEPD) guide “Use of cookies for audience measurement tools” (January 2024). The legal basis is our legitimate interest in knowing how the site is used in order to maintain and improve it (art. 6.1.f GDPR).
You can delete both identifiers whenever you like by clearing this site's data in your browser settings. On your next visit new ones will be created, unrelated to the previous ones.
3. Artificial intelligence
Only if you explicitly accept it and each time you ask, we send Anthropic, PBC (provider of the Claude model, acting as data processor) a pseudonymised summary: no name, email or identifiers, with dates as relative days and times (in the meal query, days relative to today), and free text scrubbed of emails, phone numbers and links. It is still personal health data: it includes your diabetes type, your treatment, your glucose values and what you log, and the summary is kept in your account. Anthropic processes this data under its data processing agreement and does not use it to train models. We store the summary sent and the answer so you can review or delete them.
4. Recipients and processors
- Hosting and database: Amazon Web Services EMEA SARL (región UE), on servers located in the European Union.
- Email delivery: Twilio SendGrid (login codes, invitations and notices), without open or click tracking.
- Payments and billing: Stripe Payments Europe, Ltd. (Ireland), which processes the charge and issues the invoices as an independent controller of the payment data. It receives your email, your name and your payment method details; it never receives any health data.
- Artificial intelligence: Anthropic, PBC (only pseudonymised summaries, with no direct identifiers, and only with your consent).
- Audience measurement: we do it ourselves, without Google Analytics or other third parties (see Audience measurement).
- Sign in with Google (optional): Google receives your sign-in as an independent controller under its own policy. From Google we receive your email, your name and the address of your profile photo; the photo is only copied if you choose to use it.
- LibreLinkUp (optional): we access Abbott's platform on your behalf to read your readings.
- Dexcom (optional): if you authorise the official Dexcom connection, we read your glucose readings from Dexcom's platform. You type your password on Dexcom's website and it never reaches us: we store, encrypted, the access permissions (tokens) Dexcom gives us and delete them when you disconnect. You can also withdraw permission from your Dexcom account, in its permissions section.
- People you invite: they see your charts and events in read-only mode for the period you choose.
We don't sell your data or share it for advertising.
5. International transfers
SendGrid, Anthropic and Stripe may process data in the United States. These transfers rely on the EU-US Data Privacy Framework where the provider is certified and, in any case, on the European Commission's Standard Contractual Clauses, with additional measures (encryption in transit and, for AI, prior pseudonymisation and minimisation).
6. Retention
- Health and account data: while you keep your account. If you delete it, it is removed immediately and permanently from the database; encrypted backups are overwritten within 7 days at most.
- Imported CSV files (from LibreView or Dexcom Clarity): not stored (only their fingerprint and a summary).
- Dexcom access permissions: until you disconnect Dexcom or delete your account.
- AI analyses: until you delete them or your account.
- Days you used the app: 90 days; afterwards only totals with no personal data remain.
- Followers' access log: 12 months. Security and audit logs: 24 months, without health data.
- One-time codes: expire after 10 minutes and are deleted within 24 hours.
- The campaign stored with your account (only accounts created before 14 October 2026): for as long as you keep the account; the ad click identifier is deleted after 90 days.
- Audience measurement: page views, 25 months; the browser identifier expires 13 months after it is created.
- Subscription and invoices: for as long as the subscription lasts and, afterwards, for as long as tax and commercial law requires. Stripe keeps the invoices even if you delete your account: that is a legal obligation, not data we can erase on request. Deleting your account cancels your subscription first.
7. Your rights
You can exercise your rights of access, rectification, erasure, objection, restriction and portability, and withdraw any consent at any time without affecting the lawfulness of prior processing. Most of them can be exercised directly in the app: Settings → Privacy (consents) and Settings → My data (full JSON download and permanent deletion with an email code). For anything else, write to glucobeat@wandary.com. If you are not satisfied, you can complain to your data protection authority (in Spain, the Agencia Española de Protección de Datos, www.aepd.es).
8. Security
Encrypted connections (TLS), database encrypted at rest in the EU, third-party credentials encrypted with AES-256-GCM, sessions with random tokens of which we only store a fingerprint, one-time codes with attempt limits, a log of access to your shared data, and a data protection impact assessment.
9. Minors
GlucoBeat is intended for people aged 16 and over. If you're under 16, you can only use it with the authorisation of a parent or legal guardian, who will manage the account.
10. Changes
If we change this policy in a relevant way we will tell you in the app and, when it affects a consent, we will ask for it again.