Privacy policy

Who we are

SugarTrail is made by Cenovya Labs LLC, a company registered in the United States, which is responsible for the personal data described here. For anything in this policy, write to privacy@sugartrail.app.

Where SugarTrail is today

SugarTrail is in active development and is not yet on the App Store. This matters for your privacy, so it is worth being plain about it:

• Today the app runs entirely on your device. There is no account to create, no password, and no server of ours holding your health data. Nothing you log or connect leaves your phone unless you send it.
• Later, an optional account will let data sync and be shared. That is how a caregiver will see a trail they have been granted, and how a connection such as Dexcom can keep fetching readings while the app is closed. This policy will be updated before any of that is switched on, and you will be asked before your data moves anywhere.

What the app keeps on your phone

All of this is stored in the app's private storage on your device:

• Your profile. Whose trail it is, a first name if you give one, the type of diabetes, how it is managed, your devices, insulins and medicines, and any clinic settings you choose to copy in.
• What you log. Meals and their photos, doses, glucose readings, notes and the times they happened.
• Readings read from the Health app, described below.
• Display choices, such as your glucose unit and light or dark appearance.

Deleting the app deletes all of it. We cannot recover it for you, because we never had a copy.

The Health app on your iPhone

If you allow it, SugarTrail reads blood glucose from Apple Health so your readings appear on your trail without typing. Specifically:

• The permission is read-only. SugarTrail never writes to Health.
• It reads glucose. It does not read your other Health categories.
• What it reads stays on your device, alongside everything else in the app.
• Health data is never used for advertising or marketing, never sold, and never shared with third parties.
• You can withdraw the permission at any time in iOS Settings, under Health, then Data Access & Devices.

Connections you choose

SugarTrail's purpose is to gather what already exists so you do not type it twice. Every connection is optional, is switched on by you, and can be switched off by you.

Dexcom

When this connection is available, you will sign in at Dexcom's own page - we never see or store your Dexcom password - and grant SugarTrail read-only access to your own glucose data. The access tokens Dexcom issues are held encrypted on our server and used for one purpose: fetching your readings so the app can show them to you. They are never sold, never used for advertising, and never shared with anyone else. You can revoke access at Dexcom or disconnect in the app, and we delete the tokens when you do.

Files you import

Where a device maker offers no connection, you can export a file from their site (for example Dexcom Clarity, or Glooko for an Omnipod pump) and import it. The file is read on your device and becomes part of your trail.

What we never do

• No advertising, and no advertising identifiers.
• No sale of personal or health data, in any form, to anyone.
• No third-party analytics, no trackers, no crash-reporting services. As of this version the app contains none.
• No sharing with employers, insurers or data brokers.
• No use of your health data to train a model that serves anyone other than you.

When you keep a trail for someone else

SugarTrail asks, as its first question, whose trail it is: your own, your child's, or that of someone you care for. If you keep a trail for another person you are confirming that you have the right to do so - as their parent, guardian, or with their agreement.

The record belongs to the person it describes. We do not knowingly collect data directly from a child: a parent or guardian creates and controls the record, and can export or delete it at any time. When accounts arrive, a young person who later wants their own will be able to have the record transferred rather than copied.

Security

On your phone, app data sits in storage that iOS protects with your device passcode or biometric lock. When the optional account and connections arrive, the design already built for them holds data encrypted in transit and at rest, records every read and write of clinical data in a log that cannot be edited, and grants access only through explicit, expiring permissions rather than by ownership. No system is perfect; if a breach ever affects your health data we will tell you, and we are subject to the United States Federal Trade Commission's Health Breach Notification Rule.

Your choices

• Export everything. A copy of your own records, any time.
• Delete everything. Today, by deleting the app. When accounts exist, deletion will remove the account and its data everywhere within 30 days.
• Withdraw a permission such as Health, in iOS Settings, or a connection such as Dexcom, in the app or at Dexcom.
• Ask us anything at privacy@sugartrail.app. Depending on where you live you may have rights to access, correct, delete or port your data, and to complain to a regulator. We honour these requests wherever you are, rather than only where the law compels us.

Changes to this policy

When something material changes - a new connection, the arrival of accounts, a new category of data - we will update this page and its version number, and say so in the app before the change affects you.

Contact

Cenovya Labs LLC · privacy@sugartrail.app