Privacy Policy
Effective November 18, 2026
Scrambled and Spiced is a recipe site about hearty dinners, easy breakfasts and sweet treats made with everyday ingredients. Reading recipes here doesn’t require an account, a sign-up or an email address. This policy covers the few times information does change hands: when you leave a comment, rate a recipe or write to us, and the behind-the-scenes services that keep the site online.
The short version
- Reading recipes
- Standard server and security logs only. No analytics, no ads.
- Commenting or rating
- Name, email (kept private), optional website, your comment and star rating.
- Writing to us
- Your name, email and message, delivered to us by email.
- Newsletter
- We don’t offer one at the moment, so we don’t collect any sign-ups.
Who we are
This policy applies to scrambledandspiced.com. When it says “we,” “us” or “our,” it means the people who operate Scrambled and Spiced. The best way to reach us about anything in this policy is our Contact Us page.
What happens when you simply browse
You don’t have to give us anything to read a recipe, print a recipe card or search the index. Two kinds of technical records are still created automatically:
- Server logs. Our web host records each request made to the site: the IP address, the time, the page or file requested, the page you came from and your browser type. These logs help us diagnose problems and block attacks.
- Cloudflare. Pages reach you through Cloudflare’s network, which caches the site for speed and screens out harmful traffic. Cloudflare processes your IP address and connection details for that purpose and may place a security cookie to identify bots. More detail is in the Cloudflare Privacy Policy.
We don’t use Google Analytics or any other visitor-tracking tool, and the site doesn’t display ads. If that ever changes, this policy will be updated first.
Comments and star ratings
Every recipe ends with a comment form where you can ask a question, tell us about a swap you tried or leave a star rating. The form collects your name, your email address and, if you like, a website address. Your name, comment, rating, any website link and the date are shown publicly. Your email address is never shown. WordPress also stores the IP address and browser details sent with each comment. That gives us a way to deal with spam and abuse.
Comments from first-time commenters wait for approval before they’re published. Star ratings left with a comment are added into the recipe’s overall rating.
Next to each comment, the site shows a profile image from Gravatar, a service run by Automattic. To look up your image, Gravatar receives a coded version (a hash) of your email address, and your browser fetches the picture from Gravatar’s servers. See the Automattic Privacy Policy for how that service works.
Messages you send us
The form on our Contact Us page asks for your name, email address, a topic and your message. Submitting it sends those details to us by email. The website doesn’t keep its own copy. We use what you send only to answer you, follow up on your request or correct a recipe you’ve flagged.
Cookies
The site sets very few cookies:
- Comment details. If you tick “Save my name, email, and website in this browser for the next time I comment,” WordPress remembers those three fields in your browser for about a year. Leave it unticked and nothing is saved.
- Security. Cloudflare may set a cookie that helps separate real readers from automated traffic.
There are no advertising or analytics cookies. Your browser settings let you view, block or clear cookies whenever you like.
Sharing buttons
Recipe posts include “Share This Recipe On Facebook” and “Pin this recipe for later!” buttons, plus Facebook, Pinterest and Email share links at the end of the article. They’re plain links. No Facebook or Pinterest code runs on our pages, so those companies receive nothing from us unless you click. When you click, a Facebook or Pinterest window opens and that company’s privacy policy applies.
Embedded content
Our posts don’t currently embed videos or posts from other websites. If we add embedded content in the future, it will behave as if you had visited the original site, which may collect information about you.
Why we use the information
- to publish and moderate comments and ratings;
- to answer questions and messages;
- to correct recipes when readers spot an error;
- to keep the site secure, fast and online.
Who else sees it
Besides the public parts of comments, information may be shared with:
- the companies that make the site work: our web host, Cloudflare and the email systems that carry contact-form messages;
- Gravatar, as described above;
- authorities or others when we’re legally required to share it, or when it’s needed to prevent fraud, abuse or harm.
How long we keep it
A comment and the details stored with it remain for as long as the comment is on the site. Spam and unapproved comments can be removed. Contact messages live in our email, not on the website.
Security
All pages load over encrypted HTTPS, and only authorized accounts can manage the site. Even so, no system is perfectly secure. Please keep sensitive personal details out of comments and messages.
Your requests
If you’ve commented or written to us, you can ask us to show you, correct or delete the personal information we have about you, or to send you a copy of it. Send your request through the contact form and choose “Privacy request” as the topic. To protect you, we may ask you to confirm that you own the email address linked to your comment or message. Depending on where you live, you may have additional privacy rights under local law. We’ll respond to requests as the law that applies to you requires.
Children
Scrambled and Spiced is meant for a general audience and isn’t aimed at children under 13. We don’t knowingly collect their personal information. If you think a child has submitted personal information here, let us know and we’ll delete it.
Updates to this policy
When the way the site handles information changes, for example if we add a newsletter or a new service, we’ll revise this page and update the effective date at the top.
