Your kitchen. Your data.
This application stores your account, household membership, inventory, recipes, meal plans, shopping lists and chosen preferences to provide its features.
Optional sensitive information
Allergies, intolerances and medical nutrition profiles require explicit consent. Household members can use your dietary constraints for shared meal validation only if you enable sharing. Personal profiles are not exposed to other members.
Images and assisted processing
Selected images and text are sent to the configured processing provider only with consent. Image metadata is stripped; uploaded scan and receipt images are encrypted at rest and expire after 24 hours. Photos attached to custom household foods remain available to household members until their owner deletes the account; detached uploads expire after 24 hours. Processing results remain in your account until deletion. Provider retention terms also apply and must be disclosed by the service operator before enabling the integration.
Controls
You can change consent, export account data and request account deletion in Profile → Privacy. An exported JSON file stays in the app's temporary directory until the next launch or sign-out so your chosen destination can read it. Copies you share are controlled by that destination. Shared household ownership must first be transferred. Deleting an account does not cancel an App Store or Google Play subscription; manage it in your store account.
Crash diagnostics and advertising
Release builds use Firebase Crashlytics for reliability diagnostics. EatMe+ does not intentionally attach recipes, food choices, health information, authentication tokens or private images to crash reports, and does not use health data or crash diagnostics for advertising. Authentication and transaction logs must be configured without request bodies, credentials or health details.
Operator and requests
The deployment owner must configure the legal operator, privacy contact, hosting locations, providers, retention and applicable rights before public release. This development deployment is not accepting public registrations.