sage
Sage / Legal

Privacy policy

How Sage handles personal information.

Effective September 30, 2026 · Last updated September 30, 2026

1. Who we are

Sage helps you import and organize recipes, plan meals, and prepare to cook. This Privacy Policy explains how we handle personal information when you use the Sage app, cook-sage.app, or contact us.

Sage is operated by Andrew Wilkerson. You can reach us at cooksagesupport@gmail.com or 1903 Cyndi Ct., Rolling Meadows, IL 60008, United States.

2. Information we collect

Account information. When you sign in with Google or Apple, we receive your email address, user identifiers, and authentication-provider metadata, which may include your name. Apple may provide a private-relay email address. We store your user ID and email to manage your account; authentication services may also retain sign-in metadata. Names, when available, may be included in analytics and error reports as described below.

Preferences and household information. You may provide household size, including adult and child counts; dietary restrictions and preferences; preferred proteins; disliked ingredients; staples; cooking preferences; and meal-planning settings. We also store onboarding status, cooking-tip history, and account timestamps. Household counts do not require children to create accounts.

Recipes and meal plans. We process and store content you submit or save, including recipe titles, ingredients, instructions, photos, import URLs and source information, meal plans, ratings, notes, nutrition estimates, health scores, and cooking-time information. Image records may include storage paths, dimensions, format, file size, and text extracted from handwritten recipes.

Usage and diagnostic information. We collect information about sign-in and recipe actions, such as creation, import, deletion, and rating. Analytics may include user ID, email, name when available, sign-in provider, account-creation timestamp, recipe ID and title, source type, whether an image is present, and ratings. Our custom analytics events do not intentionally include full recipe ingredients or instructions, dietary preferences, or meal-plan contents.

Error reports may include exceptions, crash details, user ID, email, name when available, device and app information, navigation and action breadcrumbs, and screenshots captured with error reports. Screenshots and error context may contain information visible in the app. PostHog session replay is disabled; Sentry error screenshots are a separate diagnostic feature.

Communications and website visits. If you contact us, we receive the information you choose to include. Website hosting and external font services may receive technical information such as your IP address, browser information, and request details.

3. How we use information

We use information to:

We do not sell or rent your personal information or share it for third-party advertising or marketing.

4. Recipe parsing and AI

We use the OpenAI API to process recipe imports. We send the recipe text, import URL, or image content needed for the request. Recipe-parsing requests do not intentionally include your account identifiers, email address, sign-in credentials, dietary preferences, or existing recipe library.

Recipe content can itself contain personal information—for example, a name on a handwritten recipe or details visible in a photo. Please remove unrelated personal information before submitting content.

OpenAI states that API inputs and outputs are not used to train its models by default unless the API customer opts in. Its default abuse-monitoring logs may retain content for up to 30 days, with legal and safety exceptions. Additional storage depends on the API features and settings used. See OpenAI’s API data controls for details. Account deletion in Sage does not necessarily immediately remove content retained by a processing provider.

AI-extracted information can contain mistakes. Review recipes and cooking guidance before using them.

5. Service providers and other disclosures

We disclose information to service providers as needed to operate Sage:

These services may process information under their service agreements and privacy policies. We may also disclose information when required by law or reasonably necessary to protect rights, safety, or security.

Sage currently has no payment or subscription processing integration. We will update relevant disclosures before introducing payment processing.

6. Cookies and similar technologies

Sign-in and app functionality may use cookies, local storage, secure device storage, or similar technologies to maintain sessions and remember settings. Analytics and diagnostic tools may also store identifiers or technical data.

The current marketing website does not include app analytics, advertising scripts, or session replay. Its hosting and font providers may still process technical connection information. Sage is not described as cookie-free, and the app’s product analytics are separate from the marketing website.

7. Retention, deletion, and security

We retain account information, preferences, saved recipes, images, and meal plans while needed to provide the service, unless you delete content or request account closure. Support messages and operational records may be retained as needed to address your request, maintain security, resolve disputes, or meet legal obligations.

You can request account deletion in the app’s account settings or by emailing cooksagesupport@gmail.com. Deletion covers account information and associated saved content. Removal from storage and third-party systems may take additional time, including when an operation needs to be retried. We do not promise that all copies disappear immediately when an account is closed.

Analytics events, error reports, authentication logs, and processing-provider records may follow separate provider retention and deletion processes. A provider’s reporting or query window does not necessarily establish when every stored copy is deleted. Limited information may remain where needed for legal obligations or security purposes; any backup copies, where present, follow their applicable retention processes.

We use technical and organizational safeguards designed to protect personal information. No system or transmission method can guarantee absolute security.

8. Your choices and privacy requests

You can update supported preferences and manage saved content in the app. You may also contact cooksagesupport@gmail.com to request access, correction, deletion, or a copy of your personal information. Depending on applicable law, you may have additional rights to object to or restrict processing or appeal a decision about a request.

We will acknowledge privacy requests within 48 hours. Acknowledgment is separate from completion; we will respond within applicable legal deadlines and explain any legally permitted extension. We may ask for information reasonably necessary to verify your identity. Please do not send passwords or sign-in credentials.

9. Children and international processing

Sage is intended for adults aged 18 and older in the United States. It helps adults prepare meals for themselves and their families and is not directed to children. If we learn that we have collected personal information from a child under 13, we will take steps to delete it. Parents or guardians can contact cooksagesupport@gmail.com with concerns.

Our service providers may process information in the United States and other countries where they operate. Privacy laws in those countries may differ from those where you live. Applicable privacy rights are not limited by our intended launch audience.

10. Changes and contact

We may update this policy as Sage evolves. We will update the date shown on this page and provide additional notice of material changes where required by law.

For questions or privacy requests, contact:

Andrew Wilkerson — Sage
cooksagesupport@gmail.com
1903 Cyndi Ct.
Rolling Meadows, IL 60008
United States.