1. Data Controller
The controller responsible for the processing of personal data in connection with RecipeStrip is:
Vantaguard, Owner René Marcel Köllgen
Quellenweg 33
50259 Pulheim
Germany
Email: support@vantaguard.de
Website: https://vantaguard.de
2. Purpose and Core Principle of RecipeStrip
RecipeStrip is an Android app that retrieves a recipe page supplied by the user directly on the device or locally structures recipe text supplied by the user, and presents its ingredients and instructions in a focused view.
No Vantaguard user account or login is required. Vantaguard does not operate a RecipeStrip server for retrieving recipe pages or processing recipe text, an image proxy or a cloud recipe library. Recipe pages and any recipe images are not routed through Vantaguard servers. Retrieval, extraction and normalisation of recipe pages, and recognition and structuring of supplied recipe text, take place on the device. RecipeStrip does not use an external AI, LLM or cloud parsing service for recipe text.
At your explicit request, RecipeStrip can create a backup file with the .recipestrip extension. You choose the destination through the Android system dialog; it may also be outside your device. Vantaguard does not operate a RecipeStrip backup server.
3. Data Supplied by the User
RecipeStrip processes a recipe URL only when you type it, use the paste-from-clipboard action or share it with RecipeStrip from another app. Copied recipe text is processed when you choose “Paste from clipboard” or share text with RecipeStrip using Android's sharing functionality.
The following recipe information may be processed locally from a supported page or recognised recipe text:
- title and, where available, source URL of the recipe
- source domain
- serving or yield information
- preparation, cooking and total time, where available
- ingredients in their recognised order
- instructions and supported section headings
- cooking tools or equipment from supported recipe pages, where clearly identified
- image URL from structured recipe data or page metadata, where available
- time at which the recipe was explicitly saved
If copied or shared recipe text also contains exactly one valid HTTPS link, that link may be retained as source attribution and stored locally with the recipe when you explicitly save it.
RecipeStrip does not invent missing recipe content. If it cannot recognise a complete supported recipe, no recipe is saved.
4. Direct Requests to External Recipe Websites
For a URL import, RecipeStrip sends a direct HTTPS request from your device to the recipe website you supplied. If a complete recipe is instead recognised locally from recipe text, an HTTPS URL contained in that text is not requested merely because it accompanies the text; it may be retained as source attribution. Where a supported recipe page provides a recipe image, RecipeStrip may obtain its image URL from structured recipe data or page metadata. When the image is displayed, it is requested directly from the recipe website or the image or CDN server used by that website. Vantaguard does not route either the page request or the image request through a RecipeStrip server or image proxy.
The operator of the requested website or the image or CDN server it uses may receive standard connection and request data, in particular:
- the IP address of your internet connection
- the time of the request
- the requested URL or image resource
- technical request headers, including a mobile browser identifier and language preferences
The applicable privacy information of the external recipe website or the image or CDN server it uses applies to that processing. RecipeStrip cannot guarantee that every website or image resource is reachable or contains a supported recipe or recipe image.
5. On-Device Processing and Storage
The retrieved HTML page content is evaluated in memory and is not stored as raw HTML after extraction. Unsaved imported recipe data, including locally structured recipe text, is handled within the running app context; the currently displayed normalised recipe is initially held only in volatile app memory.
The normalised recipe text and associated metadata are placed in the local recipe library on your device when you explicitly save a recipe for offline use with RecipeStrip Pro or explicitly confirm the import of a RecipeStrip backup file. Where a recipe image is available and the download succeeds, RecipeStrip may also store a local copy as a separate file in the app's private storage. This file is not stored in public photo or gallery folders; the recipe record may contain a reference to the private local file. The image file is not stored as a Base64-encoded part of the recipe record.
If the image download fails, the remaining recipe data can still be saved. A remote image URL that was obtained may remain available for later online display. The locally stored data remains until you delete it, clear the app data or uninstall RecipeStrip.
RecipeStrip also stores locally whether onboarding has been completed and, if the local review mode is used, its activation status. There is no cloud synchronisation or cross-device recipe synchronisation.
Backup export and import require neither RecipeStrip Pro nor a RecipeStrip account or backend service. At your explicit request, RecipeStrip creates a .recipestrip file containing saved recipes, their metadata, any source URLs and available offline images. Missing offline images are not downloaded for the backup. Purchase and entitlement data is not included.
When importing, the selected backup file is checked locally and a summary is shown. New recipes are merged with the existing library only after you confirm. The library is not replaced; in a conflict, the recipe already stored locally is kept and is not overwritten by the backup. Backed-up offline images can be restored as separate files in RecipeStrip's private app storage.
You choose the destination through the Android system dialog. Depending on your device and configured services, this may be local device storage, external file storage or a cloud or file service you have configured. If you select an external service, its privacy information applies to storage by that service. Vantaguard does not automatically receive the backup file.
RecipeStrip backup files are currently not encrypted. Anyone with access to the file can view the recipe data, source URLs and any recipe images it contains. Keep backup files in an appropriately protected location.
6. Share Feature and Clipboard
When you share text with RecipeStrip using Android's sharing functionality, the app can receive and process a recipe URL or copied recipe text from it.
The clipboard is read only after your explicit action when you choose “Paste from clipboard”. The pasted content is handled locally as a recipe URL or copied recipe text, provided a supported recipe structure is recognised. RecipeStrip does not monitor the clipboard in the background, read it continuously or access clipboard history. Clipboard content is not sent to Vantaguard.
Recognition and structuring of copied or shared recipe text is deterministic and takes place locally on the device. The recipe text is not sent to Vantaguard or an external AI, LLM or cloud parsing service for this purpose.
7. RecipeStrip Pro, Google Play and RevenueCat
RecipeStrip Pro is intended as an optional Lifetime one-time purchase. Google Play processes the purchase. RecipeStrip also uses RevenueCat, a service provided by RevenueCat, Inc., to provide and verify the Pro entitlement.
The following purchase-related information in particular may be processed:
- product and package identifier
- purchase, transaction and entitlement status
- information required to restore a purchase
- platform, app version and technical information required for purchase processing
- a random anonymous App User ID generated by RevenueCat
Recipe titles and content, including ingredients and instructions, as well as recipe and image URLs and recipe images, are not sent to RevenueCat or Google Play as part of purchase or entitlement processing. Because the app configures RevenueCat without a RecipeStrip user account, the RevenueCat SDK generates a random anonymous identifier. Google Play handles the actual payment. Vantaguard does not receive complete credit-card or bank details.
Where applicable, the legal basis for purchase-related processing is Art. 6(1)(b) GDPR for performing the purchase contract and Art. 6(1)(c) GDPR for compliance with legal obligations.
Further information is available in the privacy policies of Google and RevenueCat.
RecipeStrip backup files contain neither purchase status nor RevenueCat entitlements or Google Play account information. Purchases and Pro entitlements are managed separately from recipe backups.
8. Restore Purchases
When you use “Restore purchase”, RecipeStrip retrieves the current purchase and entitlement status through Google Play and RevenueCat. The purchase-related data required for this purpose is processed. Locally saved recipes, recipe and image URLs, and recipe images are not sent to Google Play or RevenueCat.
Importing a .recipestrip backup file does not restore a purchase. Purchases and entitlements are still restored independently of recipe backups through Google Play and RevenueCat.
9. Local Review Mode
RecipeStrip may provide a locally activated review mode for testing the Pro features. A review code entered by the user is cryptographically compared with a configured verification value on the device. The review code is not sent to Vantaguard or RevenueCat.
After a successful check, the app stores only the activation status locally. This review mode does not create a Google Play purchase event and does not change a RevenueCat purchase entitlement.
10. Cook Mode, Language and Technical Settings
At your explicit request, Cook Mode keeps the display awake while the recipe view is open. No recipe data is transmitted for this purpose.
RecipeStrip reads the preferred device language to select the German or English interface. The language selection is handled locally and is not sent to Vantaguard.
11. No Analytics, Advertising or Crash-Reporting Services
According to the current technical implementation, RecipeStrip contains no SDKs for usage analytics, personalised advertising or external crash reporting. Technical errors may be written to local development console logs; automatic transmission to a crash-reporting provider is not integrated.
12. Deletion and Storage Duration
You can delete saved recipes individually from the local recipe library. This removes the recipe record. RecipeStrip also attempts to remove any associated local image file created by RecipeStrip. This cleanup is best-effort and is limited to files within RecipeStrip's own image storage.
You can also remove all private RecipeStrip app data through the Android app settings or by uninstalling the app. Under normal Android conditions, this removes RecipeStrip's private app data.
Uninstalling RecipeStrip does not automatically delete purchase history held by Google Play or RevenueCat. The respective providers' retention and deletion rules apply to this information.
Exported .recipestrip files are stored outside RecipeStrip's private app storage. Deleting a recipe in RecipeStrip, clearing the app data or uninstalling the app does not automatically delete them. You must delete backup files you no longer need from the chosen destination yourself. After an import, restored recipe data and private offline images are subject to the app's normal deletion process.
13. Recipients and International Processing
Vantaguard does not receive the content of the retrieved recipe page or recipe image, copied or shared recipe text, your locally stored recipe library or private image copies. Depending on the feature used, data may be received by:
- the operator of the recipe website you supplied and, where applicable, the image or CDN server it uses when a page or image is requested directly
- Google or Google Play for distribution, purchase and restoration
- RevenueCat, Inc. for providing and verifying the Pro entitlement
- an external file or storage service you select through Android, when the backup file is written to the chosen destination at your explicit request
Google and RevenueCat may also process data outside the European Union or European Economic Area. Details and the safeguards described by these providers are set out in their current privacy policies.
14. Your Privacy Rights
Where the statutory requirements are met, you have in particular the right to access, rectification, erasure, restriction of processing, data portability, objection and withdrawal of consent with future effect.
Vantaguard cannot access recipes or private local image copies stored exclusively on your device. You can delete saved recipes directly in the app; under normal Android conditions, you can remove all private app data through the app settings or by uninstalling RecipeStrip. Questions concerning purchase-related data can be sent to support@vantaguard.de.
Vantaguard cannot access .recipestrip files you export yourself and cannot delete them centrally. You manage and delete these files at the chosen destination.
15. Right to Complain and Data Security
You have the right to lodge a complaint with a data protection supervisory authority if you believe that the processing of your personal data violates applicable data protection law.
The security of recipes stored locally also depends on the security of your device. Use a screen lock, keep Android updated and do not hand the device to third parties while it is unprotected. Recipe data and local image copies within the app are stored in its private storage. Exported .recipestrip backups are currently unencrypted and should be kept in an appropriately protected location. Complete security of electronic systems cannot be guaranteed.
16. Changes to this Privacy Policy
This privacy policy may be updated if RecipeStrip is further developed or if legal or technical requirements change. The current version will be published at https://vantaguard.de/en/recipestrip-privacy.html.