Information We Collect
Account information: If you choose to sign in with Google, we collect your email address, name and profile photo as provided by Google. This is used to identify your account, back up your data, and show who shared a community recipe.
Recipe content: Recipes you create (titles, categories, ingredients, instructions, notes and tags) are backed up to the cloud when you are signed in, so they can be restored on a new device. Each recipe's main photo is backed up to the cloud together with the recipe. Step photos (the photos attached to individual preparation steps) are stored only on your device, unless you have a Premium subscription, in which case they are backed up to the cloud as well. If you share a recipe with the community, a reduced-size copy of its main photo (and, with Premium, its step photos) is uploaded and shown with it to other users and on its share link; it is deleted when you stop sharing the recipe, delete it, or delete your account. Shared photos are automatically screened for inappropriate content using Google Cloud Vision.
Community recipes: If you choose to share a recipe with the community, a copy of it (without your rating) is published together with your name and Google profile photo. Shared recipes are visible to other signed-in EatMi users, and to anyone who opens a share link to that recipe, including on the web without the app. Other users can save a copy of a shared recipe to their own recipe book; those copies remain theirs even if you later stop sharing or delete the recipe.
Public page: If you choose to create a public page, it is published at its own web address (for example, eatmiapp.com/u/yourname) and shows the address you picked, the display name and bio you entered, your Google profile photo, and the recipes you shared with the community. Anyone with the link can see it, without the app or an account. The address, name and bio are automatically checked for offensive content, including with Google's Gemini model. You can edit or delete your public page at any time; once deleted, its link stops working.
Recipe notes: A signed-in user can send a note or suggestion to the author of a recipe shared in the community. We store the note with the sender's name (not their email); only the recipe's author and the sender can see it. Notes are checked automatically (including with Google Gemini) to filter abusive content. The author can delete, report or block the sender; reported notes are reviewed manually. To tell the author about a new note we store the device's notification token (FCM). Deleting your account deletes all notes you sent and received.
Reports and moderation: If you report a community recipe, we store the reason you give together with your account ID. If a recipe you shared is hidden for breaking the community guidelines and you send us a question about it, we store your message, your account ID and email address, and the recipe's title, so we can reply.
Backup files: If you export your recipe book to a backup file, the file is created on your device and saved wherever you choose (for example, Google Drive). We do not receive or have access to these files.
Nutrition calculations: When you ask the app to calculate a recipe's nutrition values, the recipe's title, ingredients and instructions are sent to Google's Gemini model (on Google Cloud Vertex AI) to produce the estimate. No account details or photos are sent. We keep a count of how many calculations you used each month, to apply the free-plan limit.
Recipe import (Premium): When you import a recipe from a website link, our server fetches that page and sends the recipe found on it to Google's Gemini model (on Google Cloud Vertex AI), which organizes it into a recipe. When you import from a photo of a recipe or from screenshots of a post (up to 5 at a time), the images are sent to Gemini for the same purpose. Links and images are used only to create the recipe and are not stored on our servers. We keep a count of imports per month.
Subscriptions: Premium subscriptions are purchased and managed through Google Play. Payment is handled entirely by Google; we do not receive your payment details, only whether your subscription is active.
Feedback: If you submit a suggestion or complaint through the app's feedback feature, we collect the message text and, if you are signed in, your email address, so we can review it.
How We Use Information
We use the information above only to:
- Let you sign in and access your account
- Back up and restore your recipes and photos across devices
- Calculate nutrition values and import recipes when you ask, and provide Premium features to subscribers
- Show recipes you choose to share in the community, and your public page if you create one
- Deliver recipe notes between users and notify you when you receive one
- Review reports, moderate community content, and respond to questions about moderation
- Review feedback you choose to submit
We do not sell your information, and we do not use it for advertising. The app does not include analytics or advertising tools.
Community Reports & Moderation
Community recipes are subject to the EatMi Community Guidelines. We review reports and may hide a shared recipe from the community if it breaks them. A hidden recipe is not deleted and stays in the author's own recipe book.
We also store when you agreed to the community guidelines, and the list of users you chose to block, so blocked users' recipes stay hidden on all your devices.
Third-Party Services
EatMi uses Google Firebase (Authentication, Firestore database, Cloud Storage, Cloud Functions, Cloud Messaging, App Check and Hosting) to store account, recipe and photo data securely, to run server features such as nutrition calculations and recipe import, to serve community recipe share links and public pages, and to send notifications about new recipe notes. Nutrition estimates, recipe imports, and public-page and recipe-note content checks are done with Gemini on Google Cloud Vertex AI, and shared photos are screened with Google Cloud Vision. Subscriptions are handled by Google Play.
See Firebase's privacy information at firebase.google.com/support/privacy and Google's Privacy Policy at policies.google.com/privacy.
The Web App, Cookies and Browser Storage
EatMi can also be used in a browser at app.eatmiapp.com. The web app requires signing in with Google or Microsoft. For it to work, your browser keeps your sign-in, recipes, photos and settings on your device (in the browser's local storage – IndexedDB and localStorage). This data stays in your browser, and you can remove it at any time through your browser settings or by signing out.
EatMi uses no advertising cookies, analytics or tracking tools, on the website or in the web app. To protect the service from abuse, the web app and shared recipe pages use Google reCAPTCHA Enterprise (through Firebase App Check), which may set cookies and collect technical information about your browser and device under Google's Privacy Policy. Signing in with Google or Microsoft happens in the provider's own window, under its own policy. Like any website, Firebase Hosting servers log basic technical request information (such as IP address and browser type) for security and operations.
Premium is purchased only in the Android app, through Google Play. No payment details are collected in the web app.
Data Retention and Deletion
Your data is retained as long as your account exists. You can stop sharing a recipe at any time from the recipe screen, which removes it from the community. Copies other users already saved to their own books are not affected.
Deleting Your EatMi Account
You can delete your account at any time from within the app: open the side menu, tap your account name, and choose "Delete account". You can also request deletion by emailing studio@midesign.digital with the subject line "Delete my account" from the email address associated with your account.
We will delete your account information, your recipes and their backed-up photos, your public page, the recipe notes you sent and received, and any recipes you shared with the community from our servers within 30 days of your request. Copies other users saved to their own recipe books are not affected. Recipe photos stored locally on your device are not affected and can be removed by deleting the app.
Children's Privacy
EatMi is not directed at children under 13, and we do not knowingly collect information from children under 13.
Changes to This Policy
We may update this policy from time to time. Changes will be posted on this page.
Contact
If you have questions about this privacy policy, contact us at studio@midesign.digital.