Privacy Policy

Last updated: 2 September 2026

Morsel is built to keep your recipes on your phone. We collect as little as possible, we don't sell your data, and we never show you ads. This policy explains exactly what happens to the information you give us.

1. Who we are

"Morsel", "we", "us" and "our" refer to the makers of the Morsel mobile app. If you have any questions about this policy or your data, contact us at morselrecipeapp@gmail.com.

2. What we collect

Stored on your device

The following stay on your phone and are not sent to us, except as needed for the extraction step described below:

• Your recipes and folders - titles, ingredients, steps, servings, macros, notes, source links and photos, stored in a local database and image cache.
• Your profile & preferences - the display name you choose, plus your theme (System / Light / Dark) and unit (Metric / Imperial) settings.

Sent to our service when you save a recipe

• The link you paste. When you add a recipe, the URL (an Instagram/TikTok post or a recipe blog/website) is sent to our extraction service so it can fetch and read that page's recipe content.
• The extracted page content. The recipe text and images found at that link are processed to produce structured recipe data and macro estimates, which are returned to your device.

Optional account, sync & Morsel Plus

Morsel works fully without an account, and the core app stays free. Some optional features - grouped under Morsel Plus - involve a little more data, and only if you choose to use them:

• Account (optional). You can create an account by signing in with Google or an email and password. We use Supabase to manage sign-in and store your account. An account is not required to save, browse or cook recipes; it exists so a Plus subscription and your library can follow you to a new device.
• Sync & backup (optional). If you sign in, your recipes and preferences can be backed up and synced to your other devices through Supabase. Without an account, everything stays on your device as described above.
• Subscriptions (optional). If you subscribe to Morsel Plus, payments are handled by RevenueCat and the app store (Google Play or the App Store). We receive your subscription status, not your card details - those are handled by the store and payment processor.

Some of these features are still rolling out. Where a feature isn't yet available in your version of the app, the data handling above simply doesn't apply until it is.

What we do not collect

• You can use the app without an account - creating one is entirely optional.
• We do not sell, rent or share your data with advertisers.
• We do not track you across other apps or websites.
• We do not handle or store your payment card details.

3. Third-party services we use

To turn a pasted link into a saved recipe, our extraction service relies on a few specialised providers. Only the data needed for that task is shared with them:

• Apify - used to fetch the content of Instagram links.
• Google (Gemini) - used to convert scraped page content into structured recipe data and estimate macros.
• Pexels - used to find a relevant stock photo when a recipe has no image of its own.
• USDA FoodData Central - used, only if you opt in, to cross-check macros against public nutrition data.
• Supabase - used, only if you create an account, to manage sign-in and to store and sync your account data.
• RevenueCat - used, only if you subscribe to Morsel Plus, to process and manage the subscription together with your app store.

These providers process only the data needed for their task, and each handles data under its own privacy policy.

4. How we use your information

• To extract recipe details and estimate macros from the links you save.
• To backfill a photo when a recipe doesn't include one.
• To let you organise, search, scale, convert and cook your saved recipes.
• To remember your display name and preferences on your device.

We do not use your recipes or links to build advertising profiles, and we do not use your personal recipe library to train models.

5. Data retention

Your recipes, folders, profile and preferences remain on your device until you delete them or uninstall the app. Links and page content sent for extraction are processed transiently to fulfil your request and are not kept as a personal profile of you. Deleting a recipe removes it, and its cached image, from your device.

If you create an account, any data you sync is retained until you delete it or ask us to close your account; email morselrecipeapp@gmail.com to have your account and synced data removed. Subscription records held by RevenueCat and your app store are retained under their own policies.

6. Your choices & rights

• Delete anything, anytime. Remove individual recipes or folders in the app, or uninstall to remove everything stored locally.
• Opt-in features. The USDA macro cross-check, creating an account, cloud sync and Morsel Plus all run only when you choose to use them.
• Close your account. If you created one, email us to delete your account and any synced data.
• Offline use. Once saved, recipes can be browsed and cooked with no network connection at all.
• Access & questions. Email morselrecipeapp@gmail.com and we'll help with any privacy request.

7. Children's privacy

Morsel is not directed at children under 13, and we do not knowingly collect personal information from them.

8. Security

Recipe extraction happens on a backend so that provider API keys stay off your device. Data sent to and from that service is transmitted over encrypted connections. No method of storage or transmission is ever 100% secure, but we design Morsel to minimise the data at risk in the first place.

9. Changes to this policy

If we make material changes to this policy, we'll update the date at the top and, where appropriate, notify you in the app. Continued use of Morsel after a change means you accept the updated policy.

10. Contact

Questions about your privacy? We'd genuinely like to hear from you at morselrecipeapp@gmail.com or through the contact form.

← Back to home