Last updated: 12 August 2026
The controller responsible for the processing of personal data in connection with Keep2Cook is:
Dr. Philip Weber, IT-Beratung Ählstraße 30 57074 Siegen Germany Phone: +49 160 1758508 Email: weberphilip [at] web [dot] de
If you have any questions regarding data protection, you can contact us at any time using the contact details above.
Keep2Cook is a web-based platform for digitizing, editing, and managing recipes, planning groceries, and supporting users while cooking.
We process personal data only where this is necessary to provide Keep2Cook, handle inquiries, communicate with users, maintain the security and further development of the platform, or comply with legal obligations.
The data processed depends on which Keep2Cook features you use.
When registering for and using Keep2Cook, we process, in particular:
You may also voluntarily provide the following profile data:
Your password is not stored by us in plain text. Authentication is provided through Supabase Auth.
When you create, import, or edit recipes, we may store, in particular:
To automatically digitize a recipe, you can upload an image of a recipe or take one directly with your device's camera.
The original image used for automatic recipe digitization is transmitted to the Gemini API for processing and is not permanently stored by Keep2Cook afterwards.
Separately, you can save a recipe image as a permanent cover image. These cover images are stored by Keep2Cook in compressed WebP format.
Permanently stored cover images are not sent to the Gemini API for automatic recipe digitization.
Keep2Cook allows recipes to be processed based on a URL you provide.
For this purpose, Keep2Cook may access the website you specify and retrieve and structure recipe information available there.
The URL of the original source may be stored with the recipe.
When using and processing content from third-party websites, you must comply with the applicable rights and terms of use. You are responsible for ensuring that you only use content whose use is legally permitted.
You can also enter recipes as free text. Keep2Cook can use AI to structure this text, for example into ingredients, preparation steps, and timers.
When using shopping lists, we may store, in particular:
You can also enter ingredients as free text.
Shopping lists are generally stored until they are deleted by an authorized user.
Keep2Cook provides a friends feature.
To provide this feature, we process, in particular:
An @handle can be searched for within the platform.
Alternatively, a friend request can be initiated through a personal link or QR code.
A friendship is generally created only once the request has been accepted. Users may optionally enable automatic acceptance of friend requests.
Friendships can be removed at any time.
Other users generally only see the @handle you have selected. Your email address is not shown to other users.
Within the friends feed, connected users can see information about their friends' activities.
This may include:
The exact time of the cooking activity is not shown to other users.
You can mark individual friends as Favorite Friends.
For these people, you can enable a notification when you start cooking a recipe.
The notification may include your @handle, the cover image, and a link to the respective recipe.
This feature must be enabled individually and is not automatically active for all friends.
Recipes are visible by default only to connected friends.
You can manually set individual recipes to private.
Private recipes are visible only to you.
Keep2Cook does not provide a generally accessible public profile or recipe library.
If a recipe URL is shared outside Keep2Cook, the URL may be used, for example, to generate a preview. The actual recipe data remain protected by the applicable access restrictions.
Shopping lists can be shared with other users.
Invited users can manage the shared shopping list according to the features provided by the platform.
Sharing can be revoked at any time.
Keep2Cook uses Google's Gemini API for various AI-powered features.
The Gemini API is used by Keep2Cook as a Paid Service.
Depending on the feature used, the following types of content may be transmitted to Google:
The data are processed in each case to provide the AI-powered feature requested by the user.
When you upload or capture a recipe image for digitization, the image is transmitted to the Gemini API.
Gemini processes the image to generate structured recipe data, such as:
The original image used for digitization is discarded by Keep2Cook after processing.
Recipe text entered by you may be transmitted to Gemini so that ingredients, preparation steps, and timers can be detected and structured.
Keep2Cook can use the Gemini API to modify recipes, including making them:
For this purpose, the recipe data required for the respective adjustment are transmitted to Gemini.
The generated variants are currently not stored as permanently separate AI-generated versions of the recipe.
Keep2Cook can use the Gemini API to check whether multiple shopping list items refer to the same ingredient.
For this purpose, the names and quantities of the relevant items may be transmitted to Gemini.
Keep2Cook can use the Gemini API to translate recipes.
This may include processing recipe titles, ingredients, quantities, and preparation steps.
Generated translations may be stored in Keep2Cook.
When the Gemini API is used as a Paid Service, prompts, associated system instructions, submitted files including images, and generated responses are not used by Google to improve its products. Google may nevertheless process or log such data for a limited period for purposes such as detecting abuse or violations of its terms of use and for legally or regulatory required purposes.
Use of the Gemini API is additionally subject to Google's applicable Gemini API terms and privacy policies.
We use Supabase for, in particular:
Among other things, account, profile, recipe, shopping list, friendship, and cooking data may be stored there.
Our Supabase project is currently located in West EU (Paris), France.
Further information: https://supabase.com/privacy
Supabase provides a Data Processing Addendum for the processing of personal data.
We use Resend for transactional and voluntary emails.
This includes, in particular:
In this context, email addresses and the content required for the respective email may be processed.
Resend processes customer data in the United States. The DPA provided by Resend contains provisions for international data transfers, including Standard Contractual Clauses.
Further information: https://resend.com/privacy
Keep2Cook uses Cloudflare Workers for hosting, delivery, and technical functions of the platform.
Technical data generated during communication between your browser and the server may be processed. This may include, in particular, IP address, timestamp, requested resource, technical request data, and other data required for operation and security.
We also use Cloudflare Workers Analytics for technical usage and performance information.
Further information: https://www.cloudflare.com/privacypolicy
Cloudflare provides a Data Processing Addendum for its services.
You can subscribe to the Keep2Cook newsletter.
Registration uses a double opt-in process. After entering your email address, you will receive a confirmation email. The subscription is activated only after you confirm it.
The following data may be stored in particular:
Processing is based on your consent pursuant to Art. 6(1)(a) GDPR.
You can unsubscribe from the newsletter at any time. You can do so using the corresponding function in your Keep2Cook account or the unsubscribe link contained in a newsletter email.
You can submit feedback through a feedback form within Keep2Cook.
The following data may be processed:
Providing an email address is optional.
Screenshots and other attachments are used solely to process the respective feedback and are deleted after the reported issue has been resolved, unless further storage is required.
Technical logs may be processed for security, troubleshooting, and technical operation.
These may include, in particular:
Keep2Cook generally uses UUIDs for internal user references.
To limit the use of AI features, AI usage events are also stored. The current limit is 30 AI requests per user per day. This limit may be adjusted.
Technical logs and other data may remain stored for a limited period after account deletion where this is necessary for security, troubleshooting, abuse prevention, or legal obligations.
Keep2Cook uses technically necessary storage mechanisms in the browser, in particular for:
Where the storage of information or access to information in a user's device is strictly necessary to provide a digital service explicitly requested by the user, this may be permitted without separate consent pursuant to Section 25(2)(2) TDDDG.
Google Analytics is currently not used by Keep2Cook.
Keep2Cook may request access to your device's camera when you want to capture a recipe image.
Access is requested only when you use the respective feature and grant the required permission.
When used for AI-based recipe digitization, the captured image is transmitted to the Gemini API and subsequently discarded by Keep2Cook unless you independently save it as a cover image.
Keep2Cook may use browser notifications for timers in cooking mode.
The relevant permissions are controlled by your browser or operating system.
Use of push notifications is not required to register an account.
Personal data are deleted as soon as the respective purpose no longer applies and there are no statutory retention obligations or other lawful reasons for continued storage.
You can delete your account using the corresponding function in Keep2Cook.
When the account is deleted, the application data associated with your account are generally deleted, including:
Technical logs, email logs, and other data may remain stored for a limited period where storage is required for technical, security-related, or legal purposes.
Original images uploaded exclusively for AI-assisted recipe digitization are not permanently stored by Keep2Cook after processing.
Feedback and related attachments are deleted after processing or resolution of the reported issue, unless further storage is required.
Newsletter data are stored for as long as you remain subscribed or for as long as evidence of the subscription is required.
Depending on the purpose, we process personal data in particular on the following legal bases:
The applicable legal basis depends on the specific processing activity.
Where we process personal data on the basis of Art. 6(1)(f) GDPR, our legitimate interests include, in particular:
Depending on how you use Keep2Cook, personal data may be transmitted to the following service providers in particular:
Data are transmitted only where required for the respective function or due to legal obligations.
Some of the service providers mentioned above process data outside the European Union or European Economic Area.
In particular, Resend processes customer data in the United States and provides appropriate contractual safeguards for international data transfers.
International data transfers may also take place in connection with Cloudflare and Google. The applicable legal and technical safeguards are governed by the respective privacy and contractual terms of the providers.
Keep2Cook uses AI to process and structure recipes and shopping list data.
However, no automated decision-making takes place that produces legal effects concerning users or similarly significantly affects them.
Subject to the applicable legal requirements, you have, in particular, the following rights:
To exercise these rights, please contact: weberphilip [at] web [dot] de
The lawfulness of processing carried out before withdrawal remains unaffected.
You have the right to lodge a complaint with a data protection supervisory authority regarding the processing of your personal data.
Providing an email address is required to register for and use Keep2Cook.
Other information, such as a display name or personal profile details, may be provided voluntarily.
This Privacy Policy may be updated if Keep2Cook, the service providers we use, technical procedures, or legal requirements change.
The latest version of this Privacy Policy will be published on Keep2Cook.
Last updated: 12 August 2026