About this policy
BodyXP is a nutrition, hydration, weight and fitness tracking app with XP, levels and optional leagues, provided by CloudMint Soft. This policy explains the information handled by the app and its connected services, and the choices available to you. BodyXP is intended for adults aged 18 or older. It is a wellness tool, not a healthcare provider.
Contact us at [email protected] about this policy or your information.
Your account
We receive your email address, account identifier and the information you provide to create or manage an account. Email sign-in sends your password to our authentication provider, Supabase. BodyXP does not save a plain-text password in your diary. The app stores a login session on your device so you can remain signed in.
If you choose Sign in with Apple or Google, the provider supplies an account identifier and may supply your name, email address or Apple private relay address. Google may also supply profile metadata such as an avatar URL; BodyXP has no profile-photo upload feature. The authentication provider keeps identity information needed for sign-in. You can choose a preferred name in BodyXP, and a nickname if you join leagues.
Body, nutrition and fitness information
Your profile can include age in years, sex selection, height, weight, target weight, activity level, weight-change goal and preferred pace. We use these entries to estimate goals and personalize your progress. We do not ask for your full date of birth.
We store your calorie, protein, carbohydrate, fat and hydration targets; the meals and quantities you record; water intake; dated weight entries; and workouts, including chosen body areas and any duration you enter. Recipes, custom foods and saved meals can include names, ingredients, servings, preparation and nutrition values. The current app does not read HealthKit, medical records, heart rate, step counts or GPS exercise routes.
BodyXP also stores the XP, levels, streaks, goals, awards and league activity derived from your entries. A time-zone offset helps calculate your tracking day. This information is associated with your account when synced; using an account identifier does not make it anonymous.
Meals, photos and other content
You can enter food manually, search for food, scan a barcode, or choose optional AI analysis. Camera and photo-library access are used for selected meal or nutrition-label images and barcode scanning. Barcode camera frames are decoded on your device; we send the decoded barcode for product lookup, not camera frames.
Chosen photos and unfinished drafts are first held on your device. When you choose AI analysis after permitting AI sharing, BodyXP uploads the selected image to private hosted storage and sends it for analysis. Before upload, BodyXP compresses images and removes embedded EXIF metadata. Please avoid including faces, documents or information you do not want processed. BodyXP does not delete the original image from your photo library.
Meal names, descriptions, food preparation text, recipes and other user-entered labels may contain information you choose to include. We do not read your email inbox, messages, contacts or photo library unrelated to the image you select.
Optional AI analysis and OpenAI
When you choose Analyze meal or nutrition-label analysis, relevant meal content is processed by OpenAI through our backend. A request contains one selected photograph or one food description, along with instructions for estimating food or extracting nutrition values. BodyXP does not separately attach your email, name, account identifier, age, height, weight, calorie goals, workout history or full diary to the OpenAI prompt. The photograph or description itself may reveal information about you.
Before the first analysis, the app explains this sharing and asks permission. You can decline and continue manually. You can withdraw permission for future analyses in Profile under Preferences → Allow AI processing. Withdrawal does not undo an earlier submission or delete information providers have already processed.
We save the returned estimates and analysis-job information to support review, retry and usage allowances. Food names and preparation information may also be sent to USDA for nutrition lookup. User changes on the review screen are stored with your confirmed meal; the current flow does not send those corrections or review answers back to OpenAI.
Our requests ask OpenAI not to store responses for later API retrieval. This does not eliminate all provider retention. OpenAI's standard API controls describe safety/abuse logs retained for up to 30 days, with exceptions, and image safety review or caching may apply. Account-specific sharing, regional processing and special retention settings have not yet been confirmed for this release. We therefore do not promise zero retention or that our particular account has all optional sharing disabled. See OpenAI data controls.
AI estimates may be inaccurate. Review them before saving; manual logging is available without sharing meal content with OpenAI.
Subscriptions and purchases
Apple processes iOS subscription payments. BodyXP does not receive your full payment-card or bank-account details from checkout. Apple and RevenueCat provide subscription and transaction information such as the product, entitlement, purchase/renewal and expiry dates, trial state, store, transaction identifiers and renewal or billing status.
RevenueCat uses your BodyXP account identifier to associate purchases with access. Its iOS SDK also sends Apple's vendor device identifier, device/OS and app versions, language/store context and network request information. RevenueCat supports purchase restoration, subscription access and subscription reporting/analytics. We do not send your nutrition, body measurements, food photos or workout records to RevenueCat.
Deleting your BodyXP account or signing out does not cancel an Apple subscription. Use Manage subscription in the app or Apple's subscription settings to cancel it separately.
Technical information and usage
Our services process ordinary network information such as IP addresses, request times, status/error information and app or device context to operate, protect and troubleshoot the service. Infrastructure may enrich IP addresses into approximate geography or retain request performance information; the exact hosted log fields and retention still need confirmation. We retain account-associated AI job/allowance records and short-lived rate-limit request records, and remember preferences, favorites and tutorial completion.
BodyXP currently has no connected general app analytics, crash-reporting, advertising or notification SDK. RevenueCat's subscription analytics is separate from general screen/tap analytics. BodyXP has no location permission or feature that deliberately records your physical location, and does not access an advertising identifier. A network IP, language preference or App Store country is not a GPS location.
The audited app and RevenueCat configuration contain no advertising tracking or data-broker integration. Account linkage is used for functionality and subscription reporting, not cross-company targeted advertising. We will reassess disclosures if the integration changes.
How information is used
We use information to authenticate accounts, sync and display your entries, calculate goals and progression, remember your settings, run the optional AI and nutrition lookup features, verify subscription access, restore purchases, prevent duplicate charges or abuse, troubleshoot services and respond to support or privacy requests. BodyXP's goals and progress displays use the profile and tracking entries you provide. RevenueCat provides subscription analytics using purchase-related information.
Services and sharing
Supabase hosts authentication, synced account records, private photo storage and backend processing. Its hosted services process technical request information as well as the content required for those features.
RevenueCat manages subscription verification and reporting using the purchase and identifier information described above. Apple runs Sign in with Apple and App Store billing; Google runs optional Google sign-in. Their independently operated services follow their own policies.
OpenAI processes chosen AI inputs as described above. USDA FoodData Central receives food-search or detected-food queries from our server. Open Food Facts receives barcode lookups from our server. These nutrition providers do not receive an explicitly attached BodyXP account identifier, profile or photograph; they see the server's network requests, and a free-form search query can still contain personal information you type.
If you email support, CloudMint Soft's Gmail mailbox and the email providers involved handle your sender address, message and any attachments you choose to send. BodyXP does not automatically send a support message or attach your diary. When you share an export, the destination you choose receives that file.
If you opt into a league, participating users can see your nickname, weekly XP, rank and league zone. They do not receive your email, full account identifier, meals, photos, body measurements or workout entries through the leaderboard. League participation starts off. You can turn it off in the league screen.
Storage and safeguards
The app keeps an account-scoped local database for offline entries, drafts and cached information. Signed-in records are synced to hosted services. Network requests use HTTPS, and our backend uses authenticated access controls and private photo storage. Administrative access still exists to operate these services; we do not claim that information is inaccessible to us or completely risk-free.
Your device, email account, chosen sharing destinations and service providers also affect security. Keep your device and accounts protected, and share exports only with destinations you trust.
Retention and photos
Tracking records, preferences, AI results and progression history have no fixed automatic expiry in the current implementation. They remain until you change/remove applicable records or delete your account, subject to backup and provider retention. Removing a diary entry does not reverse previously earned XP; progression and anti-duplicate history can remain while the account exists. Synced deletion markers can also remain to propagate deletion.
Keep meal photos in history is off by default. With it off, the service attempts to remove the server photo after analysis. Interrupted requests, early failures or deletion errors can delay removal. A daily cleanup process targets unreferenced server photos more than 24 hours old; this is not a guarantee that every photo is removed within exactly 24 hours.
With photo retention on, photos referenced by confirmed meals remain in private hosted storage. Turning it off clears those history references and attempts removal. Sync and cleanup failures can delay that removal. Saving/discarding a draft normally removes its local processed photo; unsuccessful drafts or unreferenced local files can remain until later cleanup or app removal.
Exact production backup, infrastructure-log, support-mailbox and independent vendor retention periods still need confirmation. Operational backup/log copies may survive active-record deletion. Purchase providers may separately retain transaction history; the current account-deletion flow does not erase RevenueCat's customer record. We do not promise immediate deletion of every copy held by every provider.
Your choices and export
You can edit your preferred name, units and daily targets in Profile; choose manual food entry; change AI permission and photo retention; decline camera/photo access through iOS settings; and disable league participation. These optional permissions are not required for manual tracking.
Profile provides JSON data export and meal CSV export through the device share sheet. JSON contains available account tracking, preferences, local drafts without local image paths, progression, subscription-state and AI-allowance information; CSV contains meal items. These exports are not a complete archive of all authentication or provider records and do not include original photo files or payment-card details. Pending local edits are included. BodyXP removes its temporary export file after the share operation; saved or shared copies remain under your and the recipient's control.
Privacy policy and account controls remain available from the subscription screen without an active subscription. The policy is also available before sign-in. Email us for questions, access or deletion assistance, or other privacy requests. Additional rights may apply depending on where you live; we will consider applicable requirements without assuming a particular jurisdiction applies to every user.
Account deletion and sign-out
Delete account and tracking data is available in Profile and subscription Account Options without requiring a subscription. For an Apple-linked account, we ask you to verify with the linked Apple account and securely exchange that fresh authorization code on our server to revoke BodyXP's Apple authorization before deleting application data. Other accounts may need a recent sign-in. We do not retain Apple access or refresh tokens for this process. Canceling Apple verification leaves your account intact.
The service removes your owned hosted photos before deleting your hosted authentication account and its associated tracking, progression, league membership, preferences and AI records. After confirmed deletion, the app erases that account's local database records and pending sync changes, known draft photo copies, temporary app exports and active account state on the device performing deletion. A failed cleanup can require retrying. Some photos or Apple authorization may already have been removed; the service keeps limited retry metadata until account deletion completes. If local file cleanup fails after your account is deleted, restart BodyXP to retry it.
Signing out is different: it clears your active session, while an account-scoped offline cache can remain hidden on that device. Deletion does not remotely wipe another device's offline cache, your original photo-library assets, exports you saved or shared, or device/provider backups. Unindexed local orphan files can remain outside the known account cleanup. Remove user-saved copies separately if desired.
Deleting your BodyXP account does not delete your Apple or Google account. Removing the app alone is not account deletion. Account deletion also does not cancel subscriptions or automatically erase independent Apple/RevenueCat transaction history. Use Manage subscription to manage billing separately. Contact support if you need assistance with provider-held records.
Adults and international processing
BodyXP onboarding requires adult confirmation and is intended for people 18 or older. If you believe a child has provided information, contact us so we can investigate and address it.
Connected providers may process information in countries outside your own. Exact hosting regions, applicable transfer arrangements and account-specific vendor processing settings must be verified before public release; this policy does not promise storage in any one country or claim a particular certification or legal compliance regime.
Changes and contact
We will update this text when BodyXP's practices change and show the updated date. Material new sharing should be explained in the relevant feature before it occurs. For privacy questions or requests, contact CloudMint Soft at [email protected].