MomeSnap Privacy Policy
MomeSnap Privacy Policy
JMS Tech ("we", "us") operates the MomeSnap app and the website momesnap.com (the "Service"). This policy explains what personal information we process and why. This English version is provided for convenience; if it conflicts with the Korean version, the Korean version prevails.
The Service is not a medical device and is not intended to diagnose, treat, or prevent any disease. Nutrition and blood-sugar-impact information in the Service is general reference information generated by AI.
1. Information We Process and Why
a. Created automatically when you first open the app - Account identifier (UID) - Purpose: telling users apart and storing your meal records - An anonymous account is created without any sign-up.
b. If you link an Apple or Google account (optional) - The account identifier, email address, name (display name), profile photo URL, and sign-in method provided by Apple or Google - Purpose: continuing or restoring your records on another device, confirming eligibility for World Table, and answering your inquiries - Your email, name, and profile photo are never shown to other users or on public web pages.
c. Profile stored only on your device - Sex, age, height, weight, activity level, app language - Purpose: calculating recommended calories and personalizing analysis and recommendations - This profile is sent along with analysis or recommendation requests for AI processing, but it is not stored on our servers.
d. Meal records stored on our servers - Food photos (device, time, and location metadata is removed on upload), analysis results (food names, nutrients, estimated blood sugar impact), food details you edit or add, meal times, favorites - Purpose: providing your meal history and restoring it on a new device
e. Health information (sensitive data — only if you enter it or choose to share it) - Measured blood glucose: glucose you enter or read from a health app is stored on your device and linked to meals. It is stored on our servers — value, time measured, source (manual entry, Apple Health (HealthKit), Health Connect), and the linked meal — only for meals where you choose to include measured glucose in your World Table sharing scope. - Health profile: management goals and conditions you select from a list (free-text diagnoses are not stored). We ask for separate consent the first time you choose them, and store them on our servers. - Purpose: comparing meals with measured glucose, personalizing analysis, and — only if you choose — sharing on World Table - All other features work even if you do not enter or share this information.
f. Apple Health (HealthKit) and Health Connect (if you allow it) - Read: weight, blood glucose, blood pressure, exercise, steps, active energy burned, nutrition records - Write: weight, blood glucose, blood pressure, exercise, nutrition records - Health-app data is processed on your device. If you allow blood glucose reading, readings taken around a meal are linked to that meal on your device, and are sent to our servers as described in section 1.e only if you choose to share that meal's measured glucose on World Table. If you delete the original reading in the health app, we delete the linked record on our servers as well. - We never use health-app data for advertising or marketing, and we never sell it or share it with advertisers.
g. When you use World Table - The public copy of meals you share, the sharing scope you choose, your share memo, consent records (consent version and time), and your auto-share setting - If you choose to share your age range: the age range only (by decade, e.g. 40s), calculated by the app from the birth year in your on-device profile. Your age and birth year themselves are never sent to our servers. - Reports (reporter account identifier, reason, description, time), posts you hid and sharers you blocked, saved posts, and notices from us - Purpose: showing public posts, handling reports and inappropriate content, and keeping your preferences
h. Collected automatically while you use the Service - Device model, OS and app version, app usage (screens and features used), crash logs, approximate region inferred from IP address, and advertising identifier (when ads are shown) - Purpose: usage statistics, fixing errors, improving the Service, and serving ads - The website uses only cookie-free visitor statistics (Vercel Analytics).
2. Retention - Account and linked-account information: until you delete your account - Meal records, food photos, and analysis results: until you delete them or your account - Measured glucose stored on our servers: until you withdraw that sharing, delete it (including deleting the original in a health app), or delete your account - Health profile: until you delete it or your account - World Table posts: until you withdraw them, we take action, or you delete your account. The public photo copy is deleted immediately at that point. - Reports: until account deletion. However, if an unresolved report caused a post to be hidden, it is kept until the review is finished, with the reporter identifier removed. - Account-deletion records: only an irreversibly transformed account identifier is kept for 35 days to confirm the deletion and prevent reprocessing. - Automatically collected information: according to each processor's retention policy. - Where the law requires longer retention, we keep the information for that period.
3. Deletion When the retention period ends or the purpose is fulfilled, we delete the information without delay, using methods that make electronic files unrecoverable. Deleting your account deletes your authentication account, meal records, food photos, measured glucose, health profile, World Table posts, and related records.
4. Sharing with Third Parties We do not sell your personal information or provide it to third parties, except where required by law. Information you choose to share on World Table is shown to other users and website visitors as described in section 11.
5. Service Providers (Processors) - Google LLC (Firebase Authentication, Cloud Storage for Firebase, Firebase Analytics, Firebase Crashlytics): authentication, photo storage, usage statistics, crash analysis - Google LLC (Gemini API): food photo and text analysis, inappropriate-photo screening, meal recommendations - Google LLC (AdMob): advertising (when ads are shown) - MongoDB, Inc. (MongoDB Atlas, Seoul region, Republic of Korea): meal record and account database - Render Services, Inc.: API server hosting - Vercel Inc.: website hosting (World Table public pages and food pages)
6. International Transfers To provide the Service, we transfer (including store) personal information outside the Republic of Korea as follows. Transfers happen over encrypted connections while you use the Service, and retention follows section 2. - Google LLC (United States and other countries with Google data centers) / contact: https://policies.google.com/privacy · Items: account identifier, linked-account information, food photos, profile sent with analysis requests (sex, age, height, weight, activity level), automatically collected information, advertising identifier · Purpose: authentication, photo storage, AI analysis, usage statistics and crash analysis, advertising - Render Services, Inc. (Singapore) / contact: https://render.com/privacy · Items: all information passing through our servers while you use the Service · Purpose: API server hosting - Vercel Inc. (United States and other countries) / contact: https://vercel.com/legal/privacy-policy · Items: World Table public posts, website visitor statistics · Purpose: website hosting If you do not want these transfers, you can stop using the Service and delete your account; in that case the Service cannot be used.
7. Your Rights You may request access to, correction of, deletion of, or suspension of processing of your personal information, and you may withdraw consent at any time. - In the app: delete meal records, withdraw World Table posts and turn off auto-share, delete your health profile, disconnect health apps, unlink your account, and delete your account (Settings > Delete Account) - By email: the contact in section 12 We handle requests without delay (within 10 days).
8. Security - Encryption in transit (TLS), access-token authentication, server security rules - Minimal access to personal information - Public photos are separate copies with metadata removed - Our moderation actions on posts are logged
9. Automatic Collection Tools The app uses usage-statistics and crash-analysis tools and an advertising identifier. You can opt out of or reset the advertising identifier in your device settings (iOS: Settings > Privacy & Security > Tracking; Android: Settings > Privacy > Ads). The website does not use cookies.
10. Children The Service is not directed to children under 14, and children under 14 may not use it. If we learn that we have processed personal information of a child under 14, we delete it without delay.
11. World Table Public Posts - Only meals you agree to share are made public. The legal basis is your consent. - Shown on public web pages and to other users: the food photo (public copy), food names, nutrients, AI-estimated blood sugar impact level, an indicator that measured glucose exists, and the date shared (day only). If you choose, the meal date (day only) is also shown. - Shown only to signed-in users who also share meals, and only for items you consent to individually: age range, management goals, conditions, measured glucose values, and your share memo. These items are never included on public web pages. - Your account identifier, email, name, device information, exact photo time, location, and health records such as weight or blood pressure are never made public. - Public posts are reflected anonymously in per-food statistics (for example, nutrient ranges on food pages). After you withdraw a post, it is excluded from the next calculation. - If you turn on auto-share, meals you analyze afterwards are shared with the same scope. You can turn it off at any time and withdraw each post individually. - Public posts appear on web pages anyone can view without signing in and may be indexed by search engines. When you withdraw a post, its public photo copy is deleted and the web page is taken down. We cannot control copies saved by search engines or downloaded by others before withdrawal. - Reporters' identities are never revealed to the author of a reported post.
12. Privacy Officer - Officer: Jaeha Lee, Representative, JMS Tech - Contact: aidev.app.master@gmail.com Please send privacy inquiries, complaints, and requests for remedies to this contact.
13. Remedies (Republic of Korea) - Personal Information Dispute Mediation Committee: +82-1833-6972 (www.kopico.go.kr) - Personal Information Infringement Report Center: 118 (privacy.kisa.or.kr)
14. Changes to This Policy We announce changes in the app and on the website 7 days before they take effect, or 30 days before for changes that significantly affect your rights.
Effective date: November 1, 2026 Previous versions: effective May 1, 2026; revised October 1, 2026 (World Table public posts added)
