LoopKit Data Policy

This policy covers the two ways Loop can send your data to the LoopKit developers:

• Issue reports, sent from Settings › Report a Problem › Send to the Loop Developers.
• Shared outcomes, sent from Settings › Current Setup › Share Outcomes.

Nothing is sent until you tap Submit or Send. This page explains what is sent, who can see it, how long it is kept and how to have it deleted.

Why we ask

Issue reports help the developers find and fix problems in Loop.

Shared outcomes help them judge algorithm experiments and settings changes. Comparing glucose results before and after a change, across many people, lets experiments be improved, promoted or dropped based on evidence.

What an issue report sends

• The title and description you write
• Any screenshots or photos you attach
• If you turn on Include Diagnostic Report, Loop's diagnostic report. It contains health data such as recent glucose, insulin, carbs and your therapy settings.
• Any contact details you choose to give (name, email, Zulip name, GitHub username). If you turn on Submit Anonymously, none are sent.
• Loop's version, build and customizations, your phone model and iOS version, and your pump and CGM models. These are shown under Also Sent before you submit.

What a shared outcome sends

About six weeks of history:

• Glucose readings
• Carb entries (amount, time and absorption time, but not food descriptions)
• Insulin delivery (boluses, temp basals, suspends and resumes)
• Loop's dosing decisions and glucose forecasts
• Therapy settings history, including dosing strategy and algorithm experiments
• Preset and override history, including preset names
• Pump and CGM make, model and firmware, phone model and iOS version, and Loop's version and build
• The date of your last setup change and what changed
• A random ID created by this copy of Loop, so that two shares from the same app can be linked. It isn't linked to your Apple ID, your analytics ID or anything else.
• Your note, if you add one. It's sent exactly as you write it, so leave out anything you don't want the developers to see.

A shared outcome doesn't send:

• Your name, email or any contact details
• Your phone's name, or your pump's or CGM's serial numbers
• The device communication log, alerts and notifications
• Remote-command (push) tokens

This data is not anonymous. Glucose and insulin history is health data, and a detailed history can in principle be linked back to a person. Treat sending it as you would sharing your Loop Report with a developer.

Your IP address is used only to limit how often data can be sent. It is never stored.

Who can see it

Your data is stored on LoopKit's own servers. It isn't sold, isn't sent to analytics or advertising services, and isn't combined with analytics data.

Only members of LoopKit's developer team on GitHub can see it, through LoopKit's developer viewer. Each developer must:

• sign in with their own GitHub account;
• accept LoopKit's developer terms of use first.

The terms limit use of the data to improving Loop and forbid sharing it outside the developer team. They also require developers to delete their own copies when data is deleted. Every time a developer opens or downloads a report or share, it's logged.

When an issue report arrives, its ID and title are posted to a private channel in LoopKit's developer chat (Zulip), to let the developers know. Nothing else from the report is posted, and nothing from shared outcomes is.

Developers may use AI tools to help review and analyze reports and shares.

Results from shared outcomes may be published in aggregate (for example, "time in range rose by 3% on average with experiment X"). Individual reports and shares are never published.

How long it is kept

Issue reports and shared outcomes are kept until they are deleted. There is no fixed end date.

How to have it deleted

Shared outcomes:

1. Go to Settings › Current Setup › Share Outcomes › Your Shares.
2. Tap Delete.

This removes the share from LoopKit's servers and from the developer viewer right away.

Issue reports, or a share you can no longer delete from the app: email data@loopkit.org. Include the ID shown when you sent it. Issue report IDs are shown in the confirmation after you submit; share IDs look like OC-XXXXXXXX.

Developers who downloaded the data are required by the terms of use to delete their copies.

LoopKit doesn't currently keep backups of this data. If backups are added, they will be kept on LoopKit's own equipment, and deletions will apply to them too.

Changes to this policy

If this policy changes, the new version applies only to data sent after the change.

Updated 2026-10-28