Privacy Policy

Last updated: [DATE — fill in when you publish this]

This policy explains what personal data CookBlueprint collects, why, who we share it with, and the rights you have over it. We don't sell your data, and we don't run ads or third-party analytics in the app.

CookBlueprint is operated by [YOUR NAME / LEGAL ENTITY NAME] ("we", "us"). If you have questions about this policy or your data, contact us at privacy@cookblueprint.com (placeholder — replace with a real inbox you actually monitor before publishing this policy).

What we collect and why

Account information

When you create a CookBlueprint account, we collect your name, email address, and a password (stored as a salted hash — we never see or store your password in plain text). If you add a profile picture, we store that too. We use this to identify your account, let you sign in, and send you account-related email (verifying your address, resetting your password).

Household content

The recipes, meal plans, and shopping list items you create are stored on our servers and shared with everyone in your household (the people you've invited into your CookBlueprint household). This is the core content of the app — it's not shared outside your household, and we don't use it for advertising.

If you import a recipe from a link, your device fetches that page directly (over your own internet connection) and reads its recipe information locally — the URL isn't sent through our servers or to any AI service for this feature.

If you use CookBlueprint without an account ("local mode"), this content stays only on your device until you create an account and it's copied up to our servers.

Recipe photos

If you take or choose a photo for a recipe, our apps request access to your camera or photo library to do that. This is always your choice — you can add a recipe without a photo. Uploaded photos are stored with an image hosting provider (see "Who we share data with" below).

Session and device information

When you sign in, we store a session record that includes the IP address and browser/device information (user agent) used to create it, for as long as that session is active. This helps us detect suspicious activity and keep accounts secure. On mobile, your session is also stored securely on your device so you stay signed in, and (if you use the home-screen widgets) a copy of it is stored in a space shared between the app and its widget, on your device only, so the widget can fetch your meal plan and shopping list without you having to sign in twice.

Purchases and subscriptions

CookBlueprint Pro purchases are handled entirely by Apple's App Store or Google's Play Store — we never see or store your payment card details. We use RevenueCat to keep track of which subscriptions are active. RevenueCat receives your CookBlueprint account ID and your purchase/subscription history from Apple or Google so we can unlock Pro features for your account.

Correspondence

If you email us for support, we keep that correspondence — including your email address — so we have a history to refer back to if you write again.

Children

CookBlueprint is not directed at children under 13, and we don't knowingly collect personal information from them. If you believe a child has provided us with personal information, contact us and we'll delete it.

Who we share data with

We use a small number of service providers to run CookBlueprint. Each only receives the data it needs to do its job, and none of them are permitted to use your data for their own purposes:

  • Resend — sends account emails (verification, password reset) on our behalf. Receives your email address and the email content.
  • RevenueCat — manages in-app purchases and subscription status. Receives your account ID and purchase/subscription data from Apple/Google.
  • OpenAI — powers the optional "auto-generate my week" meal-planning feature. Receives your household's recipe titles, ingredients, and meal-plan history — not your name, email, or any other account information.
  • DigitalOcean — stores recipe photos you upload.
  • Vercel — hosts our website and API. Like any web host, it processes standard connection data (such as IP address) to serve requests.
  • A database host for the Postgres database that stores everything described above.

We don't use any advertising networks, and we don't run analytics or crash-reporting tools in the app.

We may also disclose information if required to comply with a valid legal process (such as a court order or subpoena), or to protect the rights, property, or safety of CookBlueprint, our users, or others. If CookBlueprint is ever acquired or merged with another company, we'll notify you before your information is transferred or becomes subject to a different privacy policy.

Your rights

Wherever you're located, we aim to give you the same set of rights over your data:

  • Access. You can ask us what personal data we hold about you.
  • Correction. You can update your name, email, and profile picture at any time in the app's account settings.
  • Deletion. You can delete your account at any time from the app (Settings → Preferences → Log out, or the account deletion option in Edit Account) or on the web. This deletes your account, sessions, and login credentials. Recipes, meal plans, and shopping list items belonging to a household aren't deleted automatically if other members remain in it, since that content is shared — contact us if you'd like household content removed as well.
  • Portability. You can ask us for a copy of your data in a portable format.
  • Objection / restriction. You can ask us to stop processing your data in certain circumstances, subject to legal limitations (for example, we need some data to keep providing the service to you).

To exercise any of these rights, email us at privacy@cookblueprint.com. We may need to verify your identity before acting on a request. If you're in the EEA or UK, you also have the right to lodge a complaint with your local data protection authority.

How we secure your data

Data is encrypted in transit (HTTPS/TLS) between your device and our servers. Passwords are stored as salted hashes, never in plain text. Access to production systems is limited to what's needed to operate the service.

Data retention

We keep your account data for as long as your account is active. When you delete your account, your personal account data (profile, sessions, login credentials) is deleted promptly; backups that include it are cleared on our normal backup rotation schedule.

Changes to this policy

We may update this policy from time to time. If we make a significant change, we'll update the date at the top of this page and, where appropriate, notify you in the app.

Contact us

Questions, comments, or concerns about this policy or your data? Email privacy@cookblueprint.com.