Home

Mindfulness Chime Pro - Data Deletion Instructions

These instructions explain how to remove local app data and what deletion or account-control options may apply to off-device data declared for Mindfulness Chime Pro.

1. Local Device Data

Some app data is stored only 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.

You can remove local device data by uninstalling the app or clearing app storage in system settings.

2. Off-Device Data Requests

Some data is declared as transmitted off-device. Depending on the data type, removal may happen in the app, through account controls, or under the relevant provider's own privacy process.

Data that can be deleted through the app or developer support

• 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.
  Deletion options:
  You can remove this data using the deletion option provided in the app.
  If you need deletion help for this data, contact support by email.

If you need developer help for this group

1. Send a deletion request to: support@langhoangal.dev
2. Use this subject line: Mindfulness Chime Pro Data Deletion Request
3. Requests for account-linked or backup-linked data may require enough information to verify that you control the relevant account or backup before any action is taken.

Data managed by third-party providers

• 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.
  Deletion options:
  This data is not deleted directly in the app. It may be processed by Firebase Authentication, Google Identity Services, and each provider may apply its own retention or deletion policy. You may need to contact the relevant provider directly or use its available account or privacy controls.
• Purchase and subscription data
  Purchase and subscription records may be processed to validate entitlements and restore purchases.
  Deletion options:
  This data is not deleted directly in the app. It may be processed by RevenueCat, Google Play Billing, and each provider may apply its own retention or deletion policy. You may need to contact the relevant provider directly or use its available account or privacy controls.
• 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.
  Deletion options:
  This data is not deleted directly in the app. It may be processed by Firebase Analytics, Firebase Remote Config, Google AdMob, and each provider may apply its own retention or deletion policy. You may need to contact the relevant provider directly or use its available account or privacy controls.
• Crash data
  Crash reports may be processed to diagnose problems and improve app stability.
  Deletion options:
  This data is not deleted directly in the app. It may be processed by Firebase Crashlytics, and each provider may apply its own retention or deletion policy. You may need to contact the relevant provider directly or use its available account or privacy controls.
• Diagnostics data
  Technical diagnostics may be processed by platform or provider services.
  Deletion options:
  This data is not deleted directly in the app. It may be processed by Google Play Store, and each provider may apply its own retention or deletion policy. You may need to contact the relevant provider directly or use its available account or privacy controls.
• 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.
  Deletion options:
  This data is not deleted directly in the app. It may be processed by Google AdMob, Firebase Analytics, and each provider may apply its own retention or deletion policy. You may need to contact the relevant provider directly or use its available account or privacy controls.

For provider-managed data

The developer does not directly delete these records. You can use the provider links above to learn more about each provider and follow that provider's own privacy, account-control, or deletion process.

Questions?

For help with deletion requests, contact:

Email:support@langhoangal.dev