Android App

Privacy Policy – Smart Watch :Bluetooth Connect

App: Smart Watch :Bluetooth Connect Developer: Bityapp Studio Updated: May 16, 2026 Email: contact@bityapp.xyz

This Privacy Policy explains how Smart Watch :Bluetooth Connect collects, uses, and protects information when users connect Bluetooth smartwatches and wearable devices using our Android application.

1. Information We Collect

The application may collect limited technical and usage-related information including:

  • Bluetooth pairing and smartwatch connection status
  • Device model and Android OS version
  • Crash logs and diagnostics (via Firebase Crashlytics)
  • App usage events, session data, daily active users (DAU), and monthly active users (MAU) (via Firebase Analytics)
  • Advertising identifiers (Google Advertising ID)
  • Push notification tokens used by Firebase Cloud Messaging (FCM)
  • General network connectivity information
We do not sell personal information to third parties.

2. Android Permissions Used

The app requests the following Android permissions depending on your Android version and enabled features.

Permission Android Version Purpose
BLUETOOTH / BLUETOOTH_ADMIN API ≤ 30 only Required on older Android versions to discover and communicate with smartwatch devices.
BLUETOOTH_SCAN API 31+ Used to scan nearby Bluetooth smartwatches and wearable devices. This permission is declared with usesPermissionFlags="neverForLocation", which explicitly prevents the system from using Bluetooth scan results to derive your location.
BLUETOOTH_CONNECT API 31+ Allows smartwatch pairing and Bluetooth communication.
BLUETOOTH_ADVERTISE API 31+ Supports advanced Bluetooth communication features.
ACCESS_FINE_LOCATION API ≤ 30 only Required by Android versions 10 and below for Bluetooth scanning. The app does not use this data for user location tracking.
ACCESS_COARSE_LOCATION API ≤ 28 only Required by Android versions 8 and below for Bluetooth scanning. The app does not use this data for user location tracking.
POST_NOTIFICATIONS API 33+ Used for smartwatch alerts, reminders, and Firebase Cloud Messaging notifications.
AD_ID All Used for analytics and advertising services through AdMob, Meta Audience Network, TikTok SDK, and Pangle.
INTERNET / ACCESS_NETWORK_STATE All Required for ads, analytics, remote configuration, notifications, and connectivity services.
BILLING All Supports in-app purchases and premium features if available.
Location & Bluetooth: On Android 12 and above, we use the neverForLocation permission flag on Bluetooth scanning. This means we do not and cannot use Bluetooth scan results to determine your location. Location permissions on older Android versions are a system requirement for Bluetooth only — the app does not read, store, or transmit location data.

3. Third-Party Services

The application uses trusted third-party SDKs and services to provide functionality, analytics, crash reporting, monetization, and notification delivery. Each service operates under its own privacy policy, linked below.

Firebase Services (Google)

  • Firebase Analytics — collects app usage events to measure daily active users (DAU), monthly active users (MAU), session length, and feature engagement. Data is used solely to improve app performance.
  • Firebase Crashlytics — automatically collects crash reports and ANR data to help us diagnose and fix stability issues.
  • Firebase Remote Config — allows us to update app configuration and feature flags without requiring an app update.
  • Firebase Cloud Messaging (FCM) — delivers push notifications including smartwatch alerts, app updates, and service messages.

Google Privacy Policy →

Advertising & Monetization

  • Google AdMob — serves display and interstitial advertisements. May use advertising identifiers for ad targeting and performance measurement.
    Google Privacy Policy →
  • Meta Audience Network (Meta Ads) — serves advertisements through Meta's ad network. May collect device identifiers and app interaction data for ad delivery and measurement.
    Meta Privacy Policy →
  • Pangle SDK (ByteDance) — serves advertisements through Pangle's ad network. May collect device information and usage data for ad delivery.
    Pangle Privacy Policy →
  • TikTok SDK (ByteDance) — used for advertising delivery and user engagement analytics, including tracking app install events, in-app actions, and engagement metrics. May collect device identifiers and usage data for these purposes.
    TikTok Privacy Policy →

These services may independently collect device identifiers, usage statistics, crash logs, and advertising-related information according to their own privacy policies. We encourage you to review those policies for details on their data practices.

4. Advertising

The application may display advertisements through Google AdMob, Meta Audience Network, Pangle, and TikTok advertising services.

Advertising partners may use the Google Advertising ID (GAID) and other device information to serve relevant ads, measure ad performance, and prevent advertising fraud. This is standard industry practice for free, ad-supported apps.

You can opt out of interest-based advertising at any time through your Android device settings under Privacy → Ads → Delete advertising ID (Android 12+) or Google Settings → Ads → Opt out of Ads Personalization on older versions.

5. Push Notifications

Firebase Cloud Messaging (FCM) may be used to send smartwatch alerts, app updates, announcements, and important service notifications.

Users can disable notifications at any time through Android Settings → Apps → Smart Watch :Bluetooth Connect → Notifications.

6. Data Safety

In accordance with Google Play's Data Safety requirements, the following summarises the data our app and its third-party SDKs collect and share:

Data Type Collected Shared with Third Parties Purpose
Device or other IDs (Advertising ID) Yes Yes (AdMob, Meta, Pangle, TikTok) Advertising, analytics
Crash logs Yes Yes (Firebase Crashlytics) App stability & diagnostics
App interactions & usage data Yes Yes (Firebase Analytics, TikTok SDK) Analytics (DAU/MAU), app improvement
Push notification tokens (FCM) Yes Yes (Firebase / Google) Notifications
Precise location No No Not used
Contacts, messages, or media No No Not used
Data is encrypted in transit. You may request deletion of your data by contacting us at contact@bityapp.xyz.

7. Data Retention

We retain data only as long as necessary for the purposes described in this policy:

  • Firebase Crashlytics — crash reports are retained for 90 days.
  • Firebase Analytics — event data is retained for 14 months by default (configurable in Firebase Console).
  • Advertising IDs — retained until you reset or delete your Advertising ID through Android settings.
  • FCM tokens — retained while the app is installed on your device.

You may request earlier deletion of your data by contacting us at contact@bityapp.xyz.

8. Data Security

We implement reasonable technical and organisational safeguards to help protect information against unauthorised access, misuse, disclosure, or alteration. All data transmitted between the app and third-party services is encrypted in transit using industry-standard TLS.

However, no electronic transmission or storage system can be guaranteed completely secure.

9. Children's Privacy

The application is not directed toward children under 13 years of age. We do not knowingly collect personal information from children. If you believe a child under 13 has provided personal information, please contact us at contact@bityapp.xyz and we will promptly delete such information.

10. Your Rights

Depending on your location and applicable law, you may have the right to:

  • Access — request a copy of personal data we hold about you.
  • Deletion — request deletion of your personal data where applicable.
  • Rectification — request correction of inaccurate data.
  • Portability — receive your data in a portable format (where technically feasible).
  • Restriction — ask us to restrict certain data processing activities.
  • Objection — object to processing based on legitimate interests.
  • Advertising preferences — opt out of personalised advertising via Android settings.
California residents (CCPA): You have the right to know what personal information is collected, to request deletion, and to opt out of the "sharing" of personal information with advertising partners for cross-context behavioural advertising. To exercise this right, email contact@bityapp.xyz with subject line "CCPA Opt-Out Request".
EEA / UK residents (GDPR): You have the right to lodge a complaint with your local data protection authority if you believe your rights have not been respected.

To exercise any of your rights, contact us at contact@bityapp.xyz. We will respond within 30 days.

11. Changes To This Privacy Policy

We may update this Privacy Policy periodically. When we do, we will revise the "Updated" date at the top of this page. For material changes, we may notify users via in-app notification or FCM push notification. Continued use of the app after changes constitutes acceptance of the updated policy.

12. Frequently Asked Questions

Why does the app need Bluetooth permissions?
Bluetooth permissions are required to discover, scan, pair, and connect nearby smartwatch devices. On Android 12 and above, we use the neverForLocation flag to ensure Bluetooth scanning cannot be used to derive your location.
Does the app track my location?
No. The app does not use precise location tracking. On Android 10 and below, the operating system requires location permission for Bluetooth scanning functionality — we do not read, store, or share location data. On Android 12+, we use the neverForLocation permission flag to explicitly block location derivation.
Does the app send notifications?
Yes. Firebase Cloud Messaging (FCM) is used for smartwatch alerts, app updates, and important service notifications. You can disable notifications at any time in Android Settings → Apps → Notifications.
Which SDKs are used in the app?
The app uses:
  • Firebase Analytics, Crashlytics, Remote Config, and Cloud Messaging
  • Google AdMob (advertising)
  • Meta Audience Network / Meta Ads (advertising)
  • TikTok SDK (advertising and engagement analytics)
  • Pangle SDK (advertising)
How is my Advertising ID used?
The Google Advertising ID (GAID) is used by our ad partners (AdMob, Meta, TikTok, Pangle) to show relevant ads and measure ad performance. You can reset or delete your Advertising ID at any time in Android Settings → Privacy → Ads.
How do I request deletion of my data?
Email us at contact@bityapp.xyz with subject "Data Deletion Request" and we will process your request within 30 days.

13. Contact Information

For privacy-related questions, data deletion requests, or rights requests, please contact us:

Company: Bityapp Studio

Email: contact@bityapp.xyz

Website: https://bityapp.xyz

Developer Profile: View on Google Play

Get the app:

Get it on Google Play