Your Meal, My Meal Privacy Policy

Your Meal, My Meal (네밥내밥; the “App”) is an iOS and Android application for logging the meals you eat each day with photos and sharing them with people in the same group. This policy explains what information the App handles, why, and the choices you have.

In short:

• Your photos and meal records are visible only to people in the same group as you.
• The App shows Google AdMob full-screen ads and rewarded ads. Full-screen ads occasionally take up the whole screen after you close a photo or finish posting, and rewarded ads are watched only when you choose to, after you’ve used up your Nudges. There are no banner ads that stay on screen. We use Google Analytics for Firebase for usage statistics. Your name, email, photos and meal records are not passed to these services.
• On iOS, after you sign in, we ask first whether you allow ad tracking, and you can use every feature of the App even if you decline.
• You can delete your account directly in the App, and deleting it removes your photos and records along with it.

If you have any questions, please contact us at [email protected].

• Email address — Received through Sign in with Apple or Google. Used only to identify who is signed in.
• Display name — The name shown to people in your groups. You choose it yourself and can change it anytime.
• Meal photos — Photos you take yourself or pick from your album. They are the whole purpose of the App.
• Meal date and time slot — Needed to tell which meal on which day a photo belongs to.
• Device push token — Stored so we know where to send notifications.
• Comments — Text you leave on meals of people in the same group. Visible only to people in that group.
• Profile photo — A photo you upload yourself. Visible only to people in the same group as you.
• Report and block records — Who reported what and why, and whom you blocked. Used only to handle inappropriate content.
• Account identifier — A random string created automatically when you sign up. Used only to link photos and records to their owner, and unlike your name or email, it is never shown on screen.

The following information is processed for ads and usage statistics.

• App usage information — Screens viewed and features used, app instance ID, device type and OS, and approximate region. Used to understand which features are used and to improve the App, and processed by Google Analytics for Firebase.
• Advertising identifier and ad information — The IDFA on iOS or the advertising ID on Android, and ad impression and click information. Used to show ads and measure their performance, and processed by Google AdMob. On iOS, if you decline “Allow apps to request to track,” the IDFA is not used and non-personalized ads are shown.

The App does not access precise location, contacts, call history, health information or payment information.

Photos and meal records are visible only to people in the same group. This restriction is enforced in the database itself (Row Level Security), not just in the app screens, so even modifying the App or imitating its network requests cannot retrieve someone else’s meals.

The photo storage is private, and links for viewing photos are valid only for a short time.

Push tokens are kept in a separate table that only you can read. They are not visible even to people in the same group, because anyone who knows a token could send arbitrary notifications to that device.

Comments and reactions are visible only within the group where they were left. Even on the same photo, people in other groups cannot see them. Content you report or block becomes invisible to you from that moment on.

The App does not sell personal information. Your name, email, photos and meal records are not provided to third parties for advertising or analytics purposes. The App uses the following services.

• Supabase — Sign-in and data storage. The servers are located in South Korea (Seoul).
• Cloudflare R2 — Storage for meal photos and profile photos. Stored privately in the Asia-Pacific region, and served through addresses valid for one hour only after confirming the viewer is allowed to see them.
• Expo — Notification delivery, via Apple APNs on iOS and Google FCM on Android. The notification text and device token are passed on.
• Apple / Google — Sign-in. We receive your email address.
• Google AdMob — Full-screen ads and rewarded ads. The advertising identifier, ad impression and click information, and device information are passed on.
• Google Analytics for Firebase — Usage statistics. App usage information, app instance ID and device information are passed on.

You can see how Google processes this information in How Google uses information from sites or apps that use our services.

We keep your information while your account exists and delete it when you delete your account. We keep no separate copies. Usage statistics are not tied to your account and are deleted after 2 months under the Google Analytics default setting.

You can delete your account right in the App: Me > Delete account.

Deleting it permanently removes your profile and display name, profile photo, uploaded photo files, meal records, comments, reactions, report and block records, group memberships and push tokens. This cannot be undone.

Groups you created pass to the longest-standing remaining member. If no one is left, the group is deleted too. One person leaving never removes the group for everyone else.

• You can change your display name in the App at any time.
• You can immediately delete your account and all records using the method in section 6 above. If you have already removed the App, please see Account deletion.
• You can unblock people at any time in Me > Blocked people.
• You can turn off notifications at any time in your device settings.
• You can turn off ad tracking or delete your advertising ID at any time — on iOS in Settings > Privacy & Security > Tracking, and on Android in Settings > Google > Ads.
• For any other requests to access, correct or delete your information, please contact us at the email address above.

The App is not directed at children under 14, and we do not knowingly collect information from users of that age.

This policy may be revised to reflect changes in law or in the service. If what we process changes, we will update this policy and its “Last updated” date before releasing the version that includes the feature.