Privacy Policy

What we collect

Your account details (name, email, and a profile picture if you add one). The profile and goals you enter during setup and afterwards: age, sex, height, weight, body fat, waist, your goal and target weight, your training experience and schedule, and how you like to eat. What you log: foods and meal photos, body weight, measurements, workouts, weekly check-ins including the photos and the free-text answers, and your goals. Your conversations with the AI coach, and the short summary the AI keeps of what matters about you. Your messages, photos and voice notes with a human coach, if you connect one.

Some of it is asked privately during setup and is treated as more sensitive than the rest: your injuries, what you avoid eating, what motivates you, and whether you have a history of disordered eating. None of that is ever shown to a human coach.

Fasting, your starting point and your weekly notes. If you record a fast, we keep what kind it was (a whole day, a timed fast or skipped meals), the days it covered, its start and end times if it was timed, which meals you skipped, the time zone it was recorded in, and when you saved it. If you are connected to a coach and you let them see your food logs, your coach can see your fasts too. When you finish setting up, we save a dated copy of your starting point: your goal, sex, age, height, weight, waist if you gave it, your activity and training days, the rate you chose, and your calorie and macro targets with where they came from, along with the date and the units used. The app shows it to you as where you started, and it cannot be edited. If you submit a weekly review, we keep a record of the week, when you submitted it, and which parts were complete at that moment: whether there was a check-in, a weight, the check-in form and its reflection answers, and how many photos. It holds only that summary, not your answers or photos. If you write a personal reflection for a week, we keep what you wrote, up to 2,000 characters, with the week and when it was written and last changed. The app lets you see, change or remove the note for the current week. In Settings you can also see or remove any of your notes, including those from earlier weeks, and download one note at a time as a file when you use the app in a browser; downloading is not available in the iPhone app. The app does not let you change a note from an earlier week. Your notes stay with your account until you remove them, and are deleted with it. Your personal reflection is not shown to a human coach and is not sent to the AI coach, and it is separate from the reflection question in your weekly check-in. While you are writing one, an unsaved draft can be kept on your device so it is still there if you leave the screen.

We also keep three things that are not part of your plan or your logs. If you send us a report through Feedback in Settings, we keep what you wrote, the category you picked and your email address, with details of where it came from: whether you used the iPhone app or a browser, a description of your device and its system version as the app or your browser reports it, your screen size, the screen you sent it from, the time, the version of the iPhone app you have, and the release of our web app that was running. The report screen shows you those two versions before you send it. If you use the iPhone app, we record on your account which build of it is installed, so we can see who is on an older build. And we store your time zone, which the app reads from your device when you open it or come back to it, so that the app counts your days, and times the messages and reminders scheduled for you, by your own clock.

Our own record of subscription purchases. While our own subscription check is switched on, a subscription bought in the iPhone app can get a record in our database, separate from the copy Apple and RevenueCat hold. It can include Apple's identifiers for the purchase and its renewals, the product, whether it was a real or a test purchase, and what Apple and RevenueCat report about it: its state, when a trial started and ended, when the current period ends, and whether it was cancelled, refunded or had a billing problem. We may keep the messages RevenueCat sends us about it, with when each one happened and the account identifier it was for, and a short log of how a message changed the record. From time to time we may also ask RevenueCat about your subscriptions directly, and keep what it said and when we asked. We use this to check our subscription records against Apple's and RevenueCat's, and to answer you if a purchase does not show up on your account.

Coaching invitation decisions. While we check coaches' client limits, we may record attempts to take up a coaching invitation and what came of them, including invitations that were refused or could not be completed. These records can include the coach and the client involved, the outcome, how many active clients the coach had, the client limit of the coach's plan as our records showed it, whether that limit came from a paid plan or a trial, and what the limit would have meant for that invitation. Once client limits are applied, we may also record attempts to end a coaching connection or withdraw an invitation and what came of them, with the identifier of the connection concerned. When one of these requests changes a connection, we keep it with a one-time identifier, the account that sent it, what kind of request it was, a one-way fingerprint of what it asked for and its result, so the same request sent twice is acted on only once. None of this holds an invitation code, a name or health data.

Technical records of AI requests. We keep technical records to understand problems with AI requests, measure their use and cost, and apply usage limits. A record can include the account it belongs to, the feature and model used, when the request happened, and how much input and output the model used. It can also include whether the request succeeded, failed, returned no usable answer or was refused, a short error or completion code, how long it took, a request identifier, and which automatic conversation repairs were needed. These records do not contain your message text, the model's answers, photos or recordings. These technical details can be stored in our app database and server runtime logs.

Records for AI allowances and spending limits. While our AI usage checks are switched on, we also keep separate records of requests and attempts to process them. These can include the account, feature, request identifiers, a one-way fingerprint of what was sent, which allowance applies, if any, its time window, what happened to the request, and when. We record the amount of model use reserved for an attempt and, when available, how much it used. We use these records to recognize retries and apply allowance and spending limits. A retry can create another attempt record for the same request. These records do not contain your message text, the model's answers, photos or recordings.

The app does not currently run scheduled age-based deletion for these database records. Ending free access or a subscription does not itself delete them. Server runtime logs are separate and follow our hosting provider's retention settings. Account deletion and its limits are explained below.

Support and account-deletion records. We keep records to investigate support requests, reconcile subscription problems and recover from account-deletion failures. They can include your account identifier, a reference to the report or subscription record involved, staff-written case notes, who handled the case, when actions happened and their outcome. Case notes can include details you tell us, including health information if it is part of the issue. We record attempts to open a feedback message and their outcomes; this does not automatically copy the message into the case record. For account deletion, we also record cleanup steps, their status and identifiers needed to investigate remaining cleanup, including coaching-connection identifiers. We keep request identifiers and one-way fingerprints of case actions to recognize retries. These records are linked to the account and stored in our app database.

Community participation and records. Private coach communities are optional, text-only spaces for adults aged 18 or over. You explicitly join, agree to the Community Rules and choose a display name for that community. We record the agreement version, your adult self-attestation and when it was accepted; this is not verified proof of age. We keep community names, membership and role, your chosen display name, messages and their times, message identifiers used to recognize retries, read receipts, mute and block choices, reports and moderation outcomes. A report records the reporter, the person and message reported, the reason, status and handling details; it refers to the message rather than keeping a separate copy of its text.

Community visibility and review. In a private coach community, your Community display name and messages are visible to other participating members and the coach. Joining does not publish your private AI chats, direct coach conversations, food logs or other account records to the group. Information you put in a message can be read or copied by other participants, so avoid sharing private health or contact details. The existing Vercel and Supabase services process Community records to provide the feature. Method uses its own limited English word checks on new text and names; these checks do not identify every harmful message and do not send Community text to a separate AI moderation service. Reports about members go to the community coach. Reports about the coach go to independent Method support, rather than to the coach being reported. Authorized Method support reviewers can read the report and the current message needed to review it. If that independent reporting route is unavailable, the app tells you the report was not saved. We do not promise a response time.

Member Feed and shared Community identity. The member Feed is separate from private coach communities. Joining a private community does not join the Feed. Feed joining requires its own explicit agreement and adult self-attestation. Your Community display name and accent form your Community profile; your own chosen name can be reused across the Feed and your private communities. Feed posts and replies are visible to participating adult Method members, rather than only your private group. The Feed is text-only; private Community images are not available.

Feed records and personal hiding. We keep Feed profiles, admission records, posts, replies, reactions, blocks, reports and moderation records to provide the Feed. Hide for me in a private community stores a preference for your account and that message. It does not delete the message or hide it from anyone else. Undo hide restores your view only if the message is still available to you; a message removed for everyone stays removed. These preferences are included in our safety backups and are removed through account, message or community deletion, subject to the backup and deletion-failure exceptions below.

Removing Feed content and accounts. Removing a Feed post or reply clears that item’s stored text and hides it, while keeping its identifier and one-way retry fingerprint. Removing a post hides its conversation; it does not itself erase the stored text of replies. Feed reports refer to the post or reply rather than copying its text, and their status and handling records can remain after content removal. Deleting your account removes your Feed profile, admission, posts, replies, reactions and blocks through their account links. Removing a post through account deletion also removes its replies and associated reports; deleting a reporter removes that reporter’s reports. Deleting only a reviewer clears their reviewer identifier without deleting other people’s reports. Feed records and personal hiding preferences are included in the app’s safety-backup export; the backup and deletion-failure exceptions below still apply, including copies other participants have made.

Community drafts and notifications. An unfinished Community message and a message waiting for you to retry can be saved on your device for that account and community. Saved or rejected text is not proof it was sent. Reopening does not automatically resend it; retry is your choice. Deliberately signing out removes this saved Community work from the device, while an unexpected loss of sign-in can leave it available for recovery. When Community notifications are enabled, their notification text is generic and does not include the message body.

Leaving and removing Community content. Leaving a private coach community ends your participation and access; it does not delete messages you already posted. Removing a message hides it from the conversation but leaves a record of its removal, and the stored message can remain until account or community deletion. Deleting your account removes your Community messages and membership; associated reports, blocks, read receipts and admission records are removed through their account, message or community links. Deleting a coach account also removes the communities that coach owns and their contents. This does not remove copies other participants made, and the backup and deletion-failure exceptions below still apply. Community report records are separate from the retained support case notes described below; an independently written support case note is not erased just because its source report is removed.

A note about how we handle eating disorders

During setup we ask, privately and optionally, whether you have a history of disordered eating. If you say yes, we set a flag on your account that makes the app gentler: the AI coach stops using deficit and weight-loss language, it stops celebrating weight lost, it encourages you to work with a doctor or a dietitian, and the app hides loss-framed figures and awards from your progress screens.

We keep your answer to that question (yes, no or prefer not to say), when you gave it, and a number that goes up each time your answer or the flag changes, so the app can tell a no you gave from a question you never answered. Recording a fast is only available after you have answered no. If you answered yes, chose prefer not to say, or have not answered, the app does not let you record or change a fast, and any fasts you recorded earlier stay yours to view and remove.

It also puts a floor under your calorie target, and we would rather describe that floor exactly than let it sound stronger than it is. On your own targets screen, the app will not let you lower your calorie target below the number Method works out for you. If your target already sits below that number, you can still raise it or rebalance your protein, carbs and fat at the same total. If it sits above, you can lower it as far as that number. If your profile is too incomplete for Method to work one out, that particular rule has nothing to measure you against.

Underneath it there is a second floor, and this one is for everybody, flag or no flag. The targets screen will not accept a calorie figure below 1,500 for men or 1,200 for women: type one and the box simply puts your old number back. You can still build a plan under that number by entering protein, carbs and fat yourself, because there are real reasons somebody might and we would rather you did it in front of us than went elsewhere. The app says so at the time and offers to talk it through.

The app also sets this flag on its own if you describe a history of disordered eating in a message to the AI coach. It looks for you describing it about yourself. When that happens the app tells you, there and then, and shows you what it changes. It is set once and it is never cleared on its own.

Sending the flag to Google is a separate permission with its own switch, under Privacy in Settings, and it starts off. Allow it and the AI is told, so it can follow the rules above. Leave it off and the AI is not told, which means it will not hold back on weight-loss language. Everything the app itself does - hiding loss-framed figures and awards, and the floor under your calorie target - works either way, because none of it involves Google.

A human coach is never shown this flag or what you wrote about your eating history. If you connect a human coach, they can change your workout schedule and calorie and macro targets, including lowering them. A change to your number of training days can also change Method's calorie recommendation. This applies even when your eating-history flag is set. The flag still changes how the AI coach speaks to you and how your own targets editor handles reductions. You can disconnect your human coach at any time to stop future changes.

If this flag has been set and you do not want it, you can remove it yourself: open Settings, then Privacy, then What the AI coach can use. Removing it clears the flag and any answer you gave, so the question shows as not answered again rather than as a no, and the coach stays careful the way it is for anyone who has not answered. You can answer the question again, or change your answer, under Settings, then Privacy, then Eating history. You can also email us at methodaiapp@gmail.com and we will do it for you.

When you connect a human coach

Method AI lets you connect a human coach. It is your choice, nothing is shared until you accept an invite, and you can have at most three coaches at a time. Once you are connected, your coach can see:

• Your weekly check-ins, including anything you write in them
• Your progress photos and your meal photos
• Your body weight and your measurements
• Your nutrition logs
• Your training plan and the workouts you log
• The workouts you build for yourself - every training day and every exercise in them
• Your name, email, profile picture, goal, targets and profile basics: your age, sex and height

Your coach can also change:

• Your daily calorie and macro targets
• Your training plan - the equipment, how many days a week, which days, and how many walks a week
• Your workout program - they can write the training days, the exercises on each one and how many sets, or replace one you built yourself

You can change any of that back yourself, and your own screens tell you when a number was set by your coach.

Your chats with the AI coach are never shown to a human coach, and neither is the summary the AI keeps of them. What you told us privately during setup stays private too: your injuries, what you avoid eating, what motivates you, and anything about your history with food.

You can disconnect a coach at any time, and they immediately stop seeing anything new or current about you. Two things stay with them, and you should know this before you connect. They keep any notes they wrote about you while you were connected, and you cannot read or delete those notes. The two of you also keep your message history, which becomes read-only for both of you. Deleting your account removes both. A program they wrote stays on your account and stays yours to change, because it is what you are training on.

How we use it

To create and adjust your plan, power the AI coach, save your progress, and improve the app. We use Google's Gemini models for the AI work. What goes to Google, when the feature that needs it runs: your food and nutrition-label photos, anything you dictate to the AI coach by voice, your messages to the AI coach, and a summary of your plan and progress so the coach knows who it is talking to.

That summary is detailed, so here is what is in it whenever you use the coach: your name, age and sex; your goal, your goal weight and the pace you picked, your current weight and the change since you started; your daily targets, today's totals and what the app calculates you burn in a day; your training experience, how often and where you train, which phase you are in, and how many workouts you logged this week; how you eat and how many meals a day; your daily totals for the last week, the branded products you have saved, with their calories and macros, and when you last logged a meal. We do not send your progress photos to Google.

The rest is yours to allow or refuse, item by item, on a screen under Privacy in Settings: your body fat figure and your measurements; what you avoid eating; your injuries; what you told us motivates you; the titles of any goals you have set; your latest check-in answers including anything you wrote in them; the summary and facts the AI has remembered about you from your earlier conversations; your meal photos; and your voice when you dictate. Whether you have a history of disordered eating is a separate switch on the same screen. Refuse any of it and we stop putting it in front of the AI, which is different from sending it and asking the AI to ignore it.

One honest limit, because the sentence above would otherwise be an absolute we do not yet keep. The AI coach can look things up for itself while it is answering you - your log for a day, your weigh-ins, your check-ins - and those lookups happen on our server after your message arrives, so they are not covered by the switch. Today that means your check-in answers can still reach the AI that way, even with that item refused. The same is true of the pre-call brief your human coach can generate about you. We are closing both, and until we have, we would rather you knew which door is still open than read a promise with a hole in it.

Two more things reach Google. When you dictate to the AI coach we send your recent foods and saved products along with the audio, so your own brands come back spelled correctly. And if you have a human coach and they generate a pre-call brief about you, that brief sends your first name, goal, calorie target, which week you are in, your last four check-ins, your recent weigh-ins, your nutrition summary, and the notes your coach has written about you.

Messages between you and a human coach are never sent to any AI. Voice notes on that thread are sent as audio and played back as audio. They are not transcribed and no AI hears them.

About the AI provider

Google processes this data to generate your results, and does not use it for advertising. We have not set up any special data-retention or model-training arrangement with Google, so what we send is handled under Google's own published terms for the Gemini API. Those terms differ by tier, and we want you to know the worse case rather than the vague one: on the lower tier they allow people at Google to read what we send and to use it to improve its products, and that would include your messages to the AI coach. We have not yet confirmed which tier our account is on. We are checking, and we will say so here plainly once we know.

Choosing what the AI is told

Using the AI coach at all means the first list above goes to Google. There is no version of an AI coach that does not know your targets, your weight and what you logged today, and we would rather say that plainly than pretend it is a setting.

The second list is a different question, and it is yours to answer. We ask you once, on a screen that names each item, and you can change your answer at any time under Privacy in Settings. Say no and we do not put those things in front of the AI - with the one exception set out above, which we are closing. The coach keeps working without them. Two features do stop working, because sending is what they are: reading a meal photo, and dictating instead of typing. The app says so at the time and points you at the switch.

We keep a record of this on your account: which version of that list you were shown, what you chose, and when. If we ever add something to the list, the record no longer matches and we ask you again rather than assuming the old answer covers the new item.

Who else receives your data

• Vercel, where the app itself runs. Most of what the app does happens on a server, and that server is Vercel: your conversations with the AI coach, Community messages, names, membership, admission, read receipts, moderation and independent support reports, anything you dictate to it, meal photos being analysed, the foods and barcodes you look up, the text of every message in a coach conversation, along with its photos and voice notes, everything a coach reads about you, every change a coach makes to your plan, your weekly review, the pre-call brief a coach can generate, the nightly backup of your coaching history and your AI-coach conversations, the check-in reminders we send you, and what we read about you to write them, registering your device for notifications, deleting your account, which exercise demonstrations you open and press play on, the exercise demonstration still frames and films themselves, on their way to your screen, the exercise library you browse, the YouTube searches and video links you add to an exercise, a coach's own plan and client counts as our records show them, while we check coaches' client limits, staff support access to your account and app records, subscription records, feedback messages, support notes, case history and deletion-recovery records. Some things never reach it: your progress photos, your meal photos as they are stored, your profile picture upload from your device straight to storage without passing through Vercel, and so do your ordinary saves and reads.
• Supabase, our database and file storage provider. Everything you log is stored there.
• Google, for the AI features described above.
• Apple, if you use the iPhone app. Apple handles your purchase and delivers your notifications. Our notifications never contain the text of a message, a calorie figure or a weight.
• RevenueCat, which manages subscriptions, and only if you use the iPhone app. It receives an account identifier and your purchase history. Its software also runs on your phone, and every request it makes carries the same details about that phone whether or not you ever buy anything: an identifier for your device that Apple gives to us and that is the same for every app of ours on it, your iPhone model, the version of iOS it is running, our own app's version and its bundle identifier, the languages your phone is set to, the country your App Store account is in, and whether the app was open on screen when it asked. It does not receive your name, your email or any health data.
• Open Food Facts, when you search for a food by name or scan a barcode. It receives only the search text or the barcode digits, and it is not told who is asking.
• The USDA food database, when you photograph a meal. After the AI reads your photo it looks up a food name it generated from that photo, to check the calories and macros. The USDA receives that food name and nothing else, and is not told who is asking.
• MuscleWiki, who provide the exercise demonstration films. Opening an exercise fetches its still frame, the first time you open it in any given hour, and pressing play fetches the film; our server fetches both and passes them through to you. What reaches MuscleWiki is a request from our server naming that exercise and which demonstration of it to send, which we choose from the sex on your profile. What does not reach them is anything that identifies you: not your IP address, not your device, not your name, and no account identifier.
• YouTube (Google), if you or your coach attach a YouTube video to an exercise. A search sends YouTube only the words you typed, and a pasted link only that video's address; tapping a result or playing a video loads it directly from YouTube, which then sees your IP address and device. Nothing loads from YouTube until you tap; we store only each video's ID and title.
• Google or Apple, if you choose to sign in with them.

Exercise demonstrations

Exercise data and videos provided by MuscleWiki.com

The demonstration films in the Training tab that come from MuscleWiki are licensed from them. Their branding is part of each film and we show every film as it was delivered, uncropped and with nothing drawn over it, which is the other half of what that licence asks of us. None of their video or artwork is downloaded or kept by us: the still frame you see when you open an exercise and the film you see when you press play are both streamed through our server as you use them, and neither is ever written down on the way past. Two things are kept, and their licence allows both: we hold the web addresses those files live at for up to 28 days, and your own browser holds a still frame in its ordinary cache, for up to a day, because that is what MuscleWiki's own headers ask it to do. Those two numbers are about different things and the hour above is a third: the address we give your browser for a still frame changes every hour, so your browser stops using the copy it had and we fetch the picture again, even though it was allowed to keep that copy for a day. A day is the longest your browser may hold one; an hour is how often we ask for a new one. A YouTube video that you or your coach attach to an exercise is different: it does not pass through our server at all, and plays in YouTube's own player, straight from YouTube, as set out under who receives your data.

What we do NOT do

We do not sell your data. We never use health or fitness data for advertising, marketing, or data mining. There is no tracking tool anywhere in this app. The app contains no third-party analytics or crash-reporting SDK. We use the technical request records described above to operate and troubleshoot the service and enforce usage and spending limits. We load no fonts and no scripts from anyone else, except YouTube's own player, which runs inside its own frame, and only after you tap a video. Your device never talks to MuscleWiki: the still frame you see when you open an exercise and the film you see when you press play both come from our own server, which fetched them from MuscleWiki on your behalf. Your device does talk directly to Supabase, as described above, to RevenueCat if you are using the iPhone app, to Google or Apple if you sign in with them, and to YouTube if you tap a YouTube video on an exercise. The companies listed above are the only ones that receive anything, and each one receives it only to make a feature work.

Marketing emails

There are two places you can make an account, and they behave differently. We would rather set out both than describe one and let you assume the other matches.

If you signed up at the end of setup, there were two boxes and neither of them arrived ticked. The first covers these terms and the privacy policy, and it is required: you cannot create an account without it. The second is permission to send you emails about tips, new features and offers, and it is optional. Leaving the second box unticked gives you an account with no marketing email, and it does not stop the signup or change anything about your coaching. What we store from that second box is one true-or-false value: whether you agreed to the emails. We do not record which version of these terms you agreed to, or when. If you signed up with Apple or Google, even that one value is written to your account a moment after it is created rather than as part of it, so if that write fails we may hold nothing for you at all. Accounts created before 14 September 2026 saw a single box that covered both, and it arrived ticked. If that is you, the value we hold came from that box, and you can email us to come off the list.

The sign-in sheet asks you to tick an agreement box before creating an account with email, Apple or Google. Apple and Google can also create an account when used from the sign-in view, so those buttons ask for the box too. Signing into an existing account with email does not require this box. Earlier versions of this sheet displayed a notice that continuing meant agreement, without a checkbox. The sign-in sheet does not ask for a marketing email preference.

Either way, the way off the marketing list is to ask. Email us at methodaiapp@gmail.com and we will take you off it, or keep you off it, and it changes nothing about your account or your coaching. The two screens still differ and we would rather say so than let one stand for both: setup asks about email as its own question now, separately from the terms, and the sign-in sheet still does not ask at all. Asking the same question the same way on both screens is the half of this that is not done.

Storage and security

Your data is stored with Supabase, our database and file storage provider, with per-user access controls. Your photos and voice notes are kept in private storage that nobody can browse. Your meal photos, your progress photos and your profile picture sit in a folder belonging to your account, and your own account is the only one that can open them directly. Photos and voice notes inside a coach conversation are different: they sit in a folder keyed to that conversation rather than to either person, and neither of you opens them directly.

Whenever anyone is meant to see one of these files, the app mints a link that expires: five minutes for a meal or progress photo a coach is reading, ten minutes for a photo or voice note in a coach conversation, and one hour for a profile picture, which both of you can see once you are connected.

Deleting your account

You can delete your account at any time from Settings. When you do, we delete your profile, your food, weight, workout and measurement logs, your check-ins, your meal and progress photos, your chats with the AI coach, the summary it kept of you, your coaching connections, messages and notes on both sides, the reports you sent us through Feedback, your fasts, your starting-point record, your weekly review records and personal reflections, your Community records as described above, the account-linked AI-request records in our app database, and the device registration we use to send you notifications. Your sign-in is deleted last, after that sweep has run.

Before deletion starts, we create a recovery record. If that record cannot be created, deletion does not start. If we cannot record progress during deletion, we stop before the next step; some data may already have been removed while your sign-in still exists. The support and recovery records listed below remain separate from the account data being deleted.

Deleting an account is not one single action, and we would rather you knew how it can go wrong than read a sentence that pretends it cannot. It works through each table and each folder of files in turn, and it almost always finishes in one go. Two things can happen if it does not. If part of that sweep fails and we can still record its progress, the rest of the sweep continues and the app attempts to remove your sign-in, so your account can be gone while your data is not: that can be your logs, your chats, the summary the AI kept, coach messages and notes, the device registration, or your photos, in any amount up to all of it. The app tells you when that has happened rather than reporting a clean deletion: it says so on screen, and it asks you to try again, because a second run picks up what the first one left. If it keeps happening, or you want to be certain, email us at methodaiapp@gmail.com and we will check and finish it. If the last step fails instead, the opposite happens: your data is gone and your sign-in is not, so you can still sign in to an emptied account and delete it again.

Here is what deleting does not reach, said plainly because the alternative is a promise we do not keep:

• Our own safety backups. Once a day we back up chats, the summary the AI keeps, coaching messages and notes, your coaching connections, and any messages a coach has scheduled for you, which carry the time zone we send them in. These backups also include Community names, memberships, messages, blocks, reports, read receipts and admission evidence. We hold 14 days of those and delete the older ones ourselves, so a deleted account's data sits in them until it ages out. One thing can hold a day of backups past 14 days, and it is deliberate rather than a fault: if a night's backup misses one kind of record, we stop deleting old days until it succeeds again, because the day we would delete could be the last copy of the thing that was missed. We do not read any of this for any purpose other than recovering from a fault.
• Our hosting provider's backups. Supabase takes its own backup of the database once a day and keeps the last 7 days, and older ones roll off on their schedule rather than ours. We cannot reach into them to remove one person, and we do not hold a rewind-to-any-moment copy of the database.
• Corrections you made to foods. When you correct the calories or macros of a food, that correction is kept, and it is not removed when you delete your account.
• Anything already sent to Google for AI processing. It is held under Google's terms and we cannot recall it.
• Your subscription record as Apple and RevenueCat hold it. That copy is theirs rather than ours, and it is managed in your Apple subscription settings.
• A record of the subscription events themselves, which is ours and stays in our own database. Each row holds an event identifier, what kind of event it was, and the account identifier it belonged to. That identifier is the one your account had, so the row outlives the account it came from.
• Our own record of subscription purchases, described under What we collect. Deleting your account clears your identifier from the purchase record itself, but the messages and the log kept beside it can still carry the identifier your account had, and, if the purchase was ever moved to or claimed by another account, that account's identifier too. So, like the record above, they can outlive the account. We keep it so that a later purchase or restore on the same Apple ID is matched to the same purchase rather than counted as a new one. We have not set an end date for it, and nothing deletes it on a schedule.
• Our record of coaching invitation decisions, described under What we collect. Deleting your account clears your identifier from these coaching decision records. The other participant's identifier may remain until their account is deleted, alongside the decision details and connection identifier. We have not set an end date for these records, and nothing deletes them on a schedule. A one-time request identifier is deleted with the account that sent it.
• Support cases and their action history, described under What we collect. These are deliberately kept after your sign-in account is deleted, including its account identifier, staff-written case notes and the record of actions taken. Account-deletion recovery records also keep the attempt and coaching-connection identifiers, cleanup steps, times and unresolved items. Deleting the original feedback report does not delete a separate case note that contains information from it. We have not set an end date for these records, and they are not automatically deleted on a schedule. A case being marked resolved does not itself erase these records.

The list above is what we have checked rather than what we assume, and we are not going to turn it into a promise about everything else we have never named. Some records are deliberately kept after account deletion for the purposes described above, including support and deletion recovery. Server runtime logs are separate from those database records and follow our hosting provider's retention settings; deleting your account does not itself erase those logs. If you want us to confirm that one particular thing is deleted, email us at methodaiapp@gmail.com and we will check it and tell you.

One thing on this page we are re-checking rather than asserting, and we would rather name it than let you read past it. Some records attached to what is listed above, such as the individual sets inside a workout or our record of when we last asked RevenueCat about your subscriptions, or the separate AI allowance and spending-limit records, are removed by the database along with your account rather than by the sweep described above, and we have not re-verified recently that this still happens. We will say plainly here what we find.

Your other choices

You can edit your profile, delete individual logs, set an app passcode, disconnect a coach, and turn check-in reminders and other notifications off in Settings or in iOS Settings.

Changes

Each version of this policy carries a version number beside the date, and the app shows the same number on its copy. When we change what the app does with your data, both move together.

Not medical advice

Method AI provides fitness and nutrition coaching for general wellness. It is not medical advice, diagnosis, or treatment. Consult a physician before starting any training, nutrition, or fasting program.

Contact

Questions or requests: methodaiapp@gmail.com