RecipeFetch Privacy Policy

Effective date: 17 July 2026  ·  Last updated: 4 September 2026

RecipeFetch (“the App”) is operated by Metrium AI Pty Ltd (ACN 701 291 438), based in Australia (“we”, “us”). This policy explains what information we collect when you use the App, how we use it, and the choices you have. Contact: recipefetch@metrium.com.au.

1. Information we collect

Account information (required to use the App). When you create an account we collect your email address, and — if you sign in with Google or Apple — your name and email address as shared by that provider. We assign you a unique account identifier (user ID).

Your recipe library. Recipes you extract and save are stored in your account in our cloud database so they sync across sign-ins. A saved recipe includes the source URL and the extracted recipe content. We do not access your library except to operate the service.

Subscription information. If you subscribe to RecipeFetch Pro, your purchase is processed by Apple (App Store) or Google (Google Play), depending on where you installed the App. Our subscription partner RevenueCat receives your user ID and subscription status (e.g. active, expired) so we can unlock Pro features. We never see or store your payment card details.

Usage information needed to run the service. We record how many recipe extractions you have used (to enforce free-trial and Pro limits) and the URLs you submit for extraction (to process your request and to serve previously-extracted recipes faster from a shared cache).

Optional analytics (off by default). Analytics collection is opt-in and controlled by the “Share analytics” toggle in Settings. If — and only if — you turn it on, we collect: recipe URLs extracted, saved and viewed; search terms used in your library; screens visited and session timestamps; view durations; a random device identifier; your user ID; and your approximate location (country, region and city, estimated from your IP address by the ipapi.co service). We use this to understand which recipes and features are popular, including aggregated regional trends. We do not collect precise GPS location. You can turn analytics off at any time in Settings.

Crash and error diagnostics. When the App hits an error or crashes, we collect technical diagnostics through Sentry so we can fix it: the error type and message, a stack trace, the App version and build number, the over-the-air update identifier, your device model and operating system version, and a limited trail of the technical events immediately before the failure — which screens were opened, and the addresses of network requests made (addresses only, not their contents). We have configured the App not to send your email address, your account identifier, your recipe content, or its own log output, and we do not use crash data for advertising or tracking. This collection is separate from the optional analytics above and is not controlled by the “Share analytics” toggle: declining analytics should not mean we are unable to tell that the App is broken for you.

2. How we use your information

3. AI processing

Recipe content is generated by artificial intelligence. When you submit a URL, the page or video transcript is retrieved and processed by Google’s Gemini model to produce a structured recipe. Your account identity is not sent to the AI model; only the content of the URL you submitted is processed. Nutrition figures and allergen warnings are AI estimates — see the disclaimer in the Terms of Use.

4. Service providers

We share information with providers who process it on our behalf:

ProviderPurposeData involved
SupabaseDatabase, authentication, hostingAccount info, recipe library, usage counts, analytics
RevenueCatSubscription managementUser ID, subscription status
Apple / GoogleSign-in and paymentsPer their own privacy policies
ipapi.coApproximate location from IP (analytics only, opt-in)IP address
SentryCrash and error diagnosticsError details and stack traces, App and device version, random installation identifier (not your account identity or recipe content)
ApifyRetrieving content from the URL you submitThe URL (not your identity)
Google (Gemini)AI recipe extractionContent of the submitted URL (not your identity)

Some providers store data outside Australia (e.g. the United States). Where they do, we rely on their standard data-protection commitments.

5. Retention

6. Deleting your account and data

You can delete your account in Settings → Delete account. This permanently deletes your account record, profile, and cloud recipe library, and unlinks or deletes your analytics events. Subscription billing is managed by Apple or Google — deleting your account does not cancel an active subscription; cancel via your App Store or Google Play subscription settings. You may also request deletion or a copy of your data by emailing recipefetch@metrium.com.au; we respond within 30 days.

7. Your rights

Depending on where you live, you may have rights to access, correct, delete, or receive a copy of your personal information, and to object to or restrict certain processing (including rights under the Australian Privacy Principles and, for EU/UK users, the GDPR/UK GDPR). To exercise any of these, email recipefetch@metrium.com.au. If you are unsatisfied with our response you may complain to your local privacy regulator (in Australia, the OAIC).

8. Security

Data is transmitted over encrypted connections (TLS) and stored with access controls, including row-level security so that only you can access your recipe library. No system is perfectly secure; we will notify affected users and regulators of any data breach as required by law.

9. Children

The App is not directed at children under 13 (or the equivalent minimum age in your country), and we do not knowingly collect their information.

10. Changes

We will post any changes to this policy at this URL and update the date above. Material changes will be flagged in the App.