This Privacy Policy explains how Memoria from Novawise Tech handles information when you use its journaling features, optional services, and support. The iOS App Store listing is currently named Diary Journal, Life Goals. Android is coming soon. The platform-specific descriptions below apply when the corresponding features are available in your version; they do not promise identical features on both platforms.
Journal content and device permissions
Memoria stores journal entries and associated information on your device, including the text, dates, moods, tags, images, and recordings you choose to add. It uses this information to provide editing, organization, search, and other journal features. Using the journal does not require creating a Memoria account.
When you select photos or record audio, the app uses the system picker or the relevant photo and microphone permissions. You choose what to add and can manage permissions in your device settings. Revoking a permission does not delete attachments you previously added.
Exporting or sharing creates a copy of the content you select and makes it available to the destination you choose. That destination handles the copy under its own practices. Keep exported files secure; an export or backup is not made private merely because the app lock is enabled.
iOS: optional iCloud synchronization
If you enable iCloud sync in a supported iOS version, Memoria uses Apple's CloudKit to synchronize supported journal records and attachments through your private iCloud database. Apple processes this data under its iCloud terms and privacy practices. Availability depends on your Apple Account, iCloud settings, storage, and network connection.
Changes to the app's iCloud sync setting take effect after restarting the app. Turning sync off does not itself delete copies already stored in iCloud. You can also manage the app's iCloud access and stored data through Apple device settings. iCloud sync is separate from any device backup you have enabled.
Android: local storage and system backups
The Android version described here stores journals and media locally and does not provide Google sign-in or Google Drive journal synchronization. Android's own backup and device-transfer services are separate: depending on your device, account, and system settings, they may copy or restore the app's journal backup.
The permitted Android backup contains journal data and media, including tags and items in Trash. App-lock credentials and app preferences are excluded from that backup. The app does not add its own encryption to the backup archive or journal database. Any protection provided by Android or a backup provider depends on that service and your device configuration. Manage system backups in your device settings. See Android's backup information at https://developer.android.com/identity/data/autobackup.
iOS: analytics and crash diagnostics
The iOS app uses Google Firebase Analytics and Firebase Crashlytics, enabled by default, to understand feature use and diagnose crashes. Analytics events include screen views, paywall interactions, journal-completion events, and content interactions. Some events include an entry identifier or a content identifier. The app's event payloads do not include journal text, image or recording attachments, or recovery email addresses.
These services also process identifiers and technical information under their own SDK practices. Crash reports can include crash traces, installation identifiers, app version, and device or operating-system information. This information is not described as anonymous. The iOS configuration enables analytics storage and Google's advertising-related storage, user-data, and personalization consent settings by default; this is not a user-selected opt-in. These settings do not mean that Memoria displays advertising.
The app does not currently offer a separate analytics opt-out setting. Device privacy controls apply to the access they govern. Google's processing and retention information is available at https://firebase.google.com/support/privacy. The Android version described in this policy does not include these Firebase analytics or crash-reporting services or an advertising SDK.
App lock and optional recovery email
App lock uses locally protected credentials to restrict access through the app. Where supported, biometric authentication is performed by the operating system; Memoria does not receive your biometric template. App lock does not add encryption to your journal files, and it is not a promise of end-to-end encrypted storage or backup.
If you choose email recovery, we process your email address, language preference, installation and recovery identifiers, verification information, and recovery credentials to verify the address, send codes, and authorize an app-lock reset. We store the full recovery email address encrypted at rest in a form the recovery service can decrypt, together with a masked address and related recovery records. The recovery requests do not contain your journal text, attachments, or raw app-lock PIN.
The service also processes request metadata and security records to operate recovery and limit abuse. On Android, this includes installation authentication and email- and IP-based abuse controls. Cloudflare hosts the recovery service and currently delivers its verification emails through Cloudflare Email Service. Your email provider also processes delivered messages.
Email recovery is optional and is not registration for a Memoria account. It resets access to the app lock; it does not recover deleted or lost journal content. You can change or remove a recovery-email binding through the supported app controls, or contact support if you cannot access those controls.
Online content and service requests
Supported versions may download optional fonts and visual content, such as Discover covers, from Novawise Tech's HTTPS content service. These requests identify the requested resource and expose the connecting IP address and normal request metadata to our hosting provider. They do not send your journal text or attachments to the content service.
Cloudflare provides hosting and related infrastructure for our content and recovery services. Operational and security logs can be generated when you use those services. Downloading content does not connect a Google Drive account or create a social-network account.
iOS purchases and platform services
Where paid features are offered on iOS, Apple processes the purchase. The app uses purchase and entitlement information to unlock features and restore eligible purchases; it does not receive your full payment-card details. Apple handles its account, payment, and store information under its own practices: https://www.apple.com/legal/privacy/data/en/app-store/.
The Android version described here does not provide in-app purchases. If you choose to submit a rating or review through a platform's review interface, that platform handles your submission under its own terms and privacy policy.
Deletion, retention, and backups
Deleting a journal entry first moves it to Trash where that feature is available. Use permanent deletion to remove it from the journal library. Referenced or recoverable media, synchronization records, and existing backups may remain after an entry is removed; deletion does not guarantee immediate erasure of every copy. Copies you export or share remain with the destinations you selected. Cloud synchronization and system backups have their own deletion and restoration behavior.
Recovery-email bindings remain stored until removed; they do not automatically expire just because you stop using the app. Removing a binding removes the active email association. Remaining verification, security, operation, and deletion records are cleared separately through the service's retention and cleanup processes; service logs and provider-held email records have separate lifecycles. Verification codes and recovery authorizations expire, but expiry is not the same as immediate deletion: expired service records are removed by scheduled cleanup.
Uninstalling does not send a request to delete your recovery-email binding, cancel a subscription, remove exported copies, or erase data already held in cloud services or backups. Local credential storage and restoration also follow operating-system behavior. Remove optional service bindings and review your cloud and backup settings before uninstalling if you want to stop those services.
Retention of analytics, crash reports, operational logs, email delivery records, and support correspondence depends on the service and its configuration. We do not promise a single deletion deadline for all of these systems. Changing an email-delivery provider does not itself erase records previously handled by the former provider.
Your choices, support, and privacy requests
You can choose which content to enter, manage device permissions, use export and deletion controls, and decide whether to use optional iCloud sync or recovery email where offered. Android system backup choices are managed separately in device settings. Turning off a feature does not automatically delete information it already processed.
If you email support@novawisetech.com, we receive your address, message, and any attachments you choose to send. Send only the information needed for your request. Do not send PINs, passwords, verification codes, or recovery credentials. We use support information to respond and investigate the issue.
Contact that address with questions or requests concerning access, correction, or deletion of information held by Novawise Tech. We may need to verify that the request concerns your information. We cannot retrieve journal content that exists only on your device, and Apple, Google, Cloudflare, your email provider, and destinations you choose also have their own privacy controls and processes.
Service providers, security, and updates
We use the information described above to provide the requested features, maintain service security, diagnose problems, understand iOS feature use, and respond to support requests. Providers receive the information needed for their services, as described in the relevant sections. Their systems may process information outside your country; their privacy terms and available controls also apply.
We use protections appropriate to the feature, including HTTPS for our service requests and protected credential storage. No storage or transmission method is guaranteed completely secure. The app lock, transport encryption, and a provider's storage protection serve different purposes and do not amount to a blanket encryption guarantee for journals, exports, or backups.
If you have a concern about a child's information submitted to our services, contact support@novawisetech.com. We may update this policy as features or providers change and will update the date on this page and provide any notice required by applicable law.