How we handle your Chive data

First-party measurement

We store basic first-party page visit records to understand aggregate campaign performance. We also count recipe searches, recipe-result clicks, and clicks to the original publisher. Before you consent, those event records contain only coarse funnel facts, a random in-page search-session ID, recipe identifiers, result counts or positions, timestamps, and landing attribution. They do not contain your search text or parsed nutrition preferences.

Recipe searches

Your latest recipe search and results stay in your browser session so they can be restored when you return from a recipe. We send each submitted query to our search service as a new search. If you allow analytics, we also store the search text and structured criteria with the first-party event so we can learn which kinds of recipes people need and improve relevance.

Accounts and profiles

You can search without an account. If you sign in, we store your name, verified email address, saved recipes, cooking history, grocery lists, and profile settings so those features work across visits. Google sign-in and passwordless email links are handled by our authentication and email providers.

Grocery lists and offline access

Grocery lists store the recipes you add, their ingredient quantities, checklist state, and any manual items you type. When you open a grocery list, the installed web app may keep the most recently opened list in private browser storage for read-only offline access. Signing out or deleting your account asks the browser to clear that offline copy; the browser may also evict it automatically.

Chive Chrome extension

The Chrome extension does not monitor your browsing or read your browser history in the background. When you click its toolbar icon, it sends only the address of the page you selected to Chive so we can find an existing recipe or import that page. Imported page addresses and the resulting recipe data are stored as part of the Chive recipe catalog.

Connecting an account is optional. The extension stores a revocable Chive access token in Chrome's extension storage; Chive stores only a one-way hash of that token. A connection can save recipes and update your grocery list, expires after 90 days, and can be revoked from Preferences or disconnected inside the extension. The extension does not include advertising or third-party analytics code.

Recipe links sent by text

If you text a recipe link to a Chive number, our messaging provider sends us your phone number, the link, and delivery metadata so we can find or import the recipe and reply with its Chive page. We encrypt the phone number, use a keyed one-way hash for lookup and rate limiting, and store only the link rather than unrelated mobile share text. We do not use a recipe-link text as permission to send recurring or marketing messages.

An imported social recipe may be available through an unlisted, hard-to-guess result link without being added to public search. In the future, you may choose to connect your phone number to a Chive account. Reply STOP to block further replies and HELP for help. Message and data rates may apply.

Your food and cooking profile

If you choose to build a profile, an AI service turns the description you write into a structured draft. Nothing affects search until you review and confirm it. We encrypt your original description and use the confirmed profile for recipe personalization. Chive does not use this profile to provide medical advice.

Personalized activity

When personalization is on, we use limited signals such as structured search criteria, recipe views, publisher visits, saves, feedback, and recipes you mark as made. These signals help rank recipes but never replace the request you just made. This personalization record does not store a second copy of your raw search message.

Optional analytics and advertising

If you opt in, we use Google Analytics for site analytics and Google Ads for search, recipe-click, and outbound-click conversion measurement. Advertising consent is also required before we store raw Google click identifiers such as gclid, gbraid, or wbraid.

Your choices

You can update cookie preferences from the footer at any time. Signed-in users can turn personalization off, clear learned activity while retaining saved recipes and grocery lists, or permanently delete their account, profile, and grocery-list history from Preferences. Search-session IDs are random and are not placed in a persistent cookie. We do not sell recipe-search data.