Legal
Privacy Policy
Effective date: 8 September 2026 · last updated: 8 September 2026 · applies to Cuvio version 1.2.1
In short
Cuvio does not collect personal data and uses no analytics or advertising tools. Recipes and related data are stored on your device; with Cuvio Pro, also in the private iCloud database of your Apple Account. The one exception is Cuvio AI – a paid option you have to ask for: text from the recipe then goes to a language model, and your credit balance is kept for billing. Nothing from your recipes is stored; see “Cuvio AI – reading and fixing text with a model”.
What the app stores
Only what you put in yourself: recipe titles, ingredients, instructions, notes, categories, tags, food photos, and app settings (language, appearance, sorting, default number of servings).
Where your data is stored
This policy distinguishes six different situations:
- Storage on the device. Without Cuvio Pro, or without being signed in to iCloud, all data stays in your device’s storage. It leaves the device only in a file you export or share yourself.
- iCloud syncing (Cuvio Pro). With Cuvio Pro, recipes sync across devices signed in to the same Apple Account, and synced copies are stored in the private iCloud database of your Apple Account, which Apple reserves for this app and your account. See “iCloud syncing” below.
- Visiting a third-party website during import. When you paste a link to a recipe, the app requests that one page from the internet. See “Importing a recipe from the web” below.
-
A photo linked from a file you open. A single-recipe file somebody sends
you (
.cuvio) need not contain the photo – it may only link to it. When you open such a file, the app downloads that one image. The operator of that server sees your IP address, just as with a web import, and the address was chosen by whoever created the file, not by you. It happens only when the file carries no photo of its own, only for an address starting withhttps://, and only for a file with a single recipe. It happens right after the file is opened – before you save the recipe, and even if you end up not saving it. The address is stored nowhere, and nothing is sent anywhere except the request for that image. - System search on your device. So that recipes can be found in Spotlight, the app hands them to the iOS search index: title, category, tags, ingredients and a small thumbnail of the photo. That copy stays on your device, the system manages it, and the app’s developer has no access to it. It shows up in search only for you, and deleting a recipe removes its entry too. You can turn it off in Settings → Search → Cuvio → Show Content in Search.
- Cuvio AI. When you ask for it yourself, text goes to our server and on to a language-model provider – the text your device read from a scanned recipe, the text of a web page, or your own recipe when you have its wording fixed. Never the photo, never the address of the page, and never your notes. Nothing from it is stored; only your credit balance is kept, for billing. See “Cuvio AI – reading and fixing text with a model” below.
What the app does not do
- No personal data collection, no analytics.
- No ads and no third-party measurement SDKs.
- No user account, no sign-up. It uses the Apple Account your device already has.
- Your recipes are never stored on a developer’s server. The only places that keep them are your device and your own iCloud. We do run a server for Cuvio AI, and the only thing kept on it is your credit balance; text you send it, when you ask for it, passes through and is discarded – see “Cuvio AI – reading and fixing text with a model”.
- No tracking across apps or websites, in Apple’s sense of the word.
Photos and camera
You can attach a photo to a recipe in two ways:
- From your photo library, through the system photo picker. The app only ever sees the single image you hand it; it has no access to your library and never asks for it.
- From the camera, after the system asks you once for permission. The photo is used as the recipe’s picture and stored in the app’s own data. It is not uploaded anywhere and not saved to your photo library.
Scanning a recipe from paper
You can scan a cookbook page or a handwritten recipe and have the name, ingredients and instructions transcribed from it. The same works with a photo you already have on your phone – a screenshot of a recipe from the web, a photo of a cookbook page – when you share it into Cuvio from Photos.
- Even with a shared photo, the app does not see your library. Sharing hands over that one image, just like the system photo picker above; Cuvio never asks for access to your library.
- The text is read on your device, by a component built into the operating system. Neither the image nor the recognized text then leaves your phone, and it works in airplane mode. This describes the free path, which is always tried first. Only when you ask for the paid Cuvio AI does the recognized text go to our server – never the photo; see “Cuvio AI – reading and fixing text with a model”.
- The scanned pages are kept only for the review step in the form, so you can compare what was read against the original. They are not stored with the recipe and disappear when you close the form.
- Only what you confirm in the form is saved – the recipe text, exactly as if you had typed it yourself.
Cuvio AI – reading and fixing text with a model
Cuvio can ask a language model for help in three cases: with a recipe scanned from paper, with a web page no recipe could be recognized on, and with a recipe you already have whose wording you want tidied up. In all three it is an extra, paid option, and in all three you are the one who asks for it.
- It only happens when you ask for it – for a scanned recipe and for web import you either turn it on in Settings (Read scanned recipes with AI, Use AI when importing from the web) or tap “Read with AI” on a particular page; for a recipe you already have, you choose “Fix the text with AI” in its form. Each of these costs one credit.
- For a photo and for the web, the free path is always tried first, and it runs entirely on your device; only when you ask for the paid one does anything leave your device. Fixing the wording has no free counterpart – only the model can do it, so there the text is always sent.
- The photo is never sent. From a scanned recipe, only the text your device read from the page leaves it.
- From a web page, only its text and window title leave – never its address. Your device downloads and reads the page itself; our server never visits the web, so what you opened never shows up with us.
- From a recipe being fixed, only the title, ingredients, and instructions leave – exactly the text to be fixed. Your notes are not sent, and neither is the photo, the number of servings, the times, categories, tags, or the source link.
- The text is processed by a language-model provider – today OpenAI (USA) – and only for that single answer. Under that service’s terms it is not used to train models.
- Nothing from the recipe is stored on our server – neither the text you send it nor the model’s answer. Both pass through memory and are discarded; they do not reach operational logs either.
- For billing we store only your credit balance, the list of purchases already counted, and two identifiers that say whose balance it is: one issued by Apple for your download of the app, the other a random value the app itself creates. Neither says anything about you – no name, no e-mail, no recipe content.
- Without credits, without a connection, or when something fails, a scanned recipe is read the free way and nothing is sent; for a web page you are left with the message that no recipe could be recognized; a recipe being fixed stays as it was. No credit is charged in any of those cases.
Importing a recipe from the web
When you paste a link to a recipe, the app requests that page from the internet – just as a browser would – and reads the name, ingredients and instructions from it.
- The app only ever fetches the address you give it. It does not crawl, does not look anywhere else, and never does this in the background. The one other address the app ever reaches for is a photo linked from a file you open yourself – see “Where your data is stored” above.
- The site’s operator sees what they would see on any ordinary browser visit: your IP address and the address of the page. Nothing about you or your recipes is sent to them.
-
The address is adjusted before the request: campaign tags (
utm_*,fbclid) and anything after#are removed. - During import, Cuvio stores no cookies and no browsing history.
- When no recipe can be recognized on the page, you can ask for it to be read by Cuvio AI. Only then do the page’s text and window title – never its address – go to our server and on to the model provider. Without that request nothing goes anywhere, see “Cuvio AI – reading and fixing text with a model”.
- The imported recipe is then yours like any other. The link to the source is stored with it, so it stays visible where the recipe came from.
iCloud syncing
Syncing is part of Cuvio Pro. When you use it, recipes are stored in the private iCloud database of your Apple Account (technically the app’s private CloudKit database). That is what puts them on every device signed in to the same Apple Account, and what keeps them when you replace your phone. Without it, the data does not leave the device – apart from a file you export yourself.
What that means for security and privacy:
- Apple is responsible for running and securing iCloud. The transfer and storage of data in the private database are handled by Apple as part of the iCloud service.
- Access is protected by the security of your Apple Account – the same as the rest of your iCloud data.
- The developer cannot access data stored in a user’s private iCloud database.
- The data is not used for advertising or profiling.
- Synced data counts towards your iCloud storage. The app optimizes photos before saving them.
- The app keeps working without internet. Changes are saved on the device and sync once the device is back online.
- Turn iCloud off, sign out, or skip Cuvio Pro and your recipes stay on the device; syncing does not start.
Processing of data inside iCloud is also covered by Apple’s privacy policy, because iCloud is run by Apple, not by us.
Export, sharing and support mail – when data does leave the device
Three features move data out of the app. You start all of them and you decide where the data goes:
-
Export to a
.cuviofile containing all your recipes and photos. You decide where the exported file is stored and with whom it is shared. - Sharing a recipe as text or as a file, through the system share sheet, to a destination you pick.
-
Writing to support (Settings → About → Support) – opens a draft e-mail to the
developer’s address in your mail app. The draft is prefilled with the app’s version and
build number, the device model identifier (for example
iPhone17,1) and the iOS version; those are the only details you do not type yourself. Nothing is sent on its own – you see the whole message, you can rewrite or discard it, and sending is always yours. No recipes, photos or anything else from the app is attached.
If you store the file in iCloud Drive or send it by e-mail, that service’s own terms apply from then on (typically Apple’s or your mail provider’s), not this policy.
This website
The pages at cuvio.josefburger.cz use no cookies and contain no
analytics or advertising tools. No data is collected on them and there is no form that submits
anything anywhere.
The styling of the pages is loaded from the content delivery network
cdn.tailwindcss.com. Its operator receives what it would receive for any other
file downloaded from the internet: your IP address and your browser details. No further data
is sent to it.
The recipe builder
The builder is a page for writing recipes on a computer and
downloading them as a .cuvio file for the app. A file you open there is
never uploaded – your browser reads it and writes it back. Nothing you type into the
builder or load into it is sent to a server of this website or anywhere else; this website
has no such server. (The server described under “Cuvio AI – reading and fixing text with a model”
serves the app only; the builder never uses it.)
Work in progress is saved to your browser’s storage as you go, so that closing the tab does not cost you an evening. It stays on that computer and is removed when you choose “Start over” in the builder, or when you clear this site’s data in your browser.
Deleting your data
You can delete your data in the app itself: Settings → Delete data. You pick what it covers – recipes, categories and tags separately – and before anything is deleted you see a summary of how much that is. Deleting categories and tags does not delete recipes. If you sync, the deletion applies to your other devices too. Deleted recipes also disappear from system search.
Deleting the app removes the data from that device. If you sync, the iCloud copy stays, so that reinstalling – or using the app on another device – doesn’t cost you your recipes. You can delete it in Settings → your Apple Account → iCloud → Manage Account Storage → Cuvio. The developer holds no further copy of your data. We recommend exporting first, because deletion cannot be undone.
Children
The app collects no data, and therefore no data about children. It is not directed at children and contains nothing unsuitable for them.
Changes to this policy
If a feature is added that handles data differently, this text will be updated before that version ships, along with the effective date and the last-updated date.
Data controller and contact
Josef Burger, company ID (IČO) 01399021
E-mail: products@josefburger.cz
No database of users’ personal data is created on the developer’s side. You are still welcome to write to the address above with any question about this policy.