Privacy Policy

1. Who we are

Project Food is the data controller for the data described here. It is run from the Netherlands. For anything privacy related, write to info@projectfood.dev.

2. Made for adults, with room for everyone at the table

Only adults create an account and sign in. If you add children, they never sign in, never get email or notifications from us and cannot be contacted through the app.

• •You can use the app on your own. If others eat with you, you add each of them as a profile: a first name or nickname, and whether they are a child or an adult. That is all we ask. No birth dates, surnames or photos.
• •You decide what is entered, can rename or remove a profile at any time, and remove everything by deleting the account.
• •Children's profiles are never used for advertising or profiling and are never shared with other households.

3. What we store

When you use the app we store:

• •Account: your email address, and your name and profile picture if you sign in with Google or Apple. Sign-in codes go to your email.
• •Household: its name, dinner time, time zone and language.
• •People at your table: first name or nickname, child or adult, a colour, and an avatar chosen from our set.
• •Tastes: which plants each person tasted on which day, and what that unlocks (cards, achievements, the streak).
• •Notifications: whether you allowed push notifications, your preferences, a device push token, and per message whether it was delivered, opened and followed by a log within three hours. We use this to stop nudging a household that ignores us.
• •Product events: a small set of in-app events such as a plant logged, onboarding completed or a survey submitted, tied to your account. No advertising identifiers, no tracking across apps.
• •Optional: survey answers and plant suggestions, if you submit them.
• •Technical logs kept by our hosting providers (IP address, device type, timestamps) to keep the service secure.

4. What we never do

• •No advertising in the app and no ad networks.
• •No selling, renting or trading of personal data.
• •No profiling of children and no sharing of household data with other households.
• •No third-party analytics or tracking SDKs inside the app.

5. Why we may process it

Under the GDPR we rely on:

• •Contract (Art. 6(1)(b)): to provide the app you signed up for, including the profiles you create.
• •Consent (Art. 6(1)(a)): for push notifications and the optional survey. You can withdraw it at any time in the app or in your phone settings.
• •Legitimate interest (Art. 6(1)(f)): to keep the service secure and to see, through the few product events above, whether the app works.

Children's profiles, if any, are processed on the adult's instruction, as part of the adult's account. Project Food does not collect data from children itself.

6. Notifications

The app asks for push permission while you set up, right where you choose the dinner time, and you can say no. If you skip it, we ask once more after your first log, and after that only when you turn it on in Account → Notifications.

• •Essential: the daily question and the streak keeper. On by default once you allow notifications.
• •Tips & news: card and achievement teasers and the Sunday nudge. Off by default.
• •Turn each kind off in Account → Notifications, or all of them in your phone settings. If three messages in a row are ignored, we stay quiet for a week.

Messages travel through Expo's push service and Apple's or Google's notification services, which receive the device token and the message text.

7. Who helps us run the service

We use these processors, each under a data processing agreement or standard contractual clauses:

• •Supabase: database, sign-in and server functions, hosted in the EU (Ireland).
• •Vercel: hosting of projectfood.dev (USA).
• •Expo (EAS): app builds, updates and the push notification relay (USA).
• •Google: Google sign-in, Android push delivery (Firebase Cloud Messaging) and the mailbox behind info@projectfood.dev (Google Workspace).
• •Apple: Sign in with Apple and iOS push delivery.
• •Resend: sign-in codes and contact-form email (USA).

8. Retention and deletion

We keep your data for as long as your account exists. You delete it yourself:

• •In the app: Account → Delete account.
• •On the web: the delete-account page linked below, with a code sent to your email.

Deleting removes your account, the household you created with its member profiles, cards and achievements, notification history and push tokens, immediately. The tastes themselves stay as anonymous statistics: which plant on which day, under random ids that no longer link to any person or household. Database backups expire within 30 days. If you joined a household created by someone else, that household and its tastes stay with them; only your account and sign-in go.

Delete your account on the web

9. Your rights

Under the GDPR you can:

• •Access: ask for a copy of the data we hold about you (Art. 15).
• •Rectification: correct inaccurate or incomplete data (Art. 16).
• •Erasure: delete your account and everything in it (Art. 17).
• •Portability: receive your data in a structured, machine-readable format (Art. 20).
• •Restriction and objection: limit or object to how we process your data (Art. 18, 21).
• •Withdraw consent: for notifications and the survey, at any time.

Write to info@projectfood.dev. If you think we have handled your data wrongly, you can complain to the Dutch Data Protection Authority (Autoriteit Persoonsgegevens, autoriteitpersoonsgegevens.nl).

10. Cookies

The app uses no cookies. The website uses one functional cookie, pf_locale, which remembers your language for a year and needs no consent. The website uses Vercel's privacy-friendly analytics, which set no cookies and do not identify you.

11. Security

Data travels encrypted (TLS) and is stored with row-level security, so each household can only reach its own data. Access to the database is limited to the founder. No system is perfectly secure; if a breach ever affects your data we will tell you and the authority as the law requires.

12. Changes

When this policy changes we update the date at the top. For significant changes we tell you in the app or by email before they take effect.