Omnitable

Privacy Policy for Omnitable

Last updated: 16 November 2026

Omnitable is a cookbook for iPhone and iPad. It needs no account, shows no ads and does not analyse how you use it. Most of what you enter never reaches us: it stays on your device or in your own iCloud. This policy explains where your data lives and the few cases in which something reaches us.

1. Controller

Mario Mangold
Im Johannistal 25
42119 Wuppertal
Germany
Email: omnitable@mngld.me

We are not required to appoint a data protection officer. For privacy questions, write to the address above.

2. Data that stays on your device

This data never leaves your device. We have no access to it. Deleting the app removes it.

3. Data in your iCloud

Everything that belongs to your household is stored in your private iCloud database (Apple CloudKit) so it syncs between your devices:

Allergies and intolerances can be health data. They are stored only in your iCloud, not with us. We have no access to them and do not process them. Storage in iCloud is governed by Apple's terms and privacy policy (https://www.apple.com/legal/privacy/).

Shared household. If you share your household with others (iCloud sharing), all members see all of the household's data, including every member's profile with allergies. The app points this out when someone joins. The data is then stored in the iCloud of the person who shares the household. Anyone who leaves a shared household keeps none of it on their device.

4. What the app downloads

Omnitable downloads new and updated recipes as signed files from a fixed address. The files are stored with Supabase (Supabase Inc., data centre in Frankfurt am Main, Germany). The app sends nothing about you: no profiles, no identifier and no usage data.

As with any request on the internet, the provider technically receives your IP address, the time and the file requested in order to deliver the file. We do not store these requests, analyse them or combine them with anything.

The legal basis is our legitimate interest in delivering the recipes up to date and securely (Art. 6(1)(f) GDPR).

5. Submitting a recipe

You can suggest a recipe of your own for the catalog. This only happens when you start it yourself and confirm before sending.

What is sent: title, servings, ingredients, steps with timers, the language, the app version and, if you like, a display name for the credit. Never sent: profiles, allergies, household data, photos or your history.

Abuse protection: So that only genuine installations of the app can send, Omnitable uses Apple App Attest. Your device creates a key that Apple confirms. We store the public part of this key to allow at most five submissions per day and device. The key is created per installation, does not tell us who you are and is not linked to anything else.

Where and why: Submissions are stored in a database with Supabase (data centre in Frankfurt am Main). We review them by hand and use accepted recipes as the basis for a dish in the catalog. Submissions are not passed to an AI service. A recipe only appears in the catalog after editorial review.

Legal basis: your consent by sending (Art. 6(1)(a) GDPR); for abuse protection, our legitimate interest (Art. 6(1)(f) GDPR).

Retention: Rejected submissions are deleted six months after the decision. Accepted ones are kept as long as the recipe based on them is in the catalog. The device key is deleted a year after it was last used.

6. Reporting a problem with a recipe

You can report a problem with a catalog recipe. This too only happens when you start it yourself.

What is sent: the recipe concerned, the step, the kind of problem and your text. Never sent: a name, profiles or allergies. Abuse protection works as for submissions (App Attest, a limit per day and device).

Where and why: in the database with Supabase (Frankfurt am Main), only to correct the catalog. Reports are not passed to an AI service.

Legal basis: your consent by reporting (Art. 6(1)(a) GDPR); for abuse protection, our legitimate interest (Art. 6(1)(f) GDPR).

Retention: Resolved and dismissed reports are deleted six months after the decision.

7. What you share yourself

8. Purchases and subscription

Purchases of recipe packs and the Omnitable Plus subscription are handled by Apple through the App Store. We receive no payment details and no name. The app checks purchases on the device. Apple's privacy policy applies.

9. Camera

Omnitable only uses the camera when you scan a barcode or a best-before date or take a photo for a recipe. Images are processed on the device and not sent.

10. What there isn't

No account, no ads, no analytics or tracking tools, no third-party software in the app, no sharing or selling of data.

11. Recipients and transfers to third countries

12. Your rights

You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and to object to processing based on legitimate interest (Art. 21). You can withdraw consent at any time with effect for the future.

Because we keep neither accounts nor identifiers, we can only match a submission or report to you if you describe it (for example its title and the rough date). Write to omnitable@mngld.me.

You can lodge a complaint with a data protection supervisory authority, for example the one where you live or the one responsible for us: Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen, Kavalleriestraße 2–4, 40213 Düsseldorf, Germany, https://www.ldi.nrw.de.

13. Deleting data

14. This website

This website is hosted on Cloudflare Pages (Cloudflare, Inc., USA). When you open it, Cloudflare technically processes your IP address, the time, the page requested and details of your browser in order to deliver the page and protect it from attacks. We do not see or store these requests ourselves.

The website sets no cookies, uses no analytics and loads no content from other providers. The legal basis is our legitimate interest in delivering the site securely and reliably (Art. 6(1)(f) GDPR).

15. Changes

If the app changes so that other data is processed, we will update this policy. The version on this page applies.