Privacy policy

1. Information we process

• Settings and profile: glucose units, targets, therapy type if you enter it, language, and similar preferences.
• Logs you create: manual or imported glucose readings, meals and foods, carbohydrates and nutrition fields, insulin or basal entries you record, notes, and timestamps.
• Derived data: statistics, summaries, scores, patterns, and other insights computed on your device.
• Local technical data: feature settings, such as optional backup encryption, and files the App needs to run locally.

Optional health platforms. If you enable an integration, the App may read allowed types, such as blood glucose, from Apple Health or Health Connect according to your operating-system permissions. Availability and labeling depend on the platform and other apps.

2. Where data lives

App data is stored on your device in private app storage, and SugroLy does not provide cloud storage for App logs. When online food search is enabled, the search term or barcode is sent to Open Food Facts; you can disable this in Settings. Exports and backups are created under your control, and automatic local backups retain the latest seven copies.

3. Advertising (Google AdMob)

The App uses Google AdMob to show ads in some situations, for example if you choose to watch an ad to unlock a feature for the current session. AdMob is Google’s advertising service and operates separately from your glucose and meal logs.

Ad-related data is handled by Google and is separate from your health data in SugroLy.

• AdMob may collect device identifiers, such as advertising IDs, and limited technical information needed to deliver and measure ads.
• It may record interaction signals such as when an ad is shown, skipped, or tapped.
• This ad-related data is sent to Google’s servers to operate the ad service and is not stored only on your device.

SugroLy does not use AdMob to read or upload health entries kept in the App, such as glucose readings, meals, or notes. Google explains its advertising data practices at https://policies.google.com/privacy

You can limit ad tracking or reset advertising identifiers in your device settings. Names and availability depend on your device, region, and operating-system version.

4. How we use information

We use information to power logging, visualization, search, and descriptive analytics, including on-device insights. We do not make medical decisions for you and do not provide dosing recommendations.

Some analytics refer to an in-range share computed from pre-meal and post-meal readings linked to logged meals using a fixed glucose band such as 70–180 mg/dL. This is not the same as clinical Time in Range from continuous glucose monitoring (CGM), and it does not describe glucose between meals or overnight.

Carbohydrate-related bands or thresholds are statistical estimates from your own meal history. They are not clinically validated targets and must not be used alone to decide insulin doses or other treatment.

5. Sharing

We do not sell your personal information or share health logs with advertisers. We may disclose only the minimum information in the following cases:

• You ask us to, such as through export, sharing, or operating-system features that move data out of the App.
• Law or safety reasonably requires it.
• Operational vendors need minimal data, such as app stores or email support. Google AdMob processes ad-related data as described above; we do not use health logs for ad targeting.

Health platforms follow Apple and Google policies and the permissions you grant.

6. Security

We apply reasonable safeguards appropriate for a local-first app, but no security is perfect. Device loss, weak passcodes, malware, or unsecured exports may expose data. If you use optional backup encryption, we cannot recover a lost password.

7. Retention and deletion

Data remains until you delete it or remove the App, subject to operating-system behavior. “Delete all local data” in Settings removes the local database, profile, settings, saved backup secret, and App-owned local backups from that device.

8. Your choices and rights

Privacy laws where you live may give you rights such as access, correction, deletion, portability, or objection. Much of the data is local, so you can often act directly through export or deletion. Contact: sugroly@gmail.com

9. Children

The App is not directed at children under 13. We do not knowingly collect personal information from children as described here. Contact sugroly@gmail.com if you believe otherwise.

10. International use

Health information you enter is processed on your device. When ads are used, Google may process ad-related data on its servers. Apple or Google may also process limited technical data as part of the operating system and app stores.

11. Changes

We may update this Policy, publish the new version in the App and on our legal pages, and change the “Last updated” date. Continued use means you accept the update to the extent allowed by law.

12. SugroLy website and support messages

The SugroLy website operates separately from App records. The website does not read glucose readings, meals, or App analytics. When you send a support message, we store the email address, request category, message text, language, submission time, reference number, and follow-up status so we can review and answer the request.

The website measures page views, approximate visitors, pages, language, device category, and approximate country. We do not keep raw IP addresses in the analytics record. An encrypted daily identifier is used to count a visitor once per day and is automatically deleted within 45 days; aggregate counts remain. A limited automated security check is also used to prevent spam and abuse.

Do not send health information or passwords through the support form. You may request correction or deletion of a support message by emailing sugroly@gmail.com and including the reference number when possible. We retain support messages while reasonably needed for follow-up, legal obligations, and security.

13. Contact

SugroLy (شقرولي) — sugroly@gmail.com