Privacy policy

1. Controller and contact

The controller responsible for processing your personal data under the General Data Protection Regulation (GDPR) is:

For privacy questions and to exercise your rights, write to us at contact@biancuisine.com. More details about the provider are in the imprint.

2. This website

The website biancuisine.com is hosted by Cloudflare (Cloudflare Pages). When you visit it, Cloudflare processes technically necessary data on our behalf: your IP address, date and time, the requested address, where applicable the page you came from, and information about your browser and operating system. This is needed to deliver the pages and to protect them against attacks and abuse.

The website sets no cookies, uses no analytics or tracking tools and loads no content from other servers, such as fonts or scripts. Links to other websites only open when you tap them; the privacy notices of the respective provider apply there.

Legal basis

Art. 6(1)(f) GDPR. Our legitimate interest is to provide the website securely and reliably.

Recipients

Cloudflare (section 15, section 16).

Retention

Cloudflare keeps this data only for a limited time for security purposes. We do not analyze it to identify visitors or to build profiles.

3. Account and sign-in

You need an account to use BianCuisine. For this we process:

• your email address and, if you sign in with email, your password; we store the password only as a hash from which it cannot be recovered,
• an internal account ID, the times of registration, confirmation and last sign-in, and the language in which you receive emails from us,
• your sign-ins: device type (e.g. iPhone or Android device), time of sign-in and of last activity, and technical details such as IP address and app identifier (user agent). Under More → Account → Signed-in devices you can see where you are signed in and sign devices out,
• log data created whenever our servers are accessed, such as IP address, time and type of request.

Emails about your account, that is, to confirm your email address and to reset your password, and invitations to a household (section 5) are sent from no-reply@auth.biancuisine.com via Cloudflare’s email sending service. The links in them lead back to the app via our app link pages (links.biancuisine.com and open.biancuisine.com, also hosted by Cloudflare). The emails contain our logo, which is loaded from our server when you open them; as with any request, your IP address is processed. We do not analyze whether or when you open an email. We do not send newsletters or advertising emails.

Signing in with Apple or Google: Instead of an email address and password, you can sign in with Apple (on iPhone and iPad) or with Google. We then receive from Apple or Google your email address, the information that it is verified, and an identifier of your account there. Google also sends the name and the profile picture link of your Google account; we do not use or show either. With Apple you can hide your email address; we then receive a forwarding address from Apple. We do not ask Apple for your name, and in this case we do not store a password. Apple and Google process the sign-in itself on their own responsibility under their privacy policies. If you confirm the deletion of your account in the app with Apple (always the case on iPhone and iPad when your account is connected to Apple), we also revoke the sign-in with Apple; otherwise, for example after a deletion by email, you can remove the connection yourself in your Apple Account settings.

So that you stay signed in, the app stores your sign-in session on your device (section 12).

Purpose

Providing your account, secure sign-in, restoring access, preventing abuse.

Legal basis

Art. 6(1)(b) GDPR (contract). For log data Art. 6(1)(f) GDPR; our legitimate interest is secure and stable operation.

Required data

Without an email address and password or a sign-in with Apple or Google, no account can be created and BianCuisine cannot be used.

Recipients

Supabase (hosting) and Cloudflare (email sending, app link pages); if you sign in with Apple or Google, also these on their own responsibility.

Retention

Until your account is deleted. Sign-ins: until 30 days after you sign out. Log data: only as long as we need it for security and troubleshooting.

4. Cookbook, recipes and photos

We store what you create in your cookbook: recipes with title, description, ingredients, steps, times, servings, difficulty, language, origin, categories, tags, dietary labels, allergens, source and nutrition values, up to five photos per recipe, collections, favorites, saved and archived recipes, and your personal ingredients, including barcodes and nutrition values.

This content is private. Others only see it if you publish a recipe (section 9) or share a recipe version in a household (section 5).

You choose photos in your device’s system photo picker. The app only receives the photos you select there and has no access to the rest of your photo library. Before uploading, it removes metadata such as location and capture time and reduces the image size.

If you suggest a missing cuisine, category, dietary label or allergen, we store the suggestion to review it and, where appropriate, add it for everyone.

Legal basis

Art. 6(1)(b) GDPR.

Retention

Until you delete the content or your account. Suggestions: until your account is deleted.

5. Weekly plan, shopping list and household

We store your weekly plans and shopping lists. You can use them on your own or share them with others in a household. If you move an item to another area in the shopping list by store area, we store that area for the item’s name so that the same item ends up there again next time; if you move whole areas, we store their order. Both apply only to your shopping list and, in a household, to all its members.

Visible in the household are the household’s name, the name you use there, your profile photo if you have one, your role, the shared plan with its portions, the shopping list and the recipe versions selected for the plan. The rest of your cookbook, your recipe photos and your journal stay private.

Invitations: Creating a shared household and inviting people need Plus; people who are invited join for free. You enter the email address of an existing BianCuisine account. We use it to find that account and store the invitation with the account, not with the email address. The invited person sees the invitation in the app under Notifications and in the household, with the household’s name and the name you use there, and receives an email about it from no-reply@auth.biancuisine.com (section 3). They accept or decline it in the app; if they accept, after a confirmation the household replaces their personal plan or their previous household. The owner of the household sees the email addresses of invited accounts in the list of invitations, and whether they accepted or declined. An invitation is valid for seven days.

Suggestions (Plus): BianCuisine calculates week-plan suggestions from your own and saved recipes and your daily goal. “What can I cook?” looks for recipes in your cookbook and in Discover that match the ingredients you type, add by barcode or have recognized on a photo. We calculate both kinds of suggestions without AI and without passing data to third parties; only a photo of your ingredients goes to OpenAI for recognition (section 8), and the app looks up a scanned barcode at Open Food Facts as in the journal (section 7). You see a week-plan suggestion before anything is saved.

If you delete a household you own, its plan and shopping list stay with you as your personal plan, and everyone else loses access. Anyone who leaves a household or is removed from it goes on with a new, empty personal plan. If you own a household and delete your account, the household with its plan and shopping list is deleted as well, unless you transfer ownership first. Recipe versions shared in a household remain available to its other members if you leave the household or delete your account; when your account is deleted, their link to your account is removed.

Legal basis

Art. 6(1)(b) GDPR. For looking up the invited person’s account and for the notification and email to them also Art. 6(1)(f) GDPR; our legitimate interest is matching invitations to the right account and letting the invited person know about them.

Retention

Until you delete plans or lists, leave the household or delete your account. Accepted invitations: until the household or the invited account is deleted; unaccepted ones, including declined ones: until they expire after seven days.

6. Nutrition journal and daily goals

In the journal we store your entries: foods, recipe portions or your own entries with amount, meal, date and nutrition values, as well as where the values come from, for example a database, a barcode or a photo estimate. In addition, we store the daily goals you set yourself. From this, the app calculates daily totals and the weekly review; if you have set a calorie goal, “Today” shows a short summary.

Only you can see your journal; members of your household cannot.

Nutrition data is personal. That is why BianCuisine does not ask for your weight, illnesses or diagnoses, does not calculate or recommend goals, and uses your journal and goals only for the features you see in the app, not for advertising, profiles or analyses. Please do not enter health information such as diagnoses in the names of entries.

Consent: The journal is optional. Because what you eat can allow conclusions about your health, the app asks for your explicit consent before you use it for the first time. We store that and when you consented and which version of the notice you saw, so that we can prove your consent. You can withdraw it at any time under More → Privacy & security. We then delete your journal with all entries and goals and switch automatic entries off. This does not affect the lawfulness of the processing before the withdrawal.

You can also hide the journal under More → Settings → Areas and delete individual entries at any time.

Automatic entries (Plus): If you switch them on in the settings, the app adds planned meals you take part in to your journal, even when someone else in your household plans them. For this we store your setting and your device’s time zone. The feature is off by default, requires your journal consent, and only you can switch it on. Other members see neither your goals nor your entries.

Legal basis

Your explicit consent, Art. 9(2)(a) GDPR in conjunction with Art. 6(1)(a) GDPR. For the proof of consent, Art. 6(1)(c) GDPR in conjunction with Art. 7(1) GDPR.

Retention

Until you delete entries or goals, withdraw your consent or delete your account. The proof of consent until you withdraw it or delete your account. Copies in technical confirmations: up to 30 days (section 17).

7. Food search and barcode scanner

When you search for foods or scan or enter a barcode, our server searches the German Food Code and Nutrient Database (Bundeslebensmittelschlüssel, BLS), which we host ourselves. If your country is the United States, our server queries FoodData Central, the database of the U.S. Department of Agriculture (USDA), instead of the BLS; USDA only receives the search text or barcode, neither your IP address nor any details about your account. The app also searches for products in the open food database Open Food Facts. When you search for products by typing, the app sends the search text with your country and language to our server, and our server queries Open Food Facts using our own Open Food Facts account. Open Food Facts then receives only the search text, country and language, neither your IP address nor any details about your account. For this request to Open Food Facts, our server neither stores nor logs the search text. Barcode lookups and requests for the details of a product you choose go directly from your device to Open Food Facts, and so do searches if our server does not respond or you use an app version up to 1.0.1. For these direct requests, Open Food Facts receives the search text or barcode, country, language and app version and, as with any request on the internet, your IP address, but no details about your account. Open Food Facts processes all of these requests under its own responsibility.

We cache answers from USDA together with the search text or barcode, but without any link to your account, for up to 24 hours (match found) or one hour (no match) so that later requests are faster; the app keeps answers from Open Food Facts only in your device’s memory until the app is closed. To prevent abuse, we count, for each account, the requests per minute that go through our server to USDA or Open Food Facts. For this, we store only the minute and the number of requests, no search text or barcodes, and delete these counters after one day. If you add a product, we store its details, such as name, nutrition values and barcode, in your cookbook, your ingredients or your journal.

Barcode scanner: The camera is only active while the scanner is open. The app recognizes the barcode directly on your device; camera images do not leave it. The app uses only the recognized barcode for the product search (see above). On iPhone and iPad, Apple’s image recognition (Vision) reads the barcode; no data goes to Apple or third parties. On Android, the app uses Google’s ML Kit for this, but only if you consent first; the app asks at the first scan. ML Kit sends technical usage and diagnostic data to Google: details about the device and the app (such as device model, Android and app version), an identifier of the app installation, performance and error data, and which features were used. Google processes this data under its own responsibility to measure, maintain and improve ML Kit and to detect abuse. Google does not receive camera images or recognized barcodes. Without consent the camera does not start; you can type in the barcode instead. Your consent applies to the device concerned, and you can withdraw it at any time under More → Privacy & security.

Legal basis

Art. 6(1)(b) GDPR. For the request counters Art. 6(1)(f) GDPR; our legitimate interest is preventing abuse. For ML Kit on Android, your consent (Art. 6(1)(a) GDPR, Section 25(1) of the German TDDDG); you can withdraw it at any time with effect for the future.

Recipients

Open Food Facts and USDA (without details about your account); on Android, with your consent, Google (ML Kit).

Retention

Added products: until you delete them or your account. Cached search results: from USDA up to 24 hours (match found) or one hour (no match), from Open Food Facts until the app is closed. Request counters: one day. Data at Open Food Facts: according to Open Food Facts’ rules. The app stores your ML Kit consent on your device until you withdraw it or delete the app. ML Kit diagnostic data: according to Google’s rules.

8. AI features

Four features use artificial intelligence (AI) from OpenAI. They only run when you start them. Our server then sends OpenAI only the data needed for the task, never your name or email address.

Consent: Before a photo, a recipe page or item names for sorting by store area are sent to OpenAI for the first time, the app asks for your consent. Without it, nothing is sent to OpenAI. If you agree, we store your consent in your account, with the time and the version of the notice, so that the app does not ask again, not even after you sign out or on another device, and so that we can prove your consent. You can withdraw your consent at any time in the app under More → Privacy & security with the “AI from OpenAI” switch; this does not affect the lawfulness of processing before the withdrawal. If an AI feature is added, the app asks you once more.

Photo estimate

In the journal, you can photograph a meal in the app or choose a photo in the system photo picker and have calories, protein, carbohydrates and fat estimated.

1. You see the photo before it is sent. The app removes metadata such as location and capture time and reduces the image size.
2. Our server sends the photo to OpenAI once and receives an estimate.
3. You review and change the values. Only what you confirm is saved, as an entry in your journal.

We do not store the photo, not in the journal, not in our database and not in our photo storage. When you take or select a photo, your device may create a temporary file; the app tries to delete it after processing.

Please photograph only food, no people and no personal information such as documents or screens.

Ingredients on a photo (Plus)

In “What can I cook?” you can place your ingredients side by side and photograph them in the app or choose a photo with the photo picker. The app removes metadata and reduces the image; our server sends it to OpenAI once and receives the names of the recognized ingredients. They appear in your search, where you can remove any of them; we store neither the photo nor the ingredients. Please photograph only food, no people and no personal information.

Recipe import

From a link: Our server loads the public web page. If it contains structured recipe data, as most recipe pages do, the server reads the recipe directly, without AI. Otherwise it sends the text and address of the page to OpenAI to recognize the recipe. The website only sees a request from our server, not your IP address.

From a photo of a printed recipe, such as a cookbook page: The photo is sent to OpenAI to recognize the recipe. We do not store it.

In both cases, a recipe draft is created in your cookbook, which you review, change or delete. For a link, we keep the link as the source; we do not copy photos from the website.

Shopping list by store area

To sort your shopping list by store area, such as fruit and vegetables or the chilled section, our server sends only the names of new items to OpenAI, including items that other members of your household have added. We store the result so that the same name does not have to be sent again.

At OpenAI

Our contracting party is OpenAI Ireland Ltd. (address in section 15). Processing may also take place in the USA. We send requests with the setting store: false, so OpenAI does not store the responses for later retrieval. However, OpenAI may keep requests and responses for up to 30 days to detect abuse, and longer only where this is required by law or necessary to protect OpenAI’s services or third parties from harm. According to OpenAI, data from the API is not used to train AI models by default. With the requests we send a pseudonymous identifier, a hash derived from your account ID, so that OpenAI can detect abuse. It does not tell OpenAI who you are.

AI results can be wrong. You review them before you use them. We do not use them to make decisions about you.

Usage limits: Without Plus, you can use up to three photo estimates within any seven days and up to three recipe imports within any 30 days. For photo estimates and ingredient photos, shared technical limits against abuse also apply to all accounts. For this we store when you used these features, without any image or content.

Legal basis

For sending data to OpenAI, your consent (Art. 6(1)(a) GDPR). For the photo estimate in the journal, it is also your explicit consent under Art. 9(2)(a) GDPR; the photo estimate also requires your journal consent (section 6). For storing imported recipes and confirmed values, Art. 6(1)(b) GDPR. For the usage limits, Art. 6(1)(f) GDPR; our legitimate interest is limiting abuse and costs. For the proof of consent, Art. 6(1)(c) GDPR in conjunction with Art. 7(1) GDPR.

Recipients

OpenAI (section 15, section 16).

Retention

Photos: not stored by us; at OpenAI up to 30 days, longer in the exceptional cases mentioned. Imported recipes and confirmed journal values: until you delete them or your account. Assignments of items to store areas: without any link to your account, for as long as we offer the feature. Usage counters: free uses, 30 days; the counter for the photo estimate limit, until the next use and at most until your account is deleted. Your consent: in your account until you withdraw it or delete your account; a copy on your device until you withdraw it or sign out.

9. Profile, publishing and community

Your creator profile consists of a display name and, if you like, a short bio and a profile photo. Others can find it once you publish a recipe.

Publishing

Publishing recipes is optional. For this we create a separate public version with the photos you select; your private original stays private. Published recipes and your creator profile are visible to all users of the app: in Discover, in search, in feeds and on your profile. Others can save them, mark them as favorites, add them to their plan and cook them. You can withdraw a publication at any time; recipe versions that others have already added to their plan remain there.

Likes, follows and recognition

The number of likes on published recipes is visible. The “Followers” and “Following” lists are visible on public creator profiles. Saved recipes and favorites are private.

In-app notifications tell you when someone follows you, likes one of your recipes, invites you to a household or joins your household, and when we remove one of your published recipes; people with a public creator profile appear by name, household members with the name they use there, and we delete notifications after 90 days.

From your published recipes, likes from others, how long you have been a member and rankings, the app determines recognition such as badges and frames. You decide which of them appear on your profile.

“For you”

This view in Discover sorts published recipes in your recipe languages by how new they are, whether you follow the creator or have already liked recipes by them, and how many likes they have received recently.

Blocking

If you block a creator, neither of you sees the other’s public recipes and profile any more, and existing follows are removed. For this we store your block list. You can find it under More → Privacy & security → Blocked creators.

Legal basis

Art. 6(1)(b) GDPR.

Retention

Until you change your details, withdraw a publication, delete content or delete your account.

10. Reports and moderation

You can report published recipes and creator profiles in the app. We then store the reported content, the reason, your optional description, your account and the time. Anyone can also send notices of illegal content by email to contact@biancuisine.com; in that case we process the name, email address and content of the notice.

Every report is reviewed by a person. If we take action, we inform the affected person and give reasons. We only name the person who reported if this is strictly necessary, for example when rights holders report a copyright infringement. We inform the person who reported of our decision.

If we become aware of information giving rise to a suspicion of a criminal offense involving a threat to the life or safety of persons, we inform the competent authorities (Art. 18 Digital Services Act).

Legal basis

Art. 6(1)(c) GDPR in conjunction with Art. 16 to 18 of Regulation (EU) 2022/2065 (Digital Services Act). Also Art. 6(1)(f) GDPR; our legitimate interest is a safe community and the defense of legal claims. For the report function in the app Art. 6(1)(b) GDPR.

Retention

Reports: up to twelve months after our decision, or longer while a measure based on the report is still in effect, but at most until the reporting or the reported account is deleted. Moderation decisions: twelve months, or, for a removal that is still in effect, as long as it applies, but at most until the affected account is deleted, so that we can document decisions and recognize repeated violations. Reports by email: as in section 14.

11. BianCuisine Plus and purchases

You buy Plus in the Apple App Store or on Google Play. Apple or Google handle the purchase and payment under their own responsibility; their privacy notices apply to this. We do not receive payment details such as card numbers.

To verify purchases, we use RevenueCat. The app and our server send RevenueCat a pseudonymous identifier, namely your internal account ID without your name or email address, and the stores’ purchase receipts. RevenueCat verifies them with Apple or Google and tells our server whether and until when you have Plus. In doing so, RevenueCat processes purchase data, such as product, store, purchase, renewal and expiry dates, status and transaction numbers, as well as technical connection data such as IP address, operating system, app version and store country.

In our database we store whether you have Plus, with store, product and expiry date, and when you used free photo estimates and recipe imports. Apple and Google also provide us with sales reports, for example with order number, date, product, price and country, which we keep for our accounting.

Legal basis

Art. 6(1)(b) GDPR. For accounting Art. 6(1)(c) GDPR in conjunction with retention obligations under tax and commercial law. For purchase data at RevenueCat after your account is deleted Art. 6(1)(f) GDPR; our legitimate interest is being able to trace purchases, renewals and refunds.

Recipients

Apple, Google and RevenueCat (section 15, section 16).

Retention

Plus status: until your subscription ends, at the latest until your account is deleted. Usage counters: 30 days. Purchase data at RevenueCat: as long as we need it for purchases, renewals, refunds and legal obligations, also beyond the deletion of your account; on request, we have it deleted earlier unless we are required to keep it. Sales reports: for the statutory retention periods of up to ten years.

12. Data on your device and widgets

On your device, the app stores:

• your sign-in session in the operating system’s protected storage (Keychain or Keystore) so that you stay signed in,
• some device settings, such as the start screen, appearance and automatically starting timers,
• a copy of your consent to the AI features, until you sign out (section 8),
• if you use widgets (Plus): a display copy for the widgets with today’s calories and goal, the next planned meal and the open items on your shopping list. The app updates it when something changes and deletes it when you sign out. Widgets do not fetch any data themselves and send nothing to us.

Keep in mind: widgets are visible to anyone who sees your screen.

The app does not store the rest of your content permanently on the device; it loads it over the internet when needed. Temporary files may briefly be created when you take or select photos.

This storage is strictly necessary for the features you use (Section 25(2) No. 2 of the German Telecommunications Digital Services Data Protection Act, TDDDG).

Permissions

The app only uses the camera when you open the barcode scanner or take a photo for the photo estimate or for “What can I cook?”. It only receives photos through the system photo picker. The app does not use the microphone, contacts, location or push notifications. It suggests your country based on your device’s region setting.

13. Settings

We store your settings in your account, for example app language, country, recipe languages, units, visible areas and the quick filters you save in Discover, including dietary labels and excluded allergens. We use your country to show products from your country first in the food search; your recipe languages determine which recipes you see in Discover.

Legal basis

Art. 6(1)(b) GDPR. For quick filters with excluded allergens, your explicit consent, which you give when you save the filter (Art. 9(2)(a) in conjunction with Art. 6(1)(a) GDPR), because they may allow conclusions about allergies. You withdraw it by deleting the filter; this does not affect the lawfulness of processing up to then.

Retention

Until you change them or delete your account. Quick filters: until you delete them or your account.

14. Contact by email and contact form

When you write to us, we process your email address, your name if given, the content of your message and any attachments in order to handle your request. Cloudflare (Cloudflare Email Routing) forwards emails sent to contact@biancuisine.com to our mailbox at Google Workspace, where we store and handle them.

Messages from our contact form contain your email address, the topic, your message, the language of the page and, if you enter it, your name. Cloudflare receives them and sends them to us as an email to contact@biancuisine.com (Cloudflare Email Service); from then on, the same applies as for emails. We do not store the messages anywhere else. To prevent misuse, Cloudflare counts for one minute at a time how many messages come from your IP address (Art. 6(1)(f) GDPR; our legitimate interest is protecting the form from misuse).

Legal basis

Art. 6(1)(b) GDPR if it concerns your account or BianCuisine. Art. 6(1)(c) GDPR for notices under the Digital Services Act and for requests about your data protection rights. Otherwise Art. 6(1)(f) GDPR; our legitimate interest is answering requests.

Recipients

Cloudflare (contact form and forwarding) and Google (mailbox at Google Workspace), see section 15 and section 16.

Retention

We delete messages when we no longer need them, at the latest two years after the last contact. Longer only if we are required by law to keep them or need them to establish or defend legal claims.

15. Recipients and service providers

We only share personal data where this is necessary for the purposes described. Service providers that process data on our behalf are contractually bound by our instructions (Art. 28 GDPR).

Supabase

Supabase Pte. Ltd., 65 Chulia Street #38-02/03, OCBC Centre, Singapore 049513. Database, sign-in, file storage and server functions of the app. Data location: Frankfurt am Main, Germany. Processor; the data processing agreement is part of Supabase’s terms.

Cloudflare

Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA. Hosting of this website and the app link pages, sending the emails about your account, the household invitations and the messages from the contact form, forwarding emails sent to contact@biancuisine.com, and separate storage for the deletion journal and for backup copies of photos (Cloudflare R2, located in the EU). Processor.

OpenAI

OpenAI Ireland Ltd., 1st Floor, The Liffey Trust Centre, 117-126 Sheriff Street Upper, Dublin 1, D01 YC43, Ireland. AI features, only when you use them. Processor; processing may also take place in the USA.

RevenueCat

RevenueCat, Inc., 1032 E Brandon Blvd #3003, Brandon, FL 33511, USA. Verifying purchases of BianCuisine Plus. Processor.

Google Workspace

Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. Mailbox in which we store and handle emails sent to contact@biancuisine.com. Processor; Google’s data processing terms apply (Cloud Data Processing Addendum).

Apple and Google

Distribution of the app, purchase and payment of Plus, and the sign-in with Apple or Google if you choose it, each under their own responsibility. Depending on your device settings, they also provide us with aggregated statistics and crash reports without names, which we use to fix errors (Art. 6(1)(f) GDPR; our legitimate interest is an app that works without errors).

Google ML Kit (Android only, only with consent)

Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA. Usage and diagnostic data of barcode recognition, under Google’s own responsibility (section 7).

Open Food Facts and USDA FoodData Central

Open Food Facts, 21 rue des Iles, 94100 Saint-Maur-des-Fossés, France, receives, under its own responsibility, search texts with country and language from our server, without your IP address, and barcodes and product requests directly from your device, with country, language, app version and your IP address. Search texts also come directly from your device if our server does not respond or you use an app version up to 1.0.1. The U.S. Department of Agriculture (USDA) only receives search texts or barcodes from our server. Neither receives any details about your account (section 7).

Other users see what you publish or share in a household (section 5, section 9). Authorities only receive data where we are legally obliged to provide it (Art. 6(1)(c) GDPR).

16. Transfers to third countries

We store your content in the EU. Some service providers are based outside the EU or may process data there. This only happens if the requirements of Art. 44 et seq. GDPR are met:

• Cloudflare (USA): Cloudflare is certified under the EU-U.S. Data Privacy Framework. The European Commission’s adequacy decision of July 10, 2023 applies to it (Art. 45 GDPR). The data processing agreement with Cloudflare additionally contains the EU standard contractual clauses (Art. 46(2)(c) GDPR).
• RevenueCat (USA): For transfers to RevenueCat, the EU standard contractual clauses in the data processing agreement apply (Art. 46(2)(c) GDPR).
• Google Workspace: Our contracting party is Google Ireland Limited. Where Google transfers data to Google LLC in the USA, the EU-U.S. Data Privacy Framework (Art. 45 GDPR) and, in addition, the EU standard contractual clauses in Google’s Cloud Data Processing Addendum (Art. 46(2)(c) GDPR) apply.
• Google ML Kit (USA): Google LLC is certified under the EU-U.S. Data Privacy Framework. The European Commission’s adequacy decision of July 10, 2023 applies to it (Art. 45 GDPR).
• OpenAI: For processing in the USA, the EU standard contractual clauses in OpenAI’s data processing agreement apply.
• Supabase: Supabase is based in Singapore. For access from outside the EU, for example for operations and support, and for server functions executed outside the EU, the EU standard contractual clauses apply.

If other service providers process data outside the EU, this likewise only happens on the basis of an adequacy decision or the EU standard contractual clauses. You can request a copy of the standard contractual clauses from us.

17. Retention, backups and deletion journal

In general, we keep your data as long as your account exists. You can delete individual content yourself at any time. Specific periods are listed in the relevant sections.

Backups: Deleted data may remain in database backups at our hosting provider Supabase for up to seven days; after that, it is overwritten there. We also back up photos in separate storage at Cloudflare R2 in the EU; deleted photos may likewise remain there for up to seven days.

Technical confirmations: When you save or delete something, we keep a confirmation that may contain a copy of the entry, so that a repeated request does not save anything twice. We delete it after 30 days, or immediately when you withdraw your journal consent or delete your account.

Deletion journal: So that an account deletion stays effective even after a restore from a backup, we keep a minimal, encrypted deletion record for each deletion. It essentially contains the internal account ID and the time, but no email address, recipes, photos or other content. It is stored separately from the database at Cloudflare R2 in the EU and deleted after 35 days. We also log completed deletions without content for 35 days.

Legal basis

Art. 6(1)(f) GDPR; our legitimate interest is reliable restoration. For the deletion journal Art. 6(1)(c) GDPR in conjunction with Art. 17 GDPR, so that deletions stay effective. For technical confirmations, Art. 6(1)(b) GDPR and, where they contain journal data, your consent under Art. 9(2)(a) GDPR.

18. Deleting your account

This is how you delete your account for the BianCuisine app (on Google Play by the developer “Noshi Systems”) together with all related data:

In the app: More → Account → Delete account. You confirm the deletion with your password or with your Apple or Google sign-in. After that, it continues automatically on our servers, even if you close the app. It is usually completed within 24 hours.

Without the app: Write to us at contact@biancuisine.com from your account’s email address. To make sure nobody else deletes your account, we may ask you to confirm the request. If you signed in with Apple and hid your email address, tell us the forwarding address (…@privaterelay.appleid.com) shown in your Apple Account settings under “Sign in with Apple”; we will send the confirmation to that address.

What is deleted: your account with email address, password and the connection to Apple or Google, your profile, recipes, photos, collections, favorites, saved recipes and personal ingredients, your plans, shopping lists, journal entries, goals, settings and sign-ins, your likes, follows, blocks and reports, your household membership and your Plus status. Published recipes are withdrawn and their public photos deleted. If you own a household, it is deleted together with its plan and shopping list unless you transfer ownership first.

What remains:

• recipe versions in other households’ plans, without a link to your account,
• the deletion record and the log of the deletion for 35 days,
• data in backups of the database and of photos for up to seven days (section 17),
• data at OpenAI within its retention of up to 30 days,
• purchase data at RevenueCat (section 11) and data we are legally required to keep,
• emails you have sent us (section 14).

Subscription: Deleting your account does not end a Plus subscription. Cancel it first in the App Store or on Google Play.

19. Your rights

You have the right to

• access your data (Art. 15 GDPR),
• rectification of inaccurate data (Art. 16 GDPR),
• erasure (Art. 17 GDPR),
• restriction of processing (Art. 18 GDPR),
• data portability (Art. 20 GDPR) and
• withdraw consent with effect for the future (Art. 7(3) GDPR), where we process data on the basis of consent.

You can view, change and delete much of your data directly in the app. For everything else, an email to contact@biancuisine.com is enough. We reply within one month and may ask you to confirm your identity.

Right to lodge a complaint: You can lodge a complaint with any data protection supervisory authority (Art. 77 GDPR), in particular in the EU member state of your habitual residence, your place of work or the place of the alleged infringement. The authority responsible for us is:

20. If you live outside the EU

This privacy policy applies wherever you use BianCuisine, with all the rights in section 19. The controller is always Amed Bozo, Moritzstraße 43, 65185 Wiesbaden, Germany, contact@biancuisine.com. He is also the person responsible for privacy under the law of your country, for example the “accountable person” in Canada, the “responsable de la protection des renseignements personnels” in Quebec or the “privacy officer” in New Zealand. From your device, your data goes directly to us in Germany, product searches also go to Open Food Facts in France, and when you open the Plus page or buy Plus, purchase data goes to RevenueCat in the USA. We store your content in Frankfurt am Main; our service providers are also based in Ireland, the USA and Singapore (sections 15 and 16). Users in all countries can see published recipes and your creator profile.

For requests from any country, an email to contact@biancuisine.com is enough, ideally from your account’s email address; you can also view, change and delete much of your data directly in the app. Requests are free. We answer as quickly as possible, at the latest within the period that applies in your country. If we decline something, we tell you why and how you can complain.

United Kingdom

The UK GDPR and the Data Protection Act 2018 apply, with the same rights as in section 19. You can complain to us first, by email or through the contact form; we acknowledge receipt within 30 days. You can also contact the supervisory authority at any time: Information Commission (ICO), 4th Floor, No. 3 Circle Square, 5 Hawkshaw Street, Manchester M1 7BL, ico.org.uk, phone 0303 123 1113. Data goes to the EU, in particular to Germany and Ireland, on the basis of the UK adequacy regulations; to the USA, to Cloudflare and Google on the basis of the UK Extension to the EU-U.S. Data Privacy Framework and to RevenueCat and OpenAI on the basis of the EU standard contractual clauses with the UK Addendum; and to Singapore, to Supabase, on the same basis.

Switzerland

The Federal Act on Data Protection (FADP) applies. In particular, you have the right to access, rectification, erasure, disclosure and transfer of your data, and you can object to the processing; we do not make automated individual decisions. Your data goes to these countries:

• the EU, in particular Germany (us and Supabase’s servers in Frankfurt am Main), Ireland (OpenAI, Google) and France (Open Food Facts, product searches only): adequate protection under Annex 1 of the Data Protection Ordinance,
• the USA: Cloudflare and Google, which are certified under the Swiss-U.S. Data Privacy Framework; RevenueCat, on the basis of the EU standard contractual clauses with the adaptations for Switzerland; and, where OpenAI processes data there, on the basis of standard contractual clauses between OpenAI Ireland and OpenAI in the USA,
• Singapore: Supabase, for operations and support, on the basis of the EU standard contractual clauses with the adaptations for Switzerland.

Supervisory authority: Federal Data Protection and Information Commissioner (FDPIC), Feldeggweg 1, 3003 Bern, edoeb.admin.ch.

Türkiye

The Personal Data Protection Law No. 6698 (KVKK) also applies. Together with the rest of this privacy policy, this section is our information under Art. 10 KVKK (Aydınlatma Metni); we ask for your consents separately in the app. We process your data

• to perform the contract (Art. 5(2)(c) KVKK) for your account, cookbook, planning and Plus,
• on the basis of our legitimate interest (Art. 5(2)(f) KVKK) for security and moderation,
• as data you have made public (Art. 5(2)(d) KVKK) for published recipes and your creator profile,
• with your explicit consent (Art. 5(1) and Art. 6(3)(a) KVKK) for the journal, the photo estimate, the other AI features and quick filters with excluded allergens.

Under Art. 11 KVKK, you can find out whether and why we process your data and to whom in Türkiye and abroad we disclose it; you can request rectification and erasure, also towards recipients, object to automated analyses to your disadvantage and claim compensation. You can make your application in Turkish by email from your account’s address; we answer free of charge and in writing within 30 days. You can then complain to the Personal Data Protection Board (Kişisel Verileri Koruma Kurulu) within 30 days, at the latest 60 days after your application (sikayet.kvkk.gov.tr). To operate BianCuisine, we disclose your data to the service providers in section 15 in Germany, Ireland, the USA and Singapore, on the basis of contracts with the EU standard contractual clauses.

USA

We do not sell personal data, we do not use or share it for targeted advertising and we do not use it to train large language models. We do not track you across other websites and apps, so a Do Not Track signal changes nothing. For health data from the journal, the photo estimate and quick filters, our Consumer Health Data Privacy Policy also applies. You can request access, a copy, correction and deletion and withdraw consents; we answer within 45 days. If we decline, you can appeal: reply to our email with the subject “Appeal”. We decide within 45 days and, if we deny the appeal, tell you how to contact the Attorney General of your state.

Canada

The Personal Information Protection and Electronic Documents Act (PIPEDA) applies, and in Quebec also the Act respecting the protection of personal information in the private sector. Your data is processed outside Canada, in Germany, Ireland, France, the USA and Singapore, and may be accessible there to courts and authorities under local law. We use the journal and the photo estimate only with your express consent and not for profiling. You can request access, correction and a copy in a commonly used format and withdraw consents; we answer within 30 days. At BianCuisine, only the owner has access to your data, and he also handles complaints; retention and deletion periods are in section 17 and the individual sections. Please address complaints to us first, then to the Office of the Privacy Commissioner of Canada (priv.gc.ca) or, in Quebec, to the Commission d’accès à l’information (cai.gouv.qc.ca).

Australia

We comply with the Australian Privacy Principles. You can request access to your data and its correction; we answer within 30 days. In the community, you can use a display name of your choice instead of your name. Overseas recipients are located in Germany, Ireland, France, the USA and Singapore. Please address complaints to us first; if we do not answer within 30 days or you are not satisfied with our answer, you can contact the Office of the Australian Information Commissioner (oaic.gov.au, 1300 363 992).

New Zealand

The Privacy Act 2020 applies. We receive some data not from you but from Apple or Google when you sign in (section 3), from the app stores and RevenueCat about your purchase status (section 11) and from other users, for example reports, likes and follows (sections 9 and 10). We answer requests for access and correction within 20 working days. Please address complaints to us first, then to the Privacy Commissioner (privacy.org.nz).

Latin America

Your data goes to Germany and to service providers in Ireland, the USA and Singapore. The information in the journal is sensitive data: you do not have to provide it, and you can use everything else without it.

• Mexico: You have the rights of access, rectification, cancellation and opposition (ARCO) and can withdraw your consent. We decide within 20 business days and carry out the decision within 15 business days. Complaints: Secretaría Anticorrupción y Buen Gobierno.
• Argentina: “El titular de los datos personales tiene la facultad de ejercer el derecho de acceso a los mismos en forma gratuita a intervalos no inferiores a seis meses, salvo que se acredite un interés legítimo al efecto conforme lo establecido en el artículo 14, inciso 3 de la Ley Nº 25.326. La AGENCIA DE ACCESO A LA INFORMACIÓN PÚBLICA, Órgano de Control de la Ley Nº 25.326, tiene la atribución de atender las denuncias y reclamos que se interpongan con relación al incumplimiento de las normas sobre protección de datos personales.” You receive access within 10 days, rectification and deletion within 5 business days.
• Chile: You have the rights of access, rectification, erasure, objection, portability and blocking; we answer within 30 days. From December 1, 2026, you can complain to the Agencia de Protección de Datos Personales.
• Colombia: The controller and the person handling requests is Amed Bozo (contact above). We answer queries (consultas) within 10 and complaints (reclamos) within 15 business days. After your request to us, you can contact the Superintendencia de Industria y Comercio. This privacy policy applies from October 3, 2026; the database exists for as long as we offer BianCuisine.
• Peru: Your data is held in the database “Usuarios y contenidos de BianCuisine”. We answer requests for information within 8, for access within 20 and concerning other rights within 10 business days. After your request to us, you can contact the Autoridad Nacional de Protección de Datos Personales.
• Other countries: In Uruguay (URCDP), Costa Rica (PRODHAB), Panama (ANTAI), Ecuador (SPDP), El Salvador (ACE), the Dominican Republic and Paraguay, you have the rights under the law of your country. We answer requests within the period that applies there, in Uruguay within 5 business days.

21. Further information

Minimum age

You must be at least 16 years old to use BianCuisine; you confirm this once in the app. If the law of your country sets a higher minimum age, that age applies. If we learn that someone under 16 has an account, we delete the account with all its data; parents and other legal guardians can write to us about this.

Required data

For an account we need your email address and a password or a sign-in with Apple or Google; without them you cannot use BianCuisine. All other information is optional. Without it, some features are not available.

No automated decisions

We do not make automated decisions within the meaning of Art. 22 GDPR. AI results are suggestions that you review and change.

No advertising, no tracking

We show no advertising, use no analytics or tracking tools, do not track you across other apps or websites and do not sell data.

Security

Connections between the app, the website and our servers are encrypted. We store passwords only as hashes. On the server, private content is assigned to your account and protected by access rules against retrieval by others. Backups are encrypted. We continuously adapt our technical and organizational measures; however, no system can offer complete security.

Changes

We update this privacy policy when the app, our service providers or the law change. We inform you of significant changes in the app or by email. The version published here applies.