Privacy Notice

Privacy Policy for Recipe Catch

Effective Date: August 1, 2026 · Last Updated: August 1, 2026

David Perez, trading as miraiapps.de ("we," "our," or "us"), built Recipe Catch as an offline-first recipe-collection app. This Privacy Policy explains what information Recipe Catch collects, how it's used, and the choices and rights you have — wherever in the world you use the app, including the European Union.

By using Recipe Catch, you agree to the practices described in this Privacy Policy. If you do not agree, please do not use the app.

1. The Short Version

Recipe Catch is built to keep your recipes on your device:

• No account, no sign-in. We never ask for your name, email, or any credentials.
• Your recipes, photos, and notes are stored only on your device, in the app's local database. We never see them, and they are never uploaded to us or any server we operate.
• We do not operate any backend server that stores your content. There is nothing on "our side" to breach.
• We use two narrowly-scoped third-party services — RevenueCat (to run subscriptions) and TelemetryDeck (anonymous usage analytics) — described in full in Section 4.

The rest of this document exists to satisfy legal disclosure requirements (particularly the EU's GDPR) in more formal detail.

2. Information We Collect

2.1 Content You Create

Recipe titles, ingredients, instructions, tags, personal notes, and photos you add are stored exclusively in local storage on your device (Apple's SwiftData framework). This content:

• Is never transmitted to us
• Is never transmitted to any third party by us
• Is only included in an iCloud/device backup if you have enabled Apple's own device backup — a feature of iOS, not of Recipe Catch, and one we have no visibility into

If you use the "Paste Link" import feature, the web address you enter is sent directly from your device to the website you specify, exactly as if you'd opened that link in a browser — Recipe Catch fetches the page directly and does not relay it through any server of ours. That website's own privacy practices apply to that request; we have no visibility into what it or your network path logs.

2.2 Camera and Photo Library

If you grant camera permission, Recipe Catch can photograph a recipe card or handwritten note. To import a picture from your photo library instead, the app uses Apple's system photo picker, which runs in a separate, sandboxed process — Recipe Catch never requests or receives photo library access, and only sees the specific photo you pick. Text recognition ("Scan a recipe card or handwritten note") runs entirely on your device using Apple's on-device Vision framework — no image or extracted text is ever sent off your device or to us for this feature.

2.3 Purchases and Subscriptions

Recipe Catch offers an optional Premium subscription, processed by Apple and managed through RevenueCat, our subscription-management provider. See Section 4 for what RevenueCat receives.

2.4 Analytics

We use TelemetryDeck, a privacy-focused analytics provider, to understand anonymous, aggregate usage patterns (for example, that the app was opened). See Section 4 for details.

2.5 Notifications

If you allow notifications, Recipe Catch schedules reminders locally on your device using Apple's notification framework. No data about these reminders is sent to us or anyone else.

2.6 Information We Do NOT Collect

• We do not collect your name, email address, or any account credentials — there is no account system.
• We do not collect precise or approximate location data.
• We do not access your contacts, microphone, or health data.
• We do not use advertising identifiers (IDFA) and do not show ads.
• We do not sell, rent, or share personal data with data brokers.

3. How We Use Information

To the very limited extent any information exists outside your device (Sections 2.3 and 2.4), we use it to:

• Validate and manage your Premium subscription entitlement
• Understand aggregate, anonymous usage of the app to guide what we build next
• Diagnose and fix technical problems

We do not use any information to build advertising profiles, sell data, or make automated decisions that affect you.

4. Third-Party Services

Recipe Catch uses the following third-party services. Neither has access to your recipes, photos, or notes — those never leave your device.

We do not use advertising networks, social login, crash-reporting SDKs, or any service that shares data across apps for advertising purposes.

5. Data Retention

• Your recipes, photos, and notes: Stay on your device for as long as you keep the app installed, or until you delete them yourself.
• Subscription data (via RevenueCat): Retained by RevenueCat for as long as needed to manage your subscription and for their own legal/accounting obligations.
• Analytics data (via TelemetryDeck): Retained in anonymized/aggregate form. Because this data cannot be tied back to you, we cannot look up, export, or delete an individual person's analytics history.

6. Data Security

Because your content lives on your device rather than on a server we control, its security is primarily governed by your device's own security (passcode, Face ID/Touch ID, encryption at rest). For the limited data that does leave your device (Section 4), we rely on our providers' security measures, including encryption in transit (TLS/HTTPS).

No method of transmission or storage is 100% secure, and we cannot guarantee absolute security — but there is very little for us to secure in the first place, by design.

7. Your Rights

Because we don't hold an account or a server-side copy of your content, most rights below apply to the limited data described in Section 4, not to your recipes — which you already fully control on your own device.

For Users in the European Economic Area, UK, and Switzerland (GDPR)

• Data controller: David Perez, trading as miraiapps.de — see Section 10 for contact and our Impressum for our full legal notice.
• Lawful basis: performance of a contract (subscription entitlement via RevenueCat); legitimate interest (anonymous, aggregate analytics via TelemetryDeck).
• Right to lodge a complaint: with your local data protection supervisory authority. In Germany, this is the authority of the state (Bundesland) in which David Perez is based (Bavaria).
• International transfers: where our processors process data outside the EEA, they rely on appropriate safeguards such as Standard Contractual Clauses. TelemetryDeck is a Germany-based provider.
• No automated decision-making or profiling with legal or similarly significant effects takes place.
• Data Protection Officer: given the size and nature of our processing, we are not required to appoint a DPO under Art. 37 GDPR / §38 BDSG.

For California Residents (CCPA/CPRA)

We do not sell or share personal information. You may request information about, or deletion of, any data held by our processors by contacting us. We will not discriminate against you for exercising any privacy right.

For Users in Other Jurisdictions

Wherever you are, we apply the same practices: minimal data collection, no first-party servers holding your content, and narrowly-scoped third-party processors.

8. Children's Privacy

Recipe Catch is not directed at children under 16 and we do not knowingly collect personal information from children.

9. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. Material changes will be reflected in the "Last Updated" date above and, where significant, announced in-app. The current version is always available at recipecatch.app/privacy.html and within the app under Settings → Privacy Notice.

10. Contact Us