Privacy Policy

1. Scope

This policy applies primarily to the Android and iOS builds of BMI - Clinical Calculator. Some functions described below may be unavailable on other platforms or in builds where they are not configured.

2. Data Entered for BMI Calculations

The application does not require registration and does not create a user account. While using the application, a user may enter data needed for BMI calculation.

• height;
• weight;
• age or age range used for BMI interpretation;
• selected measurement units;
• selected gender;
• chosen BMI calculation mode and reference standard.

3. Data Stored Locally on the Device

The application may store the following information locally on the user's device:

• theme preference;
• selected language;
• preferred measurement units;
• selected gender;
• BMI calculation mode and reference preferences;
• saved profiles and measurement history, which may include full name, sex, date of birth, measurement date, height, weight, and calculated BMI;
• time of the last App Open ad display;
• temporary ad-free expiration time after a rewarded ad, where applicable;
• other local state needed to restore profile access, premium-related UI state, and app behavior, where applicable.

4. Advertising, Consent, and Tracking Permissions

The Android and iOS versions may use Google AdMob to display advertisements. Before requesting ads, the application may display a Google consent form where required by law or platform policy. On Android, Google and its partners may process technical data such as the Android Advertising ID, app instance identifiers, device identifiers, IP address, device and network information, ad interaction information, and data needed for fraud prevention, frequency capping, ad delivery, and measurement. On iOS, the application may request App Tracking Transparency authorization. If permission is granted, Google may use the Identifier for Advertisers (IDFA) where allowed. If permission is denied, Google may still use non-personalized or limited measurement mechanisms, including SKAdNetwork attribution and other privacy-preserving signals supported by iOS. If a paid subscription or temporary ad-free state is active, the application suppresses ads while that state remains in effect.

5. Firebase Services

The application uses Firebase Analytics, Firebase Crashlytics, and Firebase Remote Config. Firebase Analytics may process app usage information such as screen views, selected language, theme, unit preferences, BMI calculation mode, privacy option availability, subscription-related events, profile-management events, profile import or export events and counts, and aggregated BMI result categories. Exact height, weight, age values, and full saved profile contents are not sent as analytics events. Firebase Crashlytics may process crash reports and technical diagnostics such as app version, device metadata, timestamps, stack traces, and error information to help diagnose application stability and integration failures. Firebase Remote Config is used to download operational settings such as ad enablement, ad unit identifiers, refresh intervals, app version requirements, and update links. As part of Firebase service operation, Google may receive technical data such as app instance data, device metadata, and IP address.

6. Purchases and Subscriptions

The Android and iOS versions may offer a subscription that removes ads and may also unlock premium-only features, depending on the current build. The application uses RevenueCat to present subscription interfaces, restore purchases, check entitlement status, reconcile purchase status, and open subscription management tools. Purchase processing itself is handled by the relevant platform store, such as Google Play or the Apple App Store, together with RevenueCat. These providers may process subscription status, entitlement state, product or offering identifiers, purchase, renewal, expiration, cancellation, and restoration metadata, platform account identifiers or other service identifiers, and technical information needed to validate, restore, reconcile, and manage purchases. The developer does not receive or store full payment card details. The application may also keep local subscription-related state needed for app behavior, such as the current premium entitlement result, subscription UI state, and the expiration time of a temporary rewarded ad-free period. A temporary rewarded ad-free period is a local app benefit and is not itself a store-billed subscription. Subscription billing, renewals, cancellations, and refunds are generally managed by the relevant platform store under that store's own terms and privacy practices.

7. Sharing Data with Third Parties

The developer does not sell users' personal data. The developer does not send exact height, weight, or age values to the developer's own server. Technical and service-related data may be processed by Google AdMob, Google Firebase, RevenueCat, Google Play, and Apple, depending on the feature being used and the platform. If the user imports a profile backup or exports profile JSON or CSV files, the selected files may be read from device storage and the exported files may be shared with apps, services, or recipients chosen by the user through operating-system file and sharing tools.

• the developer does not sell users' personal data;
• the developer does not send exact height, weight, or age values to the developer's own server;
• technical and service-related data may be processed by Google AdMob, Google Firebase, RevenueCat, Google Play, and Apple, depending on the feature and platform;
• if the user imports or exports profile files, the selected files may be read from device storage and shared through operating-system tools.

8. Children

The application can be used to calculate BMI for adults and children, but it does not create child accounts and is not designed to knowingly collect children's personal data for the developer's own backend. Where local law requires additional protections for child-directed services, the developer recommends use under the supervision of a parent or legal guardian.

9. User Choices and Rights

Users may manage local settings, ad consent, iOS tracking permission, file import and export, subscriptions, local app data, and ad personalization.

• change local settings within the application;
• manage ad consent through the privacy options interface when it is available;
• manage tracking permission for iOS through system settings;
• import or export profile backup and history files through in-app tools where those features are available;
• restore purchases and manage subscriptions through the subscription tools provided in the app and by the relevant app store;
• clear the application's local data through device settings;
• limit ad personalization through Google tools, Apple settings, or device settings where such controls are available.

10. Storage and Security

Locally stored settings and profile data remain on the user's device unless the user chooses to export or share them. The developer takes reasonable measures to avoid collecting unnecessary data and to avoid transmitting exact BMI input values to the developer's own server. If a user exports or shares a profile file to another app, cloud service, or recipient, that destination's privacy practices will apply to the copied data.

11. Changes to This Policy

This Privacy Policy may be updated if the application's functionality, SDK integrations, data processing practices, or advertising and subscription tools change. The current version should be made available through the public privacy policy link associated with the application.

12. Contact Information

For privacy-related questions, users may contact the developer using the email address jvp.creator+bmic@gmail.com.

13. Website analytics and consent

The public website may use Google Analytics 4 to measure traffic sources, page views, scroll depth, outbound clicks, file downloads, approximate region, device type, and general navigation patterns. Analytics on the website is enabled only after the user grants consent through the banner. The choice is stored locally in the browser and can be changed later through the analytics settings link in the footer. This mechanism is not used to enable personalized advertising.