Cookie Notice
Version 2026-08-11 · Effective 2026-08-11
1. Current approach
Reciphy currently uses first-party cookies that are necessary to sign users in securely, prevent request forgery, preserve a requested recipe journey and remember language choice. The application does not currently load advertising pixels or third-party analytics scripts in its shared pages.
2. Cookie inventory
| Cookie | Purpose | Typical duration | Access |
|---|---|---|---|
| reciphy_token | Authenticated session and account security | Session lifetime | Secure, HttpOnly, SameSite=Lax |
| reciphy_oauth_state | Protects the Google sign-in callback against request forgery | 10 minutes | Secure, HttpOnly, SameSite=Lax |
| reciphy_recipe_intent | Returns the user to the recipe journey requested before sign-in | Short-lived | Secure, HttpOnly, SameSite=Lax |
| reciphy_lang | Remembers the selected display language | Up to one year | Secure, SameSite=Lax |
3. External services
Google and Stripe may use their own storage when you leave Reciphy for sign-in or hosted checkout. Their notices and controls apply on those external pages. Cloudflare may process network and security information at the edge without relying on an advertising cookie in Reciphy’s application pages.
4. Your controls
You can delete or block cookies through your browser. Blocking strictly necessary authentication or security cookies may prevent sign-in, checkout or other requested functions from working. Because Reciphy does not currently set optional analytics or advertising cookies, there is no optional-cookie banner. If optional tracking is introduced, it must remain disabled until the required preference controls are available.
5. Updates and contact
This inventory must be reviewed whenever authentication, payment, analytics, advertising or infrastructure providers change. Operator contact details will be published before the legal documents are treated as final production notices.