DiaryNote Privacy Policy

Updated and effective: October 5, 2026 · Applies to version 1.2.0 (version code 7)

Developer: liuwen-org

DiaryNote is a local-first diary app. You can start writing without registering a developer account. This policy describes how the current version handles diaries, settings, and usage analytics. Writing, viewing, editing, and searching diaries work offline, while the app also includes an online analytics service.

1. Data handled and its purposes

• Diary data: titles, text, rich text, dates, weather, moods, selected images, and creation, modification, and deletion times, used for storage, display, editing, search, sorting, calendar, and recycle-bin features. You select weather and moods manually; they are not obtained using device location.
• Settings: theme, language, sorting, reminders, mood options, and app-lock settings, used for preferences and local access control.
• Password information: setting an app password stores a salted, derived verification value locally. The app password is not sent to the developer or analytics service.
• Usage analytics: Google Analytics for Firebase automatically collects usage events, app and device information, and identifiers to understand usage and improve the app, as described below.

The app does not require your name, email address, phone number, or government identifier, or request permissions for precise location, contacts, call logs, messages, camera, or microphone. Diaries and images you choose may contain such information; you decide their contents.

2. Usage analytics and network access

The app has Internet access and includes Google Analytics for Firebase. Automatic analytics is enabled by default from app startup, without waiting for acceptance of the in-app privacy prompt. This version has no in-app switch to disable it. When online, the SDK sends automatically collected analytics to Google, independently of backup usage.

Analytics may include app launches, sessions, screen views, app and operating-system versions, device model, language, an app-instance identifier, and the Android advertising identifier when permitted and available. Google may derive an approximate region from the IP address during collection; this does not require device location permission.

The app does not send diary titles, text, images, app passwords, or backup passwords as analytics events or parameters, or upload diary content to developer servers. It contains no advertising SDK and does not sell diary data. The developer can view usage reports provided by Google.

Google processes analytics, with retention governed by the Google Analytics property's retention settings and applicable service rules. Google may process data outside your country or region. See Firebase's data collection information for SDK data categories and Google's Privacy Policy for its processing practices.

3. Images, permissions, and device authentication

The app reads images you explicitly select using the Android system photo picker and copies the original images into private app storage. It can also receive text or images you deliberately share from another app. It does not scan unselected photos. Original images may retain embedded metadata such as capture time or location.

Daily reminders use notification permission for local notifications. Boot, time, and time-zone change notifications allow reminders to be rescheduled. You can disable reminders or notification permission in app or system settings.

When fingerprint or device unlock is enabled, Android performs authentication. The app receives only the result and does not read or store fingerprints or other biometric data. You can disable this unlock method in the app.

4. Manual backups, imports, and cloud-sync availability

You can manually export a password-encrypted backup or select an existing backup to import. Backups contain diaries, associated images, and portable preferences, excluding app-lock passwords and lockout state. Files are saved to the location you select through the system file picker. If you select cloud storage or a third-party file service, that service handles the file under its own rules. Protect backup files and passwords.

Automatic backup, Google Drive sync, and diary export (PDF, images, Markdown, TXT, and HTML) are not available through the current version's user interface, and the related background backup and sync tasks are disabled. The app currently does not automatically upload diaries to Google Drive through these features. Analytics still operates independently. This policy will be updated if these features become available.

5. Android system backups and device transfers

The app allows Android system backups. Current rules include only the diary database and app-managed diary images in backups or device transfers, excluding preferences, password verification information, lockout state, and caches. Cloud backups require appropriate system encryption capability. Actual backup and transfer behavior depends on Android, your device manufacturer, and system settings.

The operating system or backup provider handles these backups without providing diaries to the developer. You can manage backups in system settings. Diary text uses a device-local Android Keystore key that is not included in these backups, so recovery of encrypted text from system backups or device transfers is not guaranteed. Use the app's manual encrypted backup for migration.

6. Retention, deletion, and your choices

Diaries and settings are stored locally by default. Deleting diaries, including using “Clear diaries,” first moves them to the recycle bin, where they can be restored for 30 days. You can permanently delete entries or empty the bin. Entries older than 30 days are removed when app cleanup runs, along with images no longer referenced by other diaries.

You can view, correct, and delete diaries, clear app data or uninstall to remove local data, and manage notifications, image access, and backups in system settings. Revoking access to an image source does not delete copies already imported into the app. Exported backups and other external files, system cloud backups, and copies on other devices must be managed or deleted separately.

Deleting diaries, clearing app data, or uninstalling does not automatically delete analytics previously sent to Google. This version has no analytics switch; stopping use and uninstalling stops future analytics collection by that installation. Contact the developer using section 10 for access, deletion, or other privacy requests.

7. Security

Android app isolation protects private app data. AES-GCM with Android Keystore encrypts locally stored diary titles, text, and rich text. Other database fields, such as dates, weather, and moods, and original image files are outside this text-encryption scope; this does not mean the entire database or all files are encrypted. Manual backups are separately encrypted with a password.

An optional app password and system authentication control app access. Protect your device, system credentials, app password, backup passwords, and external files. No security measure can guarantee absolute protection.

8. Children

The app does not request age or identity information. Minors should use it with guidance from a parent or guardian and avoid recording or distributing unnecessary sensitive information in diaries, images, or backups.

9. Policy changes

This policy will be updated when app features or data-handling practices change. Review this page's date, applicable version, and content after app updates.

10. Contact

For questions, complaints, or personal-data requests, contact the developer at liuwen.yeah@gmail.com. Do not include complete diaries, passwords, or unnecessary sensitive information in emails. The email address and request you voluntarily provide will be used to handle and respond to your request.