GlycoSnap - AI Blood Sugar & Calorie Insights

GlycoSnap Privacy Policy

GlycoSnap ("Service") Operator complies with applicable privacy laws and is committed to protecting user privacy.

GlycoSnap is developed and operated by JMS Tech (제이엠에스테크), a sole proprietorship based in the Republic of Korea.

The Service is not a medical device and is not intended to diagnose, treat, cure, or prevent any disease. Nutrition and meal impact information provided by the Service is AI-based general reference information only.

1. Purpose of Personal Information Processing The Operator processes personal information for: - User identification and service provision through anonymous authentication - Food photo AI analysis, food recognition, nutrition information, and AI-based relative meal impact information - Personalized calorie recommendations (based on gender, age, height, weight, activity level) - Health data integration, including Apple HealthKit on iOS and Google Health Connect on Android - Diet record storage, analysis history, reports, and user-facing app features - Advertising and service operations

2. Personal Information Collected

a. Automatically generated (anonymous authentication): - Unique user identifier (UID) ※ No personally identifiable information (email, name, phone) is collected.

b. User-provided (stored on device only): - Gender, age, height, weight - Activity level - In-app language setting ※ This information is stored on-device only. It may be temporarily transmitted for AI analysis but is not permanently stored on servers.

c. Collected during service use (stored on server): - Food photos, which may be stored on the server to provide food recognition, nutrition analysis, diet history, and related app features - Food analysis results, nutrition information, AI-based relative meal impact information, and diet records

d. Health data integration (requires explicit user consent): - Steps, active energy, heart rate, weight, and other health data from Apple HealthKit or Google Health Connect ※ Health data from Apple HealthKit or Google Health Connect is processed on-device by default and is not transmitted to external servers without additional user consent.

3. Retention Period - Account information (UID): Until account deletion request - Food photos, diet records, and analysis results: Retained while the account is active or until the user deletes the record or requests account deletion - Health data from Apple HealthKit or Google Health Connect: Processed on-device only and not transmitted to external servers, unless explicitly stated and consented to - Some information may be retained where required by law or where reasonably necessary for security, fraud prevention, or legitimate operational purposes

4. Third-Party Data Sharing The Operator does not sell personal information. The Service may share or process limited data with service providers, cloud infrastructure providers, advertising partners, and third-party AI analysis providers only as necessary to provide, operate, secure, analyze, and monetize the Service, or as required by law.

5. Processing Delegation

The Operator delegates processing as follows: - Anonymous authentication and cloud database services - API server hosting and operations - Diet records and food photo storage - Food photo AI analysis via third-party AI analysis providers

These services may be hosted on cloud infrastructure in the United States or other regions. Food photos may be transmitted to the server and forwarded to third-party AI analysis providers for food recognition and nutrition analysis. For details on current service providers, contact the Privacy Officer.

6. User Rights Users may exercise the following rights: - Request access to personal information - Request correction or deletion of personal information - Request suspension of processing - Request account deletion (Settings > Delete Account)

Upon account deletion, all authentication accounts and server-stored personal information, including food photos and diet records, are deleted. Some information may be retained where required by law or reasonably necessary for security, fraud prevention, or legitimate operational purposes.

7. Security Measures - Technical: SSL/TLS encryption, server-side security rules, API token authentication - Administrative: Minimized access permissions, regular security audits

8. Food Photo Data Processing - Food photos may be transmitted to GlycoSnap servers and to third-party AI analysis providers for food recognition and nutrition analysis. - Food photos may be stored as part of the user's diet history to provide analysis history, reports, and related app features. - GlycoSnap does not use food photos to train, fine-tune, or improve its own AI models. - Food photos are not sold to third parties. - Users may delete individual diet records in the app, and server-stored records associated with the account will be deleted upon account deletion, except where retention is required by law or reasonably necessary for security, fraud prevention, or legitimate operational purposes. - Analysis results, including nutrition information and AI-based relative meal impact information, may be stored separately as diet records.

9. Advertising and Third-Party Ad Networks - The Service displays in-app ads for operational support. - Ad networks may use advertising identifiers, such as Apple's IDFA on iOS and Google's Advertising ID on Android, for ad delivery, measurement, fraud prevention, and personalized or non-personalized advertising, depending on the user's device settings and consent choices.

10. Medical Disclaimer The Service is not a medical device and is not intended to diagnose, treat, cure, or prevent any disease. All nutrition analysis, AI-based relative meal impact estimates, and calorie calculations are general reference information generated by AI. They do not constitute medical advice. Users should consult qualified healthcare professionals for any health-related decisions.

11. Privacy Officer - Contact: aidev.app.master@gmail.com

12. Changes to Privacy Policy This policy is effective from the implementation date; changes will be notified 7 days in advance.

Effective date: June 19, 2026.