Privacy

For your security and privacy, GlucoRoo uses an encryption technology known as AES-256-GCM when storing your username and password (supplied by you in the Settings page), as well as when storing the CGM account IDs and session IDs that are generated by CGM cloud when GlucoRoo logs in. This ensures that nobody can log into your account using the information stored by GlucoRoo on your Karoo. AES-256-GCM (Advanced Encryption Standard with Galois/Counter Mode) is a highly secure, 256 bit, symmetric authenticated encryption algorithm. It ensures both data confidentiality and authenticity (integrity), confirming that data has not been tampered with. Your credentials are only stored on your Karoo and used to connect to the CGM cloud. They are never transmitted anywhere else.

When communicating with the Dexcom or. Nightscout cloud, GlucoRoo uses HTTPS (Hypertext Transfer Protocol Secure), the secure version of HTTP, using TLS (Transport Layer Security), so nobody can intercept and read any of the data communicated between GlucoRoo and Dexcom or Nightscout.

Besides your login information, which is encrypted, GlucoRoo does not save any other Personally Identifiable Information (PII).

GlucoRoo temporarily saves up to 3 hours of glucose readings in your Karoo’s local storage (without any identifying information attached), to allow GlucoRoo to restart and correctly display information if it is temporarily suspended.

If (and only if) you enable the “Record To FIT” option then your glucose readings will be recorded to the FIT file created for your ride, and will be visible, along with any other information in the FIT file (e.g. heart rate, speed, cadence, etc), to any service that you synchronize your ride with. GlucoRoo does not record any Personally Identifiable Information to the FIT file, just your glucose readings. Other services may record such information to the same FIT file, which would make it possible for anyone with access to that FIT file to observe your glucose readings.