Cookies & Device Storage

Necessary cookies and similar storage support authentication, security, return context, requested product state, and privacy-choice handling. Clerk and RecipeFork may set or read this storage. Blocking it can prevent features from working.

The current consent receipt is named culinary_platform_consent. It is a browser-readable receipt stored for up to one year and records analytics, marketing, and personalization fields, a version, and an update time.

The only optional category supported by the current preference interface is product analytics. Product analytics is disabled in this release, and the interface does not present marketing or personalization as selectable optional features. Saved choices are preserved for future review; they do not turn on optional analytics while the feature is disabled.

Optional product analytics is unavailable in this release. Before any future optional analytics collection, RecipeFork will update this notice and explain the available choice. A saved choice does not enable optional marketing or personalization storage.

Service, security, fraud-prevention, and basic product-operation records are handled even while optional analytics is off. Optional analytics remains off in this release regardless of a saved choice or browser privacy signal and is not required to use RecipeFork.

If PostHog cookies or local storage remain from a previous opt-in, disabling optional collection does not automatically clear that browser storage. You can clear it with your browser's site-data controls.

Open Privacy choices to see the current availability. To ask about saved preferences, contact support@cayv.com. Clearing site data through your browser can sign you out or reset saved state.

RecipeFork does not currently change its data handling automatically in response to “Do Not Track” or Global Privacy Control signals. Use Privacy choices or contact support@cayv.com about your preferences.

For broader information about data handling, read the Privacy Notice.