Privacy Policy

Controller

The controller is Théo Fundone, sole proprietor, publisher of Melipo. Contact details appear in the legal notice. Privacy contact: privacy@melipo.app.

Data we process

Without an account, recipe, meal-journal, shopping-list and loyalty-card content stays on the device. Melipo does not receive that content unless you choose a cloud feature or share it.

With an account, Melipo may process your internal user ID, email address, display name, language, authentication provider, recipes, ingredients, steps, photos, meal journal, planned meals, favorites, family and close-friend relationships, shopping list, loyalty cards you choose to save in the cloud, notification settings and subscription entitlement.

If you accept usage analytics on iOS, an Apple AdServices attribution token may be sent to RevenueCat to measure whether the installation came from an Apple Ads campaign. This standard attribution does not give Melipo access to your advertising identifier.

Support messages and the technical information you provide are processed when you contact us. Security logs may contain an IP address, date, device or request identifiers. Melipo never receives your Apple or Google password.

Purposes and legal bases

Account creation, authentication, synchronization, sharing, family features, purchases and support necessary to supply Melipo are processed to perform the contract or take steps at your request before entering it (GDPR Article 6(1)(b)).

Billing and records required by tax or accounting law are processed to comply with legal obligations (Article 6(1)(c)).

Service security, abuse and fraud prevention, defence of legal claims and strictly necessary technical logs rely on our legitimate interests in protecting Melipo and its users (Article 6(1)(f)).

Optional product analytics, crash reporting, optional push notifications and optional recap communications rely on consent (Article 6(1)(a)). You may withdraw it at any time without affecting earlier processing.

Recipients and service providers

Data is available only to people you choose to share it with and to providers that need it to operate Melipo: Supabase (accounts, database, photos and synchronization), Apple or Google (social sign-in and stores), RevenueCat (subscription entitlement and consent-based Apple Ads attribution), Expo, Apple and Google (push delivery), Resend (emails), PostHog (consent-based analytics and crash reports), and Cloudflare (website delivery and security).

These providers process only the data needed for their role under their own terms and, where applicable, data-processing agreements. Public recipes are visible to anyone; family and close-friend content is limited according to the sharing settings you select.

International transfers

Some providers may process data outside the European Economic Area. Depending on the destination, transfers rely on an adequacy decision, the European Commission's Standard Contractual Clauses, or another safeguard permitted by the GDPR. You may request information about the relevant safeguard and a copy where available by contacting privacy@melipo.app.

Optional usage analytics

Melipo uses PostHog only after you have explicitly agreed to share usage data. Before you choose, and if you decline, PostHog remains disabled.

These analytics help us understand which features are useful, measure retention during the beta, and improve limits such as the number of recipes included in the Free plan.

Data sent to PostHog

When sharing is enabled, Melipo sends limited product events such as creating or reusing a recipe, recording a meal, creating a family, or reaching a theoretical recipe quota. It also collects app lifecycle events and unhandled technical errors so we can understand reliability during the beta.

Events may include non-content properties such as the meal category, whether a photo exists, the app version, operating system and version, device type and model, locale, and time zone. Error reports may include a technical stack trace, but console logs are not collected.

A persistent pseudonymous identifier is used to understand retention over time. For signed-in users, this identifier is the internal Melipo account ID, never the email address.

Data never sent to PostHog

Melipo does not send recipe names, ingredients, preparation steps, personal notes, photos, email addresses, shopping-list text, or the content of your family notebook to PostHog.

Session replay and screen and touch autocapture are disabled. Console messages are not included in error reports.

Retention

Local-only data remains on the device until you delete it, clear Melipo's local data or uninstall the app. Account and synchronized content are retained while the account is active. After an account-deletion request, deletion is scheduled after a 30-day recovery period.

Content already copied by another user or retained in a family notebook may remain where necessary to preserve that other user's copy or the shared history, with your account identity removed when appropriate. Public content is removed or anonymized according to the deletion workflow.

Push tokens are retained until they become invalid, notifications are disabled, you sign out, or the account is deleted. Analytics and crash data sent to PostHog are retained for no more than 12 months. Security logs are retained for no more than 12 months unless an incident or legal claim requires longer retention. Support correspondence may be retained for up to five years after the last contact. Purchase and accounting records may be retained for the period required by law.

Your rights

Subject to the conditions of the GDPR, you may request access, rectification, erasure, restriction, portability, or object to processing based on legitimate interests. You may withdraw consent at any time in the app or by contacting us. No decision producing legal or similarly significant effects is made solely by automated processing.

Send requests to privacy@melipo.app. We normally respond within one month and may request information needed to verify identity. You may lodge a complaint with the French Data Protection Authority (CNIL).

Contact

For any privacy question or request: privacy@melipo.app.