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.
Digital Nomad Media LLC is the controller of the personal information described here, except where this policy names another company as an independent controller. Address: 3125 Yorkdale Ln, Reynoldsburg, OH 43068-7002, United States. Contact: admin@thedigitalnomad.io.
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 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.
Advertising
RecipEZ shows banner ads supplied by Google AdMob to users without an active premium subscription. An active premium subscription, including one shared with you through a household, removes ads.
Google is an independent controller of the data it collects through those ads. To select and measure ads, the AdMob SDK can read your device's advertising ID, approximate location derived from your IP address, device and app information, and interactions with the ads themselves. That data goes to Google, not to Digital Nomad Media LLC. We never send Google your recipes, pantry, lists, plans, journal, receipts, photos, allergy or dietary selections, account email, or any other content you store in RecipEZ, and we do not use any of it to target ads.
Where the law requires it, including in the European Economic Area, the United Kingdom, Switzerland, and certain US states, RecipEZ asks for your choices through Google's consent message before personalized ads are shown. You can review or change those choices at any time from Settings > Privacy choices in the app. You can also reset or delete your advertising ID in Android Settings, under Privacy or Ads. Google explains its own handling at policies.google.com/technologies/partner-sites.
Optional account and personalization sync
An account is optional. You can create an account or sign in with an email and password, or choose Continue with Google. Email/password sign-in sends those credentials to Supabase Auth. Google sign-in shares your Google account identity, email address, and basic profile information, such as your name and profile image when provided by Google, with Supabase Auth to create or access your RecipEZ account. RecipEZ does not receive your Google password or request access to Gmail, Drive, or contacts. Passwords are handled by the authentication service, authentication tokens are kept in private app storage, and neither is 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.
Optional personal cloud sync
Premium personal cloud sync is off until you explicitly enable it. When enabled, RecipEZ stores a portable copy of your recipes and their ingredients/instructions, pantry records, shopping lists, meal plans, cooking-journal entries, collections, meal-plan templates, and the relationships those records need in private account-scoped Supabase storage. Usage history, receipt records and images, and active cooking timers are not included. Pantry photo addresses are device-local and are not uploaded as pantry photos.
You can pause sync while retaining cloud data, inspect usage, resolve conflicts, export your data, or delete the remote account. If premium access expires, existing content remains readable and can still download, while new cloud uploads pause without silently discarding pending device edits.
Households
A household is optional and is never created for you. A household holds up to four people including its owner, and joining one requires accepting an invitation that shows you the household name, how many people are in it, and exactly what is and is not shared before you decide. Invitation links are stored only as a one-way hash, work once, and expire after seven days; the owner can cancel one at any time.
Sharing is an explicit act on specific items, and it shares a copy. When you share a shopping list or meal plan, the household receives its own copy of that list or plan, along with copies of the recipes a shared plan needs so the household can cook them. Your own copy stays yours to edit or delete. Your pantry, cooking journal and its photos, your collections, your receipts and your saved recipes that you have not shared are never part of a household and are not visible to its members. Members can see who last changed a shared item, identified by account only.
Leaving a household, or being removed from one, ends your access immediately and removes the household's shared copies from your device; your own recipes, pantry and journal are unaffected. Ownership of a household transfers only when the person receiving it accepts, and a paid subscription stays with the account that bought it. An account that owns a household must transfer or dissolve it before deleting the account, so that other people's shared data is never decided by someone else's deletion. Dissolving a household deletes its shared copies for everyone.
Community recipes
Community participation is optional and requires sign-in. Your chosen handle, display name, bio, shared recipe, caption, photos, and comments can be viewed by other signed-in community members. Posting and commenting require premium access. Photos are stored in a private Supabase bucket and delivered through access-checked links; community content is still shared with other members and should not contain private information.
RecipEZ stores likes, follows, blocks, reports, and moderation status to provide community features and address abuse. Blocks and reports are not displayed in the public feed. Authorized moderators can review reported content and report details, remove content, and restrict community accounts. Text filtering helps detect prohibited terms. We do not send community content to advertising services or a third-party AI moderation service.
Account deletion removes your community profile, posts, comments, likes, follows, blocks, reports, and uploaded community photos. Other people may retain copies they saved or shared before deletion. Unreferenced community photos become eligible for the hourly cleanup job once they are more than 24 hours old; photos still attached to retained posts remain stored.
Feedback and support
When you submit in-app feedback, RecipEZ sends your selected category, message, optional contact email, app version, device description, and Android version to private Supabase records. Signed-in submissions also include your account identifier. Only authorized service administrators can read these records. We use this information to investigate bugs, evaluate ideas, and respond if you provided contact details. Do not include passwords or sensitive personal information in a feedback message.
Deleting your account removes the account association from feedback records but does not automatically erase the message or a contact email you supplied. Contact admin@thedigitalnomad.io to request deletion of feedback or support correspondence.
Recipe share links
When you share a recipe link, its recipe content travels in the URL fragment after the # character. The link opens the recipe in RecipEZ. If a browser opens the link, the website hands it to the app without displaying the recipe. The fragment is not sent with the website request. Anyone who receives the complete link can read or import the recipe. The website and its hosting and font providers receive ordinary network information when the page loads.
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. Supabase Auth supports email/password and Google as authentication providers.
- Your Google account identity, email address, and basic profile information to Google and Supabase Auth when you choose Continue with Google.
- 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.
Subscriptions
If you choose a premium subscription, Google Play handles payment information directly under its terms; RecipEZ does not receive your payment-card number. The app sends the Google Play purchase token to the RecipEZ Supabase backend, which verifies it with the Google Play Developer API and stores the associated product/base plan, subscription state, expiry, acknowledgement status and a one-way account association needed to deliver access, prevent token reuse and reconcile renewals, cancellations, holds, refunds and restores. Real-time developer notifications contain purchase lifecycle information and trigger a fresh verification; they do not contain your recipe, pantry, journal, allergy or household content.
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.
If you turn on cloud sync, photos attached to journal entries are stored privately and can be read only by your own account. They are never made public and are not used for advertising, training, or any automated analysis. When you remove a photo from an entry, or delete the entry, its unreferenced stored copy becomes eligible for the hourly cleanup job after 24 hours; a photo you upload but never attach to a saved entry follows the same schedule. Deleting your account removes the remaining stored photos before the account identity itself is deleted. Export your data before deleting an account: deletion is not reversible.
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. Deleting your RecipEZ account does not delete your Google account, and does not change anything in your Google account other than ending its connection to RecipEZ. 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.
Legal bases (EEA, UK, and Switzerland)
Where the GDPR, the UK GDPR, or the Swiss FADP applies, we rely on these legal bases:
- Contract: creating and running your account, cloud sync, households, community features, verifying subscriptions, and handling deletion requests you make.
- Explicit consent: syncing allergy, intolerance, and dietary selections, which can reveal health information. You give it when you turn on preference sync and can withdraw it at any time by turning sync off or deleting remote data in Account & Personalization.
- Consent: personalized advertising, collected through Google's consent message and changeable in Settings > Privacy choices.
- Legitimate interests: keeping the service secure, preventing abuse and token reuse, moderating community content, and answering feedback. You can object to this processing.
- Legal obligation: keeping records the law requires.
Where your information is processed
Synced account data is stored with Supabase in Canada (AWS ca-central-1). The European Commission and the UK recognize Canada as providing adequate protection for commercial data. Google (sign-in, AdMob, Google Play) and some recipe-data providers process data in the United States and other countries. Where data leaves the EEA, UK, or Switzerland for a country without an adequacy decision, those transfers rely on the EU-US Data Privacy Framework and its UK and Swiss extensions where the recipient is certified, or on the European Commission's Standard Contractual Clauses with the UK Addendum.
Your rights
Depending on where you live, including in the EEA, UK, and Switzerland, you have the right to:
- access the personal information we hold about you and get a copy;
- correct inaccurate information;
- delete your information;
- receive your information in a portable format (the in-app export does this for local data);
- restrict or object to processing, including processing based on legitimate interests;
- withdraw consent at any time, without affecting processing that happened before you withdrew;
- complain to your data protection authority. In the UK that is the Information Commissioner's Office (ico.org.uk); in the EEA it is the authority in your country of residence.
Most of these you can do yourself in the app. For anything else, email admin@thedigitalnomad.io from your account email address. We answer within one month and may need to verify your identity first.
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.