Quick summary

  • No accounts, no login: your pantry and saved recipes stay on your device and never reach our servers.
  • AI assistant prompts are sent to a third-party AI provider for processing; we log request metadata (not message text).
  • Contact form messages are stored internally so we can read and answer them.
  • We currently show no ad network on the site — the ads integration is switched off, and no ad cookies are set.
  • We do not sell your personal data and we do not publish any personal email address.

Data we may collect

We collect as little as possible. The following categories may be processed while you use the platform:

CategoryWhenWhere it is stored
AI assistant promptsWhen you write to the assistantSent to the third-party AI provider for processing; we do not store conversation text
AI request metadata (timestamp, locale, feature, token counts, success/error)With every AI requestInternal operational log for accounting and operations — no message text
Contact form submissions (email, category, message)When you submit the contact formOur internal database (for review and replies) — stored with a SHA-256 hash of the IP for abuse review, never the raw IP
Technical infrastructure logs (IP address, browser type, user agent)Automatically while browsingServer hosting infrastructure — for security and diagnostics
Site and analytics cookies (km_geo, km_consent, _ga)While browsing and when you choose consentFirst-party cookies on your device — details in the cookie policy
Local preferences (pantry, saved recipes)When you use these toolsOn your device only (browser local storage) — never sent to us

What we do not do

  • We do not sell your personal data to anyone.
  • We do not build profiles that tie your browsing to your identity.
  • We do not read your assistant conversations afterwards — message text is not stored by us.
  • We do not ask for payment or identity data for normal use.

The AI assistant

When you write to the assistant, your prompt may be processed by third-party AI service providers (currently: DeepSeek via API). That means your message text is sent to that provider's servers for processing, and the provider's own policies apply to that processing.

  • Catalog answers never reach an external provider: when you ask about a published recipe or ask to scale its servings, the system answers from our database locally with no external model call.
  • Generated suggestions stay inside the chat: they are not stored, not published and never enter the catalog.
  • Only metadata is logged: request timestamp, locale, feature, input/output token counts and outcome — for operations and cost accounting. No message text.

Do not include sensitive data (health, financial or full identity details) in assistant messages — the assistant is designed for cooking questions, and anything you send is processed as described above.

Sharing and social platforms

The share buttons on recipe pages are plain links (WhatsApp, Facebook, Pinterest and others) or your device's native share — no third-party tracking scripts. Pressing one opens the destination platform directly — we record no tracking event of our own when you share. When you open the social platform to share a link, that platform's privacy policy applies.

You may find KitchenMind content on external social platforms; when you interact with that content there, those platforms process your data under their own policies.

Cookies and local storage

The site uses Google Analytics 4 (GA4) through gtag.js to measure usage. When analytics is allowed, GA4 sets first-party cookies (such as _ga) and receives basic page views — the address of the page you visit (which may include your search words if you search on the site) and general technical browser information. Google Consent Mode v2 is active: analytics storage defaults to denied in regions that require consent (such as the EEA, the UK and Switzerland) until you choose, and ad signals stay denied. We never send GA4 your name, your email, or your assistant chat text. We also use the km_geo cookie (one day) to resolve your region for consent and km_consent (180 days) to remember your choice, plus browser local storage for on-device tools (pantry, saved recipes). Full category detail is in the cookie policy.

Advertising

We currently serve no ad network on the platform; the ads integration (Google AdSense) exists in the code but is switched off in production, and no ad script loads on our pages. If we enable it in the future, we will update this policy and the cookie policy before it goes live, and no ads will load before the consent mechanism required in your region is in place.

Data retention

CategoryRetentionReason
Contact form messagesUntil answered, maximum 24 monthsManaging replies and improving the platform
AI request metadataReviewed periodically and deleted when no longer operationally neededOperations and cost accounting
Technical infrastructure logsKept by the hosting infrastructure for a short period per its settingsSecurity and diagnostics
Data on your device (pantry, saved)Until you clear it in your browserIt lives on your device anyway

Your rights

Because we do not create accounts, most personal data we might hold about you is contact submissions and infrastructure logs. You can always:

  • Request access to your message data or ask us to delete it via the contact form under "Privacy".
  • Ask us to correct any information we hold about you.
  • Block third-party cookies in your browser settings and control ad personalization in Google Ads Settings.
  • Clear your device-tool data (pantry, saved) at any time in your browser.

Children

The platform is not directed at children under 13 and we do not knowingly collect their data. If you believe a child has sent us personal data, contact us and we will delete it.

Cross-border processing

Our data is stored on servers we host, and AI requests may be processed by an external provider whose servers operate in different regions. Where data crosses borders, it does so under the safeguards required by law in the applicable region.

Changes and contact

We update this policy when our actual practices change, and we show the last-updated date at the top of the page. For privacy requests, use the contact form under "Privacy".