Under Trees - Journal privé - Politique de confidentialité
Dernière mise à jour : September 22, 2026
Cette politique de confidentialité décrit comment Under Trees - Journal privé, nom du package net.langhoangal.undertrees (l’"App") traite les informations lorsque vous utilisez l’App.
L’App est proposée dans le monde entier sur Google Play et l’App Store par Lang Hoang, développeur d’applications indépendant basé à Vietnam ("je", "me" ou "mon").
Cette politique explique quels types de données peuvent être collectés, comment ces données sont utilisées et comment le traitement hors appareil est protégé.
1. Accès au compte
La création d’un compte est facultative et ne concerne que les fonctionnalités qui exigent explicitement une connexion.
Fournisseur d’authentification : Google.
The local journal does not require a user-facing account on Android or iPhone. Google sign-in is optional and used only when you choose backup and restore. The Android release may create an anonymous Firebase session for supporting services.
2. Confidentialité des enfants
L’App ne s’adresse pas aux enfants de moins de 13 ans. L’âge minimum recommandé pour utiliser l’App est de 16 ans. Elle n’est pas déclarée comme une app destinée aux enfants ni comme une app Families sur Google Play. Si vous êtes parent ou tuteur et pensez qu’un enfant m’a fourni directement des informations personnelles, contactez-moi afin que je puisse prendre les mesures appropriées.
3. Données locales de l’appareil
L’app stocke certaines informations localement sur votre appareil.
Core journal content, attached media, tags, affirmations, themes, security settings, reminders, and preferences are stored on your device. Local journal and media storage is not encrypted by the app passcode.
- 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.
4. Types de données pouvant être collectés et traités en dehors de votre appareil
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.
Détails
- Catégorie: Personal info
- Type: User IDs, Email address, Name
- Collecté: Oui
- Partagé: Non
- Requis: Non
- Finalités: App functionality, Account management
- Traité par:
- Notes:
Processed only when you choose Google sign-in for backup and restore.
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.
Détails
- Catégorie: App activity, Photos and videos
- Type: Other user-generated content, Photos
- Collecté: Oui
- Partagé: Non
- Requis: Non
- Finalités: App functionality
- Traité par:
- Notes:
Journal database content is uploaded only when you explicitly create a backup.
Photos and drawings attached to journal entries are uploaded only when you explicitly create a backup.
Purchase and subscription data
Purchase and subscription records may be processed to validate Premium access and restore purchases.
Détails
- Catégorie: Financial info
- Type: Purchase history
- Collecté: Oui
- Partagé: Non
- Requis: Non
- Finalités: App functionality
- Traité par: ,
- Notes:
Used to validate Premium access and restore purchases.
Anonymous app identifier
An anonymous Firebase identifier may be processed for supporting app services without creating a user-facing account.
Détails
- Catégorie: Personal info
- Type: User IDs
- Collecté: Oui
- Partagé: Non
- Requis: Non
- Finalités: App functionality, Analytics
- Traité par:
- Notes:
The release app may create an anonymous Firebase session. It does not require you to provide a name, email address, or password.
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.
Détails
- Catégorie: Device or other IDs
- Type: Device or other IDs
- Collecté: Oui
- Partagé: Oui
- Requis: Non
- Finalités: Analytics, App functionality, Advertising or marketing, Fraud prevention, security, and compliance
- Traité par: , ,
- Notes:
Used for analytics, remote configuration, and related app operations.
Used for ad delivery, measurement, and fraud prevention where ads are available.
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.
Détails
- Catégorie: App activity
- Type: App interactions
- Collecté: Oui
- Partagé: Oui
- Requis: Non
- Finalités: Analytics, Advertising or marketing, Fraud prevention, security, and compliance
- Traité par: ,
- Notes:
Feature events such as adding or reading an entry, searching, selecting a theme, and managing tags or affirmations may be measured. Journal text is not sent in these named events.
Ad-related interaction telemetry may be collected by the advertising SDK.
Crash data
Crash reports may be processed to diagnose problems and improve app stability.
Détails
- Catégorie: App info and performance
- Type: Crash logs
- Collecté: Oui
- Partagé: Non
- Requis: Non
- Finalités: Analytics
- Traité par:
- Notes:
Used to diagnose crashes and improve app stability.
Diagnostics data
Technical diagnostics may be processed by platform services to monitor app quality.
Détails
- Catégorie: App info and performance
- Type: Diagnostics
- Collecté: Oui
- Partagé: Non
- Requis: Non
- Finalités: Analytics
- Traité par:
- Notes:
Technical diagnostics may be processed by .
6. Prestataires de services
7. Sécurité
J’utilise des mesures administratives et techniques raisonnables et adaptées aux informations que je traite directement.
Les informations transmises aux services décrits dans cette politique sont envoyées via leurs SDK et des connexions réseau chiffrées lorsque cela est pris en charge.
Aucune méthode de transmission ou de stockage électronique n’est totalement sécurisée, et une sécurité absolue ne peut pas être garantie.
8. Conservation des données
Local journal data remains on your device until you delete it, clear app storage, or uninstall the app. User-created backups remain in the app-specific Drive area until you remove them or your Google account policy removes them. Provider-processed purchase, advertising, analytics, authentication, and diagnostics data follows each provider's policy.
Données locales: Delete individual entries and related media in the app, or remove all local app data by clearing storage or uninstalling.
Données serveur: backups remain under your Google account in the app-specific data area until deleted. The app may retain an anonymous Firebase identifier through according to Firebase policy.
Données tierces: , , Firebase services, , , the , and retain data according to their own privacy and retention policies.
9. Suppression des données
Delete individual entries and backups from the relevant screens in the app. To remove all local journal data, clear the app's storage in Android settings where available or uninstall the app on Android or iPhone. backups are associated with the Google account you chose and can be removed from the backup screen where available; Google, Apple, and other providers may retain provider-processed data under their own policies. Email support if you need help identifying the applicable deletion path.
Voir les instructions de suppression des données
10. Contact
Pour toute question sur la confidentialité, contactez :
Email:support@langhoangal.dev
Journal storage and app lock
Under Trees stores the journal database and attached media in the app's private local storage. The passcode and supported biometrics restrict access through the app interface; they do not independently encrypt the journal database, media files, local backups, or backups. Android protects encrypted preferences with Android Keystore. On iPhone, Under Trees applies iOS complete file protection to its private journal and theme files while they remain inside the app container.
Optional Google Drive backup
access is optional on Android and iPhone. When you sign in and create a backup, the app uploads a copy of the journal database and referenced media to 's app-specific data area. These backups are protected by your Google account and transport encryption, but they are not end-to-end encrypted by Under Trees. Both platforms also support local file backup and restore through the device's file picker or share flow.
Advertising, analytics, and purchases
The free Android and iPhone versions may use for ads, and Remote Config for app usage and configuration, and with the applicable platform store for Premium purchases. On iPhone, tracking or personalized advertising is requested only after the applicable consent and App Tracking Transparency choices. Premium removes in-app ads.