Privacy Policy

Last updated: October 12, 2026

This policy describes what Cookmarks, LLC (“Cookmarks”, “we”) collects, why, and the choices you have. The short version: we collect what’s needed to run a recipe service, we don’t sell your data, and your recipes are yours — you can download a full export at any time, free on every plan.

What we collect

• Account data — email address, display name, and profile details you choose to add. Authentication is handled by Supabase.
• Your content — recipes you import or write, cookbooks, meal plans, grocery lists, ratings, and cooking history.
• Billing data — handled by Stripe. We store your subscription status and plan; Stripe holds your payment details. We never see your card number.
• Usage analytics — product events (e.g. sign-ups, imports, feature usage) via PostHog, tied to your account so we can understand and improve the product. We don’t sell this data or use third-party advertising trackers.
• Diagnostics & support — errors and performance diagnostics (including session replay on errors on the website) via Sentry, and website support chat via Crisp when you’re signed in.

Mobile app analytics and diagnostics

The mobile app sends selected product actions to PostHog and crash, error, and performance diagnostics to Sentry. Reports include app version, device model, operating system, and session identifiers. When signed in, reports use your account ID, without your email address or name. Signing out resets the analytics identity. These reports help us understand usage and fix failures across Cookmarks on mobile and web.

Mobile telemetry excludes recipe content, notes, passwords, authentication tokens, and shared links. Mobile session replay, screenshots, automatic screen recording, and advertising identifiers are disabled. We do not use this data for targeted advertising or tracking across other companies’ apps or websites. Providers receive your IP address when receiving reports, even though mobile location enrichment is disabled. Crash reports may be stored on your device and sent when you next open the app.

Who can see what

Your library, notes, and edits are private. Public recipe pages are our index of recipes that already exist on the open web. Whether a recipe is public depends on where it came from, never on the fact that you saved it.

• Recipes imported from a URL — the recipe page is public, because the source already is. The page never shows who saved it.
• Recipes you write, paste, or photograph — private by default. Only you can see them unless you choose to make one public or share it with a link.
• Your changes — titles, ingredients, steps, photos, and notes you edit on any recipe are yours alone and are never shown on the public page. The one exception is a cooking note you explicitly choose to share when logging a cook: with a public profile, that note can appear in your profile activity.
• Your profile — a public profile shows your display name, a short feed of recent saves and cooks, and any cookbooks you marked public. It never shows your full library, notes, or edits. Set your profile to private in Settings to hide the feed too.

How imports work

When you import a recipe from a URL, photo, or pasted text, the content is processed by AI services (currently OpenAI) to extract the structured recipe. Some blocked pages are fetched through Jina’s reader service, and assistant web searches go through Tavily. The content sent is the page, image, or query you asked us to process — these providers act on your request and don’t use it to train their models under our API terms.

Public comments and explicitly shared cooking notes or photos are sent to OpenAI for automated safety checks. Private notes are not sent for community moderation. Flagged content and abuse reports may be reviewed by Cookmarks; reporter identities are not disclosed to the reported account.

Connected AI assistants

If you connect an AI assistant such as Claude or ChatGPT to Cookmarks, it can read your library, meal plan and grocery list (and recipes that are already public), add meals and grocery items, and import recipes — only after you sign in and approve the connection. What the assistant reads is sent to that assistant’s provider and handled under their terms. We record which apps you’ve connected and when they were last used. You can disconnect any app at any time in Settings › Connected apps, and access stops immediately. See Use Cookmarks with Claude and ChatGPT.

Where data lives

Data is stored with Supabase (database and file storage) and served via Vercel. Emails (like the welcome email) are sent through Resend.

Your choices

• Download a full export of your recipes, edits, notes, cookbooks, cooking history, meal plan, and grocery list at any time from Settings → Account. Free on every plan.
• Delete your account at any time from Settings → Account. We remove your account, library, edits, notes, cookbooks, cooking history, uploaded photos, and any subscription from the live database. Recipes you wrote or photographed are deleted for everyone, including anyone who saved them; recipes imported from the web stay in the public index with nothing linking them to you.
• Ask questions or request a copy of your data: support@cookmarks.app.

Changes

If this policy changes materially, we’ll note it here and, for significant changes, notify you by email. See also our Terms of Service.