Last updated: 28 September 2026
Recimama is a cooking app made by David Rodriguez (“we”, “us”). This policy describes what the app does with your information: what stays on your device, what goes to your own iCloud, what becomes public if you publish a recipe, and what other websites receive when you ask the app to fetch something.
In short: Recimama has no accounts, no ads, no analytics and no tracking, and it contains no third-party code. Your recipes stay on your device and in your own private iCloud, which we cannot see. We can see something about you in only two situations: when you publish a recipe to Explore, which makes it public, and when you report something or email us.
Recimama keeps these on your iPhone or iPad. If you’re signed in to iCloud, they are also copied to your own private iCloud, unless you turn sync off (section 2):
These stay on this device only:
The app’s widgets, its Siri shortcuts and its Share and Safari extensions read a small summary of this (what’s cooking, what’s planned for today, recipes you’ve clipped). That summary lives in a storage area shared only by Recimama’s own parts on your device. If you have a paired Apple Watch, the step you’re on and the steps coming next are sent straight to the watch while you cook, through Apple’s WatchConnectivity.
Settings > Storage > Sync with iCloud is on unless you turn it off. While it’s on and you’re signed in to iCloud, everything in the first list in section 1 (your recipes and collections, plans, pantry, saved menus, cooking history, and your rotas and their sign-ups) is copied to your private iCloud database so it appears on your other devices. That database belongs to your Apple Account. We can’t read it, and nobody else can unless you share a rota from it (section 5). Apple stores it under Apple’s own terms and privacy policy.
Turning the switch off stops this copying from the next time you open the app, and straight away stops new rotas being put in iCloud automatically (section 5). What is already in iCloud stays there until you delete it (section 12). A rota you have already shared stays shared, so the people on it aren’t cut off, until you stop sharing it. If you tap Share > Invite people > Invite with a link while the switch is off, that one rota is put in iCloud, because that is what the button is for. The switch doesn’t affect publishing to Explore (section 3).
Explore is where people share recipes with everyone who uses Recimama. Nothing is published unless you choose to. For each recipe you publish, you open its menu, choose Share with everyone, agree to the community guidelines (asked once), and tap Share this recipe. Publishing needs you to be signed in to iCloud; browsing doesn’t.
What is published. The recipe is saved in Recimama’s public iCloud database, which Apple hosts for us. The record contains:
Who can see it. Anyone using Recimama can see your published recipe, including people who aren’t signed in to iCloud, and anyone can add a copy to their own library. We can also see everything in the public database, including the iCloud identifier.
What you can’t publish. Only recipes you wrote yourself can be published. The app refuses recipes imported from websites, recipes read from a photographed page, recipes that came from Explore or from another person, and recipes written by following a recipe published on a website. Before anything is published, the app checks its text for words Explore doesn’t allow, on your device, and refuses if it finds one. Nothing is sent when a recipe is refused.
Taking it down. In the recipe’s More menu choose Shared — manage it, or go to Explore > More > Recipes you shared. Swipe left on the recipe, tap Take down, then confirm with Take it down. The recipe stops appearing in Explore for everyone. Copies that people have already added to their own libraries stay with them. We can’t reach those, and neither can you.
If you can’t take it down yourself (for example, you have a new phone), email rodrigobayapps@gmail.com with the recipe’s title and roughly when you published it. We’ll delete it, usually within 24 hours. If you’d like us to remove everything you’ve published, tell us, and we’ll delete all the public records carrying your iCloud identifier.
Reporting. Every Explore recipe has a Report button. A report records which recipe you reported, the reason you chose, any comment you add (up to 200 characters), the time, and the identifier of the cook who published it. It is saved to the public iCloud database, where only we can read it; other users can’t. iCloud also attaches your iCloud identifier to it, as it does to anything saved there.
If the report can’t be sent (for example, you’re offline), the app offers to email it to rodrigobayapps@gmail.com instead. That email comes from your own mail account, so we’ll see your email address and anything you add. We use these details only to act on the report.
What we do with reports. We review every report within 24 hours. If a recipe breaks the community guidelines, we delete it. If a cook keeps breaking them, we add their iCloud identifier to a blocked list, which Recimama checks so their recipes are hidden for everyone. The blocked list contains identifiers only, no names.
Blocking a cook. Block hides everything that cook publishes on your device, and also sends us a report saying you blocked them, so we can spot someone many people are blocking. Hide this hides one recipe on your device and tells nobody. Your blocked and hidden lists stay on your device. You can undo them from Explore’s More menu.
A meal rota (people taking turns to bring meals) or a dinner party (“A meal with friends”) reaches the people you send it to, and anyone they pass it on to. We never see any of it.
These go wherever you send them (Messages, Mail, AirDrop and so on), and the recipients’ apps handle them under their own terms.
Share recipe, Make a card and Settings > Backup > Export a backup create files (a recipe file, an image or PDF, or a backup of your whole library). They go only where you send or save them, and we never receive them.
Apart from iCloud, the app connects to other websites only when you ask it to, and only to do what you asked:
| When you… | The app contacts… | What it sends |
|---|---|---|
| use Find one on the web (the in-app browser) | DuckDuckGo if you type words (with “recipe” added unless you typed it), or the site you type or tap | your search or the address, as any browser would |
| import a recipe from a page you have open (in Safari with the extension, or in the in-app browser) | the address of the recipe’s photo, if the page gives one | a request for the photo |
| share a link to Recimama, or use From a video link | the site of the link; then, if that page has no recipe, up to three recipe links found in its caption (or anywhere on the page, if it has no caption) | a request for those pages. No photo is fetched. |
| use What’s in my fridge, Recreate a dish or Photograph a menu | DuckDuckGo, then up to three recipe pages from its results | the dish name you confirmed, or up to five ingredient names you confirmed, plus the word “recipe”. The photo itself is never sent. |
Like any web request, these reveal your device’s IP address and ordinary technical details to the site. The shared-link, video-link and “invent” requests identify the app as Safari on a Mac, and most of them ask for English pages, because many sites won’t serve a page otherwise. The requests carry no identifier of ours, and we never see them. Each site handles what it receives under its own privacy policy. The in-app browser keeps no cookies or history once you close it. Sites contacted by the other requests can set cookies, which stay inside Recimama on your device, and we never read them.
Recimama asks for each permission when you first use the feature that needs it:
You can change any permission in the iPhone’s Settings > Apps > Recimama.
Recimama has no sign-up or login and no account with us. It contains no analytics, advertising, crash-reporting or other third-party code. It doesn’t use the advertising identifier and doesn’t track you across other companies’ apps or websites. It doesn’t sell or share your information with anyone. If you’ve chosen to share crash reports with app developers in the iPhone’s settings, Apple may pass us crash logs under Apple’s own privacy policy.
Because it has a web browser, Recimama is rated 16+ on the App Store in most places (15+ in Korea, and 17+ on devices using a system older than version 26, shown as 18+ in France). It isn’t directed at children. We don’t knowingly collect personal information from children. If you believe a child has published something to Explore, email rodrigobayapps@gmail.com and we’ll remove it.
| Information | Kept | How to delete it |
|---|---|---|
| Your library, plans, pantry, history | Until you delete it | Delete it in the app, or delete the app. For the iCloud copy: iPhone Settings > [your name] > iCloud > Manage Storage > Recimama. |
| Rotas and dinner parties | Until you delete them | Deleting a live-shared rota you organise removes it for everyone who joined. Deleting a live rota you joined takes you off it; call off any meal you signed up for first if you don’t want it left on the rota. A rota that isn’t live-shared is deleted only from your own devices. Rota files, invitations and messages you have already sent stay with the people you sent them to. If you stopped sharing a rota before deleting it, a copy stays in your private iCloud; deleting Recimama’s iCloud data (first row) removes it, along with the iCloud copy of your library. |
| A recipe you published | Until you or we take it down | “Take it down” (section 3), or email rodrigobayapps@gmail.com |
| Reports | Until we’ve dealt with them, then deleted, except where needed to deal with repeated abuse | Email rodrigobayapps@gmail.com |
| Blocked list entries | While the block stands | Email rodrigobayapps@gmail.com to ask for a review |
| Emails to us | As long as needed to answer you | Ask us to delete them |
You can ask us what we hold about you, and ask us to correct or delete it, by emailing rodrigobayapps@gmail.com. The only information we can link to you is what you published or sent us: recipes, reports and emails. Because we don’t know who you are from your iCloud identifier, tell us which recipes are yours (or send the request from the device you published from), so we can find them. You can withdraw consent at any time: take down what you published, stop sharing a rota, turn off iCloud sync (which stops your library being copied to iCloud and new rotas being put there automatically; a rota you already shared stays shared until you stop sharing it, as section 2 explains), or turn off a permission. Depending on where you live, you may also be able to complain to your data-protection authority.
Where the law asks us to state a legal basis: we publish your recipe because you asked us to, and we handle reports and blocks because keeping Explore safe is in the legitimate interest of everyone who uses it.
If this policy changes, the new version will be posted on this page with a new date. We’ll mention significant changes in the app’s release notes.
David Rodriguez — rodrigobayapps@gmail.com — Support
The community guidelines are here. Both links are also in the app under Settings > About.