Privacy Policy

Policy version: 2026-10-08. Effective and last updated: October 8, 2026

BodyTracker helps you record body measurements, weight, and progress photos. This Policy explains what information is handled, where it is stored, why it is used, and the choices available to you.

1. Who is responsible

BodyTracker is provided by Igor Korolev ("BodyTracker," "we," "us," or "our"), who is the controller of personal information processed for the purposes described in this Policy. Contact: support@bodytracker.app.

2. Information handled by BodyTracker

Information you enter or create

• progress photos and their dates or body-position labels;
• body measurements, custom measurement definitions, target weight, units, gender selection, and birth date;
• weight records that you ask BodyTracker to read from or write to Apple Health;
• feedback text that you voluntarily send through the app; and
• purchase and entitlement status needed to unlock paid features.

Technical and usage information

If Analytics & Diagnostics is enabled, Amplitude and Google Firebase may receive a pseudonymous app or installation identifier, app interactions, purchase events, app version, device model, operating-system version, language or coarse region, performance measurements, and crash diagnostics. Amplitude may also receive your self-reported gender and an age band calculated on your device. BodyTracker does not send your exact birth date, birth year, exact age, photos, body measurements, weight, Health data, name, email address, or precise location to analytics. If the locally stored birth date indicates that a user is under 16, BodyTracker does not send demographic profile properties.

When you send feedback, our feedback service receives the text, a pseudonymous installation identifier and session identifier, submission time, app name and version, locale, time zone, and ordinary network information such as an IP address. BodyTracker does not request your email address for feedback.

Meta SDK — from iOS version 6.1

Starting with iOS version 6.1, BodyTracker also uses Meta SDK when Analytics & Diagnostics is enabled, to measure the effectiveness of app advertising and understand installation and conversion. The limited app events are installation/activation, onboarding completion, and the occurrence of a successful new purchase. BodyTracker does not pass purchase amounts, currency, product identifiers, receipts, transaction identifiers, demographic profile details, photos, body measurements, weight, or Apple Health data to Meta.

Advertising identifier (IDFA) collection is disabled, and BodyTracker does not request permission to access IDFA. This does not mean that no identifier is processed: Meta SDK uses its own pseudonymous installation identifier and technical app/device information, and Meta receives ordinary network information such as an IP address when requests are sent. Automatic app-event logging is disabled; the app explicitly sends only the events described above, while the SDK may also make technical service requests.

The same Analytics & Diagnostics setting controls Meta and Amplitude. Analytics is enabled by default unless you have already turned it off. Turning it off stops new app events being sent to Meta; when the app starts with this setting off, the Meta transport is not initialized. Already queued or in-flight SDK requests may still complete. Turning analytics off does not delete events previously received by Meta. The in-app erase action resets the local Meta installation identifier and local event-deduplication state; it does not itself delete historical data held by Meta.

3. Where health and progress content is stored

Photos, measurements, custom measurements, and exact profile settings are stored on your device. If Analytics & Diagnostics is enabled, only the demographic categories described above may be sent to Amplitude. If iCloud is available, photos and measurements may also be synchronized through your private Apple CloudKit database. Apple controls the iCloud service and its security. We cannot browse or retrieve the content of your private CloudKit database.

Weight information read from or written to Apple Health remains in HealthKit under Apple’s controls and your Health permissions. We do not receive it on our servers. You can change BodyTracker’s Health access in iOS Settings or the Health app.

Copies that you explicitly export to the Photos library are controlled through Apple Photos and are no longer managed by BodyTracker.

4. Why we use information

• Provide the app: display, store, synchronize, compare, and export the content you choose to create; maintain settings; and restore paid access. This is necessary to perform our Terms of Use.
• Feedback and support: receive and investigate feedback and maintain service security. This supports our legitimate interests in operating and improving BodyTracker.
• Analytics: understand feature use, audience characteristics, conversion, and product performance. This supports our legitimate interests in improving the app, subject to your right to turn Analytics & Diagnostics off.
• App advertising measurement (iOS 6.1 and later): measure installation and conversion from app advertising using the limited Meta events and technical information described in section 2, subject to the Analytics & Diagnostics setting.
• Diagnostics and security: detect crashes, reliability problems, abuse, and technical failures. This supports our legitimate interests in maintaining a secure and reliable service.
• Legal obligations: maintain records or respond to lawful requests when applicable law requires it.

5. Service providers and disclosures

We use service providers only for the functions described above:

• Apple: App Store purchases, iCloud/CloudKit, HealthKit, and platform services;
• Amplitude: product analytics when enabled;
• Meta: limited app advertising measurement through Meta SDK from iOS version 6.1 when analytics is enabled; see section 2 and Meta’s Privacy Policy for Meta’s processing and privacy information;
• Google Firebase: analytics, crash reporting, and performance monitoring when enabled; and
• our feedback infrastructure and hosting providers: feedback delivery, security, and operation of this website.

Providers process information under their own security and data-processing terms. Information may also be disclosed when required by law, to protect users or the service, or as part of a business transfer subject to appropriate safeguards. We do not sell personal information. From iOS version 6.1, the limited disclosure to Meta for app advertising measurement is described in section 2. Disabling IDFA collection does not make that disclosure anonymous.

6. International processing

Some providers may process information outside your country, including in the United States or other locations where they operate. Where required, we rely on contractual safeguards, adequacy decisions, or another lawful transfer mechanism. Private iCloud and Health data remains subject to Apple’s storage and residency arrangements.

7. Retention

• Device, private CloudKit, and HealthKit content remains until you delete it, use the in-app erase action, or remove it through the relevant Apple service. After erasure, a minimal local and private iCloud marker containing an erasure generation and time remains to prevent older records from returning.
• Feedback and its pseudonymous technical metadata remains until you use the in-app erase action or it is no longer needed for support, product improvement, security, or legal purposes. Uninstalling BodyTracker alone does not notify our feedback service.
• Analytics data is retained according to our configured provider settings and only as long as reasonably needed for product analysis. User- and event-level Firebase Analytics and Amplitude retention is targeted at no more than 14 months where the provider account supports that setting. Previously aggregated statistics may remain without identifying an individual installation.
• Meta may retain information it has received under its applicable terms and retention controls. No fixed Meta deletion period is promised here. Turning analytics off or resetting the local installation identifier does not automatically remove previously received Meta events. Contact us with a privacy or deletion request as described in section 8.
• Firebase Crashlytics generally retains crash reports and associated installation identifiers for 90 days before deletion begins. Performance information is maintained in aggregated or de-identified form according to Firebase’s service controls.
• Purchase and entitlement records may remain as long as needed to restore paid access, maintain transaction records, prevent fraud, and meet legal obligations.
• Security logs and backups are retained for limited operational cycles and then deleted or overwritten.

8. Your choices and rights

You can turn Analytics & Diagnostics off in Settings. You can change camera, Photos, iCloud, and Health permissions in iOS. You can erase BodyTracker-managed content using Settings → Erase BodyTracker Data; see the Data Erasure Guide.

Depending on where you live, you may have rights to know or access personal information, correct it, delete it, restrict or object to processing, obtain a portable copy, or withdraw consent where consent is the legal basis. You may also appeal a refusal where local law provides that right and complain to your local privacy regulator. We will not discriminate against you for exercising privacy rights.

To make a request, email support@bodytracker.app. Because BodyTracker has no account system and intentionally holds little directly identifying information, we may ask for information reasonably necessary to locate the relevant pseudonymous record and verify that the request relates to your installation.

9. US state privacy disclosures

In the preceding 12 months, the categories handled may include identifiers, internet or electronic activity, commercial information, device or diagnostic information, user content, and health or body information stored under your control. We use and disclose these categories only for the purposes and provider categories described above. We do not sell personal information. From iOS version 6.1, limited app advertising measurement information is disclosed to Meta as described in sections 2 and 5; this version of the Policy includes that disclosure. We do not use sensitive personal information to infer characteristics for unrelated purposes.

10. Children

BodyTracker is intended for people aged 16 or older. We do not knowingly collect personal information from anyone under 16. If you believe a person under 16 has provided information through feedback or analytics, contact us so we can investigate and delete it where appropriate.

11. Security

We use measures appropriate to the nature of the information, including Apple platform protections, encrypted network transport, access controls, pseudonymous identifiers, and data minimization. No storage or transmission method is completely secure.

12. Changes

We may update this Policy when the app, providers, or legal requirements change. The current version and effective date will remain available on this page. We will provide additional notice in the app when a change materially affects your rights or how information is used.

Policy history: this revision adds the Meta SDK disclosure for iOS version 6.1 and later. Previous published policy (effective September 9, 2026). Earlier app versions remain subject to the policy applicable to their processing; this update does not add Meta SDK to an already installed older app.

13. Contact

Privacy questions and requests: support@bodytracker.app.