MunchBloom Privacy Policy

Effective date: 2026-09-15

This Privacy Policy explains how Munchbloom ("MunchBloom," "we," "us," or "our") handles information in the MunchBloom mobile application.

Adults Only

MunchBloom is intended only for adults who are 18 years of age or older. It is not directed to children or minors. MunchBloom does not currently use age-verification technology or ask users to provide a birth date. If you believe a person under 18 has provided information through MunchBloom, contact us at andresmech@gmail.com so we can review the concern and take appropriate action.

Information We Handle

Account and profile information

MunchBloom uses an email address for passwordless sign-in and account recovery. We also handle an internal account identifier, an optional saved display name, and account preferences such as experience mode. The app stores its signed-in session in encrypted device storage on supported native devices.

Private food photos and analysis

When you deliberately select or take a food photo and continue through the Scan flow, MunchBloom uploads a normalized copy to private storage. Image preparation removes device filename and location metadata from the uploaded analysis image. The photo and limited context may be sent through our server boundary to an AI analysis service to identify one food and estimate serving information, calories, nutrients, likely ingredients, warnings, and limitations.

AI food identification and nutrition are estimates, not laboratory measurements or medical advice. An estimate may later be reviewed or corrected. You should not rely on MunchBloom to determine allergens, diagnose a condition, or make a medical or dietary decision.

Discoveries, FoodDex, and meals

We handle your private discovery history, confirmation or correction, FoodDex collection links, meal entries, serving multipliers, and immutable meal nutrition snapshots. These records are associated with your account so the app can display your collection and meals and keep confirmed source information consistent.

Shared canonical foods and Food Cartoons

Approved canonical food records, taxonomy, reviewed nutrition profiles, and approved shared Food Cartoon artwork are shared application catalog data. They are not owned by one user. Shared artwork is generated from canonical food information and versioned art instructions, not from a user's private photo or private discovery data.

An unresolved discovery may temporarily have owner-private provisional artwork. That private artwork is distinct from approved shared catalog artwork and is not promoted or copied into the shared catalog.

How We Use Information

We use information to authenticate accounts; provide uploads, analysis, confirmation, FoodDex, meals, and artwork; maintain security and request integrity; prevent duplicate operations; support deletion and retention workflows; and diagnose service availability using bounded operational records. We do not describe estimated nutrition as verified health information.

Service Providers and International Processing

MunchBloom's planned production services include:

• Supabase for passwordless authentication, database services, private object storage, and authenticated server functions.
• Resend, through Supabase Auth, is configured for transactional sign-in email. Email delivery has not yet been tested.
• OpenAI for server-side food analysis and reviewed Food Cartoon generation or visual assessment. A private food photo may be sent for an explicitly initiated food-analysis request. Shared-cartoon generation receives canonical food information, not the private photo.
• Trigger.dev for bounded background Food Cartoon and private-media retention tasks. Task payloads are designed to use limited identifiers and reviewed data rather than private photo bytes.
• Expo and EAS for application build and distribution operations.

These providers may process information on our behalf under their applicable terms and configurations, including in countries other than the one where you live. The production configurations, processing locations, contractual safeguards, and required notices must be confirmed before this policy is approved for publication. Whether particular service-provider processing must be disclosed as sharing in Google Play Data safety also remains subject to final review.

We may disclose information when reasonably necessary to comply with law, protect rights and safety, investigate abuse, or complete a properly notified business transaction.

Security

MunchBloom uses safeguards supported by the application architecture, including authenticated requests, row-level access controls, private media buckets, short-lived signed delivery links, server-held credentials, bounded inputs, and encrypted native session storage. The planned release configuration uses HTTPS for network transport, but that production configuration must be verified before publication. No technical or organizational measure can guarantee absolute security.

Retention, Legal Holds, and Deletion

Private photos and provisional artwork follow database-controlled lifecycle and retention rules. Depending on state, cleanup may occur after an expiry, failure, abandonment, confirmation, discovery deletion, or account deletion. Durable cleanup may require retries or manual reconciliation and may depend on backup expiry, so we do not promise an exact deletion time.

You can delete your account in the app from Profile, then Privacy & data or account management, and choose Delete MunchBloom account. The flow requires deliberate typed confirmation and may require a recent sign-in. You may also request deletion using the external pathway at https://munchbloom.com/delete-account/ or by contacting andresmech@gmail.com.

Account deletion is designed to remove the account and owner-private profile, discoveries, original photos, provisional cartoons, meals, collection links, and related private workflow state. Limited records may remain when legitimately required for security, fraud prevention, legal obligations, an authorized legal hold, dispute resolution, or reliable deletion completion. Genuinely de-identified catalog candidates or operational evidence may remain where they can no longer reasonably be linked to an account. Non-personal shared canonical foods, taxonomy, reviewed nutrition, and approved shared artwork remain because they do not belong to one account.

Policy Updates

We may update this policy when application behavior, service providers, or legal requirements change. The current published policy will identify its effective date, and notice should be provided when appropriate to the significance of a change.

Contact

Questions or privacy requests may be sent to andresmech@gmail.com. The public policy location is https://munchbloom.com/privacy/.