Privacy policy
This policy explains what Recipe Runner collects, why, who can see it, and how you can delete it. Recipe Runner is operated by RAZR Systems LLC, a New Mexico limited liability company (“we”, “us”). We decide how your personal information is used. The policy covers the Recipe Runner apps for iPhone, iPad and Android, and this website, reciperunner.app. If anything is unclear, write to us at support@reciperunner.app.
On this page
The short version
- We collect what’s needed to run the app: your account, and the recipes, photos, notes, books and shopping lists you create or import.
- When you import a recipe, what you submit is sent to Amazon Bedrock, where Anthropic’s Claude Haiku model reads it and extracts the recipe. It isn’t used to train models. Recipe text from a public page may be kept, with no account information, and reused for later imports of that page.
- You share a book or a shopping list only by typing someone’s exact email address, or by picking that one address from your contacts. We never upload your address book.
- The camera is used only when you take a photo. On iPhone and iPad, Reminders stays on the device: we don’t upload your reminder lists.
- No advertising, and we don’t track you across other companies’ apps or websites or sell your data. If Share usage statistics is on, we keep counts of imports, finished cooks and time in the app, tied to your account. You can turn that off. You can delete your account in the app, or ask us by email.
Information we collect
Your account
Your email address, a display name and a password. The password is stored only as a salted Argon2id hash, so we can’t read it. We also keep settings such as your units and which notifications you want.
Recipes, photos, notes, books and shopping lists
The recipes, photos, notes and books you create or import, including note photos and a book’s cover, title and description. When you import from photos, the pages you submit are kept with the recipe as its source. Shopping lists you make, the recipes and servings on them, items you type, aisle choices, check-offs and your pantry staples are stored with your account.
Your personal activity
Favorites and cook history (when you cooked a recipe, and any rating or note you add) are private to you. People you share a book with can’t see them.
People you invite
The email addresses you type, or the single address you pick, when you share a book or a shopping list. If that person has no account, we store the address to deliver and activate the invitation. On iPhone you pick it with the system contact picker. On Android you pick it with the system contact picker. In both cases we receive only the address you choose, not your contacts.
Camera and photos
The camera is used when you scan recipe pages or take a photo for a recipe, a note or a book cover. You can also pick photos from your library. We don’t get access to the rest of your camera roll. Photos you save are uploaded to our servers. When we resize a photo we remove embedded metadata, such as a location stored in the file.
Reminders, on your iPhone or iPad only
If you tap Send to Reminders or Add to Reminders, the app asks for access to Reminders and writes the list you chose into the Reminders app on that device. That access stays on the device. We don’t receive your reminder lists, and we don’t read back what you tick in Reminders. Android doesn’t use Reminders. There you can hand a list to another app as text, and only the app you pick receives it.
Notifications
Timer alerts are scheduled on the phone itself. On iPhone and iPad, if you allow notifications, we also store that device’s push token and the app version so we can tell you when an import finishes or a book is shared with you. The Android app shows those notices on the device and does not register a push token with us.
Usage statistics
Settings includes a switch called Share usage statistics. While it is on, we count three things for the signed-in account: recipe imports, both the total and how many were unique; recipes cooked, which is a cook-mode completion (cook mode reached the last step, or the cook stayed open for at least three minutes); and about how many minutes the app is in the foreground. These are counts. They don’t include recipe text, photos, notes or who you share with. We store them as Amazon CloudWatch metrics and as a per-account daily total in our database. A daily total is kept for about 400 days, and the records for your account are deleted when you delete the account. The all-time totals have no account on them and stay. There is no third-party analytics SDK. This is not advertising, and it is not used to track you on other apps or websites. Turn the switch off and we stop adding to those counts.
Technical information
To limit abuse we count sign-in, sign-up and similar attempts per account and per IP address for a short time. Our host’s servers may keep standard logs, such as the time of a request and the IP address it came from. Our own logs don’t include recipe text, photos, email addresses or tokens. Crash reports are described under who we share it with.
How imports work
When you import a recipe from photos, a link or pasted text, what you submit is sent to Amazon Bedrock, a service from Amazon Web Services. Bedrock runs Anthropic’s Claude Haiku 5.5 model on a United States inference profile. A request from our region may be processed in AWS us-east-1, us-east-2 or us-west-2. The model reads the submission and extracts one recipe. For a link, our servers fetch the public page, or use the copy your phone sent. The result comes back as a draft you review before saving.
What you submit is used to create your recipe. Amazon does not use Bedrock inputs or outputs to train models. Imported recipes are private to you unless you add them to a book or a shopping list you share.
For a public recipe page, we may keep the recipe text we read (not the page’s markup, ads or comments) and the recipe we extracted, together with the page’s address and site name. That copy has no account information and no user id. We reuse it when someone later imports the same page and the text, the parser, the prompt and the model still match, and the stored parse is less than 90 days old. The stored copy itself has no expiry: deleting your account does not remove it, and we keep it so later imports of that public page don’t have to be read again. Photos of your own cards and books are not put in this shared cache. A short-lived copy of a page your phone sent for an import is kept for about a day so a retry can use it, then deleted.
Sharing, invitations and notes
- Only the owner of a book or a shopping list can share it, and only by an exact email address. We never suggest, search for or look up people.
- A shared book is view-only. People you share it with can view the recipes, cook from them, mark favorites and add notes. They can’t change or delete your recipes, or share the book onward.
- A shared shopping list is a list you shop from together. People on it can see changes, check items off and edit lines. If you delete your account, a shopping list you own is deleted for everyone on it. A book you own that other people can still see is not deleted; see deleting your account.
- People in a shared book or list see each other’s display names, not email addresses. As the owner, you see the addresses you invited.
- Notes on a recipe are visible to everyone who can see that recipe, including through a different shared book. A note shows its author’s display name, its date and its photos.
- Invitations and “shared with you” messages are emailed through Amazon SES. Anyone who receives an invitation can stop further invitations to that address with one click. To honor that, we keep a one-way hash of the address rather than the address itself.
- You can remove people or cancel invitations, and anyone can leave a shared book or list.
How we use information
- To run Recipe Runner: to sign you in, store and sync your library and shopping lists, and extract recipes from what you import.
- To send the emails the app needs: verification, password reset, invitations and notices about shared books.
- To send notifications you’ve allowed, such as an import finishing or a book being shared with you.
- To keep the service secure, for example by limiting repeated sign-in attempts and how many invitations one person can send.
- To find and fix crashes, when crash reporting is turned on for a build.
- To see how the app is used, when Share usage statistics is on: the import, cook and foreground counts described above. Not for advertising.
We don’t use your information for advertising, and we don’t sell it.
Who we share it with
A few companies process information to provide their service to us. They don’t receive it for their own advertising.
- Amazon Web Services hosts the apps’ servers, database and photo storage in us-west-2 (Oregon), sends email through Amazon SES in us-east-1, and runs Amazon Bedrock for imports. The Claude model that reads imports runs inside Bedrock, in the United States.
- Apple delivers push notifications to your iPhone or iPad when you allow them. Apple also provides Reminders on the device, which we don’t upload.
- Sentry can receive crash reports from the iPhone and iPad app, and only from a build we have configured to send them. Those reports are scrubbed: they don’t include recipe content, email addresses, tokens, your name or the device name. The Android app does not send crash reports to Sentry. Usage statistics, when you allow them, stay on our own AWS account. They are not sent to an analytics company.
- Pwned Passwords (Have I Been Pwned) is a public list of passwords found in data breaches. When you choose a password we check it by sending the first five characters of a hash of that password, never the password or your email address.
The people you share a book or a shopping list with see what the sharing section describes. We may disclose information if the law requires it.
No advertising, no tracking
Recipe Runner has no advertising. We don’t track you across other apps or websites, and we don’t use a third-party analytics SDK. The usage counts above, when Share usage statistics is on, stay with us. This website sets no cookies and loads nothing from other companies: no fonts, scripts, analytics or trackers. The only requests its pages make go to our own servers.
Storage and retention
Your account and the content you save are stored on Amazon Web Services in the United States, in the us-west-2 (Oregon) region. Email is sent through Amazon SES in us-east-1. Imports may be processed in us-east-1, us-east-2 or us-west-2, as described above.
We keep your account data until you delete it or delete your account. Photos and uploads are removed when you delete them, or the recipe, note or book they belong to. Uploads that never get attached to anything are removed after 7 days. A page snapshot sent from your phone for an import is removed after about a day. Deleted notes, deleted recipes and ended invitations leave a short record so your other devices can catch up; the note’s text and photos are removed immediately, and the leftover record, including an invitation’s email address, is removed after about 30 days. The one-way hash we keep so we can honor “stop invitations” does not include the address itself and stays until you ask us to remove it.
Database backups can be restored for up to 35 days, so deleted account data can remain in a backup for up to that long. The shared import cache described under imports is not part of your account and is kept without an expiry date. Daily usage totals are kept for about 400 days unless you delete your account sooner, which removes them.
Deleting your account
You can delete your account in the app: Settings, then Account, then Delete Account. You can also ask without the app, as described at Delete your account. Deleting starts immediately and signs you out. The rest is removed shortly after.
This deletes your profile, your password, your devices and push tokens, your favorites and cook history, your pantry and aisle memory, your imports and uploads, the usage counts stored for your account, and the recipes you own that aren’t in a book still shared with other people, along with their notes and photos. It removes your notes everywhere, including on other people’s recipes, and takes you out of books and shopping lists that were shared with you. A shopping list you own is deleted for everyone on it. Lines you added or checked on someone else’s list stay on that list.
If you own a book that other people can still see, we don’t delete it out from under them. The book, and the recipes in it with their photos, is handed to its members. They can keep viewing and cooking from it and adding notes, and one of them can claim ownership. Your notes are removed, and pending invitations to that book are cancelled. A book with no other members is deleted.
Deleting your account does not remove the shared import cache, the “stop invitations” hash, or copies that can remain in backups for up to 35 days.
How we protect your information
- Information is encrypted in transit (HTTPS) and at rest.
- Photos are stored privately. The app checks that you’re allowed to see a recipe before it gives out a short-lived link to a photo.
- Every request is checked so people can only reach their own data and what has been shared with them.
- Passwords are stored as salted Argon2id hashes, and passwords found in known breaches are rejected.
- Sign-in, sign-up and similar requests are rate-limited.
- On an iPhone or iPad, sign-in tokens are kept in the Keychain. On Android they are encrypted with a key in the Android Keystore. Android backup and device transfer exclude the app’s files, so that copy isn’t moved to another device.
No system is perfectly secure. If you think someone else is using your account, change your password and email us.
Children
Recipe Runner isn’t directed at children under 13, and we don’t knowingly collect personal information from them. If you believe a child under 13 has given us personal information, email support@reciperunner.app and we’ll delete it.
Your rights and choices
You can ask what personal information we hold about you, ask us to correct it, and ask us to delete it. Email support@reciperunner.app from the address on your account. You can also:
- change your display name and preferences in Settings;
- export your recipes as a JSON file from Settings;
- delete your account in the app, or from the account deletion page;
- turn notifications off in the app and in the system settings;
- decline the camera, Reminders or notifications and keep using the rest of the app;
- turn off Share usage statistics in Settings, which stops new usage counts;
- stop invitations to your address with the link in any invitation email.
Changes and contact
If we change this policy, we’ll post the new version on this page and update the date above. If a change materially affects how we use personal information, we’ll also tell you in the app or by email.
RAZR Systems LLC
New Mexico, United States
support@reciperunner.app