This policy explains what information Recipe Box collects, what it does with it, and what it does not do. It applies to the Recipe Box app published by Sharon Louise Palmer (“we”, “us”) on the Apple App Store.
There is no account, no sign-in and no server of ours. Your recipes live on the device you wrote them on, and nowhere else. Photographs and PDFs are read on the device itself. The only information that reaches a company other than Apple concerns your subscription, and it is limited to what is needed to confirm that the subscription is genuine and still active.
Everything you write, import or scan is stored on the device you did it on, in the app’s own private storage. It is not copied to us, and there is no account under which it could be. We have no server, no database and no dashboard in which your recipes could appear. What we receive is nothing at all.
The app does not sync between devices. A recipe saved on your iPhone stays on your iPhone, and the same app on an iPad starts with an empty cookbook. This is worth saying plainly, because a good many apps work the other way.
Your device’s own backup is the exception, and it is Apple’s rather than ours: iCloud Backup, or an encrypted backup to a computer, includes this app’s data along with every other app’s, and restoring a device from one brings your cookbook back with it. That backup sits in your own account under Apple’s privacy policy, and we cannot read it.
Deleting the app deletes the recipes with it. Take a PDF of anything you want to keep first — every recipe shares as a PDF, free, from its own page.
When you scan a recipe, the text is read by Apple’s Vision framework running on the device. When you import a PDF, it is opened and read on the device. In both cases nothing is uploaded, no image or document is sent anywhere for processing, and the feature works with the phone in aeroplane mode.
You can photograph a page in the app — a page from a book, or a recipe written out by hand. iOS asks your permission the first time, and the camera is used for nothing else: there is no video, no scanning of anything but the page in front of it, and no frame is kept except the pages you actually capture. Those pages are read on the device and become a draft recipe; the first of them is kept as the recipe’s picture, stored the same way the recipe is. Nothing from the camera is uploaded. If you refuse the permission, everything else in the app carries on working and you can still pick a photograph you have already taken.
If you pick an image from your photo library instead, iOS hands the app only the picture you chose — the app cannot see the rest of your library, and it is never asked for access to it.
When you paste a link, your device asks that website for the page, directly. The request does not pass through us — there is nothing in the middle, and we never learn which address you pasted or which recipes you save.
The website at the other end does see something, and it is the same thing it would see if you had opened the page in Safari: your IP address, the address requested, and a user-agent string. The app identifies itself as a mobile browser, because a great many recipe sites serve a stripped-down page to anything that does not look like one, and the stripped-down page is the one with the recipe missing. That site’s own privacy policy governs what it does with the request.
All purchases and subscriptions are processed by Apple. We never receive your name, your Apple Account or your payment details, and no payment information passes through us.
We use Apphud, a subscription management service, to verify that a purchase is genuine and to measure how many people subscribe. Acting as our processor, Apphud receives:
Apphud does not receive your name, your email address, your payment details, or any recipe, photograph, shopping list or note you create in the app. Its handling of this information is governed by its own privacy policy. Processing takes place on servers operated by Apphud in the United States.
A recipe exported as a PDF is produced on your device and goes only where you send it using the iOS share sheet. We are not involved and receive nothing.
Content on your device is kept until you delete it or delete the app. A recipe you delete goes to Recently Deleted and is removed permanently after thirty days, or sooner if you empty it yourself. Subscription records held by Apphud are retained for as long as needed to support the subscription and to meet accounting and tax obligations.
Depending on where you live, you may have the right to ask what information is held about you, to have it corrected or deleted, to object to processing, or to receive a copy. Because there is no account, we identify records by device rather than by person.
Email sharonlouise@gmail.com from the device concerned and say what you would like done. We will action it with Apphud and confirm when it is complete. Your recipes are not part of any such request, because we do not hold them — those are yours, on your own device, to delete in the app or by deleting the app. Deleting the app stops any further information being sent.
Subscriptions are managed in Settings › Apple Account › Subscriptions. Deleting the app does not cancel a subscription.
The app is suitable for all ages. It asks for no personal information from anyone, including children, and has no messaging, profiles or contact between users.
We do not sell personal information and we do not share it for advertising or cross-context behavioural advertising. Apphud is the only third party that receives anything from the app, and only for the purposes described above.
If this policy changes, the revised version will be published on this page with a new date at the top.
Sharon Louise Palmer
sharonlouise@gmail.com