Efaga Privacy Policy
Effective 12 November 2026
Efaga is a food log for iPhone, made by Artem Mazurin, an individual developer based in Cyprus (“I”, “me”). This policy explains what happens to your information when you use the app.
The short version
Efaga shows no ads and needs no account: you can use it without ever signing in, and you may sign in with Apple to keep Efi Plus when you change phones — see “Your account”. From version 1.0.1 it asks once, with Apple’s prompt, whether it may track you for ad measurement; if you say no, nothing about the app changes. Your food log, your profile and your products stay on your iPhone; I never receive them. Three things leave the phone for my server: a recipe you ask Efi to work out, a photo you ask her to read, and a short note of which onboarding and subscription screens you reached — see below. If you sign in, a fourth does: the email and name your Apple account shares. From version 1.0.1 the app also tells Meta that it was installed and opened, so I can see which of my ads work — see “Measuring my ads”.
What stays on your phone
- Your food log — what you ate, portions, times and meals.
- Your profile — sex, birth year, height, weight, activity level and goal, used only to estimate a daily calorie norm on the device.
- Your products and meals — anything you add or edit.
This data is stored in a local database inside the app. It is not uploaded to me or to anyone else. Like other app data, it may be included in your device backups if you use iCloud or computer backups; those backups are controlled by Apple and by you.
What leaves your phone
To find foods, Efaga uses Open Food Facts, a free public food database run by the non-profit Open Food Facts association (France).
- Search: when you search, the text you type is sent to Open Food Facts to get matching products.
- Barcodes: when you scan a package, the barcode number is sent to Open Food Facts to look the product up.
These requests carry no name, account or identifier of yours. Like any internet request, they reach Open Food Facts’ servers with your device’s IP address. See the Open Food Facts privacy policy.
Adding products to Open Food Facts. Some versions of Efaga can add a product you typed in after a scan found nothing to Open Food Facts, so the next person who scans it gets it. When this is on, the app tells you under the form before you save. Only the product is sent — barcode, name and nutrition values — never anything about you. Contributions become public under the Open Database License.
Efi's kitchen (recipes)
When you ask Efi to work out a dish, the recipe text you wrote and the names of your own products (names only, no numbers, no log) are sent to my server on Cloudflare and from there to Anthropic, whose AI model reads the recipe. They are used only to answer that one request: my server does not store the recipe or the product names and does not write them to its logs, and Anthropic processes them under its commercial terms, which do not allow training on them.
To keep the daily limit of recipes, the request carries a random ID created by the app when it was installed — or, once you have signed in, your account ID (see “Your account”). The install ID is not linked to your name or email, and my server keeps only a daily count against it, deleted after two days. My server's own log keeps only technical details of each request (the install ID, the result, how long it took, a short reason on failure, and which AI model answered and how many tokens it used). As with any internet request, Cloudflare, which hosts the server, sees your device's IP address and may record it in its request logs. The saved dish and the text you wrote stay on your phone.
Efi reading a photo
When you tap Snap to have Efi read the food on your plate or on your kitchen scale, or a nutrition label, the app shrinks the photo on your iPhone and sends it, with the names of your own products (names only), to my server on Cloudflare and from there to Anthropic, whose AI model reads it. The photo is used only to answer that one request: my server does not store it and does not write it to its logs, the app does not keep a copy, and Anthropic processes it under the same commercial terms. Point the camera at your food; anything else in the frame is sent too.
Which screens you reached
To learn where people give up before they start, the app tells my server when you open it for the first time, which onboarding step you see, whether you finished or skipped it, when you see the Efi Plus screen, which plan you pick and whether a purchase or a restore went through. Each note carries only the step's name, a few words such as where the screen was opened from, a few of your onboarding answers as short codes (the pace you chose, what got in your way before, whether you connected Apple Health), which recipe of the book you opened or cooked, the time, the app version and the same random install ID as Efi's recipes. Never your food, weight, height, age or anything you typed.
As with Efi, Cloudflare sees your IP address when the note arrives; the note itself does not keep it. The notes are kept by Cloudflare Workers Analytics Engine for three months and then deleted. The install ID is random, made by the app and gone if you delete it; it is not tied to your name, email or your phone's hardware — unless you sign in, when my server knows which installs belong to your account (see “Your account”; for Efi Plus, see below how the App Store's purchase record is linked to it). The notes are not shared with anyone and are not used for advertising or tracking.
Efi Plus (subscription)
Efi Plus is sold by Apple through the App Store: Apple takes the payment, and I never see your card or your Apple ID. To know whether a subscription is active, the app uses RevenueCat, a subscription service. RevenueCat receives the same random install ID and the App Store's record of the purchase (which plan, when it started, when it renews or ends, the price and the store country). It does not receive your food, weight or anything you typed. From version 1.0.1 the app also gives it your phone’s vendor identifier (IDFV, the same for all of my apps on your phone and nothing else) and Meta’s anonymous app ID, so RevenueCat can tell Meta that a trial started — see “Measuring my ads”. The advertising identifier (IDFA) is collected only if you allow tracking in Apple’s prompt. If you sign in with Apple, RevenueCat is also given your account ID (in place of the install ID), your email and your name, so your subscription can follow you to a new phone — see “Your account”. Before Efi reads a recipe, my server asks RevenueCat whether that install ID has an active subscription and remembers a "yes" for up to a day. I never see your Apple ID: RevenueCat links the install ID to the App Store's purchase record, not me. Like Cloudflare, RevenueCat sees the IP address the request comes from. RevenueCat processes this under its privacy policy.
If you ask for a reminder before the free trial ends, it is a notification scheduled on your phone; nothing is sent anywhere to set it.
Your account (Sign in with Apple)
Efaga works without an account. From version 1.0.2 you can sign in with Apple — on the Me tab, or on the screen that asks you to subscribe — so that your Efi Plus subscription follows you to a new phone, and so I can find it if you write to me for help. Signing in is optional, and nothing in your food log depends on it.
When you sign in, Apple gives the app a signed token. My server on Cloudflare checks it and keeps an account record: a stable account ID (a hash of the identifier Apple assigns you for my apps — not your Apple ID itself), the email Apple shares (your own, or Apple’s private relay address if you chose “Hide My Email”), the name Apple shares if you chose to share it, the date, and the list of installs signed in to this account. The same account ID, email and name are passed to RevenueCat, where they replace the random install ID on your purchase record. The account holds nothing else: no food, no weight, no photos.
To delete the account, open the Me tab (or the subscription screen) and tap “Delete account”; Apple asks you to confirm. The app then has my server remove the account record and the installs linked to it, delete the RevenueCat customer record, and revoke Efaga’s access at Apple. The subscription itself is Apple’s and continues until you cancel it in Settings → Apple Account → Subscriptions; the app reminds you of this after deleting.
Measuring my ads
I advertise Efaga on Facebook and Instagram. To know which ads bring people who actually start a trial, version 1.0.1 and later include Meta’s software development kit (SDK). It sends Meta (Meta Platforms Ireland Ltd.) that the app was installed and opened, with an anonymous ID the SDK makes for this app, your phone model, iOS version, language and IP address. RevenueCat (see above) sends Meta when a trial or subscription starts, with the same anonymous ID and the vendor identifier (IDFV).
Once, after setup, the app shows Apple’s “Allow to track” prompt. Only if you allow it, the SDK also sends Meta your phone’s advertising identifier (IDFA) so Meta can match the install to the ad you saw. If you don’t, advertiser tracking stays off in the SDK and the IDFA is never read. You can change your answer any time in Settings → Privacy & Security → Tracking. Either way, Meta does not receive your food, weight, profile, photos, recipes or anything you typed. Meta uses this to measure and improve my ads, under its privacy policy. You can limit how Meta uses activity from apps in your Facebook or Instagram settings (Accounts Center → Your information and permissions → Your activity off Meta technologies).
Camera
Efaga asks for the camera to read barcodes and, when you tap Snap, to take a photo for Efi to read (see above). Barcodes are read on the device. A photo is sent only when you tap Snap, and it is not saved on the phone or on my server.
Reports you share
If you create a PDF report, it is made on your phone and goes only where you send it through the iOS share sheet. It contains your logged food and your daily norm, not your weight, height or age.
Deleting your data
You can delete single entries in the Diary. To delete everything on the phone, delete the app from your iPhone — that removes its database for good. The only thing I hold about you is the account record, if you signed in; “Delete account” removes it (see “Your account”). Everything else lives on your phone, so there is nothing more to request from me.
Apple Health
If you connect Apple Health, Efaga reads one thing from it: your active energy (the Move ring), day by day for the last 14 days. From it the app works out an average and adjusts your daily calorie target. Efaga keeps only that average on your phone, never sends Health data anywhere — not to my server, not to anyone else — and never writes to Health. You can turn access off at any time in the Health app → your profile picture → Apps → Efaga.
Children
Efaga is not intended for children. The daily norm can only be calculated for people 16 and over.
Health information
The daily norm is an estimate from the Mifflin–St Jeor equation, not medical advice. Talk to a doctor before changing how you eat.
Changes
If this policy changes, the new version will be posted on this page with a new effective date.
Contact
Questions or requests: efaga.app@gmail.com