ChefSpark — Privacy Policy

Last updated: 8 November 2026

1. Who we are

ChefSpark is a mobile app that creates recipes with artificial intelligence (AI). This policy explains what personal data ChefSpark collects, why, who receives it, how long it is kept, and what rights you have.

The data controller is Piotr Michalski, Wrocław, Poland (“we”, “us”). Contact: support@chefspark.app.

This policy covers the ChefSpark app on iOS and Android and the website chefspark.app. We do not sell your personal data and we do not show ads.

2. Information we collect

You can use ChefSpark without signing in. If you sign in with Google (and later Apple), your saved recipes stay with your account across devices.

Data Examples Where it comes from
Random app identifier A random ID created on first launch, so the app works without an account Created automatically (Firebase Authentication)
Account details (only if you sign in) Email address, Google or Apple account ID, and the name your Google or Apple account shares. Apple users can share a private relay email instead of their real address Your Google or Apple account
Cooking preferences Dietary preferences, servings, cooking skill, cooking style, your goal for using the app Your answers in onboarding and Settings
Recipe requests The dish or ingredients you type, filters you choose What you enter on the Home screen
Saved recipes Recipes and their photos that you save to My Recipes Created when you save a recipe
Subscription status Your plan (Home Cook, Sous Chef, Head Chef), purchase and renewal dates Apple App Store or Google Play, via RevenueCat
Usage counters How many recipes you generated this month Created by our servers when you generate a recipe
Technical data IP address, device model, operating system and app version, device identifiers used by RevenueCat (such as Apple’s IDFV or the Android ID), request timings and errors Created automatically when the app connects to our servers or to RevenueCat
Crash reports Device model, operating system and app version, a random installation identifier, and technical details of the crash Sent automatically by the app when it crashes (Firebase Crashlytics)

Preferences are stored only on your device. Saved recipes (including their photos), usage counters, and whether you have used your free first photo are stored in our database (Google Cloud Firestore). Recipes you don’t save are not stored by us.

We do not collect your location, contacts, photos from your device, advertising ID or payment card details. We do not use analytics or advertising tools. We use Firebase Crashlytics only to receive crash reports so we can fix bugs. Payments are handled entirely by Apple or Google.

Sensitive dietary choices. Some dietary options can reveal information about your health (for example gluten-free, dairy-free or FODMAP-friendly) or your religious beliefs (for example halal). We use these only with your explicit consent, which the app asks for before you select them (see section 3). Lifestyle choices such as vegetarian or vegan don’t need this consent.

Please keep personal details out of recipe requests. Don’t type health conditions or other personal information about yourself or others (for example “dinner for my diabetic dad”). Describe the dish or ingredients instead. Requests are sent to our AI provider to create the recipe.

What you must provide. A recipe request is needed to create a recipe. Signing in, cooking preferences and dietary choices are optional. Without them, recipes are less personalised.

3. How we use your information

Purpose Data used Legal basis (EU GDPR)
Create recipes and recipe photos Recipe requests, cooking preferences Performing our contract with you, Art. 6(1)(b)
Use sensitive dietary choices to create recipes, including sending them to our AI provider in the USA Dietary choices that may reveal health or religious information Your explicit consent, Art. 9(2)(a)
Save and sync your recipes Saved recipes, app identifier, account details Contract, Art. 6(1)(b)
Apply your plan and its limits Subscription status, usage counters Contract, Art. 6(1)(b)
Sign-in and account security Account details, app identifier Contract, Art. 6(1)(b)
Fix bugs, prevent abuse, keep the service running Technical data, crash reports Our legitimate interest in a working, secure app, Art. 6(1)(f)
Answer your support messages Your email address and message Our legitimate interest in responding to you, Art. 6(1)(f)
Keep accounting and tax records Payout reports from Apple and Google Legal obligation, Art. 6(1)(c)
Respond to lawful requests from authorities The data the request covers Legal obligation, Art. 6(1)(c)
Establish or defend legal claims Data relevant to the claim Our legitimate interest, Art. 6(1)(f)

Consent for sensitive dietary choices. Before you select an option that may reveal health or religious information, the app shows a short statement and asks you to agree. We keep a record of that consent. You can withdraw it at any time by removing those options in Settings. Withdrawal doesn’t affect processing that happened before.

We do not use your data for advertising, and we do not use it to train AI models.

4. AI processing

Recipe text is written by an AI model from OpenAI. Recipe photos are created by an AI model from Google (Gemini API).

Neither provider receives your name, email address or account ID. According to their current business terms, OpenAI and Google do not use this data to train their models, and may keep it for a limited period (currently up to 30 days) to detect abuse.

We do not make decisions about you based solely on automated processing that have legal or similarly significant effects on you.

AI-generated recipes and photos can contain mistakes. See our Terms of Service.

5. Who we share data with

Service providers (processors). They process data only on our instructions, under a data processing agreement, and only for the purpose listed.

Provider What they do for ChefSpark Data they receive
Google Firebase / Google Cloud (Google LLC) App identifier, sign-in, database, servers, crash reporting (Crashlytics), website hosting App identifier, account details, saved recipes, technical data, crash reports
OpenAI OpCo, LLC Writes recipe text Recipe request and cooking preferences (section 4)
Google Gemini API (Google LLC) Creates recipe photos Dish name and visual description (section 4)
RevenueCat, Inc. Manages subscriptions App identifier, subscription status, technical data
Cloudflare, Inc. Routes emails sent to support@chefspark.app Your email address and message
Google (Gmail) Receives and stores support emails Your email address and message

Independent controllers. When Apple and Google distribute the app, process payments, or handle Apple or Google sign-in, they decide how they use your data themselves. Their own privacy policies apply: Apple Privacy Policy and Google Privacy Policy.

We may also disclose data when the law requires it, or to establish or defend legal claims. We never sell or rent personal data.

6. Storage on your device

The app stores some data on your device: sign-in tokens, the random app identifier, your preferences, and settings such as whether you have seen the app tour. This is strictly necessary to provide the app, so it doesn’t require your consent. We don’t use cookies or similar technologies for analytics or advertising, in the app or on chefspark.app.

7. How long we keep data

Data How long
Saved recipes and their photos Until you delete them or your account
Recipe requests and recipes you don’t save Not stored by us. Held only while the recipe is being created (seconds). AI providers: see section 4
Preferences and usage counters Preferences: on your device, until you delete your account or the app. Usage counters: in our database, until you delete your account
Account details and app identifier Until you delete your account. If you haven’t signed in and don’t use the app for 12 months, your app identifier and saved recipes are deleted
Subscription data at RevenueCat Until you delete your account
Technical logs 30 days
Crash reports 90 days
Support emails 6 months after the conversation ends
Accounting records Apple and Google are the sellers, so we receive only their payout reports, not your individual payment details. We keep these for 5 years from the end of the year in which the tax payment deadline fell, as Polish tax law requires

We don’t keep backups of our database, so deleted data is not kept in any backup.

8. Deleting your data

You can delete your data in three ways:

  1. In the app: Settings → Delete Account. This works whether or not you are signed in. It permanently deletes your saved recipes and account from our servers, deletes your customer record at RevenueCat, and clears your preferences from your device. If you signed in with Apple, we also revoke ChefSpark’s access to your Apple account.
  2. On the web, without reinstalling the app: chefspark.app/delete-account.
  3. By email to support@chefspark.app. If you never signed in, we may ask for some details to find your data.

We complete deletion requests without undue delay, and in any case within one month.

Deleting your account does not cancel a subscription. Cancel it in your App Store or Google Play account settings.

9. Your rights

To use any of these rights, email support@chefspark.app. We reply without undue delay and in any case within one month. For complex requests we can extend this by up to two more months, and we will tell you if we do.

EU and EEA users. You have the right to access your data, correct it, delete it, receive a copy in a portable format, restrict how we use it, and withdraw consent at any time.

Your right to object. You can object at any time to our use of your data based on legitimate interest: technical logs, crash reports, abuse prevention and support correspondence. We will then stop, unless we have compelling legitimate grounds or need the data for legal claims.

Complaints. You can complain to the data protection authority in the country where you live or work. In Poland this is the President of the Personal Data Protection Office (UODO, uodo.gov.pl).

US users. We do not sell personal data or use it for targeted advertising. You can ask us what data we hold about you, and ask us to correct or delete it. We reply within 45 days.

10. Children

ChefSpark is not intended for anyone under 16. We do not knowingly collect data from children under 16. If you believe a child has given us data, email us and we will delete it.

11. Security

Data is encrypted in transit (HTTPS) and at rest. Access to the database is protected by authentication and security rules, so each user can reach only their own saved recipes. No system is perfectly secure, but we take reasonable steps to protect your data.

12. International transfers

Our database is stored in the United States (Google Cloud multi-region nam5), and our AI and subscription providers are also based in the United States. If you are in the EU or EEA, your data is therefore transferred to the United States. We protect these transfers as follows:

Provider Transfer safeguard
Google (Firebase, Google Cloud, Gemini API) EU–US Data Privacy Framework, with Standard Contractual Clauses
Cloudflare EU–US Data Privacy Framework, with Standard Contractual Clauses
OpenAI Standard Contractual Clauses in OpenAI’s Data Processing Addendum
RevenueCat Standard Contractual Clauses in RevenueCat’s Data Processing Addendum

You can request a copy of these safeguards by emailing support@chefspark.app.

13. Changes to this policy

We may update this policy. We will change the “Last updated” date at the top and tell you in the app if the changes are significant. If a change affects processing based on your consent, we will ask for your consent again.

14. Contact

Questions or requests: support@chefspark.app