Mindfulness Chime Pro - Privacy Policy
This Privacy Policy describes how Mindfulness Chime Pro, package name dev.langhoangal.mindfulness_chime_pro (the "App") handles information when you use the App.
The App is provided worldwide on Google Play and the App Store by Lang Hoang, an independent app developer based in Vietnam ("I", "me", or "my").
This policy explains what types of data may be collected, how that data is used, and how off-device processing is protected.
1. Account Access
Creating an account is optional and only applies to features that explicitly require sign-in.
Authentication provider: Google.
You can use the app without an account. Sign-in is optional and only used if you choose cloud backup and restore.
2. Children's Privacy
The App is not directed to children under 13. The minimum recommended age for using the App is 16. It is not declared as a child-directed or Families app on Google Play. If you are a parent or guardian and believe a child has provided personal information directly to me, contact me so I can take appropriate action.
3. Local Device Data
The app stores some information locally on your device.
The app mainly stores your chime schedules, selected sounds, speaking settings, vibration patterns, and other app preferences locally on your device.
- Chime state and schedules:
Your chime schedules, running state, and related app behavior are stored locally on this device.
- Sounds and app preferences:
Selected sounds, speaking settings, vibration patterns, and other preferences remain on-device unless you remove them.
4. Types of data that may be collected and processed outside your device
Account information for backup sign-in
If you choose cloud backup or restore, some account information may be processed so you can sign in and link your backups to your account.
Details
- Category: Personal info
- Type: User IDs, Email address, Name
- Collected: Yes
- Shared: No
- Required: No
- Purposes: App functionality
- Processed by: ,
- Notes:
Used only when you choose to sign in for cloud backup and restore.
Cloud backup data
If you choose cloud backup or restore, the app may upload a backup file containing your app configuration data and any custom audio files included in that backup.
Details
- Category: App activity, Audio files
- Type: Other user-generated content, Other audio files
- Collected: Yes
- Shared: No
- Required: No
- Purposes: App functionality
- Processed by:
- Notes:
Used only when you choose cloud backup or restore. Backup files may include app configuration data together with any custom audio files included in the backup.
Used only when you choose cloud backup or restore. Backup files may include custom audio files together with app configuration data.
Purchase and subscription data
Purchase and subscription records may be processed to validate entitlements and restore purchases.
Details
- Category: Financial info
- Type: Purchase history
- Collected: Yes
- Shared: No
- Required: No
- Purposes: App functionality
- Processed by: ,
- Notes:
Used to validate Premium entitlements and restore purchases.
Device and app identifiers
Technical identifiers may be processed for analytics, remote configuration, and related app operations. Technical identifiers may be processed for advertising, fraud prevention, and measurement where ads are available.
Details
- Category: Device or other IDs
- Type: Device or other IDs
- Collected: Yes
- Shared: Yes
- Required: No
- Purposes: Analytics, App functionality, Advertising or marketing
- Processed by: , ,
- Notes:
Used to measure app usage and deliver remote configuration values.
Used for ad delivery, fraud prevention, and measurement where ads are available
Crash data
Crash reports may be processed to diagnose problems and improve app stability.
Details
- Category: App info and performance
- Type: Crash logs
- Collected: Yes
- Shared: No
- Required: No
- Purposes: Analytics
- Processed by:
- Notes:
Used to diagnose crashes and improve app stability.
Diagnostics data
Technical diagnostics may be processed by platform or provider services.
Details
- Category: App info and performance
- Type: Diagnostics
- Collected: Yes
- Shared: No
- Required: No
- Purposes: Analytics
- Processed by:
- Notes:
Technical diagnostics may be transmitted by platform services.
App usage and interaction data
App interaction data may be processed for advertising measurement and related provider operations. App interaction data may be processed to understand usage patterns and improve the app.
Details
- Category: App activity
- Type: App interactions
- Collected: Yes
- Shared: Yes
- Required: No
- Purposes: Advertising or marketing, Analytics
- Processed by: ,
- Notes:
Ad-related interaction telemetry may be collected by the ad SDK.
Used to understand basic app usage and improve the app.
6. Service Providers
7. Security
I use reasonable administrative and technical measures appropriate to the information handled directly by me.
Information transmitted to the services described in this policy is sent using their SDKs and encrypted network connections where supported.
No method of electronic transmission or storage is completely secure, and absolute security cannot be guaranteed.
8. Data Retention
Temporary local app state remains on your device until you clear app data or uninstall the app. If you choose cloud backup or restore, account sign-in details, selected configuration data, and custom audio files may be processed by Google and Firebase services. Purchase, advertising, analytics, and diagnostics data are retained under the policies of the relevant providers.
Local data: Temporary local state and device-specific preferences remain on-device until removed by the user.
Server data: When you choose cloud backup or restore, account-linked authentication details, selected configuration data, and custom audio files may be retained by the relevant cloud providers until removed in-app, disconnected, or handled under provider and deletion-request flows.
Third-party data: , , , Google Identity services, Firebase services, and other relevant providers retain data according to their own privacy and retention policies.
9. Data Deletion
Temporary local app state can be removed by uninstalling the app or clearing its app storage. If you used cloud backup or restore, applicable backup data may be removable in the app where that option is provided. Some off-device data, including provider-processed sign-in, purchase, diagnostics, analytics, or advertising data, may still be retained under the relevant provider's own privacy and retention policies. Contact support if you need help identifying which in-app flow or provider policy applies.
View data deletion instructions
10. Contact
For privacy questions, contact:
Email:support@langhoangal.dev