Your Weight Story
Privacy policy
Privacy information for the free V2 Android app Your Weight Story and for relevant historical installations, published by Gustavo Pacheco.
Summary
What the app does
The free V2 release of Your Weight Story is a personal-wellness app. It records weight and nutrition entries, shows BMI and trend summaries, keeps a target plan, estimates maintenance and target calories from the profile you provide, records body measurements and optional local body-progress photos, stores reminders on your device, and supports ingredient-name and barcode lookups. The ad-enabled release is supported by Google-served native and interstitial advertising.
Build 125 and later free V2 builds do not require an account, trial, or subscription to use local tracking features and do not analyze meal photos. Build 127 adds only an optional recovery action for people with a historical ad-free right; it does not create an account gate, trial, purchase, or subscription. The Historical version behavior section keeps this policy accurate for earlier installations while they remain relevant.
Data
Data the app handles
The app may store the following information locally on your device:
- Age, height, sex, and activity level
- Weight entries and dates
- Body measurement sessions, optional local measurement photos, and optional notes
- Body-composition estimates calculated from your measurements
- Nutrition entries, saved foods, and dishes
- Goal weight, goal dates, and plan settings
- Reminder preferences and local app settings
Optional body-progress photos attached to measurement sessions stay in the app's local storage on your device. The app opts out of Android cloud backup and device-to-device transfer for its app data.
Firebase Analytics may collect basic app usage, device, and session information to help us understand aggregate engagement, campaign measurement, and reliability. The Analytics property is linked to Google Ads for campaign measurement and conversion reporting. Personalized Advertising is disabled on both Google Ads links, so Analytics audiences and events or parameters are not published to those accounts for ads personalization. In an ad-enabled build, the Google Mobile Ads SDK automatically collects and shares an IP address, app and ad interactions, diagnostic information, and device or account identifiers such as the Android advertising ID and App Set ID, when available. An IP address may be used to estimate a device's general location. Google documents these uses as advertising, analytics, and fraud prevention. Data sent by the Google Mobile Ads SDK is encrypted in transit.
Usage
How data is used
Information you enter is used to calculate and display weight trends, BMI, goal pacing, estimated maintenance and target calories, consistency summaries, measurement history, body-photo comparisons, body-composition estimates, nutrition summaries, and reminders inside the app.
Barcode lookups send the scanned barcode value to the app backend. Ingredient-name searches send the search text to the same service. These requests return editable ingredient suggestions and may be subject to limited technical logging for security, rate limiting, and reliability. Firebase Analytics data is used for aggregate app analytics, campaign measurement and reliability. Personalized Advertising is disabled on the Analytics-to-Google Ads links.
The app does not add weights, measurements, body-composition estimates, nutrition entries, goals, notes, photos, email addresses, or Firebase user IDs to advertising requests, custom ad targeting, Firebase Analytics event parameters, user properties, audiences, or lookup-request metadata. Ingredient-name search text is sent only as the lookup query you request; it is not sent for advertising, custom targeting, or Firebase Analytics.
Advertising
Ads and privacy choices
In an ad-enabled build, Your Weight Story uses the Google Mobile Ads SDK to display native ads within a dashboard surface and interstitial ads at eligible transition points. Google and the advertising technology partners listed in the consent message may process the SDK data described above to deliver and measure ads, provide analytics, limit repeated ads, and detect fraud or abuse.
Depending on your region and choices, ads may be personalized, non-personalized, or limited. The app uses Google's User Messaging Platform to request updated consent information before requesting ads where required. When the platform requires a privacy-options entry point, the app provides Ad privacy options in its Data and privacy settings so you can review or change your choices. Declining or changing an advertising choice does not remove access to local app features.
Ad privacy choices presented through the User Messaging Platform govern Google Mobile Ads. They do not by themselves disable Firebase Analytics collection or change that service's consent and personalization settings.
You can reset or delete the Android advertising ID through Android settings. Learn more about Google's advertising technologies and how Google uses information from apps that use its services.
Sharing
Data sharing
Weight entries, body measurements, local body-progress photos, notes, nutrition entries, goals, and calculated estimates stay on the device and are not sold or shared for advertising. Barcode values and ingredient search text are sent to the app backend only to provide the requested lookup. Firebase Analytics data is processed by Google/Firebase as the analytics provider. The Analytics property remains linked to Google Ads for campaign measurement and conversion reporting, but Personalized Advertising is disabled on both links. In an ad-enabled build, the Google Mobile Ads SDK collects and shares the advertising, interaction, diagnostic, IP-address, and identifier data described above with Google and applicable advertising partners. If you explicitly choose Restore ad-free access, Google/Firebase also processes the temporary authentication data and owner-scoped entitlement described below only to perform that recovery. As a one-time upgrade safeguard, build 127 can also finish the same owner-scoped entitlement check for a Firebase session that an earlier installed build had already left signed in, then immediately end that historical session.
Accounts
Optional recovery of historical ad-free rights
Build 125 and later free V2 builds do not require sign-in and do not offer a trial, paywall, or new subscription purchase. Build 127 provides an optional Restore ad-free access action in Settings for people who previously paid for, or were manually granted, an ad-free right. Local tracking remains fully available if you do not use this action.
If you choose recovery, Android Credential Manager lets you select a Google account and Firebase Authentication temporarily processes the resulting sign-in. This can include an IP address, app/device and user-agent metadata, Firebase user ID, authentication token and provider, and any email address or display name supplied by Google. While authenticated, the app reads only the Cloud Firestore entitlement document whose ID matches your own Firebase user ID. The app does not write a trial or entitlement. The document may contain subscription status, plan/provider identifiers, and an expiry date.
If the entitlement contains a still-valid historical paid or manually granted ad-free expiry, the app stores only that expiry marker locally. It does not store the selected email address, display name, Firebase user ID, or authentication token in the recovery cache. The app then signs out of Firebase and clears the Credential Manager session. If no valid right is found, a newly created Firebase Authentication account is deleted immediately where possible before sign-out. If deletion cannot finish because of a network, provider, or authentication error, the account record may remain until it is deleted through the instructions below.
On the first build 127 run, an installation that still has a Firebase session from an earlier build may perform one server-only read of that already authenticated user's entitlement as a compatibility migration. A valid expiry is cached locally as described above; a missing entitlement or read error is not cached. In every outcome, the app completes that one-time check and signs out immediately. It does not keep a Firebase session or continue monitoring the account in the background.
Recovery never blocks local features, starts a trial, makes a purchase, or enables a subscription. While a plausible historical entitlement is unresolved, advertising is suppressed. Account-related data may also be used to answer support and deletion requests. Your Weight Story is intended for users aged 18 and over.
Versions
Historical version behavior
Builds 123 and earlier may have offered Google/Firebase sign-in, a trial, paid subscription access, and optional meal-photo ingredient suggestions. Those versions could process an email address, display name, Firebase user ID, authentication provider/tokens, IP and device/app metadata, trial state, subscription/discount state, and entitlement dates for authentication, account management, access, fraud prevention, support, and deletion requests.
When a user explicitly chose meal-photo analysis in an earlier version, the selected photo could be sent to the app backend or processing provider to return an editable ingredient suggestion. The app backend did not retain the meal photo after the request, although limited derived request records could be kept for limits, security, reliability, and abuse prevention. Those earlier versions could request camera access for capture and microphone access for an optional voice correction. Build 124 removed the meal-photo, trial, purchase, and account-gate paths; build 125 carries that absence forward. Build 127 adds only the optional, temporary ad-free recovery process described above and does not restore any trial, purchase, meal-photo, or account-gate path.
These historical disclosures remain applicable while an earlier artifact or installation still processes that data. They do not re-enable those paths in the free V2 app.
Permissions
Permissions used
The app may request notification permission for reminders. It may request camera permission when you choose barcode scanning or capture a local body-progress photo. You can decline or disable these permissions in Android settings. Build 125 and later do not request camera or microphone access for meal-photo analysis.
Retention
Retention
Weight entries, nutrition entries, measurements, local body-progress photos, notes, goals, reminders, and local app settings remain on the device until you clear them or uninstall the app. Consent choices are stored on the device by the User Messaging Platform and may be refreshed when required. Google/Firebase and Google Mobile Ads retain provider data according to their settings, legal obligations, and published policies.
Historical Firebase Authentication and entitlement records may be retained while needed to preserve an ad-free right, respond to deletion or support requests, handle payment disputes, prevent abuse, or meet legal and accounting obligations. A temporary recovery session is ended after the recovery attempt. A new account created during an unsuccessful recovery is deleted immediately where possible; if that cleanup fails, it may remain until a verified deletion request is processed.
A locally cached ad-free expiry marker may remain after clearing tracking data, only to avoid showing ads during a previously verified paid/manual period. It contains no weight, measurement, nutrition, photo, email, or Firebase user ID and is ignored after expiry; uninstalling the app removes it.
Deletion
Your controls
You can clear local tracking data from the app's Data and privacy settings. Removing the app deletes its remaining app-local data. Advertising choices can be reviewed through the in-app Ad privacy options entry point when it is required, and the Android advertising ID can be reset or deleted in Android settings. Data and privacy settings also provide an in-app path to the account-deletion instructions below.
If you have a historical Your Weight Story account, or if an optional recovery attempt could not delete a newly created account automatically, see the account and data deletion instructions to request deletion of associated account data.
Deleting Firebase authentication or account data does not cancel a Google Play subscription and does not stop renewals. Existing subscribers can use Manage historical subscription in the app's Data and privacy settings, or open the Google Play subscription management page, to manage or cancel separately.
Wellness note
Medical disclaimer
Your Weight Story is intended for personal wellness tracking and is not a medical device. It does not provide diagnosis, treatment, or emergency guidance.
BMI, pace, calories, body fat, fat mass, lean mass, RFM, and waist-to-height views are estimates based on the profile details and measurements you enter. They are more useful for following trends than as medical results. Review very low, high, or unsuitable targets with a licensed clinician or dietitian.
Support
Contact and scope
Health entries, measurements, body-progress photos, notes, and estimates stay local and are not used for ad targeting.
Barcode values and ingredient search text are sent only for the lookup you request.
Firebase Analytics and Google Mobile Ads process the provider data described above.
Privacy questions can be sent to noreply@toodl.xyz.