Plain English summary of what data Recipe Developer collects, where it goes, and the choices you have.
Effective 19 June 2026
Recipe Developer (the "app", "we", "us") publishes the Recipe Developer iOS app. We are the data controller for any personal data processed through the app. You can reach us at support@recipedeveloper.co.uk.
Recipe Developer is designed to keep your content on your device. The categories below describe everything the app touches, where it goes, and why.
The following data is stored locally on your iPhone or iPad. If you have iCloud Drive enabled, iOS syncs it to your private iCloud account using Apple's CloudKit — we don't have access to it.
Recipe Developer uses AI to turn a TikTok video, a cookbook photo, a web link, or a voice note into a structured recipe, and to help you create new recipes from a prompt. This processing runs on our server using AI services we operate — you don't need to bring your own API key. Each AI import uses one credit (see Payments and credits).
When you run an AI import, the app sends the content of that import to our server, which calls our AI provider on your behalf and returns the structured recipe. Depending on the import, the content sent includes:
We use the following AI providers as our processors. Your import content passes through them only to produce your result; we don't use it to build products of our own:
Your import content is processed in transit to produce the result and is not stored on our server afterwards. The credit balance we keep (see below) records only that an import happened, never what it contained.
We run a small server on Cloudflare Workers that powers the features below. None of it requires you to create an account or give us your name or email.
As described in AI processing and credits, the content of an AI import is sent to our server, which calls our AI provider to produce a structured recipe and returns it. The content is processed in transit and not stored afterwards. Each successful import deducts one credit from your balance.
Audio you dictate or audio extracted from a video you import is uploaded to our server, which proxies it to OpenAI's Whisper API for transcription using a key we operate. The audio is processed in-memory and not stored. The resulting transcript is returned to your device and used for recipe extraction (see above). Each successful transcription deducts one credit.
When you share a TikTok, Instagram, YouTube Shorts, or similar video URL into the app, our server fetches the public metadata and the video's audio track so the audio can be transcribed (step 2). We do not store the video or its audio after processing.
To meter AI imports we keep a small credit ledger on our server, stored in Cloudflare KV. It is keyed to a random per-user identifier derived from your iCloud account, and holds only: your current credit balance, whether you've received your one-time free starter credits, and the identifiers of credit packs you've purchased (so a purchase isn't applied twice). It contains no recipe content, no name, and no email. When you buy a credit pack, the app sends us the store's signed purchase receipt so we can verify it and add the credits; we don't see your card or payment details (see Payments and credits).
When you tap "Share recipe", the app sends the recipe payload (title, ingredients, method, hero image) to our server and we generate a short URL. Anyone who has the URL can open the recipe in a browser preview and tap through to the app. Shared payloads are stored in Cloudflare KV and auto-expire after 90 days.
If you pair the optional browser extension with the app, the extension drops recipe URLs into a per-pairing inbox on our server. The app polls the inbox and removes items once imported. Inbox tokens and items are stored in Cloudflare KV and removed when you unpair or when the app deletes them after import.
Cloudflare, as our hosting provider, logs basic request metadata (IP address, timestamp, request path, user-agent) for the purpose of operating the service and mitigating abuse. This is described in Cloudflare's privacy documentation. We do not connect this metadata to any in-app identifier.
We use Google's Firebase Analytics and Firebase Crashlytics to understand which features people use and to detect crashes.
tiktok.com) — never the URL itself or its content.20-49). We don't record exact counts and we don't record any recipe content.Firebase is operated by Google. Data is processed in line with Firebase's privacy and security policy.
Recipe Developer is free to download. AI imports are paid for with credits: you get a small number of free starter credits, and you can buy more in the app as one-time credit packs. There is no subscription.
Purchases are handled by the app store you downloaded from — Apple's App Store or Google Play — not by us. The store processes the payment and any refunds under its own terms (Apple Media Services Terms / Google Play Terms of Service). When you buy a pack, the app sends us the store's signed purchase receipt so we can verify it and add the credits to your balance. We never see your card number or payment details, and the store does not share your name or contact details with us.
If you are in the UK, the EU, or another jurisdiction with similar laws, you have rights over personal data we hold about you, including:
Because the app is built so that we hold as little of your data as possible, most of these rights you can exercise yourself from inside the app: delete a recipe, unpair the extension, uninstall the app. If you want us to delete a specific shared-recipe link, delete your credit ledger, or you have any other request, email support@recipedeveloper.co.uk and we will action it within 30 days.
Our lawful basis for the limited processing we do is your consent (analytics, when enabled) and our legitimate interest in operating and improving the app (sharing, transcription, crash reports).
Recipe Developer is rated 4+ on the App Store and is suitable for general audiences, but the app is not directed at children under 13 and we don't knowingly collect personal data from them. If you believe a child has provided us with personal data, contact us and we will delete it.
We will update this page when we change how we handle data — for example, if we add a new AI provider, change retention windows, or replace a third-party service. The "Effective" date at the top of the page reflects the most recent update. For substantive changes we will also notify you in the app on next launch.
Privacy questions, data requests, or anything else legal: support@recipedeveloper.co.uk.