Privacy Policy
This policy explains what information Crisp & Simmer ("we", "us") collects when you visit www.crispandsimmer.com, and how it's used. The short version: this is a recipe website — we collect as little as possible.
Information we collect
- Server & security logs. Our site is served through Cloudflare, which processes technical data (IP address, browser type, pages requested) to deliver the site and protect it from abuse. We see this data in aggregate form.
- Analytics. We use privacy-respecting, aggregate analytics to understand which recipes people find useful. This data is not used to identify individual visitors.
- Email you send us. If you contact support@crispandsimmer.com, we receive your email address and message. We use it only to reply, and we don't add you to any list.
Cookies
We do not set cookies for tracking today. If we introduce advertising or embedded features that use cookies in the future (see below), this policy will be updated first and consent mechanisms will be added where required by law.
Advertising
We plan to work with an advertising management partner to display ads on this site. When that happens, the partner and its demand partners may use cookies or similar technologies to serve and measure ads, and this policy will be updated with the partner's name, the data involved, and opt-out instructions before ads go live.
Third-party links
Articles may link to other websites (for example, product pages or other recipe sites). Their privacy practices are their own — this policy covers only our site.
Your rights
Depending on where you live (including under GDPR and CCPA/CPRA), you may have rights to access, correct, or delete personal information. Given how little we hold, the practical scope is usually your email correspondence — but for any request, contact support@crispandsimmer.com and we'll respond.
Children
This site is a general-audience recipe site and is not directed at children under 13.
Changes
We'll update this page when our practices change, and material changes will be reflected in the effective date above.