MappDev Home

Privacy Policy

MiB10 WF

How MappDev handles information in connection with the Android application MiB10 WF (Mi Band 10 Watch Faces).

App
MiB10 WF (Mi Band 10 Watch Faces)
Package
com.mappdev.miband10wf
Developer
MappDev
Effective date
August 11, 2026
Last updated
August 14, 2026

This Privacy Policy describes how MappDev (“we”, “us”, or “our”) handles information in connection with the Android application MiB10 WF (the “App”). By using the App, you agree to this Policy.

1. Overview

MiB10 WF lets you browse, preview, and install custom watch faces on a Xiaomi Mi Band 10 over Bluetooth. The App does not create its own user account. Optionally, during watch-face installation, you may sign in with your Xiaomi / Mi Fitness account so the App can fetch the band authentication key.

2. Information we process

2.1 Information stored only on your device

This data stays on your device unless you clear the App’s storage or uninstall the App.

2.2 Optional Xiaomi / Mi Fitness login

To install a watch face, the App may ask for your Xiaomi / Mi Fitness account credentials (email or Xiaomi ID and password). Those credentials are sent only to Xiaomi account / health servers so the App can retrieve the Bluetooth authentication key for your paired band. We do not receive, store, or transmit your Xiaomi password to our own servers.

The retrieved authentication key is stored only on your device and used for Bluetooth installation. You can instead enter the key manually or import it from a Mi Fitness device log without signing in.

2.3 Bluetooth / device connection

To find and connect to your Mi Band 10, the App uses Bluetooth (including Bluetooth scan and connect permissions on newer Android versions). Connection is used only to transfer watch-face data to your band.

We do not use Bluetooth scanning to determine your precise location (BLUETOOTH_SCAN is declared with neverForLocation).

Information needed for the local Bluetooth session (such as nearby BLE device identifiers visible during scanning) is used on-device for pairing/transfer and is not uploaded by us to a user profile.

2.4 Content delivery (Firebase)

The App uses Google Firebase services to provide the watch-face catalog and images:

When the App requests this content, standard technical data needed to operate the service (such as IP address, device/app identifiers used by Google’s infrastructure, and request logs) may be processed by Google Firebase under Google’s terms. We use Firebase to deliver App content, not to build a personal advertising profile about you in our own systems.

2.5 Advertising (Google AdMob)

The free version of the App shows ads served by Google AdMob (banner, interstitial, and rewarded formats). AdMob and its partners may collect or receive information such as:

This information is used to show, measure, and (where permitted) personalize ads. You can limit ad personalization in your device settings (for example, Android’s ads / privacy settings) and through any consent / privacy options presented by the ad SDK where applicable.

Learn more:

2.6 In-app purchases (Google Play Billing)

Optional subscriptions to remove ads are processed by Google Play Billing. Purchase validation and payment details are handled by Google. We only keep local flags needed to unlock the ad-free experience on your device. We do not receive your full payment card details.

Google’s handling of purchase data is described in the Google Privacy Policy.

3. Permissions

Depending on your Android version, the App may request:

The App does not request access to your contacts, camera, microphone, precise location, or photos/media library for its core features.

4. How we use information

5. Sharing of information

We do not sell your personal information. Information may be processed by service providers that power the App:

These providers process data under their own privacy policies and applicable agreements with us.

6. Data retention

7. Children’s privacy

The App is not directed to children under 13 (or the equivalent minimum age in your country). We do not knowingly collect personal information from children. If you believe a child has provided personal information through the App, contact us and we will take appropriate steps.

8. Your choices

9. International processing

Service providers such as Google may process data on servers outside your country of residence. Where required, appropriate safeguards are applied by those providers.

10. Changes to this Policy

We may update this Privacy Policy from time to time. The “Last updated” date at the top will change when we do. Continued use of the App after an update means you accept the revised Policy.

11. Contact

If you have questions about this Privacy Policy or the App’s privacy practices, contact MappDev through the MiB10 WF listing on Google Play, or email mappdev.p@gmail.com.

12. Third-party policies