BabyFood — Privacy Policy

BabyFood (the "App") is a baby-nutrition tracking and recipe app for parents and caregivers. We — the BabyFood team (the "we", "us") — take your privacy and your baby's safety seriously. This policy explains what data we collect, why, how it's stored, and the rights you have over it.

1. Who we are & how to contact us

Controller: BabyFood (sole developer).
Contact: adminbabyfood@jorasoft.com
For account deletion you do not need to email us — see Section 7.

2. Data we collect

2.1 Account data

• Email address — required for sign-in, password recovery, and verification codes.
• Display name (optional) — shown next to your community comments and shared recipes.
• Sign-in provider identifier — if you sign in with Apple or Google, we receive an opaque user ID. We do not receive your social profile, contacts, or friends.

2.2 Child & family data (you enter)

• Child profile: first name (or nickname), date of birth, sex (optional), weight/height, allergens, preterm status.
• Mother profile: pregnancy week, due date (if you choose to use the pregnancy tracker).
• Daily nutrition entries, food diary photos, growth records, milestones, vaccine schedule, medication reminders, breastfeeding log.

This is sensitive health data. We process it solely to provide the App's functionality on your device and to sync between your devices. We do not sell it, share it with advertisers, or use it to train AI models.

2.3 Scanner data

• Barcodes you scan are sent to Open Food Facts (an open public database) to look up the product.
• Photos of ingredient labels are processed on your device using Apple's Vision framework (OCR). The image itself is not uploaded.
• The recognised ingredient text (without the photo) is stored on our server with the barcode so the next user gets a faster lookup.

2.4 Community data (user-generated content)

• Topic comments and replies you post.
• Recipes you submit, including title, ingredients, steps, photo, allergen tags.
• Reports you file against other users' content.

This data is visible to other BabyFood users by design. See Section 8 for moderation.

2.5 Technical data we do not collect

• We do not use third-party analytics (no Google Analytics, no Firebase Analytics, no Mixpanel).
• We do not use advertising SDKs or tracking pixels.
• We do not use the IDFA / App Tracking Transparency framework — our PrivacyInfo.xcprivacy manifest declares NSPrivacyTracking = false.
• We do not collect your contacts, calendar, photos library (we only access individual photos you pick), or location.

3. Why we collect this data (legal bases under GDPR)

• Performance of contract (Art. 6(1)(b)): account creation, sign-in, syncing your data between devices.
• Legitimate interest (Art. 6(1)(f)): running the community feature, moderating user content, security and abuse prevention.
• Consent (Art. 6(1)(a)): push notifications, camera access, photo library access — you can withdraw at any time in your phone's Settings.
• Health data (Art. 9(2)(a)): we process child health data on the explicit consent you give when creating a child profile.

4. Where your data lives

• Supabase (Postgres database + auth + edge functions) — EU region (Frankfurt). Supabase is GDPR-compliant; their DPA is on file.
• Netlify (sends verification-code emails) — handles only the email address and the 6-digit code. Does not persist your data.
• Open Food Facts (open public database) — receives the barcode string only.
• Apple / Google sign-in providers — only if you choose to use them.
• Your device — most data lives on-device via SwiftData; it syncs up only when you're online and signed in.

5. How long we keep your data

• While your account is active: as long as you keep it.
• After you delete your account (see Section 7): everything is purged within 30 days. Backups are rotated within 30 days.
• Password-recovery codes: deleted automatically 15 minutes after issuance.
• Anonymised barcode→ingredient lookups (no link to you): kept indefinitely as a public crowd-sourced cache.

6. Your rights

Under GDPR (EU/EEA), UK GDPR, KVKK (Türkiye), and CCPA (California), you have the right to:

• Access a copy of your data.
• Correct inaccurate data — most of this you can do yourself in the App.
• Delete your account and all linked data (see Section 7).
• Port your data — request a machine-readable export via email.
• Object to processing or restrict it.
• Lodge a complaint with your local data-protection authority (e.g. Türkiye: KVKK Kurumu, Germany: BfDI, EU: your national DPA).

To exercise these, email adminbabyfood@jorasoft.com. We respond within 30 days.

7. Deleting your account

Apple Guideline 5.1.1(v) — and we agree it's the right thing — requires every account-based app to offer in-app deletion. In BabyFood:

• Open Settings → Profile → Delete Account.
• Confirm twice. The action is irreversible.
• We immediately remove your auth row, all child/mother profiles, all health entries, your community comments and recipes, and all related data from our servers. Backups roll off within 30 days.

8. Community content (UGC)

Comments, replies, and shared recipes you post are user-generated content (UGC). All UGC:

• Passes an automated moderation check (profanity / abuse keywords) before going live.
• Is visible to other signed-in BabyFood users.
• Can be reported with the ⚑ flag — moderators review within 24 hours.
• Can be deleted by the original poster at any time.
• Cannot be used to identify you by us beyond what you choose to display (display name).

When you delete your account, your UGC is removed too. Other users' replies to your content are kept but become anonymous parents of the thread.

9. Children's privacy

BabyFood is intended for parents and caregivers, not for children to use directly. You must be 18+ to create an account. Child profiles describe a child but are managed by the adult account holder. We never market to children, never let children create accounts, and never enable child-to-child communication.

10. Cookies & tracking

The iOS app does not use cookies or tracking pixels. The Supabase backend uses a session cookie purely for authentication (essential cookie, no consent required).

11. International transfers

Our primary servers are in the EU. If you sign in with Apple/Google, those providers may process data in the United States; both have valid GDPR transfer mechanisms (SCCs / EU-U.S. Data Privacy Framework).

12. Security

• All traffic between the App and our servers is encrypted via TLS 1.3.
• Passwords are stored hashed (bcrypt). We never see the cleartext.
• Database access is restricted via Postgres Row-Level Security — you can only ever read/write rows that belong to your own user ID.
• Edge functions that perform admin actions (e.g. account deletion) require a valid signed JWT from Supabase Auth.

13. Changes to this policy

We'll update this page when we change anything material. The "Last updated" date at the top reflects the latest revision. Significant changes are also surfaced in-app the next time you open it.