iSpike
Back to home

Privacy Policy

Last updated: 1 October 2026

iSpike is built by someone who lives with Type 1 diabetes. I understand how sensitive health data is — it's my data too. This policy explains in plain language what iSpike collects, why, and what control you have over it.

What data iSpike stores

When you use iSpike, the following data is stored on our servers:

  • Account info — your email address and a securely hashed password. We never store your password in plain text.
  • Diabetes settings — your insulin-to-carb ratio, insulin sensitivity factor, target blood glucose, preferred units, insulin type, and dose increment. These stay private to your account.
  • Meal logs — photos you upload, the AI-generated carb estimates, foods identified, and any dose you log alongside a meal.
  • Blood glucose readings — manual entries and, if you connect a CGM, readings synced from your FreeStyle Libre via LibreLinkUp or from your Dexcom via Dexcom Share.
  • Insulin doses — bolus, correction and basal doses you log, including timing and BG context.
  • Exercise logs — type, duration, and intensity of exercise sessions you record.
  • Food memory — iSpike learns from your meals to improve future carb estimates. This data is tied to your account only.

CGM connection (FreeStyle Libre / Dexcom)

If you choose to connect your FreeStyle Libre sensor, iSpike accesses your glucose readings via the LibreLinkUp API using the credentials you provide. Your LibreLinkUp email and an encrypted authentication token are stored on our servers to maintain the connection. iSpike does not share your CGM data with any third party. If you connect a Dexcom sensor, iSpike reads your glucose readings via Dexcom Share (the service used by the Dexcom Follow app) using the Dexcom username and password you provide; your username and an encrypted copy of your password and session are stored so readings can keep syncing. This is not an official Dexcom integration. You can disconnect either service at any time from Settings, which removes the stored credentials.

Where your data lives & security

  • Your data is stored in a secure, encrypted database hosted within the European Union.
  • All connections to iSpike use HTTPS (TLS encryption in transit).
  • Passwords are hashed using bcrypt — we cannot read your password.
  • Meal photos are stored in encrypted cloud storage and are only accessible to your account.
  • We do not sell, rent, or share your personal data or health data with anyone.

What iSpike does NOT do

  • We do not sell your data to advertisers, data brokers, or any third party.
  • We do not use your health data for targeted advertising.
  • We do not share individual-level data with insurance companies, employers, or anyone outside your account.
  • We do not track you across other websites or apps.
  • We do not use advertising or social-media tracking pixels (no Facebook/Meta pixel, no ad networks).

Analytics & cookies

With your permission, iSpike uses Google Analytics to understand, in aggregate, how the website and app are used — for example which pages are visited and which features are popular — so we can decide what to improve.

  • Google Analytics only loads after you tap Accept on the cookie banner. If you decline, it never loads.
  • We send page paths only (e.g. “/dashboard”), with IP anonymisation switched on. We do not send your meals, carb counts, doses, glucose readings, name or email to Google.
  • Google Analytics sets its own cookies (named _ga and _ga_*) to tell visits apart. Google processes this data under its own privacy policy (policies.google.com/privacy).
  • Other than that, iSpike only uses the cookies and local storage needed to keep you signed in and remember your settings.

Tapping this brings the banner back so you can accept or decline again.

AI & meal photo processing

When you analyse a meal, your photo is sent to an AI model to identify the food and estimate carb content. This processing happens in real time and is not stored by the AI provider beyond the request. The results (identified foods, carb estimates) are stored in your iSpike account. Meal photos are stored in cloud storage linked to your account and are not used to train AI models.

Community (optional)

The Community is off until you choose to join. Joining requires accepting the Community Guidelines and confirming you are 16 or older.

  • Other signed-in members can see your display name, optional badge, and anything you post or reply. Your email and real name are never shown.
  • When you share a meal, only the food, carbs and outcome are shared. Your dose is included only if you switch it on for that post.
  • Posts and replies are automatically checked for links, contact details and harmful content before they appear.
  • Reports are reviewed by the iSpike team within 24 hours. Reported content may be hidden, and accounts that break the guidelines may be removed from the Community.
  • You can delete your own posts and replies at any time, and block any member so you no longer see each other’s content.

Your rights & data deletion

You have the right to:

  • Export your data — you can download your meal history as a CSV from Settings at any time.
  • Delete your account — contact us and we will permanently delete your account and all associated data (meals, doses, BG readings, photos, settings) from our servers. This is irreversible.
  • Correct your data — you can edit or delete individual meals, doses and BG readings from within the app.
  • Withdraw consent — you can disconnect your CGM, stop using the app, or request account deletion at any time with no penalty.

Under GDPR (UK and EU), you also have the right to access a copy of all personal data we hold about you. Contact us to make a request.

Children

iSpike is not intended for use by anyone under 16 without the supervision of a parent or guardian. We do not knowingly collect data from children under 16. If you believe a child has created an account without parental consent, please contact us and we will delete it.

Medical disclaimer

iSpike is a self-management tool that provides carbohydrate estimates and insulin dose estimates based on the settings you enter. It is not a medical device, does not provide medical advice, and should not replace the guidance of your diabetes care team. Always discuss changes to your insulin regimen with a healthcare professional.

Contact

If you have any questions about this privacy policy, want to request your data, or want to delete your account, contact:

Andrew Allen
[email protected]

Changes to this policy

If we make significant changes to how we handle your data, we'll update this page and the "last updated" date above. We may also notify you via email or within the app.