Privacy Policy

1. General Provisions

The App is a local health tracker and does not require registration, an account, or social media login. The App has no server infrastructure for storing medical data. Medical data remains on your device unless you explicitly export, back up, or share a file.

The App automatically transmits only limited technical device data for installation registration (Section 2.3) and data processed by advertising SDKs (Section 4).

2. What Data Is Collected and Stored

2.1. User-Entered Data

The App stores the following information on your device that you enter manually:

• Profiles: name, color, avatar photo, date of birth, weight, height, initial health parameters;
• Medications: name, dosage, form, unit of measurement, color, description, image, meal association, intake schedule, stock balance;
• Medication intake log: date, time, dose, status (taken / missed / cancelled), notes;
• Health metrics: metric type (blood pressure, heart rate, weight, etc.), value, date, time, notes;
• Measurement schedules: metric, schedule, reminder offset;
• Doctor visits: date, time, specialist, notes, reminders;
• Doctor contacts: name, specialty, phone, email, website, clinic, address (street, postal code, city), notes;
• Images: photos of medications or profile, selected from the gallery or taken with the camera;
• App settings: interface language, theme, time format, notification settings, home screen widgets.

2.2. Data Not Collected by the App

The App does not collect or transmit:

• Geolocation data;
• The device's contact book;
• Audio data — the App does not record or process sound;
• Data about the use of other apps;
• Device advertising identifiers (IDFA/AAID) — except where processed by the advertising SDKs described in Section 4, subject to platform and SDK privacy settings.

The App stores only the personal data you voluntarily enter for profiles (name, date of birth, weight, height). This data is not automatically transmitted and leaves the device only when you explicitly export, back up, or share it.

2.3. Automatically Transmitted Technical Data (Device Registration)

On each cold start, the App sends a single registration request to the developer's server at app.dev-lab.app containing only technical and statistical information:

• Anonymous installation identifier (a random UUID generated and stored on your device; it is not linked to your identity or accounts);
• Device brand, manufacturer, model, and type (phone/tablet);
• Total memory and device year class;
• Platform and operating system version;
• Language tag/code, region code, and text direction;
• Timezone, 24-hour clock setting, and first weekday;
• App version, advertising provider, and launch timestamp.

No profile, medication, health metric, doctor, image, or other user-entered data is included in this request. If the request fails, it is not retried until the next app launch and does not affect the App's functionality.

3. Where Data Is Stored

• Local device storage: domain data is stored in a local SQLite database; limited first-run settings are stored in AsyncStorage.
• Servers: the App does not transmit your medical data to our servers because the App has no account or medical-data backend. The only automatic transmission is the technical device registration described in Section 2.3.
• Operating-system backup: data may be included in an iCloud / Google Drive device backup if you enable that feature at the operating-system level.
• In-app export and backup: the App can create reports (CSV/PDF) and a password-encrypted .balancium-backup file. Files remain local until you explicitly choose a destination or third-party app through the system share/file picker; that destination then handles the file under its own privacy terms.

4. Advertising (Google AdMob and Yandex Mobile Ads)

The App uses the Google Mobile Ads SDK (Google AdMob) and Yandex Mobile Ads SDK to display banner, interstitial, and rewarded ads. The App does not send profile, medication, health, or doctor data to either SDK or use it to target ads.

4.1. Data Processed by Advertising SDKs

Depending on the platform and SDK configuration, the advertising providers may process limited technical and advertising data needed to deliver and measure ads, such as:

• Device advertising identifiers or other device identifiers, where available under the operating system and SDK settings;
• IP address and network information used for ad delivery;
• Device and operating-system information;
• Ad request, impression, and interaction data.

For details, see the providers' privacy information:

• Google Privacy Policy
• How Google uses information from sites and apps that use our services
• Yandex Ads Privacy Policy
• Yandex Mobile Ads data safety for Android

4.2. Ad Personalization and Consent

Google ad requests are configured for non-personalized ads. The App does not implement an App Tracking Transparency (ATT) prompt. The Yandex SDK is configured with setUserConsent(false) at startup; this is not a consent dialog and does not grant consent to process personal data. Yandex documents that this setting restricts processing of personal data for users in GDPR-covered regions when consent has not been given. The SDK may still process technical and advertising data needed to deliver and measure ads, subject to platform and SDK settings.

You can manage advertising identifiers and ad privacy controls in your device settings. Any future change to consent, personalization, or tracking must be reflected in the App, this Policy, and applicable store disclosures before release.

5. Notifications and Reminders

The App uses local notifications for medication intake reminders, health measurement reminders, and doctor visit reminders.

5.1. Permissions Requested by the App

• Notifications: for displaying reminders;
• Exact alarms (Android): SCHEDULE_EXACT_ALARM, USE_EXACT_ALARM — for timely reminder triggers;
• Boot on startup (Android): RECEIVE_BOOT_COMPLETED — for restoring scheduled reminders after device reboot;
• Ignore battery optimization (Android): REQUEST_IGNORE_BATTERY_OPTIMIZATIONS — so reminders are not missed due to power saving;
• Full-screen notifications (Android): USE_FULL_SCREEN_INTENT — for displaying full-screen reminders.

5.2. Camera and Photos

• Camera: used only at your request to photograph a medication or profile image;
• Photo gallery: used only at your request to select a medication or profile image.

Images are stored locally on the device and are not transmitted to servers.

5.3. Microphone

The App does not record, store, or transmit audio. No app feature uses the microphone.

5.4. Haptic Feedback

The App uses haptic feedback (vibration) via expo-haptics for tactile confirmation of certain actions. No data is collected or transmitted through haptic feedback.

6. External Links and Actions

The App may open external apps via system intents:

• Doctor's website: opens in the device's browser;
• Doctor's email: opens in the device's email client with a pre-filled address;
• Doctor's phone: opens in the phone app with a pre-filled number;
• Doctor's address: opens in browser/maps for directions.

The App also allows you to share a link to the App via the system share sheet (SMS, messengers, social networks). No data is transmitted to third parties during these actions — only the data you entered for the doctor contact or the App's store link is used.

7. Data Sharing with Third Parties

The App does not sell, rent, or automatically share your medical data with third parties. You may explicitly send exported reports or backup files to a destination you select.

The only automatic data transmissions are:

• Device registration — limited technical data sent to the developer's server app.dev-lab.app, as described in Section 2.3;
• Google AdMob and Yandex Mobile Ads — limited advertising and technical device data, as described in Section 4.

8. Data Security

The working database relies on your operating system's access controls and device encryption. User-created .balancium-backup files receive additional password-based encryption using AES-256-GCM with PBKDF2-HMAC-SHA256 key derivation. Report exports such as CSV/PDF are not encrypted by the App, so you should choose their destination and recipients carefully.

9. Data Deletion

You can delete all App data at any time:

• Via the App interface: delete individual records, medications, measurements, visits, and doctor contacts;
• Profile deletion: delete entire profiles with all associated data;
• App deletion: completely removing the App from the device will delete all related data.

The anonymous installation identifier sent during device registration (Section 2.3) is not linked to your identity or to any data stored in the App.

10. Children

The App is not intended for use by children under 13 and does not knowingly collect children's data. If you believe a child has provided us with data, please contact us to have it deleted.

11. User Rights

Depending on your region (GDPR for EU/UK, CCPA for California, etc.), you have the right to:

• Access data: all data is available to you directly in the App;
• Delete data: you can delete data via the App interface or by deleting the App;
• Correct data: you can edit any data in the App at any time;
• Export data: the App provides a data export and backup feature via the data management screen;
• Manage ad privacy: through device settings; Google ad requests are non-personalized and Yandex consent is not granted by the App (see Section 4.2).

Since medical data is stored only locally, we cannot delete or modify it remotely — all operations are performed on your device. For questions about the technical data received through device registration, contact us (Section 14).

12. International Users

The App is available in three languages: English, Russian, Ukrainian. Medical data is stored locally unless you explicitly export or share it. Advertising and technical data processed by Google AdMob or Yandex Mobile Ads, technical registration data sent to app.dev-lab.app, and files sent to destinations you select, may be transferred across national borders under the recipients' policies.

13. Changes to the Policy

We may update this Privacy Policy. Changes will be communicated by updating the effective date at the beginning of the document. We recommend periodically checking the current version.

14. Contacting the Developer

If you have questions about this Privacy Policy or data processing in the App, please contact us: