Last updated: November 10, 2026
Who we are
BellaHealth is a personal health dashboard for iPhone. It brings together data from Apple Health, Oura Ring, Garmin, and your own daily logs to help you understand what your health numbers mean in the context of your real life.
Developer: BellaHealth
Contact: bellahealth.support@gmail.com
Your data is not for sale
BellaHealth does not sell your personal information or health data.
BellaHealth does not share your personal or health information with advertising networks, data brokers, or marketing platforms. We do not use your data for cross-context behavioral advertising. We do not have relationships with any third party that receives your data for its own independent marketing purposes.
BellaHealth uses service providers — described below — to operate the product. Using a service provider to process information necessary to provide BellaHealth is not the same as selling your data. The distinction is explained in the Third-Party Service Providers section.
These commitments cover everything in the BellaHealth app. Our website uses the Meta Pixel to measure our Instagram and Facebook ads, as explained in the "Our website" section below.
Health data and AI
BellaHealth includes AI-powered features — including AI Chat, food photo analysis, and health document extraction. These features require sending some of your health information to an external AI service provider, Anthropic.
Data from Garmin is never included in AI requests.
When you use AI Chat, BellaHealth constructs a personalized system prompt using your current health data and sends it to Anthropic's API. This is what allows the AI to give you specific, personalized answers rather than generic responses.
The following categories of information may be included in AI requests, depending on what you have set up and what you have logged:
| Information | Sent to AI | Notes |
|---|---|---|
| Your first name | Yes | Used so the AI addresses you by name |
| Sleep hours | Yes, if available | From Oura or Apple Health |
| Sleep score | Yes, if available | From Oura |
| Readiness score | Yes, if available | From Oura |
| HRV (heart rate variability) | Yes, if available | From Oura or Apple Health |
| Steps today | Yes | From Apple Health or Oura |
| Workout (type, duration, calories) | Yes, if logged | From Apple Health or Oura |
| Water intake | Yes, if logged | Daily total only |
| Nutrition (calories, macros) | Yes, if logged today | Aggregated daily totals |
| Alcohol (yes/no) | Yes | Whether you logged alcohol the prior night |
| Supplements | Yes, if entered | The supplements list you entered in your profile |
| Cycle information | Yes, female users | Current cycle day, energy/stress ratings, physical signs — if cycle tracking is enabled. Free-text cycle notes are never sent. |
| Health documents | Yes, if uploaded | The extracted content of documents you upload (blood work, DEXA, etc.) is included to enable contextual answers |
| Life context types | Conditional | If you open Chat from the Context screen, the types of active context (e.g., "travel", "illness") are included — not specific dates or notes |
| Prior chat messages | Yes | Recent conversation history (up to 40 messages) is sent to maintain context within a session |
| Email address | No | Never sent |
| BellaHealth user ID | No | Never sent |
| Device identifier | No | Never sent |
| Age, height, weight | No | Used locally for calculations only |
| Resting heart rate | No | Not included in AI requests |
| Journal or gratitude notes | No | Free-text entries are never sent to any AI provider |
| Context notes / event details | No | Specific descriptions or notes attached to context events are never sent |
When you use food photo analysis or health document upload, the image or document content is sent to Anthropic for processing. Meal photos are not stored by BellaHealth's servers. Extracted document summaries are stored locally on your device and used as context in future AI Chat sessions.
About Anthropic and model training: BellaHealth accesses Anthropic's API as a business customer. Per Anthropic's API usage policies, data submitted through their API by business customers is not used to train Anthropic's AI models. Anthropic's data handling practices are described in their Privacy Policy and Terms of Service. BellaHealth does not control Anthropic's data retention practices and cannot make absolute guarantees on their behalf. If this matters to you, we encourage you to review Anthropic's current policies directly.
AI-powered features are opt-in by nature — the AI Chat and food/document analysis features are only triggered when you actively use them. Your health data is not automatically sent to Anthropic when you open the app.
Information BellaHealth accesses from Apple Health
If you grant permission, BellaHealth reads the following categories from Apple Health on your device. This data is used to power your home dashboard, trends charts, and AI Chat. It is read directly from your device and is never uploaded to BellaHealth's servers.
- Steps
- Heart rate variability (HRV)
- Resting heart rate
- Active energy burned
- Sleep analysis
- Workout activity
- Dietary water
- Height and body weight (used locally for goal calculations)
- Biological sex (used for UI and pronoun selection)
- Date of birth (used to calculate age for goal recommendations)
BellaHealth does not write any data to Apple Health. Revoking Apple Health permission in iPhone Settings → Health → BellaHealth immediately stops data access. No Apple Health data is stored on BellaHealth's servers, so revocation completes fully at the device level.
If you use a device or app that syncs to Apple Health (such as WHOOP, Garmin Connect, or Strava), BellaHealth may read that data from Apple Health. BellaHealth has a direct, optional integration with Garmin, described below. It has no direct integration with WHOOP or Strava; for those, it reads only what they have shared with Apple Health. If you use Garmin Connect and also share data to Apple Health, BellaHealth uses each source once and does not add them together.
Information BellaHealth accesses from Oura Ring
If you connect your Oura Ring, BellaHealth requests access to the following data through the Oura API, with your explicit authorization:
- Sleep score, sleep duration, and sleep stage data
- Readiness score
- HRV average
- Daily activity (steps, active calories)
- Workouts
- Menstrual cycle data (if your Oura account includes it)
- Stress summary data (if available on your account)
Oura data is fetched on-demand when you open the app and is not stored on BellaHealth's servers. Your Oura access token is stored locally on your device. The initial OAuth token exchange is handled through a server-side proxy so that Oura's client credentials are never present in the app binary.
To disconnect Oura, go to Profile → tap Disconnect under Oura Ring. This removes your access token from your device. BellaHealth will no longer be able to fetch Oura data. You can also revoke BellaHealth's access directly in your Oura account settings.
Information BellaHealth accesses from Garmin
Garmin is an optional, invitation-only connection while we test it. If you connect your Garmin account, you sign in on Garmin's own page and choose what to share; BellaHealth never sees your Garmin password. Garmin then sends BellaHealth the following summaries for your account, and only these:
- Daily steps, resting heart rate, and average stress level
- Sleep duration and sleep stages (deep, light, REM, awake)
- Overnight heart rate variability (a nightly average and a short-window high)
- Workouts: type, start time, duration, distance, calories, average heart rate, and the model of the Garmin device that recorded it
Garmin also sends us an identifier for your Garmin account and the list of permissions you granted, which we use to match the data to you and to stop collecting if you change your mind. BellaHealth ignores every other kind of Garmin data it might receive, including menstrual-cycle and pregnancy data, and does not keep it.
Where it is kept. Garmin pushes new data to BellaHealth's server, which holds it temporarily until your phone collects it. After your phone confirms it has saved the data, we delete it from the server. Anything your phone has not collected is deleted automatically after 7 days. The data your phone has collected is stored on your device, kept for 30 days, and removed immediately when you disconnect Garmin. Your Garmin connection details (including the access keys Garmin issues for your account) are stored on our server in encrypted form so we can keep your connection working and disconnect it on request, until you disconnect, delete your account, or Garmin tells us you removed access.
How it is used. Garmin data appears alongside your Apple Health and Oura data on the Today, Trends, and Context screens and in Your Story and Patterns We've Noticed, labelled as coming from Garmin (with the device model for workouts). It is not shown in the home-screen widget. If you have several sources, BellaHealth uses one source for each measurement instead of adding them together. Garmin data is never sent to any AI service, including AI Chat, and is never used to train, test, or improve any AI model. Insights shown to you are generated on your device by fixed rules, not by AI.
No selling or sharing. We do not sell Garmin data. We do not share it with anyone other than Supabase, which hosts BellaHealth's server, and we do not use it for advertising, credit, insurance, or employment decisions.
Disconnecting and deleting. To disconnect, go to Profile → Connected Health → Garmin Connect and tap Disconnect. That immediately deletes any Garmin data waiting on our server and the Garmin data on your phone, and tells Garmin to end the connection; your encrypted connection details are deleted once Garmin confirms. If Garmin cannot be reached, we keep the connection details encrypted and retry. If you delete your BellaHealth account, we do the same, then delete the account. If Garmin cannot be reached at that moment, your account is still deleted, and we keep a temporary, encrypted disconnect request and retry it for up to 30 days, then delete it. That request contains no name, email, BellaHealth account identifier, or health data; it contains a one-way code derived from your Garmin account ID, used only so an old disconnect request cannot end a newer connection. You can also end the connection yourself in your Garmin Connect account settings. After you disconnect or delete your account, BellaHealth discards any data Garmin sends for it.
Garmin handles your data under its own privacy notice.
Nutrition and meal logs
When you log a meal, BellaHealth saves the meal name, food description, estimated calories, protein, carbs, fat, and the time you ate. This data is stored on BellaHealth's server, linked to your anonymous account, and is also available on your device.
If you use the food photo feature, your photo is sent to Anthropic for nutrition estimation. Photos are not stored server-side by BellaHealth. The estimated values (calories, macros) are saved as a nutrition log entry.
Cycle and hormonal health
BellaHealth includes an optional cycle tracking feature for users who enable it. Period dates, energy ratings (1–5), stress ratings (1–5), physical signs, and optional free-text notes are stored locally on your device only.
When you use AI Chat, structured cycle information — current cycle day, energy level, stress level, and physical signs — is included in the AI system prompt for female users who have cycle tracking enabled. Free-text notes you write in your cycle journal are never sent to any AI provider.
Health documents
You may upload health documents (blood work results, DEXA scans, hormone panels, etc.) for AI analysis. When you upload a document, its content is sent to Anthropic to extract relevant health metrics. The extracted summary is stored locally on your device and is included as context in future AI Chat sessions. BellaHealth does not store raw document content or original files on its servers.
Context and life events
BellaHealth lets you log life context such as travel, illness, training blocks, stressful periods, and more. The structured details of context events — event type and dates — are stored on your device and synced to BellaHealth's server, linked to your anonymous account. Any personal notes you attach to context events are stored locally on your device only and are never uploaded.
When you open AI Chat directly from the Context screen, the types of currently active context (for example, "travel" or "illness") are included in the AI system prompt. Specific notes, dates, locations, or details attached to context events are never sent to any AI provider.
Profile data and goals
Your name, training goals, body composition goals, and supplement list are stored on your device and synced to BellaHealth's server, linked to your anonymous account. This allows your profile to be restored if you reinstall the app or sign in with Apple on a new device. Your name and supplement list are included in AI Chat prompts when you use that feature. Height, weight, and age are used locally for goal calculations only and are not sent to any server.
Your drink log (daily drink count and estimated calories) is also stored on your device and synced to BellaHealth's server.
Gratitude journal
Free-text entries you write in the gratitude journal are stored locally on your device only. They are never uploaded to BellaHealth's servers and are never included in AI requests.
Analytics
BellaHealth uses its own analytics system to understand how features are being used. This helps us improve the product.
Analytics events are associated with a randomly generated device identifier — a UUID created on your device's first launch of BellaHealth. This identifier is not linked to your name, email address, Supabase account, Oura account, or any personal identifier. It is a random number that allows BellaHealth to understand usage patterns at the device level without knowing who you are.
Examples of events tracked: app opened, meal logged, AI chat used, context added, trends viewed.
Analytics events never include health values (no sleep scores, steps, HRV, calories, etc.), free-text content, or personal information. Events record that an action happened — not what you entered.
Analytics data is not shared with third-party analytics platforms. It is stored in BellaHealth's own database. When you delete your account, analytics events are retained because they contain no personal or health information and cannot identify you.
Authentication
BellaHealth automatically creates a private, anonymous session when the app first launches. You will not see a sign-in screen. This anonymous account is used to authenticate your access to BellaHealth's servers and to protect your nutrition data with server-side access controls.
Optional: Sign in with Apple. You may choose to link your anonymous BellaHealth account to a Sign in with Apple identity. Doing so makes your account persistent and recoverable — if you delete and reinstall the app or switch devices, signing in with the same Apple ID restores your data. Your BellaHealth data is preserved when you link; nothing is lost. BellaHealth requests your name and email address from Apple only to associate your account. Your name and email are stored in your profile and are subject to the same protections as other profile data.
If you do not link a Sign in with Apple identity, your session remains tied to your device. Deleting and reinstalling the app without linking Apple creates a new anonymous session, and data from the previous session will not be accessible.
Where your data is stored
| Data | Where it lives | Server? |
|---|---|---|
| Apple Health data | Your device only (Apple Health) | No |
| Oura data | Your device (fetched live from Oura API) | No |
| Oura access token | Your device only (local storage) | No |
| Garmin data waiting to be collected | BellaHealth's server, temporarily (deleted once your phone confirms it, or after 7 days) | Yes (temporary) |
| Garmin data on your phone | Your device only (kept 30 days, removed on disconnect) | No |
| Garmin connection details | BellaHealth's server, encrypted, until you disconnect or delete your account | Yes (encrypted) |
| Nutrition / meal logs | Your device + BellaHealth's server | Yes (linked to anonymous account) |
| Cycle entries | Your device only | No |
| Health documents (raw) | Your device only | No |
| Document summaries | Your device only | No |
| AI Chat history | Your device only | No |
| Life context events (types & dates) | Your device + BellaHealth's server | Yes (linked to anonymous account; personal notes are local only) |
| Profile and goals | Your device + BellaHealth's server | Yes (linked to anonymous account) |
| Drink log | Your device + BellaHealth's server | Yes (linked to anonymous account) |
| Gratitude journal | Your device only | No |
| Analytics events | BellaHealth's server (anonymous device ID + event name only) | Yes (no PII, no health data) |
Deleting your data
Tap Delete All My Data in Profile → Data & Privacy. This action:
- Permanently deletes your anonymous Supabase account and all server-side data associated with it: nutrition logs, profile, training goals, context event records, and drink log entries
- If you had linked a Sign in with Apple identity, BellaHealth also revokes the associated Apple refresh token
- If you had connected Garmin, BellaHealth first tells Garmin to end the connection and deletes your Garmin data and connection details (see "Information BellaHealth accesses from Garmin")
- Clears all locally stored data from your device (chat history, cycle journal, context events, Oura token, document summaries, and other app data)
Analytics events are retained after account deletion. They contain no personal information or health values — only a device identifier and event names — and cannot be used to identify you.
Deleting your BellaHealth account does not delete your data from Oura, Apple Health, or any other connected service. Your data in those services is governed by their respective privacy policies.
Revoking access
Apple Health: Go to iPhone Settings → Health → Data Access & Devices → BellaHealth. Toggle off any or all data categories. BellaHealth will stop reading those categories immediately. Because HealthKit data is never stored server-side, there is nothing to delete on BellaHealth's end.
Oura Ring: Tap Disconnect in BellaHealth's profile screen. You can also revoke access in your Oura account settings at ouraring.com. Either action removes BellaHealth's ability to access your Oura data.
Garmin: Go to Profile → Connected Health → Garmin Connect and tap Disconnect, or end the connection in your Garmin Connect account settings. BellaHealth then stops receiving your Garmin data and deletes what it holds.
Data retention
Nutrition log data on BellaHealth's server is retained until you use Delete All My Data, at which point it is permanently removed.
Garmin data is held on BellaHealth's server only until your phone collects it, and for at most 7 days. Garmin data on your phone is kept for 30 days. Encrypted Garmin connection details are kept until you disconnect, delete your account, or Garmin tells us you removed access.
Analytics events are retained indefinitely. They contain no personal or health information.
BellaHealth does not currently operate an automated data deletion schedule beyond account deletion.
Third-party service providers
BellaHealth works with the following service providers to operate the product. These are companies that process information on BellaHealth's behalf to provide specific functionality. They are not data buyers and do not use your information for their own marketing purposes.
Anthropic processes AI Chat sessions, food photo analyses, and health document extractions. When you use AI-powered features, the information described in the "Health Data and AI" section above is sent to Anthropic's API. Anthropic's privacy practices are described in their Privacy Policy.
Supabase provides database infrastructure, authentication, and server-side functions. Supabase stores your anonymous account and nutrition logs. Supabase's privacy practices are described in their Privacy Policy.
Oura is the source of Oura Ring data. When you connect your ring, BellaHealth accesses your Oura data through Oura's API with your explicit authorization. Oura's privacy practices are described in their Privacy Policy.
Garmin is the source of Garmin data. When you connect, BellaHealth accesses your Garmin data through Garmin's API with your explicit authorization. Garmin's practices are described in its Privacy Policy.
The BellaHealth app does not use advertising networks, third-party analytics platforms, crash reporting services, or tracking SDKs. No data from the app is shared with any entity for advertising, marketing, or profiling purposes.
Our website
The BellaHealth website (bellahealthapp.com) uses the Meta Pixel on its home page to measure how visitors who arrive from our Instagram and Facebook posts and ads use the site. When you visit the home page, Meta may receive information such as the page you viewed, your browser and device type, your IP address, and cookie identifiers. Meta may combine this with information it already holds about you, as described in Meta's Privacy Policy.
The Meta Pixel runs only on the website. It does not run in the BellaHealth app and never receives your health data, app activity, or anything you log in BellaHealth. You can limit this by blocking third-party cookies in your browser or by adjusting your Meta ad preferences.
Apple HealthKit
BellaHealth's use of HealthKit data complies with Apple's HealthKit developer guidelines. HealthKit data is not used for advertising, not shared with data brokers, and is used exclusively for the health and fitness functionality described in this policy.
Notifications
BellaHealth may send local notifications for hydration reminders and other in-app prompts. These are scheduled locally on your device and do not involve any server-side push infrastructure. You can manage notification permissions in iPhone Settings.
Children's privacy
BellaHealth is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided us with information, please contact us and we will take steps to delete it.
Your rights and controls
You can control what BellaHealth accesses and stores:
- Revoke Apple Health access at any time in iPhone Settings
- Disconnect Oura from within the BellaHealth profile screen
- Disconnect Garmin from Profile → Connected Health → Garmin Connect; Garmin data can be accessed and erased through the same disconnect and delete controls, or by emailing us
- Delete all your data using Delete All My Data in Profile → Data & Privacy
- Disable AI features by simply not using Chat, food photo analysis, or document upload — no health data is sent to Anthropic unless you actively use those features
By default, BellaHealth's server records are linked only to an anonymous account generated on your device. If you choose Sign in with Apple, BellaHealth also stores the email address Apple provides (which may be a private relay address) with your account, as described in the Authentication section. BellaHealth does not otherwise ask for your name or contact details to use the app. If you believe you have additional rights under applicable privacy law (such as GDPR, CCPA, or other state or national laws), please contact us at the email address below.
Changes to this policy
When we make material changes to this policy, we will update the "Last updated" date at the top of this page. For significant changes affecting how health data is handled, we will notify users within the app where feasible.
Contact
BellaHealth
Email: bellahealth.support@gmail.com
Support: bellahealthapp.com/support