Privacy Policy

Recipe text and the active Recipe Lab workspace

Your active Recipe Lab text is designed to stay in browser session storage rather than an account based recipe database. Session storage lets the current workspace survive ordinary navigation during the browser session. It is not intended to create a public recipe page or a permanent KitchenMathHub recipe library.

KitchenMathHub does not place your recipe text into the page URL. Serving changes, unit conversions, pan choices, and other Recipe Lab transformations are calculated from the working recipe without creating an indexable recipe link. This reduces the chance that private working text is exposed through a copied URL, browser history entry, or search engine crawl.

Calculator results may still be visible to anyone who can access your unlocked browser or device. Use normal device security when you are working with recipe material that you consider private or commercially sensitive.

Recent Recipes use local browser storage

A recipe is stored in Recent Recipes only after you choose Save to recent. The original recipe text, a short title, and the save time are stored in local browser storage on that browser and device. KitchenMathHub does not require an account or email address for this feature.

You can remove individual recent recipes or clear the complete recent list from Recipe Lab. Clearing KitchenMathHub site data through your browser can also remove these locally stored recipes. A recipe saved on one browser is not automatically synchronized to another browser or device.

Recent Recipes are saved from the original working text rather than a chain of converted copies. This supports accurate recalculation when you reopen a recipe and choose a new serving size, measurement system, pan, oven mode, or other transformation.

Recipe URL import

When you use Import recipe, the recipe page URL is sent to a KitchenMathHub server endpoint so the public page can be requested. The importer looks for standard Recipe structured data such as the recipe name, yield, ingredients, and instructions. It does not intentionally use private network addresses or authenticated pages.

The imported recipe text is returned to your browser for review. KitchenMathHub does not use the URL import feature as a permanent hosted recipe library. The website you import from can receive a normal web request from KitchenMathHub infrastructure, and routine infrastructure logs may record technical request information according to the hosting provider's settings.

If a page does not expose usable Recipe structured data, KitchenMathHub asks you to paste or speak the recipe instead. This reduces the need to collect unrelated webpage content and avoids presenting an incomplete scrape as a reliable recipe.

Speech input and spoken cooking steps

Speech input depends on speech recognition features provided by your browser or device. KitchenMathHub receives the recognized text in the webpage and organizes that text for the recipe parser. Depending on the browser, speech recognition may be processed on the device or through a service operated by the browser provider. That processing is governed by the provider's own privacy practices.

Kitchen Mode read aloud uses browser speech synthesis when available. The written instruction remains visible even when spoken read-back is unsupported. KitchenMathHub does not require voice features to use the recipe converter.

Do not rely on voice output alone for safety-sensitive cooking information. Check the written recipe, appliance instructions, and appropriate food temperature guidance when cooking time or internal temperature affects food safety.

Limited ingredient demand events

KitchenMathHub can record limited interaction events to understand which ingredient conversions need better coverage. Examples include a sanitized ingredient search term, the selected ingredient ID, the number of search matches, a database-to-converter click, or a Recipe Lab ingredient match correction.

Full pasted recipes, full spoken recipe transcripts, serving quantities, pan choices, and converted recipe output are not intentionally included in these ingredient demand events. The tracking code is designed so analytics activity cannot interrupt a calculator workflow.

Routine hosting logs may also contain technical request information. This can include data normally processed by a web hosting platform, such as request time, route, response status, and network information needed to deliver and protect the service.

Sharing, copying, and printing

Share Recipe uses the browser or device sharing interface when that feature is available. The destination you choose, such as a messaging app or notes service, handles the shared recipe under that service's own privacy terms. If browser sharing is unavailable, KitchenMathHub can fall back to copying the converted text to the clipboard where supported.

Copying and printing happen at your direction. Once recipe text is copied, printed, saved, or sent to another service, that copy is outside the KitchenMathHub browser workspace and should be managed according to your own privacy needs.

Browser controls and data retention

You can control most Recipe Lab storage through the browser itself. Closing a browser session can remove session storage, while Recent Recipes remain only if you deliberately saved them to local storage. The exact behavior of private browsing, automatic site-data deletion, synchronized browser profiles, and storage limits depends on your browser and device settings.

KitchenMathHub does not need a user account to provide the core calculators described in this policy. That means there is no KitchenMathHub password database, saved payment profile, or account-based recipe history required for the current tools. If account features are introduced in the future, this policy should describe the new information and controls before those features become part of the normal service.

Technical infrastructure can retain operational information for a different period than browser recipe storage. Hosting and security systems may process request logs needed to deliver pages, diagnose errors, limit abuse, and protect the service. Ingredient demand events are intentionally narrower than full recipe content and are designed to answer product questions such as which ingredient references users search for or correct most often.

Do not use Recipe Lab as the only archive for an important recipe. Browser storage can be cleared by the user, the browser, device cleanup software, or a reset of site data. Copy, print, or save an important recipe in a storage system you control if you need a durable record.

Children and sensitive information

KitchenMathHub is a general cooking utility and is not designed to collect sensitive personal profiles. Recipe calculations normally do not require a name, date of birth, home address, financial information, health record, or precise location. Avoid entering sensitive personal information into recipe text, ingredient searches, or support messages when it is not needed for the cooking task.

Parents and guardians should supervise online use by children according to their own household rules and applicable local requirements. The cooking tools can involve hot appliances, sharp equipment, raw ingredients, and food-safety decisions, so online calculator use does not replace appropriate kitchen supervision.

External links and source websites

KitchenMathHub links to external references so users can inspect important culinary, government, educational, and manufacturer sources. External websites operate under their own privacy policies and may use cookies, analytics, or other technologies that KitchenMathHub does not control.

Contact information

If you email KitchenMathHub, the information in your message is used to read and respond to your request. Do not send passwords, payment details, health records, or other sensitive personal information when reporting a calculator issue.

Privacy questions can be sent to contact@kitchenmathhub.com.