Home

Under Trees - Private diary - Data Deletion Instructions

Last updated: September 22, 2026

These instructions explain how to remove local app data and what deletion or account-control options may apply to off-device data declared for Under Trees - Private diary.

1. Local Device Data

Some app data is stored only on your device.

• Journal entries and organization:

  Entry titles and text, dates, moods, formatting, tags, affirmations, and related journal records are stored in the app's local database.

• Photos and drawings:

  Media attached to entries is copied into the app's private local media folder.

• Security settings and preferences:

  Security settings and preferences are stored in platform-protected app storage. Android protects encrypted preferences with Android Keystore; iPhone applies iOS complete file protection to private journal data. The app passcode controls access through the app interface and does not independently encrypt journal files or exported backups.

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

• Optional Google Drive backup
  A backup can contain journal entries, dates, moods, formatting, tags, affirmations, and related journal data. It is uploaded only when you start a Drive backup. Attached photos and drawings may be included with a user-initiated Google Drive backup.
  Deletion options:
  You can remove this data using the deletion option provided in the app.
  This data is not deleted directly in the app. It may be processed by Google Drive, 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.

If you need developer help for this group

Data managed by third-party providers

• Optional Google account information
  Your Google account identifier, name, and email address may be processed to authorize access to the app-specific Google Drive backup area.
  Deletion options:
  This data is not deleted directly in the app. It may be processed by 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 Premium access 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.
• Anonymous app identifier
  An anonymous Firebase identifier may be processed for supporting app services without creating a user-facing account.
  Deletion options:
  This data is not deleted directly in the app. It may be processed by Firebase Authentication, 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 when ads are shown.
  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.
• App usage and interactions
  Basic feature interactions may be processed to understand usage and improve the app; the app's named analytics events do not include your journal text. Interactions with ads may be processed for delivery, measurement, and fraud prevention.
  Deletion options:
  This data is not deleted directly in the app. It may be processed by Firebase Analytics, 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 services to monitor app quality.
  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.

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