Privacy Policy
Your baby's feeding log lives on your phone. FeedEase has no account and no server of its own. The app does use a few outside services to count how it is used, catch crashes, measure where installs come from and handle subscriptions. This page lists each one and exactly what it receives.
Last updated: September 30, 2026.
1. Who is responsible for your data
FeedEase is published by Mickael Akim Gauthier, individual entrepreneur (entrepreneur individuel) registered in France under SIREN 879 819 480 (SIRET 879 819 480 00044), Bureau 326, 78 Avenue des Champs-Élysées, 75008 Paris, France. He is the data controller for the processing described on this page.
Contact for any privacy question: contact@feedease.app.
2. What stays on your phone
Everything you type into FeedEase is stored in a local database on your device. It is not sent to us or to any of the services listed below. This includes:
- your baby's first name, date of birth and photo (all optional);
- every feed you log: bottle amounts, nursing duration and side, pumping sessions, times, milk storage choices, leftovers and notes;
- your settings, such as the volume unit (ml or oz) and reminders.
Reminders are scheduled by your phone itself. No server sends them. FeedEase does not sync your data to iCloud or to any cloud of ours.
If you choose to share a stats summary from the Stats screen, the app creates an image that can include your baby's first name and feeding figures, then opens the iOS share sheet. That image goes only where you send it.
Your phone's own backups (iCloud Backup or a backup to a computer) may include the app's data. Those backups are managed by Apple and by you, not by us.
3. What the app sends to outside services
FeedEase relies on the following services. None of them receives your baby's name, date of birth, photo, feeding amounts, durations or notes.
| Service | Why we use it | Data concerned | Their privacy policy |
|---|---|---|---|
| Google Firebase Analytics | Understand how the app is used (for example, how many people finish setup or open the Stats screen) so we can improve it. | App usage events listed in section 4, an app instance identifier generated by Firebase, device and app information (model, iOS version, app version, language, approximate country). | Firebase privacy |
| Google Firebase Crashlytics | Find and fix crashes and database errors. | Crash reports and technical error details, an installation identifier, device model, iOS version and app version. | Firebase privacy |
| AppsFlyer | Measure which of our marketing campaigns led to an install, and report subscriptions to those campaigns. | An AppsFlyer identifier, the identifier for vendor (IDFV) that iOS assigns to our app, IP address, device model, iOS version, language, install and app open events, and when you subscribe, the product identifier, price and currency. | AppsFlyer privacy policy |
| RevenueCat | Manage Premium subscriptions: check whether you are subscribed, restore purchases, and forward subscription events to AppsFlyer. | An anonymous identifier created by RevenueCat, your App Store purchase and subscription history (product, price, dates, transaction identifiers), the identifier for vendor (IDFV), IP address, your AppsFlyer identifier, and an Apple Search Ads attribution token collected through Apple's AdServices framework. | RevenueCat privacy policy |
| Apple (App Store, StoreKit, SKAdNetwork) | Download the app, pay for Premium, ask for an App Store rating, and receive anonymous install notifications for ads. | Payments are handled by Apple under your Apple Account; we never see your payment details. If you installed FeedEase after seeing one of our ads, Apple may send an install notification (SKAdNetwork postback) to AppsFlyer that contains no identifier of you or your device. | Apple privacy policy |
If you write to us, we receive your email address and whatever you choose to put in your message.
This website. feedease.app is hosted by Vercel. To count visits we use Vercel Web Analytics, which sets no cookies: a visitor is recognised by a hash built from the incoming request, discarded after 24 hours, and each page view records only the page address, the referring site, the approximate location (country, region, city), the browser, the operating system and the device type. We only see aggregated statistics, never individual visitors. Vercel Web Analytics privacy
Baby basics. The app downloads its baby basics carousels (images and a list of titles) from feedease.app, hosted by Vercel. These requests carry no identifier of you and none of your baby's data, but like any web request they reveal your IP address to Vercel, which keeps it in its technical logs. The images are then stored on your phone so they can be viewed offline.
4. Exactly what the usage events contain
The events sent to Firebase Analytics carry only the details below:
- Setup: which setup step you view or complete (step names such as "name" or "photo", never what you typed), the feeding style you pick (bottle, breastfeeding or both), whether you skipped the photo and whether you allowed notifications.
- Logging: each time a feed is saved, its type only (bottle, nursing or pumping). No amount, duration, time or note.
- Premium: which screen showed the offer, the plan type (monthly or yearly), whether a purchase was completed, cancelled or failed, and the result of a restore.
- Other: that you opened the Stats screens, that you shared a stats summary (not its content), and that you switched between ml and oz.
- Reminders: when you open the app by tapping a reminder, the reminder's identifier. For milk storage, leftover bottle and formula pitcher reminders, that identifier includes the date and time the milk was pumped, the bottle was fed or the pitcher was prepared. This is the only case where a time linked to a feed leaves your phone.
Firebase also records standard events on its own, such as the first app open, sessions and app updates.
5. What we do not do
- We do not sell your personal information, and we do not share it for cross-context behavioral advertising.
- FeedEase never shows the "Allow to track" (App Tracking Transparency) prompt. Without that permission, iOS does not give the app or its partners your advertising identifier (IDFA).
- There are no ads inside the app.
- We do not ask for your name, email address, phone number or location, and there is no account to create.
6. Why we are allowed to process this data
- Subscriptions (RevenueCat, Apple): to perform the contract you enter into when you subscribe.
- Usage events, crash reports and install measurement (Firebase, AppsFlyer): our legitimate interest in keeping the app working, improving it and knowing which campaigns bring new users.
- Support emails: our legitimate interest in answering you.
7. Where the data goes
Google, AppsFlyer and RevenueCat may process data outside the European Union, notably in the United States. Those transfers rely on the safeguards each provider offers, such as the European Commission's Standard Contractual Clauses.
8. How long it is kept
- On your phone: until you delete the app. FeedEase has no button to erase all data; deleting the app erases its database.
- Firebase Analytics: event data tied to an app instance is kept for 14 months at most.
- Firebase Crashlytics: crash reports are kept for 90 days.
- AppsFlyer and RevenueCat: for as long as needed for install measurement and subscription management, under their own retention rules.
- Support emails: as long as needed to answer you and follow up.
9. Your rights
Wherever you live, you can ask us to access, correct or delete your personal data, to restrict or object to its processing, or to receive a copy of it. Residents of the European Union and the United Kingdom have these rights under the GDPR. California residents have the right to know, to delete, to correct and to opt out of sale or sharing (we do neither), and we will never treat you differently for using these rights.
To use any of these rights, email contact@feedease.app. We answer within one month (45 days for California requests).
Please note: the data sent to our providers is not linked to your name or email address, so we may not be able to find it from your request alone. Tell us what you need and we will do everything we reasonably can, including asking our providers to delete data tied to your device. The data on your phone is in your hands: deleting the app removes it.
If you are in the European Union, you can also file a complaint with your data protection authority. In France, that is the CNIL.
10. Children
FeedEase is made for parents and caregivers, not for children. The information about a baby is entered by a parent and stays on the parent's phone. We do not knowingly collect personal information from children under 13, or under the age of digital consent in their country (between 13 and 16 in the European Union). If you think a child has sent us personal information, email us and we will delete it.
11. Security
The feeding log is protected by the security of your iPhone, including its passcode and iOS data protection. Data sent to the services above travels over encrypted connections.
12. Changes to this policy
If the app starts collecting something new, we will update this page and its date before that version is released.
13. Contact
Mickael Akim Gauthier, FeedEase, Bureau 326, 78 Avenue des Champs-Élysées, 75008 Paris, France. Email: contact@feedease.app.