RecipEZ is a local-first recipe, pantry, receipt, shopping-list, and meal-planning application published by Digital Nomad Media LLC. This policy explains how the Android app handles information.
Information stored on your device
RecipEZ stores saved recipes, pantry items, shopping lists, meal plans, notification preferences, usage history, receipt text, optional cached receipt images, allergy and dietary selections, and personalization settings in the app's private storage. An account is optional; guest mode retains the full local feature set. The app does not include advertising or first-party analytics. Android cloud backup is disabled. You control any JSON backup or profile export created in the app and the document location where you save it.
Optional account and personalization sync
If you create an account, RecipEZ sends your email and password to Supabase Auth. Passwords are handled by the authentication service and are not included in RecipEZ exports. If you consent to sync, RecipEZ stores your allergy and intolerance selections, dietary preferences, disliked ingredients, household serving count, explicit cuisine choices, and personalization settings in owner-only records protected by row-level security.
Allergy information is sensitive preference data and can be incomplete or outdated. RecipEZ asks for an accuracy acknowledgement, lets you edit or export this data, and provides separate controls to disable learned-preference sync, reset learned history, sign out while keeping local data, delete remote account data, and clear local personalization history. Allergy warnings are informational and never replace checking ingredients and package labels.
Camera, images, and receipt text
Camera access is requested only when you choose a barcode or receipt camera action. Gallery and document access use Android's system pickers. ML Kit performs barcode and receipt text recognition on-device; Google states that input images, text, and recognition results are not sent to its servers. ML Kit may send Google performance, utilization, compatibility, model-update, and abuse-prevention metrics. RecipEZ does not use receipt content for advertising or analytics.
Network requests and service providers
RecipEZ uses encrypted HTTPS connections for its own network requests. Depending on the feature you choose, the app may send the following information to third-party services:
- Recipe searches, filters, and requested recipe identifiers to configured recipe-data services, which may include TheMealDB, Suggestic, Spoonacular, Tasty, and RecipeAPI.io. Release builds route secret-backed services through the RecipEZ Supabase function. RecipeAPI.io is used only for image-independent text enrichment.
- Account authentication, explicit preference sync, account deletion, and proxied recipe-data requests to Supabase when those optional network features are used.
- A product barcode to Open Food Facts when you request product lookup.
- A recipe webpage address to that website when you request URL import.
- An image address to its hosting website when the app displays a remote recipe image.
Those services receive standard network information such as your IP address and request metadata and process it under their own policies. RecipEZ does not sell personal information.
Notifications and background work
Low-stock, expiry, stale-item, and receipt-retention checks run locally through Android WorkManager. Notifications are generated on the device and can be disabled in RecipEZ or Android settings.
Retention and deletion
App data remains on your device until you edit or delete it, import a replacement backup, clear the app's storage, or uninstall RecipEZ. Cached receipt records follow the retention period selected in Settings. Exported backup files remain wherever you saved them and must be deleted there separately. If you use an optional account, Account & Personalization settings can permanently delete the remote authentication identity and synced account data. Signing out does not delete local data. Clearing local personalization history does not delete remote data. Exported files remain wherever you saved them and must be deleted there separately.
To request deletion without the app, email admin@thedigitalnomad.io with the subject RecipEZ account deletion request from the email address used for the account. Do not include your password. Digital Nomad Media LLC will verify the request, permanently delete the remote RecipEZ authentication identity and associated synced account data, and confirm completion. Data may be retained only when required for security, fraud prevention, or legal compliance, and any such retention will be disclosed to the requester.
Security
RecipEZ uses Android private app storage, validated document URIs, bounded backup and receipt files, HTTPS-only app network transport, and confirmation before a backup replaces existing data. No security measure can guarantee absolute protection, so keep exported backup files in a location you trust.
Children
RecipEZ is a general-audience utility and is not directed to children. It does not knowingly collect children's personal information and does not offer child-directed account features.
Changes and contact
Material changes will update this policy's effective date. Privacy questions and support requests can be emailed to Digital Nomad Media LLC at admin@thedigitalnomad.io.