app screenshot

Who Provides the App

Mindfulness Bell is provided by Hoàng Lạng as an individual developer.

Contact email: support@langhoangal.dev
Address: To 2, To dan pho 3, Thi tran A Luoi, Huyen A Luoi, Hue, Thua Thien Hue 49506, Vietnam.

Summary

Mindfulness Bell does not require you to create an account and does not ask for your name, phone number, or email address inside the app. Most app settings are stored locally on your device.

The app does use third-party services for ads, consent management, analytics, crash reporting, remote configuration, Google Play billing, and support-development purchases. These services may collect or process data such as device identifiers, advertising identifiers, app usage events, diagnostics, approximate location inferred from IP address, and purchase history.

Data Stored Locally on Your Device

The app stores settings on your device so that the bell and reminder features work correctly. This may include:
  • Bell sound, custom sound URI or name, volume, audio channel, and interval settings;
  • Bell schedule, next bell time, running state, random interval state, and chime mode settings;
  • Mute rules for silent mode, vibrate mode, Do Not Disturb mode, airplane mode, phone calls, recording, and time ranges;
  • Language, theme, time format, photo/theme choices, notification preferences, and battery optimization reminder state;
  • Ad-related local flags, such as whether ads are enabled and remote ad feature flags.
The app may also keep local app logs for troubleshooting. These logs are stored on your device and are normally retained for up to 3 days. Some local settings may also be included in Android device backup if backup is enabled on your device and Google account. You can delete local app data by clearing the app data in Android settings or uninstalling the app.

Data Collected or Processed Through Third-Party Services

The app uses third-party SDKs and services. Depending on your device, region, consent choices, and how you use the app, these providers may process the following categories of data:
  • App identifiers, device identifiers, advertising ID, Firebase app instance identifiers, or RevenueCat anonymous App User ID;
  • Approximate location inferred from IP address, country or region, language, device model, manufacturer, operating system version, app version, and network-related information;
  • App usage events, screen views, ad events, ad consent status, ad eligibility state, and general interaction events used to understand and improve the app;
  • Crash reports, diagnostics, performance and error information, including some app state useful for troubleshooting;
  • Purchase history and entitlement/support-development status for Google Play Billing and RevenueCat.

Advertising and Consent

Mindfulness Bell may show ads through Google AdMob. The app may use banner ads, interstitial ads, app-open ads, and native ads. The app does not use ad mediation.

The app uses the Google User Messaging Platform (UMP) SDK to request and manage consent where required by applicable law or Google policies. In regions where privacy choices are required, the app may show a consent form and may provide a privacy options entry point inside the app so you can update your choices.

AdMob and related Google services may process data such as advertising ID, IP address, device information, ad interactions, and approximate location. Your ad experience may depend on your consent choices and Google’s own policies and settings.

Analytics, Crash Reporting, and Remote Configuration

The app uses Google Analytics for Firebase to understand app usage and improve the app. Analytics may record events such as screen views, ad events, app actions, support/feedback actions, FAQ opens, and settings or feature interactions. The app may set user properties such as ad consent status, ad/support status, whether ads are enabled, and whether the bell is running.

The app uses Firebase Crashlytics to collect crash reports and diagnostic information. Crashlytics may include device information, app version, operating system version, timestamps, stack traces, error details, and limited app state or custom diagnostic keys. I do not intentionally attach your name, email address, or phone number to Crashlytics reports.

The app uses Firebase Remote Config to download configuration values, such as ad feature flags and other app behavior settings.

Purchases and Support Development

The app offers optional purchases through Google Play Billing and RevenueCat so users can support development. Google Play processes payment transactions. I do not receive your full payment card details.

RevenueCat may create an anonymous App User ID and process purchase history, transaction information, entitlement status, product identifiers, country or region, device/app information, and related diagnostics to validate purchases and keep your support-development status available in the app.

Support Emails and Diagnostic Attachments

If you contact me for support, I may receive your email address and any information you choose to include. The app may prepare a support email that includes diagnostic details such as platform, RevenueCat App User ID, background optimization status, notification status, exact alarm status, Android version, app version, device model, and manufacturer.

When you send feedback from the app, the email may also include troubleshooting attachments such as recent local app logs and a preferences snapshot. The preferences snapshot may contain app settings like bell schedule, mute rules, theme/language settings, ad flags, and custom sound URI/name. These attachments are used only to understand and troubleshoot your request.

Permissions

The app requests Android permissions needed for its features, including internet access, notifications, vibration, wake locks, exact alarms, foreground service/media playback, billing, restart after device boot, and battery optimization handling. These permissions are used to run bells/reminders reliably, show local notifications, process optional purchases, and support ads and third-party services. The app does not request camera, microphone, contacts, or precise location permission.

Third-Party Service Providers

How Data Is Used

Data is used to:
  • Provide app features such as bell scheduling, notifications, sounds, settings, and purchases;
  • Show and manage ads, including consent and privacy choices where required;
  • Understand app usage and improve app quality;
  • Detect, diagnose, and fix crashes or technical problems;
  • Respond to support requests;
  • Comply with legal obligations, enforce policies, prevent abuse, and protect the app and users.

Sharing and Disclosure

I do not sell or rent your personal information. Data may be processed by the third-party service providers listed in this policy to provide ads, analytics, crash reporting, remote configuration, purchases, and related app services. If you send a support email, your email provider and my email provider will process that message. I may also disclose information if required by law, to protect rights and safety, or to investigate abuse or security issues.

Data Retention

Local app settings remain on your device until you change them, clear app data, or uninstall the app. Local troubleshooting logs are kept for up to 3 days on your device unless cleared earlier.

Data processed by Google, Firebase, AdMob, RevenueCat, and Google Play may be retained according to those providers’ own policies and retention practices.

If you contact me for support, I may retain your email and the information you provide only for as long as necessary to respond to your request, troubleshoot issues, comply with legal obligations, resolve disputes, prevent abuse, or improve the app.

Data Deletion

Mindfulness Bell does not require an account, so there is no in-app account deletion process.

You can delete locally stored app data at any time by clearing the app data in Android settings or by uninstalling the app.

If you want to request deletion of data you provided directly to me, such as support emails or diagnostic attachments sent during support requests, contact me at: support@langhoangal.dev. Please include the app name and any relevant information that can help me locate your request. I will process deletion requests within 30 days unless I am required to retain certain information for legal, security, fraud prevention, dispute resolution, or accounting purposes.

International Processing

The app is available globally on Google Play. Third-party providers may process data on servers located in different countries from where you live. By using the app, you understand that data may be processed outside your country or region, subject to applicable law and the providers’ privacy practices.

Website Data

This Privacy Policy page is hosted on a website that may load third-party web services such as Google Tag Manager, Google Fonts, and Font Awesome. These web services may process browser or device information such as IP address, user agent, referrer, and usage information according to their own policies. This website data is separate from data handled by the Android app.

Security

I use reasonable technical and organizational measures to protect information handled by the app and support process. However, no method of transmission over the internet or electronic storage is completely secure, so I cannot guarantee absolute security.

Links to Other Sites

The app may contain links to other sites. If you click on a third-party link, you will be directed to that site. Note that these external sites are not operated by me. Therefore, I strongly advise you to review the Privacy Policy of these websites. I have no control over and assume no responsibility for the content, privacy policies, or practices of any third-party sites or services.

Children’s Privacy

Mindfulness Bell is intended for adults and is not directed to children. The app is not declared on Google Play as an app made for children. I do not knowingly collect personal information from children. If you believe a child has provided personal information to me, please contact me so I can take appropriate action.

Changes to This Privacy Policy

I may update this Privacy Policy from time to time. I will post the updated version on this page and update the effective date below.

Effective date: 2026-06-25

Contact Me

If you have questions, suggestions, or deletion requests related to this Privacy Policy, contact me at support@langhoangal.dev.