Privacy Policy

Last updated: June 18, 2026

MyMealStream ("the App") is developed by NamedToaster Studios LLC. This policy explains what data the App collects and how it is used.

Data Stored on Your Device

All of the following data is stored locally on your device and is never uploaded to our servers unless you explicitly trigger an action (e.g., importing a recipe or scanning a food photo):

• Recipes you save (titles, ingredients, instructions, macros)
• Meal plans and shopping lists you generate
• Food log entries you record
• Dietary preferences and macro targets you set
• Nutrition search cache (for faster lookups)
• Macro corrections you make to logged foods (kept on-device by default)

Data Sent to Our Server

When you use certain features, data is sent to our server for processing:

• Recipe import: Recipe text or Instagram URLs you provide are sent to our server, which uses OpenAI to extract structured recipe data.
• Food photo scanning: Photos you select are sent to our server, which uses OpenAI's vision API to identify foods. Photos are processed in real-time and are not stored on our server.
• Food text parsing: Text descriptions of foods you enter are sent to our server for macro estimation.
• Nutrition search: Food search queries are forwarded to the USDA FoodData Central API.

Device Identifier

The App generates a random, app-specific identifier (UUID) on first launch. This identifier is sent with server requests for rate-limiting and to count unique users. It is not tied to your device hardware, Apple ID, or any personal information.

Analytics

The App uses PostHog to capture anonymous product-usage events that help us understand how the App is used and where to improve. Events include things like which screens you visit, when you log a meal, when you import a recipe, and when subscription purchases succeed or fail. The PostHog API key embedded in the App is a public, write-only key (similar to a public Sentry DSN).

Session recordings

To diagnose usability problems and see where people get stuck, the App also records anonymous sessions of how the interface is used. These recordings capture your interactions with the screen: taps, scrolling, navigation between screens, and how long screens are shown. Recordings are tied only to the anonymous device identifier described above and are not linked to your name or identity.

What is masked (not captured):

• Text you type into input fields, including your email address at sign-in and any search terms, is masked before the recording is sent.
• Food photos you take or select, and recipe images, are masked.

What is visible in recordings: text that the App displays on screen, such as food names, recipe titles, and the calorie and macro numbers shown on your plan and food log, can appear in recordings. We use this only to understand how the App is used and to fix problems. We do not sell this data or use it for advertising.

You can request that we delete recordings associated with your device by contacting us at the email listed on the App Store.

The App also uses Sentry to capture crash and error reports so we can fix bugs. Crash reports include technical details (stack trace, app version, device model) but no meal data, photos, or personal information.

Future: Optional Anonymous Macro-Correction Sharing

We are developing an opt-in feature that would let users contribute anonymous macro corrections (e.g., "this food's calories were closer to 220 than the AI's estimate of 165") so that the App's nutrition estimates improve over time. This feature is not active today. When it ships:

• Sharing will be off by default and require an explicit opt-in.
• Submissions will not include your account, name, or any persistent identifier linking your corrections together. The server will only be able to tell that some device has already submitted a correction for a particular food, not which device, and not what other foods that device has corrected.
• Only the corrected macro values, the food fingerprint, and the original AI estimate are sent. No food log context, no timestamps tied to your activity, no personal data.
• This policy will be updated with full details before the feature is enabled.

Third-Party Services

• OpenAI: Recipe text and food photos are processed using OpenAI's API. See OpenAI's Privacy Policy.
• USDA FoodData Central: Nutrition data is retrieved from the USDA's public API. No personal data is sent.
• Instagram: When you import a recipe from Instagram, we fetch the post's public caption. No Instagram credentials are used.
• PostHog: Anonymous product-usage events and masked session recordings. See PostHog's Privacy Policy.
• Sentry: Anonymous crash and error reports. See Sentry's Privacy Policy.
• RevenueCat: Subscription management. See RevenueCat's Privacy Policy.

Photo Library Access

The App may request access to your photo library to let you select food photos for scanning. Photos are only accessed when you explicitly choose them. The App does not access your photo library in the background without your knowledge.

What We Do Not Collect

• No personal information (name, email, phone number) unless you sign in with Apple or Google, in which case we store only the email and name you authorize.
• No location data
• No advertising identifiers
• No cross-app tracking

Data Retention

All meal planning data is stored locally on your device. If you delete the App, all local data is permanently removed. Our server does not retain the recipe text, food photos, or search queries you send for AI processing. They are processed in real-time and discarded. Anonymous analytics events and session recordings sent to PostHog are retained per PostHog's standard retention policy.

Children's Privacy

The App is not directed at children under 13 and does not knowingly collect data from children.

Changes to This Policy

We may update this policy from time to time. Changes will be reflected on this page with an updated date.

Contact

If you have questions about this privacy policy, please contact us at the email address listed on the App Store.