Privacy Policy
Effective date: 5 November 2026
This policy covers the Krumbs: Recipe Keeper apps for iOS and Android and this website (krumbs.com.au). Krumbs is built so that your recipes stay yours: there is no account to create, nothing to sign up for, and no advertising or tracking of any kind.
At a glance
- No account, no sign-up, and no personal profile — we don't know who you are.
- Your recipes are stored on your device and, if you use iCloud, in your own private iCloud database that we cannot access.
- No ads, no advertising identifiers, no usage analytics of our own, and no data sold or shared for marketing — ever.
- Some recipe content is processed by a cloud service when on-device extraction isn't available or fails, and anonymous error reports help us fix bugs. Both are described in full below.
- On Android, there is no cloud sync and every import uses the cloud service.
What Krumbs doesn't collect
Krumbs has no accounts, so it never asks for your name, email address, or any other personal details. The app contains no advertising SDKs and no analytics SDK of our own, does not use advertising identifiers, and does not track you across apps or websites. On Android, the text-recognition library (Google ML Kit) reports its own usage and performance metrics to Google, as described under "Krumbs for Android".
Your recipes
Recipes you save — including ingredients, instructions, photos, meal plans, and shopping lists — are stored in a database on your device. If your device is signed in to iCloud, this data also syncs through your private iCloud (CloudKit) database, which is tied to your Apple ID and protected by Apple; we have no ability to read it. Apple's own privacy terms govern iCloud storage.
Turning links into recipe cards
When you save a link, Krumbs extracts the recipe from it. On devices that support Apple Intelligence, this happens on your device. When on-device extraction isn't available (older devices, or very long pages) or fails, the app sends the page's text or caption and its web address over an encrypted connection to our extraction service, which passes it to OpenAI's API to produce the structured recipe card. No name, account, or location is attached to these requests, the extraction service stores none of this content, and under OpenAI's API terms the content is not used to train their models. Each request to our extraction service carries an anonymous attestation produced by Apple's App Attest, which proves the request came from a genuine copy of Krumbs. It identifies your installation of the app, not you or your Apple ID. To prevent abuse, our service keeps the installation's attestation key for up to 90 days after its last use and a count of its requests per day; older versions of Krumbs that cannot attest are rate-limited by internet address for an hour at a time until they are retired.
Fetching the pages you share
To read a shared link, Krumbs fetches that page directly from your device, just as a web browser would. The website you shared from sees an ordinary page request coming from your internet connection.
Photos you add
You can photograph a printed recipe to import it. The text on the photo is recognised on your device using Apple's built-in text recognition; the recognised text then follows the same extraction path described above. Photos you attach to recipes stay with your recipes — on your device and in your private iCloud.
Purchases
Krumbs Pro is sold through Apple's App Store, and payment is handled entirely by Apple: Krumbs never sees your payment details, your name, or your Apple ID. The app asks Apple whether a Krumbs Pro subscription or purchase is active, and which version of Krumbs your Apple ID first downloaded (so that early users keep unlimited imports). Both checks happen on your device; their result goes nowhere except, if something goes wrong, as technical context inside an error report as described below.
Krumbs for Android
Krumbs for Android has no cloud sync. Your recipes, photos, meal plans and shopping list are stored on your device, not in any cloud service of ours. If Android's automatic backup is turned on, Android may copy the app's database and settings to your own Google Drive, as it does for other apps; the photos are excluded from that backup.
On Android, every recipe you import is read by the extraction service described under "Turning links into recipe cards"; there is no on-device extraction. The same applies to the text recognised from a photo.
In place of Apple's App Attest, each request to our extraction service on Android carries a Google Play Integrity token, which lets Google confirm that the request came from a genuine, unmodified copy of Krumbs. It identifies your installation of the app, not you or your Google account. The request also carries a random identifier for your installation, created by the app, which our service counts against a daily limit to prevent abuse and keeps for 48 hours.
On Android, Krumbs Pro is sold through Google Play, and payment and refunds are handled entirely by Google: Krumbs never sees your payment details. The app asks Google Play on your device whether a Krumbs Pro subscription or purchase is active.
On Android, Krumbs sends the same error reports as described under "Diagnostics and error reporting": crash reports, reports of the app becoming unresponsive, and error reports, with the Android version in place of the iOS version. Error reports may also include the links of your recent imports.
On Android, the text on a photo is recognised on your device by Google's ML Kit text recognition. ML Kit reports its own performance and usage metrics to Google (device and app information, a per-installation identifier, timings and the image size); Google states that it does not send the photo or the recognised text.
Google Play's Data safety section files error diagnostics under its "Analytics" purpose; Krumbs itself collects no usage analytics.
Diagnostics and error reporting
So that we can find and fix problems, Krumbs sends an automatic error report when something goes seriously wrong (on Android, also reports of the app becoming unresponsive) — for example, when a recipe fails to extract. Reports go to Sentry, an error-monitoring service (data ingested in the EU), and include technical context such as device model, iOS or Android version, app version and what went wrong. Extraction-failure reports also include the shared link and the captured page or caption text, so we can reproduce the failure without asking you for anything. Each report also carries a random identifier that the error-reporting service creates for your installation of the app. These reports are not tied to your identity, are used only for fixing problems, and are never used for advertising or analytics. Error reports are deleted automatically after 90 days; to ask for earlier deletion, email support@krumbs.com.au.
Notifications
On iOS, Krumbs uses silent background notifications solely so iCloud can tell the app that your recipes changed on another device. On Android, Krumbs shows a notification on your device when a recipe you shared has been imported in the background, could not be imported, or is waiting for room in your library, and, on older Android versions, while it is importing; on Android 13 and later it asks for permission first. On either platform, Krumbs sends no marketing or promotional notifications.
Export and deletion
You can export any cookbook as a file at any time and keep it wherever you like. Deleting a recipe removes it from your device and, via sync, from your iCloud database; deleting the app removes all local data. To remove the app's iCloud data as well, go to Settings → your name → iCloud → Manage Account Storage on your device. On Android, deleting a recipe removes it from your device, and deleting the app removes all local data. Android's own backup may still hold a copy of the app's database and settings in your Google Drive: you can delete that backup in the Google Drive app under Backups (this deletes the backup of your whole phone, not only Krumbs' copy), and stop future backups by turning backup off in your phone's Settings → Google → Backup (the exact path varies by phone).
Children
Krumbs is not directed at children under 13 and, as described above, collects no personal information from anyone — including children.
This website
krumbs.com.au is a static site. It sets no cookies and runs no analytics or tracking scripts.
Changes to this policy
If Krumbs' data practices change, we will update this page and revise the effective date above.
Contact
Krumbs is developed by Microcline Pty Ltd in Australia and handles personal information in accordance with the Australian Privacy Principles. Questions or requests about privacy: support@krumbs.com.au.