Privacy
RitualHeart
Last updated 4 November 2026
The short version
RitualHeart has no account and no server of its own. What you keep in it (your lists, what you have at home, your recipes and your food diary) lives on your device and in your own private iCloud, and we cannot see it. We never sell your data. Only two outside services are involved: Google AdMob, which shows a non-personalized banner ad, and, only when you ask for it, the Open Food Facts database, which receives a barcode you scanned or asked a product photo for.
RitualHeart ("the app") is made by Wild Rose Works. This policy explains what happens to your information when you use the app. It reflects what the app does today; if that changes in a future update, this page is updated too.
Who is responsible
Razvoj programske opreme, Anja Remic s.p.Trnovec 6, 3332 Rečica ob Savinji, Slovenia
Registration no. 8971218000 · VAT ID SI99283425
[email protected]
Wild Rose Works is the trading name of this sole proprietorship. In this policy, "we" means Anja Remic s.p.
Your data stays in your own iCloud
RitualHeart is local-first. You do not create an account and you do not sign in to us. What you create in the app is stored on your device and, if you use iCloud, in your own private iCloud database (Apple's CloudKit), which syncs it across your Apple devices. That includes your shopping lists and items, what is in your storages, the prices and receipts you import, your recipes and cooking history, the photos you add to items and recipes, your food diary, the foods you save and your goal. We do not operate a server that receives this data, and we cannot see it. This data is handled under Apple's privacy policy.
Your food diary and household allergens
Two kinds of information in the app are about health: the food diary in Meals (what you ate, its calories and nutrients, the foods you save and your goal) and the allergens your household looks out for, which you can switch on in Settings. Both stay on your device and in your private iCloud. The diary's contents are kept in encrypted fields, encrypted on your device before they are uploaded. Neither is shared with the people you share a list or a storage with, sent to us, or used for advertising. The food diary is included when you export your data; the household allergens are not. The app does not use Apple Health (HealthKit).
The nutrition numbers, allergen marks and diet labels are general food information, worked out on your device from a built-in ingredient table and what you enter. They are estimates, not medical advice: always read the label.
Sharing a list or a storage
If you choose to share a shopping list or a storage, the people you invite can see it and, if you allow it, change it. They see everything in it: its items, notes, prices, where things were bought, and photos. Sharing happens through Apple's iCloud sharing, between your iCloud account and theirs. We do not process or store the shared content ourselves. You can stop sharing at any time from within the app. Recipes and the food diary are never shared.
To invite someone, you enter their email address or phone number. The app hands it to Apple's iCloud sharing to find that person's iCloud account; we never receive or keep it. Members of a shared list can see which member added, changed, moved or removed an item.
Change history and deleted items
The app keeps a log of recent changes to your shopping lists, such as an item being added, edited, moved or removed, and which list member did it, so that you can restore a deleted item or undo an edit. It is kept for 30 days or the most recent 500 entries, whichever is smaller.
What you delete in Storage or Recipes is also kept for 30 days, so that you can restore it, and is then deleted. On a storage you shared, the people it is shared with can see and restore what you deleted for that time.
These records are stored with your data on your device and in your iCloud, and nothing of them reaches us. You can clear them at any time: on the shopping list from ⋯ → Recently changed, in Storage and Recipes from ⋯ → Recent activity.
Your own AI assistant
RitualHeart contains no AI and sends nothing to an AI service. For receipts, what you have at home, recipes and meals, the app can copy instructions to your clipboard. You paste them into an AI assistant of your own choice, together with any photos or text you decide to give it, and paste its answer back into the app, which checks it and shows it to you before anything is saved. What the assistant's provider does with what you give it is governed by that provider's terms and privacy policy, not ours. The app reads your clipboard only when you tap its Paste button.
The copied instructions describe the format of the answer and hold only what their preview in the app shows: the names of your storage locations (for what you have at home), your storage list if you switch that on (for receipts), the names of the ingredients asked about (for recipe facts), and the foods you saved, with their calories, unless you switch that off (for meals).
Looking up a barcode (Open Food Facts)
When you scan a barcode in Meals, the app can look the product up at Open Food Facts, a free public food database. It asks you before the first lookup and sends the barcode over an encrypted connection, without cookies. The request also names the app, its version and our contact address, as Open Food Facts asks apps to do; it contains nothing about you. The app saves nothing before you have seen it. As with any website, Open Food Facts receives your device's IP address with the request, under its own privacy policy. You can switch lookups off in Settings → Meals.
On a receipt you import, an item in Storage or a food you saved, you can also ask for the product's photo. The app then looks the barcode up at Open Food Facts in the same way and downloads the product's photo from Open Food Facts' image server (images.openfoodfacts.org). It asks you before the first one and keeps the photo only if you choose to use it; it is then stored with your item or food like a photo of your own, marked as coming from Open Food Facts. Open Food Facts' photos are shared by its contributors under the Creative Commons Attribution-ShareAlike licence.
Photos and the camera
The app uses the camera only when you take a photo of an item or a recipe, or scan a barcode. Photos you add to items and recipes are stored with them, as described above. Every photo is re-encoded when you add it, so its location and camera details are removed. When you choose a photo from your library, the app sees only the photo you picked. A photo used only to read a barcode is read on your device and not kept, and a picture you pick as a theme's background stays on that device.
Advertising (Google AdMob)
The free version of RitualHeart shows a single banner ad supplied by Google AdMob. Ads are non-personalized by default: the app does not build a profile of you, does not track you across other apps or websites, and shows no App Tracking Transparency prompt. The app never sends your shopping, storage, recipe, diary, allergen or household information to the ad service.
To deliver ads, prevent fraud and report aggregate performance, Google may still collect a device identifier and technical information, such as your approximate region, your device type, whether an ad was shown or tapped, and diagnostic data about the ad component. This is governed by Google's Privacy Policy and how Google uses information from sites or apps that use its services. If you are in the EEA, the UK or Switzerland, the app shows Google's consent form before requesting ads, including the option not to consent. You can change or withdraw your choice at any time in Settings → Privacy choices.
What we do not do
- We do not require an account, an email, or a sign-up.
- We do not sell your personal data to anyone.
- We do not use analytics SDKs or third-party trackers other than the AdMob advertising described above.
- We do not use your data to track you across other companies' apps or websites.
- We do not send your data to an AI service.
Children
RitualHeart is not directed at children. Ad content is capped to a general (G) audience rating.
Legal basis and transfers
Where the law requires consent for ads, Google's consent form asks for it (Article 6(1)(a) GDPR). We answer your emails to do what you asked us to (Article 6(1)(b) GDPR). Google, Apple and Cloudflare are based in the United States, take part in the EU–US Data Privacy Framework and use the European Commission's standard contractual clauses. Open Food Facts is based in France.
Your choices and rights
Because your data lives on your device and in your own iCloud, you stay in control of it: you can edit or delete anything in the app, export your lists, storages, recipes and food diary as a readable JSON file from Settings → Export your data… (the file is not encrypted and holds your food diary, so keep it where only people you trust can open it), and remove everything by deleting the app and clearing its iCloud data from your device settings. You can review or change your advertising consent from the app's settings at any time.
Under the GDPR you can ask us for a copy of the data we hold about you, and ask us to correct it, delete it or limit how we use it, and you can object to how we use it. For anything we can help with, contact us below. If you think we've handled your data wrongly, you can complain to the Information Commissioner of the Republic of Slovenia (Informacijski pooblaščenec) or to the data protection authority where you live.
Changes to this policy
If the app changes what it collects, we will update this page and the "last updated" date above.
Contact
Questions about privacy? Email [email protected]. Some versions of the app send Report a problem to our older address, [email protected], which reaches us too.
If you write to us, we receive your email address and what you send: your message and the few technical details the app fills in for you (app version, iOS version, device model and an error code). Nothing from your lists, storages, recipes or diary is included. We use it only to answer you and to fix the problem.
Mail to [email protected] is forwarded by Cloudflare to our Gmail inbox, provided by Google. We answer from Gmail, so copies of conversations are kept there.