This Privacy Policy explains how Peachy Life Pty Ltd (ACN 680 350 163, ABN 52 680 350 163) ("we", "us", "our") collects, uses, stores, and protects your personal information when you use The Peachy Life mobile application and website (together, "the Service").
We have written this policy in plain English, but it is legally complete. Please read it carefully. If you have questions, email us at hello@thepeachylifecompany.com.
1. Who We Are
Peachy Life Pty Ltd
Sydney, New South Wales, Australia
Email: hello@thepeachylifecompany.com
Website: thepeachylifecompany.com
For users in the United Kingdom, Peachy Life Pty Ltd acts as the data controller within the meaning of the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018.
For users in Australia, we are bound by the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs). Although the small business exemption under the Privacy Act may technically apply based on our current revenue, we voluntarily comply with the APPs in full because we handle health information, which is always subject to the Act regardless of business size.
For users in California, USA, please also read the dedicated section at the end of this policy covering your rights under the California Consumer Privacy Act (CCPA) and related California laws.
2. What Data We Collect and Why
We only collect data that is necessary to provide and improve the Service.
2.1 Account and Identity Data
- What: Email address and display name.
- Why: To create and authenticate your account, and to identify you within the app.
- How collected: You provide this directly when you register.
- Retention: For the duration of your account. Erased when you delete your account.
- UK GDPR lawful basis: Performance of a contract (Art. 6(1)(b)) — you cannot use the Service without an account.
2.1a Date of Birth and Age Check
- What: Three items, recorded once when you create an account. Date of birth: the day, month and year. Birth year: the year again, kept on its own, because our servers check it (Section 13). Verification time: the date and time you completed the age check. If you created your account with an earlier version of the app, we did not ask for the day or month, and we do not hold them.
- Why: To confirm you are old enough to use the Service, and to keep a record that we carried out that check. We also use your age in years, worked out from your birth year, for three things. Our servers check it before you take a wellbeing assessment, because assessments are for adults only. If you set a nutrition goal, the app offers your age for the calorie estimate, and you confirm or change it. If you use Activity, the app sets your heart-rate zones from it.
- How collected: If you start from the welcome screen, you choose your date of birth first, before any account exists and before we ask anything about your wellbeing. It stays in the app's memory on your phone. We do not save it anywhere until your account is created, and if the app is shut down before then, it is lost. This is the same whether you then create your account with email, Google or Apple. If you are new and sign in with Google or Apple from the log-in screen instead, you choose your date of birth straight after that sign-in creates your account, before we ask anything about your wellbeing. The list of years runs up to this year, so you can answer honestly whatever your age.
- If your answer shows you are under 18: We never store the date you chose, and we ask you nothing else. If you started from the welcome screen, no account exists yet, so there is nothing to delete, and we keep no record of your answer or of the block. If you signed in with Google or Apple from the log-in screen, an account exists for the few seconds in between, and we delete it. That deletion removes the account itself, your sign-in credentials and anything attached to them, and we sign you out. After deleting such an account, what we keep is a record that a signup was blocked and the time it happened. That record contains nothing that identifies you: no account reference, no email address, no date of birth. We then show you information about support services suitable for your age, and the signup process ends.
- Retention: For the duration of your account. All three are erased when you delete your account, at the same time as the rest of your account data.
- UK GDPR lawful basis: Performance of a contract (Art. 6(1)(b)). Our Terms let only people aged 18 and over use the Service, and we cannot provide it without checking.
- Why we collect it (Australia): Collecting your date of birth is reasonably necessary for our functions and activities under Australian Privacy Principle 3, because we operate an age check, and we tell you about it before we collect it under Australian Privacy Principle 5.
We do not use your date of birth to target advertising, and we do not run advertising. Apart from the uses listed above, we do not use it to decide what you see.
2.1b Consent and Agreement Records
- What: When you accept our Terms of Service and this Privacy Policy, we record the date and time you accepted, the version of the Terms of Service you accepted, and the version of this Privacy Policy you accepted. You accept by ticking the box when you sign up with email, or by tapping "Accept and continue" when you sign up with Google or Apple. Versions are identified by their version date.
- Why: So we hold an accurate record of what you agreed to and when. Without it we cannot show that we obtained your agreement, and we cannot tell you which version of these documents applied to you.
- How collected: Recorded automatically when you complete signup.
- Retention: For the duration of your account, and for 7 years after you delete it. We keep it because it is the evidence that you consented. It is stored apart from your wellbeing data, contains no health information, and we use it for nothing else.
Acceptances before 25 August 2026. We began recording document versions in August 2026. If you accepted our Terms and Privacy Policy before then, your record holds the date and time of your acceptance and nothing more. It does not identify which version of the documents you saw. We cannot reconstruct the exact text displayed to you at that moment, and we will not claim otherwise. Email us and we will tell you what we do hold, and which published version was current on that date.
2.1c How You Describe Yourself
- What: Your answer to "How do you describe yourself?": Woman, Man, Non-binary or Prefer not to say.
- Why: To choose the figure the app shows on your body map.
- How collected: You answer straight after your date of birth. You need to pick one to carry on, and "Prefer not to say" is always a choice. If you start from the welcome screen, your answer stays in the app's memory on your phone, and we record it with your date of birth once your account is created. If you sign in with Google or Apple from the log-in screen, we save it as soon as you answer. You can change it at any time in Settings. If you created your account with an earlier version of the app, we did not ask this question.
- Not sent to AI, and not used for advertising. We do not send your answer to any AI provider, and we do not add it to our analytics.
- UK GDPR lawful basis: Legitimate interests (Art. 6(1)(f)): showing you a body map that matches how you describe yourself. You can object at any time by choosing "Prefer not to say" or changing your answer in Settings, or by contacting us.
- Retention: For the duration of your account. Included when you export your data, and erased when you delete your account.
2.2 Mood and Wellbeing Data
- What: Mood scores, emotion words, activity tags, responses to validated wellbeing check-ins like the WHO-5, any signals you create yourself under names you choose, and associated timestamps you submit.
- Why: To generate personalised mood insights, trends, and weekly reports for you.
- How collected: You enter this data directly through the app.
- Special category status: This data constitutes health or mental health data under UK GDPR Article 9 and Australian law. We treat it accordingly (see Section 3).
- UK GDPR lawful basis: Explicit consent (Art. 6(1)(a) and Art. 9(2)(a)). You give this consent when you create an account and begin logging. You can withdraw consent at any time by deleting your data or account.
2.2a Caffeine and Alcohol
- What: If you switch on caffeine tracking, the caffeinated drinks you log and the drink sources you save. Alcohol logging is built but is not yet switched on for anyone. We are naming it here because the capability exists in the app you have installed; if and when we switch it on, it will be off until you turn it on, exactly like caffeine.
- Why: So the app can put a drink beside the mood you logged that day.
- How collected: You enter them. Caffeine tracking is off until you switch it on in Settings → Privacy & data. Switching it off again deletes everything you logged under it.
- Special category status: We treat these entries to the same standard as health data, because of what they sit beside (see Section 3).
- UK GDPR lawful basis: Explicit consent (Art. 6(1)(a) and Art. 9(2)(a)), given when you switch the tracking on.
- Retention: For the duration of your account, or until you switch the tracking off. Erased when you delete your account.
2.2b Coping Cards
- What: When you use a coping card from the app's library, which card you used and when, and any answers or notes you add to it.
- Why: So your cards are there when you need them, on whatever device you are signed in to.
- How collected: You write them. Nothing you type into a coping card is sent to an AI provider. Your weekly insight does receive the names and types of the coping cards you use most, how far along you are with each, and how many days you used one, and if you start a chat from a card, the chat opens with that card's name (Section 5a).
- Special category status: Your coping-card entries are health data and are covered by Section 3 in full.
- UK GDPR lawful basis: Explicit consent (Art. 6(1)(a) and Art. 9(2)(a)).
- Retention: For the duration of your account. Erased when you delete your account.
2.2c Records Our System Writes About You
Some records in your account are written by our system rather than by you. You should know they exist, because they are about you and they feed what the app tells you.
- Distress signals from assessments. When an assessment answer indicates a risk to your safety, we record that it did, and any follow-up check-in the app scheduled.
- Themes. Recurring subjects drawn from your journal entries, so your weekly summary can refer to them.
- Readings the system works out. Readiness figures from your wearable data, other values the app derives from what you have logged, a record of which findings we have already shown you so the same one is not repeated every week, and mid-week observations (we no longer create these, but older ones are kept).
These are our own inferences, not things you told us, and we treat them as special category data because of what they are derived from. Distress signals, scheduled follow-ups, themes and mid-week observations are included in your data export; readiness figures, the other derived values and the record of findings shown are not. All of them are erased with your account. You can ask us about any of them at hello@thepeachylifecompany.com.
2.3 Journal Entries
- What: Free-text content you write in the journalling feature.
- Why: To provide a private, secure space for self-reflection and to connect journal content with your broader wellbeing picture (where you choose to).
- How collected: You type this directly into the app.
- Special category status: May contain sensitive mental health information. Treated as special category data.
- UK GDPR lawful basis: Explicit consent (Art. 6(1)(a) and Art. 9(2)(a)).
2.4 AI Conversation Messages
- What: Messages you send to, and responses you receive from, the AI chat feature.
- Why: To provide the AI coaching and support feature.
- How collected: You type or dictate messages. To generate a reply we send your message, and a rolling summary of the recent conversation, to an external AI provider. Section 5a sets out exactly what we send and what we do not. If you dictate rather than type, Section 2.9 explains where the audio goes.
- Retention: AI conversation messages are retained for up to 90 days and then deleted. This deletion process is actively being implemented; in the interim, messages may be retained until the automated deletion job is live.
- Special category status: May contain sensitive mental health information. Treated as special category data.
- UK GDPR lawful basis: Explicit consent (Art. 6(1)(a) and Art. 9(2)(a)).
2.4a Notes the AI Assistant Keeps
- What: Separately from the messages themselves, the assistant can keep short notes about things you have told it, so it does not ask you the same question every week. A note is a sentence or two, written by our system, drawn from what you said.
- Why: So a conversation can pick up where the last one left off. The notes are sent to Anthropic with your chat messages for that reason (Section 5a).
- How collected: Automatically, from your conversations, and only while you have session memory switched on. It is off until you switch it on, and you are asked first. You can read the notes in the app, delete any one of them, or switch session memory off, which deletes all of them.
- Special category status: These notes are drawn from conversations that may be about your mental health, and are treated as special category data.
- UK GDPR lawful basis: Explicit consent (Art. 6(1)(a) and Art. 9(2)(a)).
- Retention: 90 days from when the note was written, then deleted automatically, usually within a day after that.
2.5 Biometric and Health Metrics
- What: Health and activity metrics from the integrations you choose to enable. What we read depends on the platform, and we list it in full rather than summarising it.
- From Google Health Connect (Android): step count; heart rate; sleep, including its stages; resting heart rate; heart-rate variability; total energy burned; active energy burned; basal (resting) metabolic rate; exercise sessions; and body weight. We read body weight only for the weight log described below, and only if you allow it in Health Connect. We do not read height or distance on Android.
- From Apple Health (iOS): step count; active energy burned; basal energy burned; workouts; sleep, including its stages; heart rate; heart-rate variability; resting heart rate; body weight; and height. Apple Health asks your permission for each of these separately, and anything you do not grant, we never see.
- From Garmin Connect™: once you connect your Garmin account, Garmin sends us the following from your Garmin devices, and we store it.
- Daily activity: your daily summary, including steps, distance, active calories, and minimum, maximum and resting heart rate. We do not keep the heart-rate samples Garmin takes through the day.
- Stress and Body Battery™ energy levels through the day.
- Sleep, including its duration, stages and breathing rate.
- Heart-rate variability overnight.
- Blood oxygen (pulse ox) readings.
- Breathing rate through the day.
- Body composition, if you use a Garmin scale: weight, BMI, body fat, muscle and bone mass, and body water.
- Workouts and activities you record on your watch or edit in Garmin Connect, including the type of activity, when it started, how long it lasted, distance, calories, heart rate, and the model of Garmin device that recorded it.
If you disconnect Garmin, in the app or in Garmin Connect, we stop receiving new Garmin data. The Garmin data we already hold stays in your account, so your history and trends stay complete, until you delete your account or ask us to delete it (hello@thepeachylifecompany.com). If you turn off health or activity sharing in Garmin Connect, we stop storing that kind of data.
Garmin's notifications to us. Each time Garmin sends us your data, we keep a copy of that notification as Garmin sent it for 90 days, so we can check our records against it, and then delete it. The incoming file is deleted as soon as we have processed it, and in any case within 7 days.
- Weight log. If you use Food & Nutrition, you can keep a weight log.
- What we store. We store the weigh-ins you type in yourself: the weight and when you measured it. Weigh-ins read from Apple Health or Health Connect are copied into your account with the time they were measured, so your log, its 7-day trend and the goal form can show them. Disconnecting a health source stops new syncs and does not erase weigh-ins already copied into your account. They are erased when you delete your account.
- Goal weight. If you set a goal weight, we store it too.
- What we use it for. We use your weight to show your log and trend, and, if you ask, to suggest the weight used for your calorie estimate in Macro Goals.
- Safeguard. The weight log is hidden while the eating-disorder safeguard is switched on. Switching the safeguard on deletes any goal weight you have set.
- Deleting and exporting. You can delete a weigh-in at any time. Your weigh-ins and goal weight are included when you export your data, and deleted when you delete your account.
- Status and basis. Body weight is health data, which is special category data. It is processed only because you turned on Food & Nutrition tracking, which is your explicit consent (Art. 6(1)(a) and Art. 9(2)(a)).
- Why: To enrich your wellbeing picture by correlating physical health data with mood patterns.
- How collected: Only with your explicit, separate in-app permission for each integration. You can revoke access at any time from your device's health app settings or within The Peachy Life app.
- Special category status: Biometric and health data is special category data. We do not collect this unless you actively grant permission.
- UK GDPR lawful basis: Explicit consent (Art. 6(1)(a) and Art. 9(2)(a)).
2.6 Usage Analytics and Crash Reporting
- What: Which features you use and general navigation flows, and technical diagnostic data when the app crashes, such as device model, operating system version and the state of the app at the time. If you turn on Allow analytics, it also includes some health information, listed below.
- Why: To understand how the app is used, prioritise improvements, and diagnose and fix crashes. We use it only to improve the app.
- Beta testers: If you are testing a pre-release version of the app and answer the optional welcome questions, we also record your two answers, each chosen from a fixed list: how you describe yourself (a friend or family member, a healthcare professional, a wellbeing advocate, an app developer or a beta tester) and how you heard about us (for example a TestFlight link, a personal recommendation, our website or a social event). They are sent only if you turn on Allow analytics, they go to Firebase Analytics only, never to PostHog, and you can skip either question.
- How collected: In the app and in the web app, via PostHog (product analytics, hosted in the European Union), and in the app via Firebase Crashlytics (crash reporting). During a changeover period that ends no later than 31 December 2026, the app also sends the same usage analytics to Firebase Analytics (Google Analytics); after that date it no longer does. Analytics and crash reporting are off until you turn on Allow analytics in Settings → Privacy & data (or at the same choice in Meet Peachy), and you can turn them off at any time. On our website, see Section 2.6a.
- The health information sent when you turn on Allow analytics. This sends our analytics providers how you use the app, and some health information:
- your mood range, and whether it was in the distress range
- your wellbeing check-in range, and whether your wellbeing is trending up, down or steady
- which mood signals you choose for your check-in, such as anxiety
- your workouts: the type, how you entered it and how many minutes
- your daily food grade, and a broad range for the calories you logged
- the category of a goal or habit you create, complete or archive, such as sleep
- which health area you open: weight, or one of the body views (today, sleep, heart, activity)
- which kind of wellbeing practice you start, finish or stop, such as breathing, grounding or sleep, or an activity of your own
- when you import your journal from Notion: whether it started, finished (with a rough count) or failed, and why. Never what is in it
- when a weight or unwell check-in reminder is set
- in a week when your weekly report is kept shorter because your mood has been hard, whether you switch between its shorter and longer versions
PostHog does not receive your mood range, whether it was in the distress range, or your wellbeing check-in range. During the changeover, those three items go to Google Analytics only.
- What is never sent: It never includes your journal, messages or anything else you type, your exact scores, your name or your email.
- People who agreed before are asked again. If you turned on Allow analytics before this version, the app asks you again, in the app, to agree to this updated list. Until you do, the items in the health information list above that were added since your earlier agreement are not sent.
- This data is pseudonymous, not anonymous. When you have Allow analytics on, we give PostHog an analytics ID made from your account by a one-way calculation. It is not your name, email or account number, and PostHog cannot work back from it to any of those. Because it is the same ID on every device where you sign in, PostHog can see that the app on your phone and the web app belong to the same person. That is why we treat it as personal information. We cannot read your journal or chat content from it. PostHog stores it in the European Union (Frankfurt). PostHog Inc. is a US company and may also process it in the United States and elsewhere (see Section 6). Google, during the changeover, stores its copy in the United States, keyed to a random ID for each installation, not to your analytics ID.
- UK GDPR lawful basis: Your explicit consent (Art. 6(1)(a) and, for the health information above, Art. 9(2)(a)), given when you turn on Allow analytics. You can withdraw it at any time by turning Allow analytics off; withdrawal does not affect what was sent before.
- Events sent by our servers. A few analytics events are sent by our servers rather than the app, for example that a weekly report was created or a reminder was sent. Our servers check that you have Allow analytics on before sending them, and send nothing for people who have it off.
2.6a Website Measurement
- What: When you visit our website, it sends us short notes about how the visit went, through a measurement tool of our own. For each page you view, it records:
- which of our pages it was
- how far down the page you scrolled, and which parts of the page came into view
- whether you clicked a button to request an invite or get the app, and which part of the page that button was in
- how far you got with the invite form: whether you saw it, started it, sent it or hit an error, and, if you sent it, whether you chose iPhone or Android
- whether you sent the newsletter sign-up form or a message through the contact form (never what you typed)
- how many questions you opened in the page's frequently asked questions
- whether you played or finished a video, if the page has one
- which other website you went to, if you followed a link off our site
- a broad description of how you arrived: from a search engine, an AI assistant, social media, another page of ours, a QR code on one of our flyers, one of our emails or newsletters, another link of ours tagged for a campaign, another website, or no link at all. If the link you followed carries campaign tags, your browser uses them to pick one of these descriptions; the tags themselves are never sent
- the country the visit came from, as Cloudflare reports it, and whether the device is a phone, a tablet or a computer
- What is never recorded: Nothing is stored on your device: no cookies, no local storage, nothing else. Nothing on your device gives you an ID. To count how many different people visit in a day, PostHog works out a code from your IP address and browser details mixed with a random value that changes every day and is then deleted. The code is the same for your visits on one day and different the next, so we can count daily visitors but cannot follow anyone from one day to the next. PostHog does not keep your IP address, and the code cannot be turned back into it. We do not keep your IP address, your browser's identifying details (its user agent), your city, the full web address you visited or the address of the site that sent you. We never record your email address or anything else you type. We never record clicks on crisis-support services, including the phone numbers and links on our crisis page and in our crisis-support boxes.
- Why: To see which parts of our website help people understand The Peachy Life, where people stop reading, and whether the invite form works for them, so we can improve the site.
- How collected: A small script on our website, served from our own web address, sends each note back to our own web address. Cloudflare, which already hosts our website, receives it there and stores it for us. Until 31 December 2026 we are also trying PostHog, an analytics service, for the same measurement. Its script sends the same kind of notes to our own web address, which passes them to PostHog. PostHog stores them in the European Union (Frankfurt). PostHog Inc. is a US company and may also process them in the United States and elsewhere (see Section 6).
- How to object: Turn on Global Privacy Control (GPC) or Do Not Track (DNT) in your browser. When either is on, the script sends nothing, and our server discards any note that arrives carrying either signal. Blocking scripts on our website also stops it. None of this changes how the website works for you. These signals switch off our own measurement; they may not switch off Cloudflare Web Analytics. The same signals and script blocking switch off PostHog on our website.
- How long we keep it: Each note is kept for 3 months, then deleted automatically. We keep daily totals worked out from the notes, such as how many invite requests came from search engines on a given day, for up to 2 years. A daily total says nothing about any single visit. Notes sent to PostHog are kept for 1 year.
- Whether it is personal information: We designed this measurement so that it does not identify you. Nothing is stored on your device. Our own measurement gives you no ID, and nothing links one of its notes to another. PostHog's daily code, described above, links the notes from your visits on a single day and cannot link one day to the next. If any of this did count as personal information in a particular case, the following applies.
- UK: The Privacy and Electronic Communications Regulations, as amended by the Data (Use and Access) Act 2025, allow information to be collected for statistical purposes, to improve a website, without asking for consent, as long as visitors are told clearly (this section) and given a simple way to object (above). Our lawful basis under the UK GDPR is legitimate interests (Art. 6(1)(f)): understanding how our website is used, so we can improve it. You can object at any time, as above.
- European Union and EEA: Our lawful basis under the GDPR is legitimate interests (Art. 6(1)(f)), for the same purpose. You can object at any time, as above.
- Australia: This section is our notice of what we collect and why. If any of it were personal information under the Privacy Act 1988, we would handle it under the Australian Privacy Principles and use it only for the purpose described here.
2.7 Communications Data
- What: The content of any emails or messages you send us, and your email address.
- Why: To respond to your enquiries and support requests.
- UK GDPR lawful basis: Legitimate interests (Art. 6(1)(f)) — responding to communications you initiate.
2.8 Psychometric Assessments
- What: Your answers to structured wellbeing assessments, the scores calculated from them, and the written reports we generate to help you interpret your results.
- Why: To give you a structured view of specific areas of wellbeing over time, and to explain what your results mean in plain language.
- How collected: You complete an assessment in the app. Taking one is your choice, and the Service works without them.
- Special category status: Health data under UK GDPR Article 9 and health information under the Privacy Act 1988.
- What we send to the AI provider: When we generate a written report we send a descriptive band rather than your result, for example "a developing area". We do not send your numeric score, and we do not send your answers to individual questions.
- Retention: For the duration of your account. Erased when you delete your account.
2.9 Dictated Audio
- What: Audio of anything you dictate instead of typing, including journal entries, mood notes and chat messages.
- Why: To convert your speech into text.
- How collected: When you tap the microphone, your device's built-in speech recognition captures the audio.
- Where it goes: Dictation is not processed on your device. Our app uses the speech recogniser built into iOS or Android, configured for server-side recognition, so the audio is sent to Apple or Google in the United States to be transcribed. Whatever you say reaches them, which can include distress or health disclosures.
- If you would rather it did not: Type instead of dictating. Nothing is sent for transcription unless you use the microphone.
- What we keep: We store the resulting text as part of the entry you were writing. We do not store the audio.
2.10 Food and Nutrition Logging
- What: Food and drink you log, and the nutrition information attached to it. If you ask the app to read a photograph or a screenshot, we use the image to do that and do not keep it.
- Why: To let you keep a food diary and see it alongside your mood and wellbeing data.
- Meal photographs go to OpenAI. If you log food by taking a photo of a meal, the photograph is sent to OpenAI in the United States to identify what is in it. There is no setting that keeps this on your device or routes it elsewhere. If you would rather your photographs did not leave the device, log food by searching or typing instead.
- Nutrition labels are read by OpenAI, or on your phone. While you line up the shot, your phone checks the camera picture itself, and those frames never leave your device. What happens to the photograph you take depends on whether you have accepted AI features. If you have, and you are online, the photograph is sent to OpenAI in the United States to read the panel; if that fails or takes too long, your phone reads it instead. If you have not, your phone reads the label itself and the photograph does not leave your device.
- Recipe pages work the same way. When you photograph a page from a recipe book (up to three pages), and you have accepted AI features and are online, the photographs are sent to OpenAI to read the title, the servings and the ingredient lines. Otherwise your phone reads the pages itself and sends only the ingredient lines to our servers, with no AI involved.
- Screenshots of another food diary go to OpenAI. If you bring in food entries from a screenshot of another app's food diary, the screenshot is sent to OpenAI to read the rows. This works only if you have accepted AI features, and there is no on-device option.
- Recipes you import from a link. When you give the app a link to a recipe, our server fetches that web page. If the page lists its ingredients in a standard form, no AI is involved. If it does not, and you have accepted AI features, text from the page is sent to Anthropic in the United States to find the ingredient lines. Ingredient lines our food library cannot match are also sent to Anthropic, to estimate their nutrition, and again only if you have accepted AI features.
- We do not keep these images. A photograph or screenshot is sent, read and discarded. It is not stored in your account or on our servers. What OpenAI does with it is governed by its terms (Section 5a).
- Food searches are not private to us. When you search our food database, the search term is sent from our servers to USDA FoodData Central, a United States federal government agency, to look up nutrition data.
- Barcode and packaged-product lookups go somewhere else again. When you scan a barcode or search for a packaged product, your phone asks Open Food Facts, a French non-profit database, directly. That request does not pass through our servers, so we do not see it, and they see your device's IP address. If you would rather that did not happen, add the food by typing it in.
- Meals you describe in your own words go to our AI provider. If you type a meal as a sentence, the text is sent to Anthropic in the United States to turn it into food items. Searching for a food sends only the search term, as described above.
- Retention: For the duration of your account. Erased when you delete your account.
2.11 Goal Sharing and Accountability Partners
If you choose to share a goal with someone, two things happen that involve another person's information as well as your own.
We collect their email address. You give us the email address of the person you nominate. That is personal information about someone who is not our user and has not read this policy. We use it only to send them the updates you asked us to send, we do not add them to any mailing list, and we do not use it for anything else. If you nominate someone, please make sure they are happy to hear from us first.
We disclose your goal data to them. The person you nominate receives your goal and your progress against it. Once we have sent it to them, we cannot retrieve it or control what they do with it. Only share with someone you trust.
You can stop sharing at any time in the app. That stops future updates and does not undo updates already sent. If you have been nominated by someone and want your email address removed, email hello@thepeachylifecompany.com and we will remove it.
2.12 Journal Import from Notion
Journal import from Notion (optional). If you connect a Notion workspace, we receive the pages you choose to import and store an access token so we can keep them in sync. Imported pages are saved as journal entries. They are only sent for AI processing if you separately allow it in the import settings. You can disconnect Notion at any time in Settings.
2.13 Habits and Goals
- What: The goals and habits you set up, including their names, categories and schedules; the days you mark a habit Done; the days you answer Not today; and your progress against your goals.
- Why: To show you your own progress. Where your app includes habit insights, the Done and Not-today answers for movement, fitness, sleep, rest, connection and relationships habits are also compared with your mood check-ins, so your weekly report can show whether days you did a habit tended to feel different.
- How collected: You enter them. The comparison runs on your phone, and your own report keeps only the overall findings, labelled by the habit's category and never by its name, over at most the last 84 days. Each habit has a Use in insights switch, on by default, that leaves it out of the comparison.
- Never sent to an AI model. Your habits, the answers you give them, the findings drawn from them and the titles of your goals are not sent to any AI provider. If you write about a habit in a chat message, that text is sent as part of the message, like anything else you type (Section 5a).
- Special category status: Sleep, rest and movement habits can say something about your health, so we treat this data as health data (see Section 3).
- UK GDPR lawful basis: Explicit consent (Art. 6(1)(a) and Art. 9(2)(a)), given when you set up a habit or goal. You can withdraw it by deleting the habit or goal, or your account.
- Retention: For the duration of your account. Not-today answers older than 84 days are removed whenever the habit is next saved. Everything else is erased when you delete your account.
2.14 Illness and Cycle Marks
If you choose to track days you feel unwell or your cycle, we store only what you mark: for unwell days, the date, a broad body area and a level; for your cycle, the dates. Peachy's AI uses these marks in your weekly insights and, when you ask about your mood or patterns, in chat. To do that they are sent to our AI provider, which processes them on our behalf. They are never used for advertising, never sold, and never shown on share cards, notifications or widgets. You can switch either off at any time in Settings → Privacy & data, which deletes everything you marked; past insights and chats that mention them stay until you delete them.
2.15 Recipes and Recipe Sharing
- What: Recipes you save or write, including their ingredients, method and any notes; the foods you mark as favourites or add yourself; and the products you save. If you share a recipe, a short-lived record that connects the share link to your account.
- Why: So your recipes are available on any device you sign in to, and so a recipe you share arrives.
- How sharing works, stated plainly: sharing a recipe creates a link. If someone opens it and accepts, our servers write a copy of that recipe into their account. The copy does not carry your account identifier, and once it exists it is theirs: we cannot retrieve it, and stopping sharing does not remove a copy already made. So that the link itself does not contain your account identifier, our server keeps one record connecting the link to your account. That record is deleted when the link expires after 7 days, when you stop sharing, or when you delete your account, whichever comes first, and it is not part of your data export.
- UK GDPR lawful basis: Consent (Art. 6(1)(a)) for the recipes themselves; performance of our agreement with you (Art. 6(1)(b)) for delivering a share you asked us to make.
- Retention: For the duration of your account. Erased when you delete your account. A copy already delivered to another user lives in their account and is erased when they erase it.
2.16 Streaks, Quests and Other Progress Records
- What: As you use the app it keeps a record of that use: your streak and points; daily quests and which you completed; wellness activities and sessions you logged; workouts you recorded or imported, and any workout templates you saved; your goals' outcomes; answers to any in-app survey you chose to answer; assessments you started but did not finish; support issues you raised in the app; notes you add to days on your mood history; and, if you joined the beta programme, that you did. Habits are covered in Section 2.13.
- Why: To show you your own progress and to run these features.
- How collected: Mostly as a by-product of using the app, rather than by asking you. In Settings → Display mode you can hide streaks, scores and celebrations; hiding them changes what you see, not what is recorded.
- UK GDPR lawful basis: Consent (Art. 6(1)(a)) for features you choose to use; our legitimate interest in operating the Service (Art. 6(1)(f)) for the app's own counters, such as your streak.
- Retention: For the duration of your account. Erased when you delete your account.
3. Special Category Data — Health Information
Mood scores, journal content, wellbeing self-assessments, AI conversation messages, and biometric data are all treated as health or mental health data. Under UK GDPR, this is "special category" data that attracts heightened protections under Article 9. Under Australian law, it is "sensitive information" and "health information" under the Privacy Act 1988.
We process this data exclusively on the basis of your explicit, freely given, informed consent. This means:
- We explain clearly what data we collect and how we use it before you provide it.
- You can withdraw consent at any time without penalty by exporting and deleting your data through the app's Settings, or by contacting us.
- We never use your health data for advertising, profiling, or sale to third parties.
- Access to this data is limited. Within our own systems only you and our authorised engineers can read it, engineers are bound by confidentiality obligations, and their access is audit-logged. Some of it also goes to the external companies listed in Section 5 so that the features you use can work: the AI companion, and speech-to-text if you dictate. Sections 5a and 2.9 set out exactly what goes where.
We also apply data minimisation: we only ask you for data that is directly useful to you. Beyond the analytics and crash reporting you choose to turn on, described in Section 2.6, and the progress records described in Section 2.16, we do not collect information about you in the background. We never collect your location, your contacts, or anything from other apps you have not connected yourself.
4. Data We Do Not Collect
- Payment information: All payments are processed directly by Apple (App Store) or Google (Play Store). We receive no raw payment card data, bank details, or full billing addresses. We may receive a transaction confirmation and subscription status from the platform.
- Advertising identifiers: We do not use advertising SDKs, tracking pixels, or ad identifiers such as IDFA or GAID.
- Device identifiers beyond what Firebase requires: Firebase Authentication may generate an anonymous installation ID for technical operation. We do not use this for advertising.
- Location data: We do not collect precise or coarse location data. The one exception is our website measurement (Section 2.6a), which records the country a visit came from, as Cloudflare reports it, and nothing finer.
- Contact lists or social graph: We do not access your contacts, social accounts, or friends lists.
5. Third-Party Data Processors
We use the following third-party services to operate The Peachy Life. Each is a data processor acting on our instruction — they may not use your data for their own purposes.
| Recipient | Purpose | What it receives | Country | Privacy information |
|---|---|---|---|---|
| Anthropic, PBC | Default AI provider: chat replies, wellbeing insights, psychometric report text, reading meals you describe and recipes you import from a link | Your chat messages, which may contain health disclosures; rolling summaries of recent conversation; journal text you submit for analysis; descriptive result bands from assessments and WHO-5 band labels, never numeric scores; summaries derived from your wearable data such as sleep, heart-rate variability, activity and engagement; context about your goals (never their titles), workouts, wellness sessions and food logs, and which days you checked in, journalled, completed a quest or used a coping card; the text of a meal you describe; and, when you import a recipe from a link, text from that web page and ingredient lines whose nutrition needs estimating (Section 2.10) | United States | anthropic.com/legal/privacy |
| OpenAI, L.L.C. | Reading food photographs and screenshots, and standby provider for psychometric report text | The photograph or screenshot you ask the app to read: a meal, a nutrition label, a recipe page, or a screenshot of another app's food diary (Section 2.10). Also, only if we switch psychometric reports to it while Anthropic is unavailable, the descriptive assessment bands those reports are written from. Never your chat | United States | openai.com/policies/privacy-policy |
| Google Firebase — Cloud Firestore | Primary database for your app data | Mood entries, journal entries, AI messages, assessment results, food logs, settings, wearable records | Australia (australia-southeast1) | firebase.google.com/support/privacy |
| Google Firebase — Authentication | Account authentication | Email address, display name, sign-in metadata | United States | firebase.google.com/support/privacy |
| Google Firebase — Analytics and Crashlytics | Usage analytics and crash reporting, only if you turn on Allow analytics. Firebase Analytics only until 31 December 2026 | Usage events, crash diagnostics, device and installation identifiers, and a shortened scrambled form of your account identifier. Some health information, as listed in Section 2.6 (for example mood and wellbeing ranges, workouts, food grade, goal and habit categories). For beta testers who answer the optional welcome questions, how they describe themselves and how they heard about us (Section 2.6). Never your journal, messages, anything else you type, or your exact scores | United States | firebase.google.com/support/privacy |
| PostHog Inc. (PostHog Cloud EU) | Product analytics for the app and web app, only if you turn on Allow analytics; cookieless website measurement | App and web app: usage events, your analytics ID (Section 2.6), device and app version, country, and the health information listed in Section 2.6 except your mood, distress and wellbeing check-in ranges. Never your journal, messages, anything else you type, your exact scores, your name, email or account number. Website: the items in Section 2.6a, with no ID stored on your device | European Union (Frankfurt). PostHog Inc. is a US company; see Section 6 | posthog.com/privacy |
| Apple (iOS) | Speech-to-text; app distribution; in-app purchases; optional Apple Health integration; push notification delivery | Audio you dictate. Payments handled entirely by Apple. Health data only with your permission. | United States | apple.com/legal/privacy |
| Google (Android) | Speech-to-text; app distribution; in-app purchases; optional Health Connect integration; push notification delivery | Audio you dictate. Payments handled entirely by Google. Health data only with your permission. | United States | policies.google.com/privacy |
| USDA FoodData Central | Nutrition database lookups | The food search terms you enter | United States (federal government agency) | fdc.nal.usda.gov |
| Open Food Facts (Open Food Facts association, France) | Barcode and packaged-food lookups | The barcode or search text, sent directly from your device, and your device's IP address | France | world.openfoodfacts.org/privacy |
| Garmin | Optional integration syncing fitness and biometric data from Garmin devices | Fitness and biometric metrics you choose to sync, only if you connect a Garmin account | United States | garmin.com privacy policy |
| Notion (Notion Labs, Inc., United States) | Optional journal import | The pages you choose to import, and an access token for your workspace | United States | notion.so/privacy |
| Cloudflare, Inc. | Website hosting, cookieless website analytics (Cloudflare Web Analytics), and storing our own website measurement (Section 2.6a) | Like any web host, Cloudflare handles each request to our website, including your IP address; we do not keep it. Cloudflare Web Analytics: aggregated website statistics. Our own measurement: the items listed in Section 2.6a, with no ID, IP address or user agent kept. | United States / global edge network | cloudflare.com/privacypolicy |
| Web3Forms | Delivers messages sent through the website contact form and beta signup form | Your email address, the content of your message, and — if you sign up for the beta — whether you told us you use an iPhone or an Android phone | United States | web3forms.com/privacy |
| Buttondown | Beta signup and newsletter mailing list | Your email address; for beta signups whether you use an iPhone or an Android phone; and a broad description of how you arrived (for example "from a search engine" or "from our newsletter"), not sent if Global Privacy Control or Do Not Track is on | United States | buttondown.com/legal/privacy |
We do not authorise any of our processors to use your data for their own purposes, to sell your data, or to transfer it to further parties beyond what is required to provide their service to us.
5a. What We Send to AI Providers, and What We Do Not
The AI features work by sending some of your information to an external AI company, which generates a response and sends it back to us. Our default provider is Anthropic, in the United States, and your chat is only ever sent to Anthropic. OpenAI, also in the United States, is a standby provider we can switch some non-chat features (today, psychometric reports) to if Anthropic is unavailable. OpenAI also reads the photographs and screenshots described in Section 2.10: a meal, a nutrition label, a recipe page, or a screenshot of another app's food diary.
What we send:
- The text of your chat messages, and rolling summaries of your recent conversation for context.
- If you have session memory switched on, the notes the assistant keeps (Section 2.4a).
- The names and types of the coping cards you use most and how far along you are with each, for your weekly insight (Section 2.2b).
- Journal text, when you use a feature that analyses a journal entry.
- Descriptive bands from assessments, such as "a developing area", and WHO-5 band labels.
- Summaries derived from your wearable data, such as sleep, heart-rate variability, activity and engagement patterns. See the note on the setting below.
- Context about your goals (never their titles), workouts, wellness sessions and food logs, and which days you checked in, journalled, completed a quest or used a coping card. Your habits are not sent: the answers you give a habit stay out of every AI prompt (Section 2.13).
- The photograph or screenshot, when you ask the app to read a meal, a nutrition label, a recipe page or another app's food diary (Section 2.10). These go to OpenAI.
- When you import a recipe from a link: text from that web page, if our server cannot find its ingredients without AI, and ingredient lines whose nutrition needs estimating (Section 2.10). These go to Anthropic.
- If you track them, your illness and cycle marks (Section 2.14): for unwell days, the date, body area and level; for your cycle, only how many days it has been since a period you logged, never the dates themselves.
What we do not send:
- Your account identifier. The AI provider receives nothing that links a request back to your account.
- Your email address or display name.
- Your numeric assessment scores, or your answers to individual assessment questions.
Your wearable data and the AI: this setting is on by default. The setting that lets the AI use summaries of your wearable data is switched on when you connect a wearable. You do not have to turn it on, and it will be on until you turn it off. You can switch it off at any time in Settings, and once you do, we stop sending those summaries. We are telling you this plainly because it is the opposite of how an opt-in setting works, and you should know which one this is.
We remove contact details we can spot, and here is what that is worth. Before your text goes to an AI provider, our server scans it for email addresses and phone numbers and strips out any it detects. This reduces the contact details in the text as a side effect. It is not anonymisation and it is not de-identification. It is pattern matching, it misses things, and it cannot remove names, places, or anything else you have written about yourself or another person. Assume that anything you write in a message or journal entry sent for analysis reaches the AI provider substantially as you wrote it. We do not treat this step as a safeguard for your health information and neither should you.
What we can and cannot tell you about how these companies handle your data. We send this data under the providers' standard commercial API terms for business customers. We do not use your data to train or fine-tune any AI model ourselves. What the providers do is governed by their terms, and here is what each of them publishes, as we read it on 27 September 2026:
- Anthropic states that retained API data "is never used for model training without your express permission", that prompts and outputs are "not retained by default" (some models require 30-day retention), and that content flagged by its safety systems may be kept for up to 2 years (Anthropic: API and data retention).
- OpenAI states that data sent to its API "is not used to train or improve OpenAI models (unless you explicitly opt in to share data with us)", and we have not opted in; its abuse-monitoring logs are retained for up to 30 days unless the law requires longer (OpenAI: Data controls).
These are the providers' public statements, not our guarantee. We do not yet hold written confirmation from Anthropic about how it handles the data we send through its API. We will update this section when the position changes.
Turning it off. The AI chat, insights and generated reports are optional, and nothing is sent to an AI provider until you accept AI features in the app. Mood tracking, journalling and assessments work without them. Photo food logging is optional too, and you can log food by searching or typing instead. Once you have accepted, you can narrow what is shared in Settings (turn off individual data sources, delete your chat history, and clear what Peachy remembers). You can withdraw your consent at any time. A single switch that turns every AI feature back off is not built yet; until it is, the way to fully stop AI processing is to delete your account, which removes your data apart from the records Section 7 says we keep after deletion.
6. Where Your Data Goes
Your journal entries, mood check-ins, chat history, assessments and wearable summaries are stored in Australia, in Google Cloud's Sydney region. We moved our primary database there on 2 August 2026. Your health and wellbeing records are held onshore in Australia under the Australian Privacy Act.
Storing your records in Australia is not the same as everything happening in Australia. Some of our processing still runs on servers in the United States, including for people using older versions of the app, which continue to call our previous United States servers until they update. Several features send data overseas by design. Where a feature sends data overseas we say so, and you can turn that feature off.
The overseas transfers that involve your personal information are:
- AI processing (United States). Chat messages, journal text submitted for analysis, assessment band descriptors, wearable-derived summaries, goal, workout and food context, text from recipes you import from a link, and illness and cycle marks if you track them, go to Anthropic. Your chat only ever goes to Anthropic. Photographs and screenshots you ask the app to read (a meal, a nutrition label, a recipe page, another app's food diary) go to OpenAI, which is also a standby we can switch psychometric reports to. This includes health information. Section 5a sets out exactly what is sent.
- Speech-to-text (United States). Audio you dictate goes to Apple or Google. See Section 2.9.
- Usage analytics (European Union) and crash telemetry (United States). Only if you turn on Allow analytics. Usage analytics go to PostHog, which stores them in Frankfurt. PostHog Inc. is a US company, and our agreement with it allows it to process this data in the United States and elsewhere, protected by the EU Standard Contractual Clauses in that agreement. Crash reports go to Firebase Crashlytics in the United States. Until 31 December 2026, usage analytics also go to Firebase Analytics in the United States. All of it is pseudonymous. It includes some health information listed in Section 2.6. It never includes your journal, messages, anything else you type, or your exact scores.
- Nutrition lookups (United States). Food search terms go to USDA FoodData Central.
- Food product lookups (France). When you scan a barcode or search for a packaged product, your device contacts Open Food Facts directly. They receive the barcode or search text and your IP address.
- Wearable data (United States). If you connect a Garmin account.
- App distribution, payments and notification delivery. Via Apple and Google.
- Website contact forms, mailing list and website analytics. As listed in Section 5. Website measurement sent to PostHog is stored in Frankfurt. As with app usage analytics, our agreement with PostHog allows it to process this data in the United States and elsewhere, protected by the EU Standard Contractual Clauses in that agreement.
For Australian users
Under Australian Privacy Principle 8, before disclosing personal information to an overseas recipient we must take reasonable steps to ensure the recipient does not breach the Australian Privacy Principles. For Google services we rely on Google's Data Processing Addendum and its standard contractual clauses. For PostHog we rely on its data processing agreement, which we signed on 27 October 2026. For our AI providers we currently rely on their standard commercial API terms. We are working to put specific data processing agreements in place and will update this section when we do.
For UK users
Transfers of your personal data from the United Kingdom to the United States are governed by appropriate safeguards. For transfers to Google we rely on the UK International Data Transfer Agreement (UK IDTA) or equivalent standard contractual clauses approved by the UK Information Commissioner's Office (ICO). PostHog stores data in the European Union, which the UK recognises as giving adequate protection. PostHog Inc. is based in the United States, and where its staff can access that data we rely on the EU–US Data Privacy Framework and its UK Extension, and on the EU Standard Contractual Clauses with the UK International Data Transfer Addendum in our data processing agreement with PostHog. For our AI providers, the transfer mechanism is under review as part of putting formal data processing agreements in place, and we will state it here once settled. You may ask us at any time which mechanism applies to a given transfer by emailing hello@thepeachylifecompany.com.
7. How Long We Keep Your Data
| Data type | Retention period |
|---|---|
| Account data (email, display name) | For the duration of your account. Deleted when you delete your account. |
| Mood entries | For the duration of your account. Deleted when you delete your account. |
| Journal entries | For the duration of your account. Deleted when you delete your account. |
| Habits and goals | For the duration of your account. Not-today answers older than 84 days are removed whenever the habit is next saved. Erased when you delete your account. |
| Illness and cycle marks | For the duration of your account, or until you switch the tracking off or remove them. Switching off deletes them. Erased when you delete your account. |
| Notes the AI assistant keeps | 90 days from the date of each note, then deleted automatically. Switching session memory off deletes them all. |
| AI conversation messages | Up to 90 days from the date of each message, then automatically deleted. (Automated deletion job actively being implemented.) |
| Biometric/health data | For the duration of your account, or until you revoke integration permission. Deleted when you delete your account. Garmin is different: Garmin data stays in your account after you disconnect Garmin, until you delete your account or ask us to delete it, and the copy we keep of each Garmin notification is deleted after 90 days (Section 2.5). |
| Website analytics (Cloudflare Web Analytics) | Aggregated website statistics only. No personal data retained. |
| Website measurement (our own, Section 2.6a) | Each note is kept for 3 months, then deleted automatically. Daily totals worked out from the notes are kept for up to 2 years. |
| App usage and crash telemetry (Firebase Analytics, Crashlytics) | Pseudonymous. Only if you turn on Allow analytics. Retained by Firebase under Google's standard retention periods for analytics and crash data. Turning Allow analytics off stops new collection. Collection stops on 31 December 2026; what was collected before then is kept under Google's standard periods. |
| App and web app usage analytics (PostHog) | Only if you turn on Allow analytics. Kept for 1 year, then deleted. Deleted sooner when you delete your account. Turning Allow analytics off stops new collection. |
| Date of birth and age check (date of birth, birth year, verification time) | For the duration of your account. Erased when you delete your account. |
| How you describe yourself (Woman, Man, Non-binary or Prefer not to say) | For the duration of your account. Erased when you delete your account. |
| Consent records (acceptance time, document versions) | For the duration of your account, and 7 years after deletion. See Section 2.1b. |
| Assessment results and generated reports | For the duration of your account. Erased when you delete your account. |
| Food logs | For the duration of your account. Erased when you delete your account. Photographs and screenshots you ask the app to read are not kept (Section 2.10). |
| Recipe-share link record | Until the link expires after 7 days, you stop sharing, or you delete your account, whichever comes first. |
| Crisis-safety records | Erased with your account. See below. |
| Compliance audit trail | Kept indefinitely. See below. |
| Support correspondence | Kept while we need it to resolve your issue and to see whether the same problem recurs. We do not currently expire it on a fixed schedule, so we are not going to publish a period we do not enforce. If you delete your account, your support correspondence is erased with it. You can ask us to delete a support conversation at any time (contact details in Section 17). |
When you delete your account in Settings, deletion is immediate. As soon as you confirm, we erase your records permanently, including files held in storage, and then delete your sign-in. This usually takes a matter of seconds. There is no recovery window: once you have confirmed, the deletion cannot be undone and we cannot get your account back. Residual copies may persist in encrypted backup snapshots for a short period afterwards, consistent with our backup and disaster-recovery practices, before being overwritten.
Two things outlive that erasure, and we would rather you knew before you pressed the button than after.
Consent records, kept for 7 years. The record of your acceptance of these documents, as described in Section 2.1b.
A compliance audit trail, kept indefinitely. When you ask us for a copy of your data, or ask us to delete your account, we keep a record that you asked, when you asked, and what kind of request it was. It never contains the content of your data. We keep it because it is our evidence that we honoured your request, and deleting it would destroy the proof that the deletion happened.
Crisis-safety records do not outlive it. If the Service detected content suggesting a risk to your safety and responded, for example by showing you crisis support resources, or scheduled a follow-up check-in, those records are erased along with the rest of your account. We keep only counts that cannot identify you, such as how many times safety resources were shown in a month, so that we can check the safety features are working.
Apart from these two, erasure is complete as soon as the deletion has run.
8. How We Protect Your Data
- Encryption in transit: All data is transmitted over HTTPS/TLS.
- Encryption at rest: Data stored in Google Cloud Firestore is encrypted at rest by Google's infrastructure.
- Credentials for connected services: When you connect a service such as Garmin, we hold an access credential for it. We encrypt these credentials with a key managed in Google Cloud Key Management Service in Australia, on top of the encryption Google's infrastructure already applies.
- Access controls: Access to production data is restricted to authorised personnel only, on a need-to-know basis, and is audit-logged.
- Firebase Security Rules: Firestore rules are configured so that users can only read and write their own data. No user can read another user's records directly. Where you deliberately share something (a goal with an accountability partner, or a recipe with another user), our servers make a copy for the recipient, on your instruction. That server path is the only route by which anything of yours reaches another person, and Sections 2.11 and 2.15 describe exactly what moves and what happens to it afterwards.
- Authentication: Firebase Authentication handles credential storage and management. We never store raw passwords.
No method of transmission over the internet or electronic storage is 100% secure. While we use commercially reasonable measures to protect your data, we cannot guarantee absolute security. In the event of a data breach that poses a risk to your rights and freedoms, we will notify you and relevant authorities as required by law.
9. Your Rights
You have the following rights in relation to your personal data, regardless of where you are located. Additional jurisdiction-specific rights are set out in Sections 10 and 11.
- Get a copy of your data: You can view your data within the app. You can request a copy of the records you created — your mood check-ins, journal entries, chat history, assessments and wearable summaries — as a machine-readable JSON file, from Settings → Privacy & data → Export my data. The app downloads the file to your device, where you can save or share it. Once you share it, it is under your control. A copy also stays on our servers, readable only by your account, for 7 days; it is then deleted, and destroyed for good within about 15 days. Some internally generated records are not included in that file: some of the records our system works out about you (Section 2.2c), the credentials for services you have connected, and safety audit logs. You can ask us about those separately at hello@thepeachylifecompany.com.
- Delete your data: You can delete your account from Settings at any time (Settings → Account & Security → Manage account deletion). Deletion is immediate: as soon as you confirm, your records are erased permanently, including files held in storage, and this cannot be undone. Two narrow exceptions apply, both described in Section 7. You do not need the app to ask us to delete your account. Our public page at thepeachylifecompany.com/delete-account explains what deletion removes, what is kept and for how long, and how to ask; you do not need to sign in or install anything to read it. You can also email support@thepeachylifecompany.com from the address you signed up with, with the subject "Account deletion request".
- Correct your data: You can update your display name and account details within the app. For other corrections, contact us.
- Withdraw consent: Where we process your data on the basis of consent (including all special category data), you can withdraw that consent at any time. Withdrawal will not affect the lawfulness of processing that occurred before withdrawal. Withdrawing consent for core data processing will require deleting your account.
- Disable health integrations: You can revoke Apple Health, Google Health Connect, or Garmin permission at any time from your device settings, from Garmin Connect, or within the app. Disconnecting Garmin stops new data arriving; it does not delete the Garmin data we already hold (Section 2.5). To delete that too, contact us or delete your account.
To exercise any right, or for any privacy-related request, contact us at hello@thepeachylifecompany.com. We will respond within 30 days.
10. For UK Users — UK GDPR Rights
If you are located in the United Kingdom, you have the following rights under the UK GDPR and Data Protection Act 2018, in addition to the general rights above:
- Right of access (Art. 15): You have the right to receive a copy of your personal data and information about how it is processed.
- Right to rectification (Art. 16): You have the right to have inaccurate personal data corrected and incomplete data completed.
- Right to erasure (Art. 17): You have the right to request deletion of your personal data ("right to be forgotten") in certain circumstances — for example, where you withdraw consent and there is no other lawful basis for processing.
- Right to restriction of processing (Art. 18): You have the right to request that we restrict processing of your data in certain circumstances — for example, while the accuracy of data is contested.
- Right to data portability (Art. 20): Where processing is based on consent or contract and carried out by automated means, you have the right to receive your data in a structured, commonly used, machine-readable format and to transmit it to another controller. You can export your data at any time from the app's Settings.
- Right to object (Art. 21): You have the right to object to processing based on our legitimate interests. We will stop processing unless we can demonstrate compelling legitimate grounds that override your interests.
- Rights related to automated decision-making (Art. 22): The Peachy Life does not make automated decisions that produce legal or similarly significant effects on you. AI-generated coaching suggestions are informational only and do not constitute automated decision-making in the Art. 22 sense.
How to exercise your UK GDPR rights
Email us at hello@thepeachylifecompany.com with the subject line "UK GDPR Data Rights Request". We will acknowledge within 5 working days and respond in full within one calendar month (extendable by a further two months for complex or numerous requests, with notice).
Right to complain to the ICO
If you are unhappy with how we have handled your personal data, you have the right to lodge a complaint with the Information Commissioner's Office (ICO), the UK supervisory authority for data protection:
- Website: ico.org.uk/make-a-complaint
- Telephone: 0303 123 1113
We would appreciate the opportunity to address your concern directly before you approach the ICO, so please contact us first.
11. For Australian Users — Privacy Act 1988
If you are located in Australia, we comply with all 13 Australian Privacy Principles (APPs) under the Privacy Act 1988 (Cth). Key rights and obligations include:
- APP 5 — Notice at collection: We notify you of our data collection practices at the point of collection — through this policy and in-app notices.
- APP 6 — Use and disclosure: We only use and disclose your personal information for the primary purpose for which it was collected, or with your consent, or as required by law.
- APP 1 — Openness: This policy is our openness statement. It describes the kinds of personal information we collect and hold, how we collect it, why we hold it, how you can get at it and correct it, how to complain, and which countries your information may go to.
- APP 8 — Cross-border disclosure: Your journal, mood, assessment and wearable records are stored in Australia. Several features send information overseas, mostly to the United States. Section 6 describes them and Section 5 names the companies involved and the countries they operate in.
- APP 11 — Security: We take reasonable steps to protect personal information from misuse, interference, loss, unauthorised access, modification, and disclosure (see Section 8).
- APP 12 — Access: You have the right to access your personal information. Make a request by emailing hello@thepeachylifecompany.com. We will respond within 30 days. We may charge a reasonable fee to cover the cost of providing access (we will notify you in advance).
- APP 13 — Correction: You have the right to request correction of inaccurate, out-of-date, incomplete, irrelevant, or misleading personal information. You can update most data directly within the app.
Automated decisions (APPs 1.7 to 1.9)
Some things in the Service happen automatically, by computer program, using your personal information. We list them here so you know which ones could affect you. Each of these is made solely by a computer program, with no person involved at the time:
- The age checks. If the date of birth you give at signup shows you are under 18, signup stops automatically and you cannot use the Service; if you signed in with Google or Apple from the log-in screen, the account that sign-in created is closed and deleted automatically. This uses only your answer to the age question, which we do not keep (Section 2.1a). Our servers also check your birth year before you take a wellbeing assessment, and turn the request down if it shows you are under 18.
- Crisis-safety responses. If something you write suggests a risk to your safety, the Service automatically shows you crisis support resources instead of an AI reply to that message. On a week with signs of distress, your weekly report is shortened and cannot be shared, and Peachy does not remember that conversation. This uses your chat messages, journal entries and mood data. It never suspends or removes your account, and it is not a diagnosis (Section 7 describes the record we keep).
- Limits on AI messages. To keep the service stable, the number of AI chat messages you can send in an hour is limited automatically. This uses only the count of messages you have sent.
- AI-generated reflections and insights. The AI writes reflections, summaries and weekly insights from the data you choose to share. They are information for you only. Apart from the age checks and the hourly message limit above, no automated process decides your eligibility, pricing or access.
If you think an automated process has affected you unfairly, contact us at hello@thepeachylifecompany.com and a person will review it.
Notifiable Data Breaches
If we suffered a data breach likely to cause you serious harm, Part IIIC of the Privacy Act 1988 requires us to notify you and the Office of the Australian Information Commissioner as soon as practicable after we conclude that has happened. We would tell you what happened, which of your information was involved, and what we recommend you do. We would publish a notice on our website if we could not contact you directly.
Complaints — Australian users
If you believe we have breached the APPs, please contact us first at hello@thepeachylifecompany.com. We will investigate and respond within 30 days. If you are not satisfied with our response, you may lodge a complaint with the Office of the Australian Information Commissioner (OAIC):
- Website: oaic.gov.au/privacy/privacy-complaints
- Phone: 1300 363 992
12. For California Users — CCPA / CalOPPA
If you are a California resident, you have the following rights under the California Consumer Privacy Act (CCPA) as amended by the California Privacy Rights Act (CPRA), and the California Online Privacy Protection Act (CalOPPA).
Categories of personal information we collect
In the preceding 12 months, we have collected the following categories of personal information from California residents:
- Identifiers: Email address, display name.
- Personal records: Content of mood entries, journal entries, and AI chat messages.
- Health and medical information: Mood and wellbeing entries, journal entries, AI conversation messages and the notes the assistant keeps, wellbeing assessments and the signals derived from them, illness and cycle marks, caffeine entries, coping-card entries, habit answers, and biometric data (where explicitly permitted), and the ranges and categories listed in Section 2.6 if you turn on Allow analytics. Section 2 describes each.
- Internet or network activity: Pseudonymous app usage and crash data via PostHog, Firebase Analytics and Crashlytics, if you turn on Allow analytics, aggregated website statistics via Cloudflare Web Analytics, and the website measurement described in Section 2.6a, which stores no identifier on your device (that section explains PostHog's daily counting code).
- Age information: Date of birth, collected to check eligibility to use the Service. Section 2.1a lists the other ways we use your age.
- Gender: How you describe yourself (Woman, Man, Non-binary or Prefer not to say). Section 2.1c describes how we use it.
- Audio: Speech you dictate, transcribed by Apple or Google.
- Visual information: Photographs and screenshots you ask the app to read: meals, nutrition labels, recipe pages and another app's food diary. We do not keep them (Section 2.10).
Business or commercial purpose for collection
We collect this information to provide the core features of The Peachy Life: mood tracking, journalling, AI coaching, and personalised wellbeing insights.
We do not sell or share your personal information
Peachy Life Pty Ltd does not sell, rent, trade, or share your personal information with third parties for their own commercial or advertising purposes. This applies to all users, including California residents. There is no "opt-out of sale" mechanism because we do not engage in the sale of personal information.
Your CCPA rights
- Right to know: You have the right to request disclosure of the categories and specific pieces of personal information we have collected about you, the sources from which it was collected, the business purpose for collection, and the categories of third parties with whom we have shared it.
- Right to delete: You have the right to request deletion of personal information we have collected from you, subject to certain exceptions. You can delete your account directly from the app's Settings. Section 7 explains how erasure works and the two exceptions that outlive it.
- Right to correct: You have the right to request correction of inaccurate personal information.
- Right to opt out of sale/sharing: We do not sell or share personal information. No opt-out is needed, but you may contact us to confirm.
- Right to non-discrimination: We will not discriminate against you for exercising your CCPA rights. Exercising these rights will not result in denial of service, different pricing, or a different quality of service.
Shine the Light (California Civil Code Section 1798.83)
California residents may request information once per calendar year about personal information shared with third parties for direct marketing purposes. We do not share personal information with third parties for their direct marketing purposes, so no such disclosure is required. To confirm, contact us at hello@thepeachylifecompany.com.
How to exercise your California rights
Email hello@thepeachylifecompany.com with the subject "California Privacy Rights Request". We will acknowledge within 10 business days and respond in full within 45 calendar days (extendable by a further 45 days with notice). We may need to verify your identity before processing your request.
CalOPPA — Policy effective date and updates
This policy carries the version date shown at the top of the page. We will post any changes to this page and update that date. For material changes, we will provide notice through the app.
13. Children's Privacy
The Peachy Life is for people aged 18 and over. When you sign up we ask for your date of birth, and we offer you every year to choose from so that you can answer honestly rather than being nudged into a year that lets you through.
If your answer shows you are under 18, we do not keep it. If you start from the welcome screen, we ask before any account exists, so none is created and nothing is kept. If you signed in with Google or Apple from the log-in screen, we delete the account that sign-in created, together with your sign-in credentials and anything attached to them, and we sign you out. Section 2.1a sets out what survives that deletion, which is a record that a signup was blocked and when, carrying nothing that identifies you. A signup from the welcome screen that stops at the age question leaves no record at all.
This is enforced by our servers, not only by the app. The app checks your full date of birth. Our database also refuses to store a birth year that would make you under 18 whatever your birthday, so tampering with the app on a device cannot get round that check.
We do not knowingly collect personal information from anyone under 18. If you are a parent or guardian and believe your child has given us personal information, email hello@thepeachylifecompany.com and we will delete it promptly.
For everyone who does meet the minimum age, we keep the date of birth you gave and when you gave it, so that we can show we carried out this check. Section 2.1a explains what else we use it for. We do not use it to target advertising, and we do not run advertising.
A note on crisis content. The Service is not a crisis service and is not a substitute for professional help. Section 15 lists free confidential helplines. If the app detects content suggesting a risk to your safety, it shows you those resources and records that it did so. Section 7 explains how long that record is kept.
14. Cookies and Tracking Technologies
Our website (thepeachylifecompany.com) sets no cookies and stores nothing on your device. It uses Cloudflare Web Analytics, which is cookieless and does not track individual users, our own website measurement (Section 2.6a), and, until 31 December 2026, PostHog in cookieless mode. None of them stores anything on your device. You can switch our own measurement off with Global Privacy Control or Do Not Track. We do not use advertising cookies, tracking pixels, or any cross-site tracking technologies on our website. No cookie consent banner is shown. Our Cookie & Data Retention Policy has the details.
The mobile app does not use advertising cookies. Firebase Authentication and Firestore use technical tokens stored on your device to maintain your login session. These are strictly necessary for the app to function. When you turn on Allow analytics, the app and web app keep your analytics ID and a session ID on your device so PostHog can group your events. They are removed when you turn Allow analytics off.
15. Wellbeing and Crisis Disclaimer
The Peachy Life is a holistic wellness and self-knowledge tool. It is not intended for use as a medical device and is not intended to diagnose, screen for, monitor, treat, cure or prevent any medical condition, and it is not a substitute for professional care. For medical advice, diagnosis or treatment, please speak to a qualified healthcare professional. Crisis resources are always one tap away and never gated.
It is designed to support self-reflection and healthy habits. It is not:
- A clinical diagnostic tool.
- A substitute for professional psychological, psychiatric, or medical advice, diagnosis, or treatment.
- A crisis service or emergency intervention resource.
If you are experiencing a mental health crisis, thoughts of self-harm, or need urgent support, please reach out to a qualified health professional or contact emergency services. Crisis support resources in key regions:
- Australia: Lifeline — 13 11 14 | Beyond Blue — 1300 22 4636
- UK: Samaritans — 116 123 | Crisis Text Line — Text SHOUT to 85258
- USA: 988 Suicide & Crisis Lifeline — call or text 988
16. Changes to This Policy
We may update this Privacy Policy from time to time to reflect changes in our practices, technology, legal requirements, or for other operational reasons. When we make changes:
- We will publish it as a new version, and the version date at the top of this page will change. Previous versions are kept (see below).
- For material changes (changes that significantly affect how we use your data or your rights), we will provide notice through the app and, where required by law, seek your renewed consent before the changes take effect.
- For minor or administrative changes, updating this page is sufficient notice.
Continued use of the Service after a policy update constitutes acceptance of the updated policy, to the extent permitted by applicable law.
Each version of this policy carries a version date at the top of the page. When you accept this policy in the app we record which version you accepted, so we can tell you later exactly which document you agreed to. Section 2.1b explains the limits of the records we hold for acceptances before 25 August 2026.
We keep previous versions of this policy and will provide any of them on request. Email hello@thepeachylifecompany.com with the version date you want.
17. Contact Us
For any questions, concerns, or requests relating to this Privacy Policy or your personal data, please contact us:
Peachy Life Pty Ltd
Sydney, New South Wales, Australia
Email: hello@thepeachylifecompany.com
We aim to respond to all privacy-related enquiries within 30 days. If you are not satisfied with our response, you have the right to escalate to the relevant supervisory authority for your jurisdiction (see Sections 10 and 11 for contact details).