Legal

Cookie Policy

Draft — for counsel review. Last updated 8 September 2026. This is not legal advice.

Draft. This site (recipeyield.io) is a static publisher-facing brochure. The cookies that matter for the product live on the food blog, not here.

recipeyield.io

We do not set an analytics or advertising cookie on this marketing site in the current build. CloudFront may process the request (IP, user agent) to deliver the page. If we later add a strictly necessary cookie (for example a load-balancer session), we will name it here.

Publisher domains

• sponsor_ent — first-party, HTTP cookie set by the blog’s WordPress claim endpoint after checkout or OTP restore. Holds an ES256 JWT. Purpose: remember which recipe URLs this browser has paid to view without ads. Lifetime: the sponsorship duration (day / month / year).
• sponsor_ent_1, sponsor_ent_2, … — continuation cookies if the token list would overflow a single cookie (~3KB). Same purpose and lifetime. The plugin unions them; it does not drop recipes to save space.

These are not third-party RecipeYield cookies. They are first-party on the blog host that matches the site’s home_url (www and apex are different hosts).

Stripe

Stripe.js and Checkout may set cookies on Stripe’s domain when a card is used. See Stripe’s cookie documentation. We do not control those.

How to clear

Use the “turn the ad-free setting off” link in the OTP/receipt email, or clear cookies for the blog in your browser. That shows ads again on that device even if the server-side entitlement still exists.