Your data, kept simple.
Effective 20 September 2026
MiSousChef doesn’t have an account, a sign-in, or a server. There is nothing to create, nothing to log into, and nothing tied to an identity. Everything below describes what actually happens, verified against the app’s own source code — not a legal template.
Your recipes stay yours
Your saved recipes and meal plans sync through your own private iCloud account — the same mechanism Apple uses for Photos or Notes. That data moves directly between your devices through Apple’s infrastructure. There is no MiSousChef server in the middle, which means the developer cannot see, access, or recover your recipes. If iCloud isn’t available, the app stores everything on your device instead and works fully offline.
What actually leaves your device
MiSousChef makes outbound network requests in exactly two situations, both initiated by you and run from your own device:
- When you import a recipe from a link, the app fetches that page directly from the website you chose, to read the recipe off it.
- To build your Discover feed, the app checks the cooking blogs and sites on its curated source list for new recipes.
Neither of these touches a MiSousChef server, because none exists. No third-party analytics, no ad tracking, no telemetry, no crash-reporting library. The app ships with zero third-party SDKs and zero remote package dependencies of any kind — that’s a statement about what code is and isn’t in the app, not a policy promise.
Purchases
Any purchase you make in MiSousChef is handled by Apple’s In-App Purchase system. Apple processes the transaction and handles your payment details end to end — MiSousChef never sees your card number, billing address, or any other payment data.
Questions
If anything here is unclear, or you want to ask about a specific case, email [email protected]. That address goes straight to the developer, not a support queue.