Information handled when you visit

Foodoobie’s WordPress host and Hostinger delivery infrastructure receive request information needed to serve and protect the site, such as an IP address, browser or user-agent information, the requested URL, and request time. The Hostinger/CDN layer sets a first-party session cookie named hcdn. Foodoobie self-hosts its production font files. Google Site Kit remains installed but disconnected; Google Tag Manager and Google Analytics are not currently active, and Foodoobie does not currently load advertising, remarketing, or Meta Pixel tracking.

Polls

When you vote, your poll and choice identifiers are sent to Foodoobie’s public WordPress REST endpoint. The server combines your IP address, browser user-agent, and the poll identifier, then creates a one-way HMAC-SHA-256 fingerprint. Foodoobie stores the fingerprint—not the raw IP or user-agent—with the poll, choice, and vote time. Individual vote and fingerprint records are automatically deleted after the poll has been closed for 30 days; aggregate choice totals are preserved. A first-party cookie named fdb_voted_[poll ID] stores the selected option so the site can show the prior choice and reduce duplicate voting. If a poll has a scheduled close, the cookie expires no later than that close; otherwise its absolute maximum is one year, and it is removed on a later Foodoobie visit after the poll closes. It uses SameSite=Lax and is readable by Foodoobie page JavaScript.

Pick My Craving

Your selected craving, effort level, and content type are sent to Foodoobie’s WordPress REST endpoint. The server uses those choices to select from published Foodoobie content and returns recommendations. The current implementation does not create a feature-specific cookie or persistent request record for Pick My Craving.

Foodoobie It

When you request a recipe remix, your selected remix mode and recipe identifier go to Foodoobie’s server. The server reads the canonical recipe JSON and sends the mode, recipe data, recipe identifier, recipe hash, and routing metadata to Pickaxe at api.pickaxe.co for processing. The Pickaxe credential remains on the server. For anonymous visitors, Foodoobie hashes the request IP with a WordPress salt and uses a WordPress transient counter to enforce a daily limit; that counter expires after one day. Foodoobie It returns the remix to the browser and does not add it to a dedicated local database table.

Recipe Grabber

Recipe Grabber accepts pasted text, a recipe URL, or an uploaded image through same-origin WordPress REST requests. For a URL, Foodoobie’s server fetches the submitted page. If complete Recipe JSON-LD is available, the recipe can be processed locally without Pickaxe. Otherwise, readable recipe text and source details are sent to Pickaxe. For an image, Foodoobie temporarily saves a randomly named copy, gives Pickaxe its temporary URL, deletes it after the request, and removes orphaned temporary images older than one hour.

Recipe extraction results are cached in WordPress for 30 days. Expired cache rows are physically deleted by a daily cleanup task. Usage records store a salted identifier hash, a WordPress user ID when logged in, source type, processing flags, and time, and are deleted after 90 days. Anonymous Recipe Grabber visitors receive a first-party foodoobie_rg_bid browser identifier cookie for one year. Logged-in users can save a recipe as a private WordPress recipe associated with their user account; saved data includes the canonical recipe JSON and related recipe metadata.

Third parties

• Pickaxe: receives recipe extraction or remix inputs only when those features need its processing.
• AltText.ai: Foodoobie loads the InstantAlt browser script from ujs.alttext.ai. On pages with images missing persistent alt text, the script can send the Foodoobie hostname and qualifying image URLs to AltText.ai to generate and serve alt text.
• Hosting and delivery providers: process normal web requests to serve and protect Foodoobie.
• Submitted recipe sites: receive a server request when Recipe Grabber is asked to fetch their URL.

Your choices

You can clear or block cookies in your browser. Doing so can reset the site’s browser-side memory of poll votes and Recipe Grabber usage identity, although server-side fingerprint or usage records may still prevent duplicate or excess requests during their retention periods. To ask about Foodoobie data, use the Contact page.

Changes

If Foodoobie’s features or data behavior change, this page should be updated to match the implementation.