LoopKit Developer Data Access: Terms of Use

You must accept these terms before you can view issue reports or shared outcomes in the LoopKit developer viewer. If they change, you'll be asked to accept the new version before you can continue.

1. What this data is

People who use Loop to manage their diabetes send issue reports and shared outcomes to the LoopKit Developers.

Both can contain health data: glucose readings, insulin doses, carb entries and therapy settings. Issue reports can also contain screenshots, free-text descriptions and any contact details the person chose to give.

Shared outcomes have no names or contact details, but a detailed glucose and insulin history can still identify a person. Treat all of it as confidential health data.

2. You have read the data policy

You confirm that you have read and understood the LoopKit Data Policy. It describes what people were told when they sent their data. Those promises bind you as well as LoopKit.

3. Permitted use

You may use this data only to:

• diagnose and fix problems in Loop and its related projects;
• evaluate and improve Loop's algorithm, settings guidance and algorithm experiments;
• prepare aggregate results that cannot identify any person (see section 5).

Use for any other purpose is not allowed unless LoopKit has approved it in writing and the data policy allows it. This includes:

• commercial use;
• training machine learning models outside LoopKit's own work;
• marketing;
• research for other organizations.

4. Protecting the data

• Don't share the data, downloads or screenshots of it with anyone who hasn't accepted these terms. This includes posting it in public channels, issues, pull requests or chats.
• Keep downloaded files only while you are actively using them, on a device protected by a passcode or password and disk encryption. Delete them when you're done.
• You may use AI tools to review and analyze the data. Don't upload it to other third-party services, such as cloud notebooks or file-sharing sites, unless LoopKit has approved them.
• Use your own account. Don't share your login.
• Access is logged. Open only the reports and shares you need for your work.

5. Publishing results

When you publish results, publish only aggregates or examples that cannot identify a person. Don't publish:

• individual traces with dates;
• rare-event details that could identify someone;
• install IDs, report IDs or share IDs.

6. Deletion requests

When someone deletes a share, or asks for a report or share to be deleted, delete any copies you have made, including downloads and notes that contain their data.

7. Incidents

If you think data has been exposed, lost or misused, by you or anyone else, tell a LoopKit administrator at admin@loopkit.org right away. Include what happened, which data was involved and when it happened.

8. Ending access

LoopKit may suspend or remove your access at any time, including if you break these terms. When your access ends, or when you stop working on Loop, delete any copies of the data you still have.

By checking the box and selecting I agree, you confirm that you have read these terms and the data policy, and that you will follow them.

Version 1 · updated 2026-10-28