Ladle is an iPhone, iPad and Mac app made by me, Jess. It connects to your own Mealie server. The short version: Ladle has no accounts of its own, no ads and no tracking, and I don’t keep or see any of your information.
What Ladle stores
These are saved on your device:
- Your Mealie server’s address and the API token Ladle signs in with, in your device’s Keychain. Ladle never stores your password.
- Copies of the recipes, recipe pictures and shopping lists you’ve opened, so they still show when your Mealie can’t be reached
- Your settings, such as which shopping list you use and whether to keep the screen on while cooking
I can’t see any of it. If you back up your device, for example with iCloud Backup, this information is included in your own backup like the rest of your device.
What leaves your device
- Your Mealie server. Ladle talks straight to the Mealie server you enter. It reads your recipes, meal plan, shopping lists, and your own ratings and favorites, and saves the changes you make: adding or ticking off shopping items, changes to the meal plan, ratings, favorites, when you made a recipe, and recipes you save from websites. When you sign in with a password, Ladle sends it to your Mealie once and creates an API token named “Ladle on …” in your Mealie profile. Signing out deletes that token. On the account and household screens, Ladle also reads and saves what you change there: your name, email and password, invitations, people’s permissions and household settings, and, if you’re a Mealie admin, people’s accounts, households, groups and backups. A backup you download is saved on your device, and goes somewhere else only if you send it.
- Recipe websites, through your Mealie. When you save a recipe from a website, Ladle sends the link to your Mealie, and your Mealie fetches the page. Ladle doesn’t visit the page itself.
- Single sign-on, only if you use it. If you tap Sign in with …, your sign-in page opens in a secure browser window from Apple. What you type there goes to your sign-in service, not to Ladle. Ladle gets back a one-time code and passes it to your Mealie to finish signing in.
Nothing goes through me or anyone else. The sample recipes are built into the app, and looking at them sends nothing anywhere.
Invitations
An invitation code holds your Mealie’s address and a one-time invitation code made by your Mealie. Ladle draws the QR code on your device; it only goes somewhere if you show it or send it. When someone uses an invitation, Ladle sends the name, email, username and password they choose straight to your Mealie to make their account.
Notifications
Cooking timers use notifications your device schedules itself, only if you allow them. They aren’t sent from anywhere, and nothing about them leaves your device.
Sharing a page to Ladle
When you share a page to Ladle from Safari or another app, Ladle reads only the web link you shared and sends it to your Mealie. It uses the same sign-in as the app.
Ads, analytics and tracking
Ladle has none. It does not track you across apps or websites.
If you have chosen on your device to share analytics with app developers, Apple may send me anonymous crash reports and usage totals. They do not identify you.
Children
Ladle is not directed at children under 13 and does not knowingly collect information from them.
Deleting your information
Signing out in Ladle’s Settings deletes Ladle’s API token from your Mealie and the copies of recipes saved on your device. Deleting the app removes what it saved on that device. Your device may keep the sign-in in its Keychain, so if you delete the app without signing out, also delete the “Ladle on …” token in Mealie: open your profile, then API Tokens.
Mealie
Your recipes and lists live on your own Mealie server, which you (or whoever runs it) control. Ladle is an independent app. It is not made by, endorsed by or affiliated with the Mealie project.
Changes
If this policy changes, the new version will be posted on this page with a new date.
Contact
Questions? Email me at jessicahart94@icloud.com.