Privacy Policy

Effective date: 2 October 2026

Last updated: 7 October 2026

1. Who we are and what this policy covers

1.1 Who we are. Feed Me is provided by Envy Applications (ABN 95 927 268 876), a business based in Western Australia, Australia (“Feed Me”, “we”, “us” or “our”). We are responsible for the personal information described in this policy.

1.2 What it covers. This policy applies to the Feed Me mobile app for iPhone and iPad and, when it is released, Android (the “App”), our website at www.feed-me-app.com (the “Website”) and related support. It also covers coaching features, to the extent we handle information for them (see section 7). It does not cover other companies’ websites and apps that we link to, or what a coach does with information after taking it out of Feed Me.

1.3 The law. We handle personal information in line with the Australian Privacy Principles under the Privacy Act 1988 (Cth). Where the privacy law of another place applies to you, such as the UK and EU General Data Protection Regulation or the California Consumer Privacy Act, we also follow it. Section 12 explains your rights.

1.4 Related documents. Our Terms of Service govern your use of Feed Me. Our Consumer Health Data Privacy Notice adds information for residents of certain US states. Our account deletion page explains how to delete your data.

2. The information we collect

You choose what to enter, and you do not have to give us any particular piece of information. But a feature that needs a piece of information cannot work without it: for example, we need an account to sync your data, and your body details to calculate your targets.

2.1 Information you give us

Category	What it includes
Account	Email address (or Apple’s private relay address if you choose “Hide My Email”), display name, how you sign in (email and password, Google or Apple) and a unique account ID. We never see your password. If you sign in with Apple, we also store a token from Apple so that we can try to revoke your Apple sign-in if you delete your account.
About you and your body	Age in years (earlier versions of the App asked for your date of birth instead, and an account set up then may still hold it until you next change your age), sex, height, weight, body-fat percentage and activity level; your goal (for example lose, maintain or gain weight), its amount and pace; units; and your daily calorie, nutrient and water targets.
Diet	Your dietary preference (for example vegetarian or vegan) and ingredients you choose to avoid (such as gluten or dairy). These can imply an allergy, a medical condition or a religious or ethical belief.
What you log	Food and drink entries (with calories, nutrients, times, meal slot, notes and optional photos), water, weigh-ins, body measurements, progress photos, habits and check-in answers.
Your content	Recipes (including ones you import), cookbooks, meal plans, shopping lists, saved and favourite meals, and your scanned-product history.
What you send to AI features	A meal photo or description, a nutrition-label photo, a recipe link, pasted text or screenshot, a message to the in-app assistant, or a voice note (see section 4).
Coaching	Invitations, the sharing choices you make, targets and goals a coach sets for you, and check-ins you submit (see section 7).
Your choices and communications	Notification settings, whether you opted in to marketing emails, your ad-measurement choice, when you accepted our Terms, codes you redeem or share (if you share a referral code, the person who redeems it sees your display name), and anything you email to support.

2.2 Information collected automatically

Category	What it includes
Device and technical data	Device model, operating system and version, app version, language and region settings, your IP address, and crash and error details.
Push notification token	A token for your device, created when you allow notifications. It is kept on your account until you sign out, the device stops being registered with our notification provider, or you delete your account, even if you later turn notifications off in the App. When you sign out, the App removes this device’s token from your account (a token that belongs to another of your devices is left in place). If you are offline, or the connection is too slow, at that moment the request can fail, and the token then stays until it is replaced or you delete your account, so notifications addressed to the account you signed out of could still reach the device.
Last-opened time and time zone	Roughly when you last opened the App (updated every few hours) and your time zone as an offset from UTC. We use these so that reminders and messages arrive at a sensible local time, and to decide whether a reminder or an offer you opted in to is relevant.
Usage analytics	Events that record that an action happened, such as completing a setup step or using an AI feature. Where analytics is on (section 5.5), the first event (your tap on “Get started”) carries only a random device ID, and every later event is linked to your account ID, which exists from that tap as a temporary account. See section 5.
Ad-measurement data	Device identifiers and a small number of events, only while ad measurement is on for your device, and never for anyone under 18. See section 6.
Subscription status	Whether you have an active Pro subscription or trial, received from the app store through our subscription provider.

2.3 Information from other sources

• Apple and Google, when you sign in with them: the name and email address you allow them to share.
• Apple Health or Health Connect, if you connect them. On iPhone, Feed Me reads the active and resting energy you burn, and writes the calories, protein, carbohydrate and fat of meals you log, with each meal’s name, to Apple Health. On Android, Feed Me reads active, total and basal energy and writes a nutrition record for each meal you log to Health Connect. These values are read on your device to keep your calorie ring accurate. They are not uploaded to our servers.
• The app stores, about your purchases and subscriptions.
• Food databases, such as Open Food Facts, when you scan a barcode.
• Public web pages and posts, which you ask us to import.
• Your coach, if you have one: targets, goals and feedback they set for you.
• A friend, if you redeem their referral code: we may show you the name or label attached to that code.

2.4 What we do not collect

We do not collect your payment card details (the app stores handle payments), your contacts, your calendar or your precise location. The App never asks for location or contacts permission, although we do receive your IP address (from which our providers work out an approximate location), your device’s region setting and your time zone. We do not read your photo library in the background: you choose each photo. The camera is used when you take a photo or scan a barcode, and the microphone only while you record a voice note. We do not record your screen or use session replay.

2.5 Setting up before you register

While you set up the App, before you create an account, it signs you in to a temporary account so that your answers (including the body details you enter) can be saved. The first setup screen tells you, before it asks for any body detail, that continuing means you agree to our Terms, to this Privacy Policy, and to us using your height, weight and goals to build your plan (section 3), and we record when you did. Where analytics is on (section 5.5), it starts at this point. Whether or not analytics is on, from here our subscription provider and our crash-reporting provider also use your temporary account ID. Where ad measurement is on for your device (section 6.5), AppsFlyer does too. If you finish sign-up, the temporary account becomes your account. If you do not, it is deleted automatically (see section 10).

2.6 Data kept on your device

The App keeps some data on your device: your sign-in session, caches of your recent entries and recipes, your conversation with the in-app assistant, your AI permission, your usage-analytics choice and your ad-measurement choice, and a small summary of your day (totals, last meal, planned meals and shopping list) that home-screen widgets read, plus a share token, your language and your theme that the iPhone share extension reads. Signing out or deleting your account clears the data tied to the account, including your ad-measurement choice, so the next person to use the device is asked afresh. Your AI permission and usage-analytics choice stay on the device.

3. How we use information, and why

Why we use it	What we use	Legal basis (UK and EU/EEA users)
To run Feed Me: your account, sync across devices, targets, logs, plans, recipes and lists	Account, body and diet details, logs, content	Contract (it is needed to provide the service you asked for)
To personalise targets and recipes using your health-related details	Body and diet details	Your consent. For body details, we tell you on the first setup screen, before any is requested, that continuing means you agree to us using your height, weight and goals to build your plan, and we record when you did. For diet details you add later, you consent when you choose to enter them. The answers you give before you register are held in a temporary account
To provide AI features	What you send to them	Your consent (the in-app permission)
To keep Feed Me secure, prevent fraud and abuse, and apply usage limits	Device, IP address, account and usage data	Our legitimate interests in running a secure service
To understand how the App is used and improve it	Analytics events and technical data	Your consent for events the App sends in the UK, the EU/EEA and Switzerland (you switch it on); our legitimate interests for server-side and subscription events there, and for all analytics elsewhere
To find and fix crashes	Crash reports	Our legitimate interests
To measure our advertising	Ad-measurement data	In the UK, the EU/EEA and Switzerland (and where we cannot tell your region): your consent — it is off until you switch it on. Elsewhere: our legitimate interest in measuring our own advertising, and you can switch it off at any time. Never for anyone under 18
To manage subscriptions, trials, promo and referral codes, and support	Account, subscription and code data, your emails	Contract, and our legitimate interests
To send service messages (account, security, billing, coaching activity)	Account, device and push-token data	Contract, and our legitimate interests
To send marketing emails and notifications, if you opt in	Email address, push token	Your consent (you opt in)
To let a coach support you	What you choose to share	Your consent
To follow the law, handle disputes and enforce our terms	Whatever is needed	Legal obligation, and our legitimate interests
To produce aggregated, de-identified statistics	De-identified data	Our legitimate interests

We do not use your information to make automated decisions that have legal or similarly significant effects on you. Estimates and targets in the App are suggestions, not decisions about you.

4. AI features

4.1 What is sent and to whom.

Feature	What is sent	To
Calorie scan from a photo	The photo, compressed on your device, with an optional note, the meal slot, the local time, your units, your language and your device’s region	Anthropic
Describe a meal (and re-estimate, when available)	Your text, or the transcript of your voice note, with the same context; your corrections when re-estimating	Anthropic
Read a nutrition label	A photo of the label	Anthropic
Suggest a recipe	Your idea or ingredients, a calorie target, and your dietary settings (for example gluten-free or pork-free)	Anthropic
Import a recipe from a web page, pasted text or a screenshot	The page text, your text or the screenshot	Anthropic
Import a recipe from a YouTube video	The video link	Google (Gemini, through Vertex AI on Google Cloud) and Anthropic
Import a recipe from a TikTok, Instagram or Facebook post	The post link. We retrieve the post’s public details and media through a media-retrieval service, transcribe the audio, and send the text to Anthropic.	A media-retrieval service, Deepgram and Anthropic
In-app assistant	Your messages and the conversation so far; your display name, calorie and macro targets, dietary preference and ingredients you avoid; today’s food log; and, when it looks them up to answer you, other days’ logs, your saved recipes and the recipe library	Anthropic
Voice input	Your voice note (up to 60 seconds), sent when you stop recording	Deepgram
Coach AI tools (used by coaches)	When a coach you are connected to uses the AI assistant or asks for a check-in summary: your name; a day’s food diary when the coach asks for it (meal names, calories and macros); summary figures over a period (days logged, average calories, macros and water, weight change and logging streak); your calorie and macro targets; the meals you log most often, with their calories; your meal plan; and your check-in answers	Anthropic
Restaurant lookups (when enabled)	The restaurant and menu item you described	Anthropic, which searches the restaurant’s official website

4.2 Your permission. Before the first AI request on a device, the App asks whether we may send the relevant content to our AI providers. If you say no, we send nothing to them, and the features that need them are unavailable. There are two exceptions. First, importing a link through the iPhone share extension counts as your instruction to import it, and we do not show this prompt, even if you have not answered it yet. Second, when a coach uses the coach AI tools on information about you that the coach can already see, we do not ask you separately. There is currently no switch to withdraw the permission once you have given it: you can stop using AI features, email us, or delete and reinstall the App to be asked again.

4.3 How providers treat the data. Our providers act on our behalf, under contract.

• Anthropic. Anthropic’s commercial terms say it may not train its models on content we send through its API. By default it deletes API inputs and outputs within 30 days, and keeps them longer only where content is flagged for misuse or the law requires it.
• Google (Gemini, through Vertex AI on Google Cloud). Google Cloud’s terms say it will not use our content to train its models without our permission.
• Deepgram. We tell Deepgram not to use your audio to improve its own models.

4.4 What we keep. We do not keep your voice notes. We do not keep the photo you send for a scan unless you log the meal with its photo, in which case it is stored in your account like any other log entry. Our server logs record technical timings, never the content of your request. A link you share into Feed Me, and the recipe we extract from it, stay in your import queue until you dismiss them or delete your account. For public posts you import, we may keep a shared copy for a short time (see section 10).

4.5 Accuracy. AI output can be wrong. Check it before you rely on it. See our Terms.

4.6 Other people’s information. Please do not send photos, text or recordings that contain other people’s personal information.

5. Analytics and app performance

5.1 Mixpanel. We use Mixpanel, Inc. for product analytics, to see which features are used and where people get stuck. Where analytics is on (section 5.5), events start when you first tap “Get started”, before you create an account. The App sends events that record that an action happened, such as opening the App, finishing a setup step, signing up (and by which method), viewing a subscription screen, starting a trial, using an AI feature, sending a message to the assistant, importing a recipe, or answering a rating prompt. When you log a meal from an AI scan, the App can also send how far the number you saved differs from the AI’s estimate, as a percentage, and how the estimate was made (no calorie figures and no food name), and it sends technical timings of each AI request. The first event carries only a random device ID. Every later event is linked to your account ID (a temporary account until you finish sign-up) and carries a few details: whether you are a Pro member, whether you joined with a referral code, whether you mainly use the App for nutrition tracking or meal planning, how many reminders you have turned on and whether push is enabled. Mixpanel keeps a profile for your account ID with the same details and your sign-up date, and receives subscription events (such as starting a trial, subscribing, renewing or cancelling) from our subscription provider. Mixpanel also records the app version, device model, operating system version, screen size and approximate location (country, region and city) worked out from your IP address. Mixpanel does not store the IP address itself as a property.

5.2 What we do not send to Mixpanel. Food names, meal photos, anything you type, your weight or other measurements, your goals, calorie figures, health-app data, your name or email address. The only food-related number it receives is the percentage described above. We do not use session replay or automatic event capture.

5.3 Server events. Our servers also send Mixpanel a few events about notifications we send and about recipe imports, tied to your account ID and with no personal content. These, and the subscription events in section 5.1, do not depend on the switch in section 5.5.

5.4 Where and for how long. Mixpanel stores this in the United States. We keep analytics for up to 24 months.

5.5 Your choices. In the UK, the EU/EEA and Switzerland, and wherever we cannot tell your region, the App sends no analytics until you switch on Me → Notifications → Usage analytics. We rely on your consent, which you can withdraw there at any time. We decide using your device’s region setting, which may not match where you live. Because the switch is in Settings, the setup steps you complete before you find it are not recorded. Everywhere else, analytics is on by default and you can switch it off in the same place. The switch controls what the App sends from your device, and your choice is stored on the device. It does not stop the server events in section 5.3 or the subscription events in section 5.1. You can also ask us to delete the analytics data linked to your account, or object to this use, by emailing support@feed-me-app.com.

5.6 Crash reports and performance (Sentry). If the App crashes or hits an error, it sends a report to Sentry (Functional Software, Inc.) with the error message and stack trace, device model, operating system and app version, a short trail of recent app activity (for example network requests the App made, such as the barcode you looked up, and launch and setup steps), and your account ID. For a small sample of sessions it also sends performance timings, and Sentry receives basic session information. Sentry does not receive your name or email address. We strip request details from reports and set Sentry not to collect personal data automatically, and we do not intend to send what you type, what is on your screen or your images. Reports are kept for up to 90 days.

6. Advertising measurement

6.1 What and why. We advertise Feed Me on Meta (Facebook and Instagram) and TikTok. To find out which ads bring people to the App, we use AppsFlyer, an attribution service. If you opt in, AppsFlyer tells us which ad led to an install and a sign-up, and passes these events to Meta and TikTok so they can see which ads worked. Because using a food-tracking app can itself say something about a person, we ask first and we never turn this on for anyone under 18.

6.2 What AppsFlyer receives. If you have opted in: your device identifiers (the vendor identifier on iOS; your advertising ID if you allow tracking on iOS, or your Google advertising ID on Android), your IP address, app and operating system version, install and session times, and your account ID as a customer ID. It also receives one event from the App, that you created an account and by which method (email, Google or Apple), and, through our subscription provider RevenueCat, that you started a trial, subscribed, renewed or cancelled.

6.3 What it never receives. From the App, AppsFlyer never receives your name, email address, weight or other measurements, calories, food entries, goals, photos, health-app data, or anything you type. Health information from Apple Health or Health Connect is never used for advertising.

6.4 Who else gets it. AppsFlyer Ltd. acts for us under contract. Meta Platforms and TikTok receive the install and event data from AppsFlyer to measure and improve their ads, and they handle it under their own privacy policies.

6.5 When it is on.

• Where you are decides whether we ask first. In the UK, the EU/EEA and Switzerland, and wherever we cannot tell your device’s region, ad measurement is off until you switch it on under Me → Notifications → Ad measurement. Everywhere else it is on from the moment we know you are an adult (on iPhone, once you have answered Apple’s tracking question, see 6.6), and that same switch turns it off. Apart from Apple’s question on iPhone, we do not ask about advertising while you are setting the app up, and agreeing to our Terms is not an agreement to this.
• Never for anyone under 18, or whose age we do not know. For them the switch is not shown, nothing we store and no regional default can turn it on, and nothing is sent to AppsFlyer or our subscription provider for advertising.
• Region. In the UK, the EU/EEA and Switzerland, and wherever we cannot tell your region, we also tell AppsFlyer that you have consented, in the form those laws require. We decide using your device’s region setting, which may not match where you live.
• Withdrawing. Switch it off at any time under Me → Notifications → Ad measurement. This stops new data being sent. Data already sent stays with the recipients under their own policies. If you switch it off, we also clear the AppsFlyer ID and advertising ID we had passed to our subscription provider (its record of your device’s vendor or Android ID stays until you ask us to delete it).
• Switching it ON belongs to your signed-in session on that device. When you sign out, the App forgets that you switched it on and clears the same two IDs, so on another device or after a reinstall it goes back to the default for your region. Switching it OFF is kept: a device where you have turned it off stays off, including after you sign out and sign back in.

6.6 iOS tracking prompt. On iPhone, nothing is sent to AppsFlyer until you have answered Apple’s question about tracking you across other companies’ apps and websites. Outside the UK, the EU/EEA and Switzerland, the App asks it once, if you are an adult: while you set the app up (on the screen where your plan is built), or shortly after you sign in if you sign in to an existing account instead. In the UK, the EU/EEA and Switzerland it is asked only when you switch ad measurement on yourself. If you choose “Allow”, AppsFlyer also receives your advertising identifier. If you choose “Ask App Not to Track”, your advertising identifier is not used and attribution works through Apple’s own aggregated measurement instead; ad measurement otherwise stays as described in 6.5, and you can still switch it off under Me → Notifications → Ad measurement. You can change your answer to Apple’s question in iOS Settings → Privacy & Security → Tracking.

6.7 Apple Search Ads. While ad measurement is on for your device, our subscription provider on iPhone also collects an attribution token from Apple, which tells us whether you installed Feed Me after an Apple Search Ads campaign. This does not use your advertising identifier. It follows the same regional and age rules as the rest of this section, and it stops when you switch ad measurement off.

6.8 US privacy laws. Under California and some other US state laws, sending this data to advertising partners may count as “sharing” (or a “sale”) of personal information for cross-context behavioural advertising. In the United States this is on unless you turn it off: Me → Notifications → Ad measurement is your opt-out, and it is also how you exercise the right to say “do not share my personal information”. You can switch it off at any time, or email us and we will do it. Turning it off is remembered on that device, including after you sign out.

7. Coaching

7.1 If you are a client. You decide whether to connect with a coach: you send a request using the coach’s code, and the coach accepts it. From then on, and for as long as you stay connected, your coach can see, with no separate switch:

• your food diary with its full nutrition breakdown and the times you logged meals, including photos of meals;
• your water intake and your weight log;
• your weekly meal plan, including the custom shopping items and pantry items stored with it, and your recipe library;
• your habits and when you complete them;
• your calorie, macro and water targets, your name, your units, your time zone and the date you last logged;
• any check-in answers you submit (check-in photos are visible only if you switch on photo sharing); and
• a “gone quiet” alert that includes your name, if you have not logged for 3, 7 or 30 days.

You cannot switch these off one at a time. Ending the connection stops all access. Three more items stay off until you switch each one on: your body statistics (height, weight, age, sex, activity level, body-fat percentage and goal), your body measurements, and your progress photos and check-in photos.

A coach can also set your targets and goals, edit your meal plan, add recipes to your library, assign habits, leave feedback on your check-ins, export your diary as a PDF, spreadsheet or text, and use the coach AI tools described in section 4. A coach cannot edit what you have logged, and does not see your email address or account details. Feed Me has no chat or direct messaging. Coaches can write feedback on check-ins and short notes with the targets they set, and send fixed nudges and sharing requests, and clients answer check-in questions in writing.

7.2 Ending a connection. You can end a connection at any time. The coach’s access to your data in Feed Me then stops. A coach may already have exported or copied information while connected, and what they do with it is their responsibility. Links to meal photos that a coach copied while connected may keep working until the photo is deleted. If you reconnect with the same coach, they can again see the check-ins you exchanged earlier. A record that a connection existed is kept for 180 days after it ends.

7.3 Notes. Coaches can keep private notes about a client. They are stored in the coach’s own account, on the coach’s behalf, and clients do not see them in the App. Deleting your account does not delete notes that are stored in a coach’s account, so to see or remove what a coach holds about you, ask the coach.

7.4 If you are a coach. We collect your name and account details, the clients you connect with, and the actions you take in the coaching tools. Clients you invite can see your display name. We do not check a coach’s identity, qualifications or registrations. You must handle client information as our Terms require. If you delete your account, items you added to a client’s own account, such as targets, recipe copies and habits, stay in the client’s account.

7.5 Who is responsible for what. Feed Me hosts the information in the App. A coach is an independent person who decides what to do with anything they copy or export, and is responsible for doing so lawfully.

7.6 Notices. When a coach does something that involves you, such as updating your targets, we may send you a notification. These are fixed notices that we write.

8. Who we share information with

We share information only as described here. We do not sell personal information for money. The companies below act on our behalf under contract, except for the social platforms, websites and Open Food Facts (which respond to requests from our servers or your device under their own terms), Meta and TikTok (which receive ad-measurement data under their own policies), and the people you choose to share with.

Recipient	What for	What they receive
Google (Firebase, Google Cloud, Google Sign-In)	Hosting, database, file storage, sign-in, app functions, security	Everything stored in your account, and technical data
Apple and Google Play	App downloads, billing, Sign in with Apple, push delivery networks, Apple Health and Health Connect, device-integrity checks	Purchase and device data, handled by them directly
Anthropic, PBC	AI features	What you send to AI features (section 4)
Google Cloud (Gemini)	Understanding YouTube videos you import	The video link
Deepgram, Inc.	Turning speech into text	Voice notes, and the audio of public posts you import
A media-retrieval service, accessed through the RapidAPI marketplace	Getting the media and details of a public TikTok, Instagram or Facebook post you import	The post link
TikTok, YouTube, Instagram and Facebook	Retrieving a public post’s caption and thumbnail	The post link, requested from our servers
Websites you ask us to import a recipe from	Reading the recipe page	The page address, requested from our servers
Open Food Facts (France)	Product details when you scan a barcode	The barcode, your app language and your IP address
RevenueCat, Inc.	Subscription management, and passing purchase events to analytics and (only while ad measurement is on) ad measurement	Your account ID, email address, IP address and purchase events; and, only while ad measurement is on for your device, device identifiers and attribution IDs
Mixpanel, Inc.	Product analytics	See section 5
AppsFlyer Ltd., and through it Meta Platforms and TikTok	Measuring our ads	See section 6
Sentry (Functional Software, Inc.)	Crash reports	See section 5.6
Expo (650 Industries, Inc.)	Delivering notifications and app updates	Your push token; notification content, which can include a name or a recipe title; and your device and app version and a random install ID when the App checks for updates
Your coach	Coaching	What you share (section 7)
People you choose	Sharing	A recipe, image or export you create and send

If you share a referral code, the person who redeems it will see your display name.

We also disclose information when the law requires it, to protect people or our rights, to professional advisers, and to a buyer or successor if our business is sold or reorganised, in which case we will tell you and this policy will continue to protect your information.

When you preview, print or create a PDF from the App, the document may load fonts from Google Fonts, so Google can see your IP address.

9. Where your information goes

We are in Australia, and our providers operate mainly in the United States, where most of the data above is stored and processed. AppsFlyer (Israel and elsewhere) and Open Food Facts (France) also receive some data. Our own access to it is from Australia.

• Australia. Under Australian Privacy Principle 8 we take reasonable steps, mainly through contracts, to make sure overseas recipients handle your information in line with the Principles.
• UK and EU/EEA. Where your information is sent outside your region, we rely on the European Commission’s and the UK’s approved safeguards, such as standard contractual clauses and the UK addendum, or on an adequacy decision, as available.

10. How long we keep information

Information	How long
Your account and everything stored in it	Until you delete your account. We do not delete accounts for being inactive.
The temporary account the App creates while you set up, if you never finish creating an account	Deleted automatically about two days after it was created, once it is no longer in use
Your push token	Until you sign out (the App then removes it from your account, when it can reach our servers quickly enough), the device stops being registered with our notification provider, or you delete your account
Links you shared into Feed Me and the recipes extracted from them	Until you dismiss them or delete your account
Analytics events (Mixpanel)	Up to 24 months
Ad-measurement records (AppsFlyer)	Up to 24 months
Crash reports (Sentry)	Up to 90 days
Server logs, which can include your account ID	Usually 30 days
Per-request records that count AI use and block abuse	3 days, then removed automatically
Counters of your daily and weekly AI use and of code-redemption attempts	Until you delete your account
A shared copy of a public post you imported (caption or transcript, the creator’s public name, handle and profile-picture link, the recipe derived from it, and a copy of the cover image)	Up to 30 days, and the cover image up to about six weeks. It is keyed to the post, not to you, so deleting your account does not remove it.
A connection with a coach that has ended	The connection record is deleted 180 days after it ended
Declined coaching requests, and check-ins exchanged on a connection that has ended	Until you or the coach delete your account
Published calorie values for restaurant items looked up for other users (no personal data; only if this feature is enabled)	30 days, or 7 days if nothing was found
Data you deleted, in our hosting provider’s backups and systems	For a limited time, while it is erased under the provider’s own schedule
Content you sent to our AI providers	Held by them for the short periods in section 4.3. It is not removed when you delete your account.
Subscription and billing records	Held by the app stores and RevenueCat for as long as the law and their rules require
Emails to support	Up to three years after we resolve them
Records of your consents and choices	Until you delete your account, because they are part of your profile

11. Deleting your account

11.1 How. In the App, go to Me → Delete account, type the confirmation phrase and follow the prompts, or follow the steps on our account deletion page. If you cannot sign in, email support@feed-me-app.com from the address on your account.

11.2 What is deleted. When you delete your account, we delete from our systems:

• your account and sign-in record;
• everything stored under your account: your profile and preferences, food, water, weight and measurement logs, habits, recipes, cookbooks, meal plans, shopping lists, and your scanned-product and meal history;
• the files you uploaded, such as recipe, meal, progress and check-in photos;
• referral codes you created;
• your coaching connections, invitations, check-ins, alerts and notices, whether you were the coach or the client;
• your subscription entitlement and usage records on our servers, and our records of notifications sent to you;
• your share-extension tokens and any pending shared imports; and
• if you signed in with Apple, the token we hold for your Apple sign-in, which we try to revoke with Apple when you delete your account in the App. If we delete your account for you by email, we cannot revoke it from our side, so please also remove Feed Me under Settings → your name → Sign-In & Security → Sign in with Apple.

11.3 What is not deleted straight away.

• Copies held by our analytics, advertising-measurement, crash-reporting, notification and subscription providers. They are linked to your account ID or device IDs, and RevenueCat also holds your email address. Deleting your account does not delete them automatically. On request we ask Mixpanel, AppsFlyer, RevenueCat, Sentry and Expo to delete the records for you, and we aim to send those requests within 30 days.
• Content you sent to our AI providers, which they hold for the short periods in section 4.3.
• The shared copy of a public post described in section 10.
• Private notes a coach wrote about you, and anything a coach exported, which are in the coach’s control.
• Records we must keep by law, and billing records held by the app stores.
• Data in our hosting provider’s backups and systems, until it is erased.

11.4 Subscriptions. Deleting your account does not cancel a subscription. Cancel it in your App Store or Google Play account first.

12. Your choices and rights

12.1 Controls in the App.

• Delete your account: Me → Delete account.
• Ad measurement: Me → Notifications → Ad measurement (not shown to anyone under 18, who are never measured).
• Usage analytics: Me → Notifications → Usage analytics.
• Notifications and marketing: Me → Notifications.
• Apple Health or Health Connect: Me → Health sync, and your device settings.
• Camera, photos, microphone and notifications: your device settings.
• Edit your details: most of what you entered can be changed in the App.
• Export your meals: Me → Export logged meals (a Pro feature).

12.2 Everyone. You can ask for access to the personal information we hold about you, ask us to correct it, ask us to delete it, and complain about how we handle it. Email support@feed-me-app.com. We will reply within 30 days, or within the longer deadline a law allows (for example 45 days under US state laws).

12.3 Australia. Under the Australian Privacy Principles you may access and correct your personal information. You can answer the setup questions before you register and use Apple’s “Hide My Email” if you do not want to give us your email address. If you are not happy with our response, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.

12.4 UK and EU/EEA. You have the right to access your data, correct it, have it erased, restrict or object to its use, receive it in a portable format, and withdraw consent at any time (which does not affect what we did before). You can also ask not to be subject to a decision based solely on automated processing. You can complain to your data protection authority, for example the Information Commissioner’s Office in the UK (ico.org.uk), or the authority in your EU country.

12.5 California and other US states. We describe the categories of personal information we collect and why in sections 2 and 3. In the last 12 months we have collected identifiers (such as account ID, device IDs and IP address), contact details, age and sex, commercial information (subscription status), internet and app-activity information, approximate location, photos and audio you provide, health and diet information, and inferences such as targets. We collect them from you, your device and the providers in section 8. We use them for the purposes in section 3.

• Sharing and sale. While ad measurement is on for your device — which in the United States is the default for adults until you turn it off (section 6.5) — we share identifiers, app-activity and commercial information (the events in section 6) with AppsFlyer, Meta and TikTok, which may be a “sale” or “sharing” under those laws. We never do this for anyone under 18. We do not sell personal information for money.
• Sensitive information. Health and diet information is sensitive personal information. We use it only to provide the services you asked for, so we do not offer a right to limit its use. We do not share it for advertising.
• Your rights. You can ask to know, access, correct and delete your personal information, to opt out of sharing or sale (with the switch in section 6, or by email), to receive your data in a portable format, and not to be treated differently for using these rights.
• How. Email support@feed-me-app.com. We will confirm your identity by matching what you tell us to your account. An authorised agent may act for you with your written permission. We respond within 45 days, and may extend once by 45 days, and we will tell you if we do.
• Appeals. If we refuse a request, reply to our message within 60 days to appeal, and we will answer within 45 days. If you are still not satisfied, you can contact your state’s Attorney General.
• Washington, Nevada and similar laws. See our Consumer Health Data Privacy Notice.

12.6 Elsewhere. If you live somewhere else, you have the rights your local law gives you, and we will handle your request in the same way.

13. Children

Feed Me is not for children under 13, and we do not knowingly collect personal information from them. Where the law sets a higher age to use a service like this one (for example 16 in parts of the EU), you must meet that age to use Feed Me. If you are under 18, you may use Feed Me only if a parent or guardian has agreed to our Terms and to your use of it (Terms section 2.2), and we recommend that you talk to a doctor or dietitian before you set a weight goal or change how you eat. We do not offer ad measurement to anyone under 18, and nothing is sent to our advertising partners about them (section 6.5). If you believe a child has given us personal information, email us and we will delete it.

14. Security

We protect your information with:

• encryption in transit (TLS) between the App, our servers and our providers, and encryption at rest by our hosting provider;
• security rules that limit each account to its own data, and server-side checks for coaching access;
• sign-in through Firebase, Google or Apple, so we never see your password;
• the secret keys for our AI and speech providers kept on our servers, never in the App;
• device-integrity tokens from Apple or Google, which the App sends and which we currently monitor but do not enforce;
• rate limits and abuse controls; and
• removal of request details from crash reports.

No system is perfectly secure. If a data breach is likely to cause you serious harm, we will tell you and the regulator as the law requires, including under Australia’s Notifiable Data Breaches scheme and, for UK and EU users, without undue delay.

15. Our website

The Website does not use cookies, advertising or analytics trackers. It stores one preference on your device, your light or dark theme, only when you press the theme button. Our web host keeps standard server logs (such as IP address, time and page requested) for security and operations. Calculators on the Website run in your browser and do not send or store what you enter. A referral link contains a code in its address, which our host’s logs may record. Links to the App Store, Google Play and our social profiles take you to those companies, which have their own policies. If we add analytics or a sign-up form to the Website, we will update this policy first and ask for consent where the law requires.

16. Links and imported content

We are not responsible for the privacy practices of websites, platforms or creators we link to or whose content you import. When you import a public post, we handle only its public content, and you should not import anything you are not entitled to use.

17. Changes to this policy

If we make a material change, we will publish the updated policy on our Website and update the “Last updated” date, and we will also tell you in the App or by email, where we can, before it takes effect. Where the law requires your consent for a change, we will ask for it.

18. Contact and complaints

Envy Applications (ABN 95 927 268 876)
Western Australia, Australia
Email: support@feed-me-app.com

If you have a privacy complaint, please email us first. We will acknowledge it promptly and aim to resolve it within 30 days. You can also complain to the regulators named in section 12.