This page explains what data Desert Food Feed collects, why, and what choices you have. We've kept it plain — no boilerplate copied from somewhere else, no lawyer-speak.
The short version
We don't run analytics, we don't sell anything, and we don't share your data with advertisers. The only data we hold about you is what you choose to give us when you leave a comment or rate a recipe.
What we collect
When you visit a page
Your browser sends standard request data — the page URL, your IP address, the time, your browser type — which our web server records in short-lived access logs. We use these only to debug errors and detect abuse, and they roll off automatically.
We do not place any tracking cookies on first visit. The session cookies we use (dff_csrf for cross-site-request-forgery protection and dff_admin for site administrators only) are functional and stored only when needed.
When you leave a comment
Posting a comment captures: your display name, the comment body, an optional star rating, an optional email address (never displayed publicly), your IP address (used for spam defence) and your user-agent string. Comments wait in a moderation queue until an editor approves them, then appear publicly under the recipe.
If you supply an email address, we generate a Gravatar avatar from a hash of it. The email itself is never published and is used only to contact you about your specific comment if needed.
What we do not collect
No analytics scripts, no Google Analytics, no Facebook Pixel, no advertising cookies, no fingerprinting. We do not build a profile of your reading habits.
Third parties we load
- Google Fonts serves the typefaces used across the site. Google receives your IP address when fonts are fetched.
- Gravatar (run by Automattic) serves comment avatars when commenters supply an email address.
- YouTube embeds appear on recipe pages that include a video. Playback is handled by YouTube; their privacy notice applies once you press play.
- Google reCAPTCHA may run on the comment form if the administrator has enabled it; this helps block automated spam.
Each of these third parties has its own privacy policy. We chose them because they're widely used and reasonably privacy-respecting, but we cannot speak for what they do with the data their endpoints receive.
How long we keep things
Comments stay published until you ask us to remove them or until an editor deletes them. Pending comments that are flagged as spam are deleted on a rolling basis. Server access logs are kept for short periods (typically two weeks) for debugging, then rotated out.
Your choices
- Request removal of a comment you've posted — email us with a link to the comment and we'll delete it.
- Browse without commenting — no personal data of yours touches our database.
- Block third-party fonts and avatars at the browser level if you'd rather; the site still works, just with different typography.
Children
This site is general-audience and family-friendly, but it isn't directed at children under 13. We do not knowingly collect personal information from minors. If you believe a child has submitted a comment, contact us and we'll remove it.
Changes to this policy
If we change how the site handles data, we will update this page and note the date below. Material changes will be flagged on the home page for at least a week.
Contact
Email us through the address listed in the site footer for any privacy-related question, correction request or deletion request. We aim to reply within seven days.
Last updated: this version was published when the site moved from WordPress to a custom platform. Earlier versions may exist in archive snapshots of the older site.