Summary
ZenSugarX is a glucose-data companion. Its core records are stored locally on the user's Apple device. Remote services are used when the user deliberately configures a feature such as Nightscout, Apple Health, or a server-delivered Live Activity path available in a supported release.
ZenSugarX is designed so that health data is not sold or used for advertising.
Data the app can process
Depending on the features you enable, ZenSugarX can process glucose values, timestamps, trends, sensor information, calibrations, treatment entries, carbohydrate and insulin records, alarms, statistics, application settings and diagnostic information required to operate and troubleshoot the app.
When compatible Bluetooth hardware is used, the app processes the device information required to communicate with that hardware.
Local storage and Nightscout
ZenSugarX stores its application history locally on the device. If you configure Nightscout, ZenSugarX connects to the server address and credentials you provide to download or, where a feature explicitly supports it, upload the data you requested. Your Nightscout operator controls that server and its retention policy.
Nightscout credentials should be treated as sensitive. ZenSugarX does not require you to publish a Nightscout instance publicly.
Apple Health, Watch and notifications
If you enable Apple Health integration, ZenSugarX reads or writes only the categories allowed by the permissions you grant. Apple Health permissions can be changed in system settings.
The Apple Watch app, complications, widgets and Live Activity surfaces receive the minimum application state needed to display the features you enable. Apple notification and background-delivery services are governed by Apple's platform policies.
Server-delivered Live Activity updates
For releases that offer remote Follower Live Activity delivery, ZenSugarX may register a device-specific ActivityKit push token with a Kvanta22-operated relay. The relay is designed to receive authorized Nightscout reading events, transform only the minimum state required for the Live Activity, and send that state through Apple Push Notification service.
The relay is not intended to become a permanent glucose-history database. Production retention, deletion, security controls and regional availability will be documented here before that feature is enabled for users.
Retention, deletion and user control
Local ZenSugarX data remains under the user's device controls and application features. Data stored by Nightscout follows the policy of the configured Nightscout service. If a Kvanta22 relay is enabled, its production retention will be minimized to the operational data required for delivery and troubleshooting.
Disconnecting an integration stops future app access through that integration. System permissions such as Bluetooth, notifications and Apple Health can also be changed in Apple Settings.
Analytics and advertising
ZenSugarX is not designed around advertising or behavioral profiling. Any future crash-reporting, analytics or support service added to the App Store build will be documented here and reflected in the App Store privacy disclosure before release.
Security
ZenSugarX uses platform security controls and HTTPS for supported remote services. Users remain responsible for the security of third-party or self-hosted services they configure, including Nightscout credentials, server access and account permissions.
Medical notice
ZenSugarX does not make an iPhone or Apple Watch measure glucose. It displays and processes data supplied by compatible external sources. Glucose information can be delayed, unavailable, incomplete or inaccurate.
Development software. ZenSugar is not a validated medical device and must not be the sole basis for insulin dosing or emergency decisions. Verify important readings using the methods recommended by your device manufacturer and healthcare team.
Contact
Questions about ZenSugarX privacy or support can be sent through the Kvanta22 contact channel.