Privacy Policy
Eat Schedule ("the app" or "the Service") values your privacy and complies with applicable privacy laws. This Policy explains what information the app collects, why it is used, and which external services help us process it.
1. Information We Collect
a. Account and authentication information
- Social sign-in information provided through Apple, Google, or Kakao, such as user identifiers, email address, name, and profile information
- Supabase Auth account and session information
- Internal app user ID
b. Profile and eating habit information
- Nickname, profile photo, or avatar URL
- Country, gender, birth year or birth date, height, and weight
- Weekly exercise, activity level, meal goals, meals per day, meal times, and same-menu recommendation interval
- Dietary restrictions, allergies, intolerances, and other eating or health-related information you provide
c. Meal records and recommendation usage
- Meal date and time, meal type, food name, notes, ingredients, calories, and estimated nutrition values
- Meal photos and profile photos uploaded by you
- Food preferences, likes, dislikes, re-recommendation history, and menu selection history
- Recommendation inputs such as condition, taste preference, portion preference, recommendation mode, and recent meal history summaries
- Recommendation results, menu-choice results, recommendation session logs, achievements, and statistics
d. Friends and eat-together features
- Friend requests, friendships, nickname search results, and friend profile image URLs
- Eat-together session participant IDs, nicknames, acceptance status, participant preferences, and recommendation results
e. Payment, subscription, and support information
- Subscription status, free trial status, purchase and restore results, and customer center information processed through RevenueCat, the App Store, and Google Play
- Promo code use status and redemption time
- Feedback content, category, optional reply email, app version, and platform
f. Device, notification, error, and technical information
- FCM registration token for push notifications
- App version, platform, notification settings, and user ID or settings stored locally on the device
- Diagnostic information such as errors, crashes, and stack traces collected through Firebase Crashlytics
- App usage events such as recommendation views, selections, abandonment, and feedback for service quality improvement
g. Location information
- If you grant location permission, the app may temporarily access your current location to derive a city/province-level Korean region code for regional bonus recommendations.
- The app does not store precise GPS coordinates on the server. Recommendation logs may store the derived region code, location availability, and whether a regional bonus was shown.
2. Purposes of Use
- Apple, Google, and Kakao social sign-in and user identification
- AI-based meal recommendations, menu choice, and food photo or text analysis
- Meal record storage, nutrition analysis, statistics, achievements, and favorites
- Friends, eat-together sessions, invitations, and friend request notifications
- Subscription status checks, paid feature access, purchase restoration, and promo code processing
- Push notifications and meal reminders
- Error diagnosis, security, abuse prevention, service stability, and quality improvement
- User support and feedback handling
3. AI Processing
The app uses Firebase AI Logic (Gemini) to provide food photo analysis, food-name normalization, nutrition estimation, recommendation reason generation, and menu choice assistance. To provide these features, information such as uploaded food photos, food names you enter, profile data, dietary restrictions, recent meal history summaries, and food preferences may be transmitted to Google Firebase AI services.
AI-generated food names, nutrition information, and recommendation reasons are automated estimates and are not guaranteed to be accurate.
4. Retention
- Account and profile information: until account deletion
- Meal records, photos, preferences, friend relationships, recommendations, and achievement data: until account deletion
- When you delete an individual meal record, it is removed from the app view, and related stored data may be cleaned up after an operationally necessary period or when the account is deleted.
- When you delete your account, account-related data in Supabase Database and Storage is deleted without undue delay.
- Feedback content, promo code history, payment and subscription records, and similar records may be retained as required for legal compliance, dispute handling, abuse prevention, or external payment platform policies, or retained after removing user identifiers.
- Information retained by Firebase Crashlytics, Firebase Cloud Messaging, RevenueCat, the App Store, and Google Play is governed by each service's own policy.
5. Third-Party Sharing
We do not sell personal information. Personal information may be provided to or processed by third parties only in the following cases:
- You have consented
- Disclosure is required by applicable law or by a lawful request from a court, regulator, or public authority
- External services or processors listed below are used as necessary for payments, authentication, AI processing, push notifications, data storage, and other Service features
6. Processors and External Services
- Supabase: authentication, database, Storage, Realtime, and Edge Functions
- Google Firebase: Firebase AI Logic (Gemini), Cloud Messaging, and Crashlytics
- Apple, Google, and Kakao: social sign-in authentication
- RevenueCat: subscription status checks, purchase and restore processing, and customer center display
- Apple App Store and Google Play: in-app purchases, subscriptions, refunds, and payment management
- Device operating systems and location/geocoding services: permission handling and regional code lookup
7. Your Rights
- Request access, correction, deletion, or restriction of processing
- Edit your profile and delete meal records in the app
- Log out and delete your account
- Withdraw notification, location, camera, and photo access permissions
You may request account deletion through the in-app account deletion feature. Active subscriptions may need to be canceled separately through the App Store, Google Play, or RevenueCat Customer Center.
8. Security
- SSL/TLS encryption during transmission
- Access controls such as Supabase authentication and Row Level Security
- No use of service-role keys or other secret keys in public clients
- Cleanup of Storage and related data during account deletion
- Restricted access to error logs and operational logs
9. Cookies and Automatic Collection
The app does not use web browsing cookies. However, technical information and usage records such as FCM tokens, app version, platform, error logs, and recommendation, selection, and feedback events may be generated or collected automatically to provide app features and maintain service stability.
10. Children
We do not allow sign-up for users under 14. If we learn that a user under 14 has signed up without appropriate guardian consent, we may delete the account and related information.
11. Privacy Contact
For privacy inquiries, complaints, or rights requests, please contact:
12. Changes
This Privacy Policy applies from the effective date above. We will notify users of material changes through the app or by other reasonable means.