Fuel the next generation of diabetes innovation.

We remove identifiers and anonymize data in these ways: 

• For each user: 
  
  • Included: The month and year of birth and diagnosis
  • Not included: Name, address, email address, exact birthday, exact diagnosis day, notes, photos, customized basal profile names, or other personally identifiable information
• For all diabetes devices: 
  
  • Included: Device event and data timestamps
  • May be included: Brand and model of the device (some device makers preclude this)
  • Not included: Device serial number
• For blood glucose monitors: 
  
  • Included: Blood glucose (BG) readings
• For continuous glucose meters (CGM): 
  
  • Included: Estimated glucose values, events tracked by the CGM, including meals, insulin, calibration, exercise
• For insulin pumps: 
  
  • Included: All pump settings, including bolus calculator parameters, basal rates, insulin-to-carb ratios, and insulin sensitivity factors, as well as all events tracked by the pump, including meals, insulin dosed, temp basals and suspends events, primes, and BG inputs

Note: Some of the terms above may have slightly varying language on your device. 

We will not include in the anonymized datasets (1) freeform text and notes entered by you or your Care Team Members, or (2) any other data that could identify a specific individual.

See our Privacy Policy for more information.

After anonymizing and removing all identifying information, the data we provide researchers is in either .csv, .json, or .xlsx format that looks like this.

‍

We store data in Tidepool’s secure, HIPAA-compliant servers that are hosted by Amazon Web Services (AWS). Within AWS, we use MongoDB, a popular, modern database. ‍

‍

Here is an example data file (6MB compressed) for our demo user, “Jill Jellyfish" before anonymization and removing identifiers. It follows the Tidepool data model (how we internally represent data) here.

Tidepool uses industry best practices, including end-to-end encryption, to secure your data. You can read detailed information all about our security infrastructure in this document.

‍

Tidepool strips all identifying information from anonymized data sets for the Tidepool Big Data Donation Project. In addition, Tidepool replaces your Tidepool user identifier (that looks something like 0a1b2c3d) with a “hash” value that is generated using a cryptographically secure one-way hash function. These identifiers cannot be decrypted into their original form, even by Tidepool, but they allow researchers to correlate anonymized datasets over time from the same user.

‍

We take great safeguards to prevent hacks and data breaches, and it has never occurred. If a data breach were to occur, we would follow HIPAA guidelines for notifying our user base about the details of the breach.

At any time after you have opted in, you can choose to opt out. After you’ve logged into your account, click on the account name at the top of the page to navigate to your profile settings. Remove any nonprofit diabetes organizations you’ve selected to receive 10% of proceeds generated by your data donation.

‍

Uncheck “Donate my anonymized data” and click “Save.” If you opt in, and then later change your preference to opt out, you will not be able to remove or delete data that had been previously donated.

We recently upgraded our consent process to provide even more information before you decide to donate your anonymized data. At Tidepool, we are committed to ensure our communication with users about information sharing is both effective and transparent. Don’t worry, donating your data will still be just as easy as it was. If you’re creating a new account, you will be asked to consent during sign-up. If you already have an existing account, you can opt in or out of the project in your account profile page. You can follow these step-by-step instructions to get set up.