Cookies

Foodoobie policies

Cookies

Last updated: September 10, 2026

This page lists the cookies and similar identifiers visible in Foodoobie’s current implementation.

Foodoobie cookies

Name	Purpose	Duration
`hcdn`	First-party session cookie set by Foodoobie’s Hostinger/CDN delivery layer to support site delivery or protection. Secure and HttpOnly in the current implementation.	Browser session
`fdb_voted_[poll ID]`	Stores the selected choice, shows the visitor’s prior choice, and helps reduce duplicate voting. SameSite=Lax; Secure on HTTPS; readable by Foodoobie JavaScript.	Until a scheduled poll close where available; otherwise no more than one year, and removed on a later Foodoobie visit after closure.
`foodoobie_rg_bid`	Provides a pseudonymous browser identifier for anonymous Recipe Grabber rate limiting when combined with a salted hash of the request IP.	1 year

WordPress cookies

WordPress can set authentication, security, or preference cookies for signed-in users and administrators. Public visitors are not required to sign in for ordinary browsing, Pick My Craving, Polls, or Foodoobie It.

Analytics and advertising

Google Site Kit remains installed but disconnected. Foodoobie does not currently load Google Tag Manager, Google Analytics, advertising or remarketing tags, Meta Pixel, or analytics event tracking. These services therefore do not currently create visitor analytics or advertising cookies through Foodoobie.

AltText.ai

Foodoobie loads AltText.ai’s InstantAlt browser script to generate and serve alt text for production images that are missing persistent alt text. No AltText.ai-specific first-party cookie was found in the current implementation; the service can still receive browser requests as described on the Privacy page.

Server-side identifiers and retention

Poll duplicate protection stores a one-way fingerprint derived from IP address, browser user-agent, and poll ID. Individual vote/fingerprint records are removed after a poll has been closed for 30 days while aggregate totals remain. Recipe Grabber stores a salted identifier hash and usage records for 90 days; its cached recipe results expire after 30 days and expired rows are removed daily. Foodoobie It stores an expiring WordPress transient counter derived from a hashed visitor identifier for one day. These are not browser cookies, but they support security, duplicate protection, and rate limiting.

Managing cookies

Your browser can delete or block cookies. Blocking the functional cookies can cause Foodoobie to forget a displayed poll choice or assign a new Recipe Grabber browser identifier. Server-side duplicate-vote and request-limit records may still apply during their retention periods. Questions can be sent through the Contact page.