Legal

Privacy Policy

Last updated 4 August 2026 · Effective 4 August 2026

This policy explains what PicyFood collects when you use the app, why we collect it, who we share it with, and what you can ask us to do with it.

Who we are

PicyFood ("we", "us") provides a mobile application for finding recipes, generating recipes with AI, planning meals and building shopping lists.

The data controller is PicyFood. For any privacy question, contact support@picyfood.com.

Data we collect

Information you give us

DataWhen
Email address, first name, last nameWhen you create an account
PasswordStored only as a salted cryptographic hash — we never see or store the password itself
Google account email and nameIf you choose Sign in with Google. We receive only your email, given name and family name, and only after Google confirms your email is verified
Recipe prompts, available ingredients, dietary preferencesWhen you use AI Kitchen
Photographs of foodIf you use image nutrition analysis
Favourites, calendar entries, shopping listsAs you use the app

Information collected automatically

  • Server logs — IP address, request path, timestamp, response status and user-agent string, recorded for every request.
  • Error reports — if the app hits an error, we log the error message, a stack trace, the screen it happened on, your user-agent, and, if you are signed in, your email address, so we can reproduce and fix it.
  • Subscription status — whether your account is premium, the plan, its status and renewal date.

Payment information

Payments are processed by Stripe. Card numbers, CVCs and billing details are entered into and held by Stripe — they never reach our servers and we cannot see them. We store only the identifiers Stripe gives us (customer ID, subscription ID) and your subscription status.

How we use it

  • Create and secure your account, and sign you in
  • Save your favourites, meal plans and shopping lists across devices
  • Generate recipes and nutrition information you ask for
  • Take payment and manage your subscription
  • Diagnose faults, monitor performance and keep the service reliable
  • Detect and prevent abuse, fraud and automated attacks
  • Reply to you when you contact support

We do not sell your personal data, and we do not share it with advertisers.

Who we share it with

We use a small number of processors, each receiving only what it needs to do its job:

ProviderPurposeWhat it receives
StripePayments and subscriptionsYour email and payment details you enter directly
OpenAIAI recipe generation and image analysisThe prompt text and any photo you submit — see below
GoogleSign in with GoogleOnly verifies the token you present; we receive your email and name
Google FirebaseCrash reporting and product analyticsDevice model, OS version, app version, a random install identifier, crash diagnostics and in-app event names — see section 06

We may also disclose data where we are legally required to, or to establish or defend legal claims.

AI features

When you use AI Kitchen, the text you enter — the ingredients you list, your dietary preferences and any instructions — is sent to OpenAI to generate a recipe. When you use image nutrition analysis, the photograph you submit is sent to OpenAI.

Please do not enter personal or sensitive information into AI prompts. Describe your ingredients, not yourself.

We send your prompt and nothing else — not your name, not your email, not your account identifier. Generated results are cached temporarily so that identical requests do not need to be regenerated.

OpenAI processes this data under its API terms. [Confirm the current OpenAI API data-retention and training position and state it here.]

Analytics & crash reporting

The app uses Google Firebase for two things: reporting crashes so we can fix them, and counting how features are used so we know what to improve.

Crash reporting (Firebase Crashlytics)

When the app crashes we receive the error, a stack trace, your device model, OS version and app version. This is diagnostic data — it tells us what broke, not who you are.

Product analytics (Firebase Analytics)

We record that certain actions happened, so we can see where people get stuck. We log the event, never the content:

EventWhat is recorded
App opened, session startedThat it happened, and when
Signed up, signed inWhich method — email or Google. Not your address
Viewed a recipeThe recipe identifier
Generated an AI recipeHow many ingredients and results — not the ingredients themselves
Added to a meal plan or shopping listMeal type and a count
Started or completed a subscriptionPlan name and price

We attach two properties to these events: whether the account is premium, and the subscription status. We do not send your email address, name or account identifier to Firebase, and we do not use analytics for advertising.

Firebase assigns a random installation identifier to your app install. It is not linked to your identity by us. Deleting and reinstalling the app generates a new one.

You can stop Firebase Analytics collection at the device level: iOS — Settings → Privacy & Security → Tracking; Android — Settings → Privacy → Ads, where you can also reset or delete your advertising ID.

How long we keep it

DataRetention
Account and content (favourites, plans, lists)Until you delete your account
Server logs and error reports[e.g. 30 days]
Cached AI results1 hour
Crash reports (Firebase)90 days
Analytics events (Firebase)Up to 14 months, then aggregated
Payment and invoice recordsAs required by tax law, typically [6–7 years]

When you delete your account, your personal data is deleted or irreversibly anonymised within [30 days], except where we must keep records to meet a legal obligation.

Your rights

Depending on where you live, you may have the right to:

  • Access — get a copy of the personal data we hold about you
  • Rectification — have inaccurate data corrected
  • Erasure — have your data deleted
  • Portability — receive your data in a machine-readable format
  • Restriction and objection — limit or object to certain processing
  • Withdraw consent — where processing relies on consent

To exercise any of these, email support@picyfood.com. We respond within one month. You can delete your account at any time from within the app.

If you are in the UK or EU and are unhappy with our response, you can complain to your local data protection authority. In the UK that is the Information Commissioner's Office (ico.org.uk).

California residents: we do not sell or share personal information as those terms are defined by the CPRA, and we will not discriminate against you for exercising your rights.

Deleting your account

You can delete your account and everything in it at any time — from Profile → Personal Information → Delete account in the app, or by emailing picyfood@picyfood.com if you can no longer sign in.

Our account deletion page lists exactly what is removed, what we must keep for tax purposes, and how long it takes.

Deleting your account does not cancel a subscription bought through the App Store or Google Play — cancel that in your store settings first, or you may keep being charged.

Security

  • All traffic is encrypted in transit with TLS
  • Passwords are stored only as salted hashes, never in readable form
  • The database is a managed service with encryption at rest, automated backups and network-level access restricted to our application servers
  • Administrative access requires key-based authentication; password logins are disabled
  • Secrets are held outside the application image and are never committed to source control

No system is perfectly secure. If a breach occurs that is likely to put your rights at risk, we will notify you and the relevant regulator as the law requires.

International transfers

Our servers and database are located in the European Union (Frankfurt). Some processors — notably OpenAI and Stripe — may process data in the United States. Where data leaves the EEA or UK, transfers are covered by Standard Contractual Clauses or another approved safeguard. [Confirm the mechanism each processor relies on.]

Children

PicyFood is not directed at children under [13/16, depending on your markets] and we do not knowingly collect their personal data. If you believe a child has given us personal data, contact us and we will delete it.

Changes & contact

We may update this policy. When we make a material change we will update the date above and notify you in the app or by email before it takes effect.

Questions, requests or complaints: support@picyfood.com, or [postal address].