Privacy Policy

1. Who we are

This Privacy Policy applies to the HealthArchive mobile application (“App”) published by Mobicolon (“we,” “us,” or “our”).

Contact: support@mobicolon.com

2. Scope

This policy describes how the App handles information when you install and use HealthArchive on an Android device. HealthArchive is an Offline-First application. Your medical records remain on your device unless you explicitly export or share them. By continuing to use the App, you acknowledge that you have read this Privacy Policy.

3. Health and personal data stored on your device

The App allows you to store information locally on your device, which may include:

• Family member details (name, relationship, date of birth, blood group, gender, phone number, notes, photo)
• Health records (title, type, date, hospital, doctor, notes, tags)
• Medical documents (images, PDFs, scanned files)
• App settings (theme, PIN lock, biometric lock, last backup time)
• Recent search terms (saved locally on your device)

This data may be sensitive and health-related. It is stored in the App’s private storage on your device. Sensitive data is protected using AES-256 encryption with Android Keystore where applicable. Encryption keys are never stored in plain text.

We do not upload, access, sell, or sync your health records to Mobicolon servers.

3.1 Biometric authentication

HealthArchive uses the official Android BiometricPrompt API for optional app lock. You should know that:

• Fingerprints and Face Unlock data are never collected, stored, or transmitted by HealthArchive.
• Biometric authentication is handled entirely by Android and your device manufacturer.

3.2 PIN lock

If you enable PIN lock:

• Your PIN is stored securely on your device.
• Your PIN is never uploaded to Mobicolon or any third-party service.
• Your PIN is never shared with other users or applications.

4. Data we collect and send to our systems

We do not collect your medical records, patient names, family member names, doctor names, hospital names, notes, images, PDFs, backup contents, search text, or PIN.

HealthArchive does not use customer medical records to train artificial intelligence models.

The App may send limited, non-medical technical information to Google Firebase:

4.1 Firebase Analytics (anonymous usage)

Used to understand feature usage and improve the App. Analytics events never include:

• Medical records
• Patient names
• Family member names
• Doctor names
• Hospital names
• Notes
• Images
• PDFs
• Search text
• Backup contents

Only anonymous feature usage statistics are collected. Examples of events:

• Backup created (success or error category only)
• Restore completed (mode and success or error category only)
• Search used (filter type, result count range, query length range — not search text)
• Member saved (new or edit only)
• Record saved (new or update only)
• PIN lock enabled
• Biometric lock enabled

We do not use analytics to identify you personally. Advertising ID collection is disabled in our configuration.

4.2 Firebase Crashlytics (release builds only)

Used to diagnose crashes and stability issues in production releases. Crash reports contain only technical diagnostic information used to improve app stability. Crash reports never include medical content. May include:

• App version and device/OS information
• Non-sensitive error categories (e.g., backup corrupted, invalid format)
• Technical stack traces

Crash reports do not include health record content or user-entered medical text. Crashlytics is disabled in debug builds.

5. Google Play Data safety summary

The following summary is provided to help you understand our data practices for Google Play. This Privacy Policy is designed to comply with the Google Play User Data Policy, Google Play Health Apps requirements, and Firebase Analytics and Crashlytics disclosure requirements.

Data is not sold. Data is not used for targeted advertising of health content.

6. Permissions

Permissions are used for on-device features. They are not used to upload your health data to Mobicolon.

7. Backup and restore

You may create encrypted .healtharchive backup files and save them anywhere you choose. Backup files are encrypted, include integrity verification, and corrupted or modified backup files are rejected before restore. Backup files are never uploaded to Mobicolon servers. You control those files. If you store backups in Google Drive or other cloud services, their privacy policies apply. We do not receive your backup files unless you independently send them to us.

8. Sharing and export

When you share records or PDFs using Android’s share menu, the app or person you select receives the data you export. We do not control third-party apps or services you choose for sharing.

9. Third-party service providers

• Google Firebase — Analytics and Crashlytics (Firebase Privacy)
• Google ML Kit — On-device document scanning
• Google Play services — Required Android platform services

10. Data retention and deletion

• On-device health data: Kept until you delete it, restore a backup, clear app data, or uninstall the App.
• Analytics and crash data: Retained by Google Firebase according to Google’s retention policies.

Because we do not host your health data, we cannot delete it remotely. You can delete data in the App or uninstall the App.

11. Security

We use measures intended to protect your information, including:

• AES-256 encryption for sensitive data at rest
• Android Keystore for secure key management (encryption keys are never stored in plain text)
• Biometric authentication via Android BiometricPrompt (handled entirely by Android)
• PIN lock stored securely on device; never uploaded or shared
• Encrypted backups with integrity verification
• Local storage — health records remain on your device unless you export or share them

No security method is perfect. Keep your device updated and protect your PIN and backup files.

12. Children’s privacy

The App is not directed to children under 13. We do not knowingly collect children’s information on our servers. If a child uses the App, a parent or guardian should supervise use and data remains on the device.

13. International users

Your health data stays on your device. Limited technical data sent to Firebase may be processed by Google in various countries. See Google’s privacy documentation for international transfer details.

14. Your choices

• Delete records and members inside the App
• Disable PIN or biometric lock in Settings
• Avoid cloud backups if you do not want copies outside your device
• Uninstall the App to remove local app data from your device

15. Changes to this policy

We may update this Privacy Policy. The “Last updated” date will change when we do. Continued use of the App after updates means you accept the revised policy.

16. Contact us

Mobicolon
Email: support@mobicolon.com
App: HealthArchive

See also: HealthArchive Terms & Conditions · Mobicolon Website Privacy Policy