Privacy Policy
How Recipe Converter handles recipe text and other information.
Last updated: 2026-11-02
Overview
Recipe Converter offers a free fixed example and paid conversion packs for your own recipes. This policy explains what information is processed when you use the tool and how third-party services are involved.
Information We Collect
When you use Recipe Converter, we may process:
- Recipe text that you submit for conversion.
- Technical information normally sent with a web request, such as IP address, browser type, device type, request time, and error information.
- Conversion usage records, including request time, conversion type, success or failure, a generic error category, and processing duration. These server-side records contain no recipe text, IP address, or visitor identifier.
- First-party activity records, only if you allow analytics: a random browser identifier, a session identifier, event time, conversion mode, and actions such as viewing the converter, displaying a conversion result, copying, requesting a print dialog, initiating a download, checking a grocery item, or clicking support. These records contain no recipe text, ingredient names, IP address, email address, or payment details.
- Analytics information, if you choose to allow analytics cookies, such as page views, broad location, device and browser information, and interactions with the recipe converter.
- Messages you send by email, including your email address and the contents of your message.
To convert your own recipes, we store your account name, email address, authentication records, purchased balance, order references, payment status and credit activity. Passwords are stored as hashes by our authentication system. Payment providers process payment details; we do not store full card numbers or security codes.
Payments and Order Records
Depending on the payment option enabled when you purchase, checkout is provided by Waffo, Stripe, or Creem. The checkout identifies the provider handling your transaction. Their privacy information is available here: Waffo Privacy Policy, Stripe Privacy Policy, and Creem Privacy Notice. Only the provider used for your transaction receives the checkout information for that purchase.
To create and reconcile a purchase, we send the selected provider your account email, internal account and order identifiers, the selected conversion pack, price and currency, and checkout return information as needed by that integration. We do not send your recipe text or conversion results to payment providers. You provide payment credentials and any required billing information directly through checkout; the provider handles that information under its own policy.
We receive payment confirmation and transaction information needed to verify the order and grant conversions, such as provider transaction references, amount, currency, payment status, and associated account and order references. We use these records to deliver purchased conversions, maintain your balance, provide support, investigate duplicate charges or fraud, and review refunds and payment disputes. Account, order, and credit records may need to remain after account closure where necessary for accounting, legal obligations, or resolving a dispute; we retain them only for as long as those purposes require.
How Recipe Text Is Used
Recipe text is processed to identify the recipe title, servings, ingredients, and instructions. We do not store raw submitted recipe text on our server. Structured results (including extracted ingredients and instructions) are encrypted and available for recovery for 24 hours. Expired results are cleared on subsequent billing activity; this is not a scheduled deletion guarantee. We retain a keyed recipe fingerprint and conversion status for accounting and duplicate-request protection.
Google Sign-In
If you choose Google sign-in, we receive basic account information such as your name, email address, profile image and Google account identifier. We keep account-linking and authentication records to sign you in and associate your purchased conversions with your account. We do not request access to Gmail messages or Google Drive files. Google processes the sign-in under its own privacy policy. Existing email accounts must sign in before explicitly connecting Google.
Google Gemini
Recipe parsing uses the Google Gemini API. The recipe text you submit is sent to Google for processing.
Google's treatment of submitted content depends on the API service tier. Under Google's current terms:
- Content submitted through unpaid Gemini API services may be used to improve Google products, and human reviewers may process API input and output.
- For paid Gemini API services, Google states that prompts and responses are not used to improve its products, although limited logging may occur for safety, security, and legal purposes.
Do not submit sensitive, confidential, or personal information in a recipe. For details, read the Gemini API Additional Terms and Google Privacy Policy.
Other Uses and Sharing
We may use limited technical information to operate, secure, troubleshoot, and improve the website. We may disclose information when required by law or when reasonably necessary to protect the website, its users, or others.
Google Analytics
With your consent, Recipe Converter records the limited first-party activity described above and uses Google Analytics to understand how visitors use the website. Google Analytics uses cookies to measure visits, page views, approximate location, device and browser information, and anonymized interactions such as completing a conversion or copying a grocery list. We do not send recipe text, ingredient names, or contact details to Google Analytics.
You can choose not to allow analytics cookies through the cookie choice shown on the website. For more information about how Google processes data, see Google's Privacy Policy.
We do not sell personal information.
Data Retention
Raw recipe text is not retained on the server after processing. Encrypted structured results are available for 24 hours and then cleared on subsequent billing activity. Account, order and credit records are retained for service delivery, accounting, dispute resolution and applicable obligations. When checkout starts, a draft of your recipe and settings is saved in this browser tab’s session storage, restored for up to 24 hours, and removed after successful conversion or when you clear the form. Closing the tab or clearing site data also removes it. Third-party providers may retain or process information according to their own terms. Your analytics cookie choice is saved in your browser until you clear site data. If you accept analytics, a random first-party browser identifier is stored locally for up to 90 days. A new session identifier is created after 30 minutes without a tracked interaction. Activity records are excluded from reports after 90 days and deleted on the next recorded activity. Clearing site data or declining analytics removes the local activity identifiers; it does not delete previously recorded activity. You can request deletion of retained activity records by providing your random browser identifier from the recipeconverter.activity-identity local storage entry; please provide only the visitorId value.
Emails you send may be kept as long as reasonably necessary to respond and maintain support records. Technical logs may be kept for a limited period for security and troubleshooting.
Access, Correction, and Deletion Requests
You can email suki41719e@gmail.com to ask what personal information we hold about you, request a copy, correct inaccurate information, or request deletion. Describe your request and provide only the information needed to identify the relevant interaction, such as the email address you used to contact us or an order reference if you purchased a conversion pack or made a support payment. Do not send passwords or card numbers. We may ask for reasonable verification before disclosing or changing personal information.
We review requests and respond within the time required by applicable law. Some information may need to be retained for legal obligations, security, or resolving disputes; where a request cannot be fulfilled in full, we explain the reason. We cannot identify an individual from conversion statistics that contain no visitor identifier, and we do not retain raw recipe inputs for retrieval. Temporary structured results can contain recipe content as described above.
To request account closure or deletion, contact us using your account email. We verify ownership and explain any records retained for accounting or dispute resolution. You may stop using the service at any time and clear website data in your browser to remove drafts and the saved analytics preference. To withdraw analytics consent, clear site data and choose to reject analytics when prompted again. Information held independently by Google or a payment provider is subject to that provider's own request procedures and privacy policy.
Changes to This Policy
We may update this policy when the website or its service providers change. The updated date at the top of this page shows when it was last revised.
Contact Us
For privacy questions, email suki41719e@gmail.com.