Lucidity Level Privacy Policy

Privacy Policy for Lucidity Level
Last updated: 29 October 2026

Your journal, your choice

Lucidity Level is developed by Nathan Woolmore. This policy explains what information the app uses, why it is used, and the choices available to you. Features described here apply where available in the version and platform you use.

You can keep a journal without creating a Lucidity Level account. Your entries are saved on your device. If you choose cloud features, the relevant information is also processed by the cloud service you select. Your journal is not published or shared with other users by signing in.

1. Information used by the app

The app stores the content you provide, such as dream entries, titles, notes, tags, dream signs, ratings, recordings, selected images and your optional Lucid Signature drawing. It also stores collections, vessels, goals, quest and level progress, practice history, preferences and relevant onboarding answers so these features work together.

Automated tags, ratings, emotion summaries and dream-pattern suggestions are generated from your journal on your device. They are suggestions, not medical assessments, and you can review or change the information you enter.

2. Optional accounts and account backup

If you create or sign in to an account using Apple, Google or email and password, Google Firebase Authentication processes the information needed to authenticate you. This may include an account identifier, email address, sign-in provider and profile information provided by that provider. A name you choose in the app is saved with your account. Apple’s private relay email can be used when you choose Hide My Email.

Account creation does not by itself upload your journal. When you choose to connect your device journal to account backup, the app uploads your journal and associated data to Google Firebase/Google Cloud services operated for Lucidity Level. This includes attached recordings, collection artwork, folders and vessels, rewards, progression, goals, dream-sign notes, portable preferences, your optional signature drawing and a saved entry draft where present.

Account backup requires Pro for new uploads. Once connected, changes are saved automatically when connectivity and device background execution allow. The app shows storage and sync status in Profile & Settings. Existing account data remains available to restore or delete if Pro ends; new changes stay on the device while account syncing is paused.

When enabled, account backup processes your selected journal data on our backend. Access is restricted through account authentication and access controls. We use this information to provide backup, restoration, synchronization, security and support—not to sell your journal, advertise to you based on its contents, or publish it.

3. iCloud as an alternative

You may choose supported iCloud sync features instead of Lucidity Level account backup. iCloud uses your Apple account and may store journal content, progression and other supported app data; recording sync has its own control where offered. We do not receive your Apple account password or directly access your private iCloud journal through our account backend.

The app does not actively use iCloud sync and account sync together. Signing in pauses iCloud sync. Turning off sync or signing out does not automatically delete a previously saved cloud copy. Device-level iCloud backups are separately controlled by Apple’s settings.

4. Health data, recordings and permissions

With your permission, the app reads sleep duration, timing and available sleep-stage information from Apple Health to show sleep analysis and support sleep-related features. HealthKit sleep records are not included in Lucidity Level account or journal cloud archives. They are not used for advertising, sold, or shared with RevenueCat. The current app does not write HealthKit records. You can change Health access in Apple’s Health or Settings app.

On Android, with your permission, the app reads sleep sessions and available sleep stages from Health Connect to provide sleep analysis and sleep-related alarm guidance. These records are processed on your device and are not included in Lucidity Level account backups or journal exports. They are not used for advertising, sold, or shared with RevenueCat. The app does not write Health Connect records. You can review or revoke access in Health Connect or device settings.

Microphone permission is used when you record audio. If you choose transcription, Apple’s Speech Recognition service processes the recording; depending on device, language and service availability, processing may involve Apple’s servers. Recordings and resulting text can be included in cloud backup when you enable it.

On Android, transcription uses the device's on-device speech recognition service on supported devices and languages. A speech-model download or setup may be needed before transcription is available. The app does not send recordings to a cloud transcription service. Recordings and resulting text can still be included in account backup when you enable it.

Selected photos or files are used for the import, artwork, profile or community posting feature you request. Notifications support reminders, alarms and community alerts where enabled. Optional Face ID or Touch ID protection uses Apple’s authentication system; the app does not receive your biometric templates. Permissions can be changed in device settings.

On Android, optional app protection uses the system's biometric or device-credential authentication. The app does not receive your biometric templates or device passcode. Permissions can be changed in device settings.

5. Purchases and service providers

Apple handles App Store payment processing. Google handles Google Play payment processing. RevenueCat helps validate purchases, restore access and determine Pro status. It processes app user identifiers, purchase and subscription records, and associated app/device information. When you sign in, your Lucidity Level account identifier may be linked to RevenueCat so account backup and community Pro access can be verified. We do not receive your full payment card details or Apple/Google account password.

We require service providers handling information on our behalf to protect it consistently with this policy and applicable privacy requirements, and to use it for the services they provide. Relevant policies include:
Apple: https://www.apple.com/legal/privacy/
Google/Firebase: https://policies.google.com/privacy
Firebase service information: https://firebase.google.com/support/privacy
RevenueCat: https://www.revenuecat.com/privacy/

6. Diagnostics, security and support

Apple diagnostics you choose to share, app diagnostic events, and cloud service logs may include device/app versions, errors, request metadata, account identifiers and network information such as IP addresses. These help operate the service, diagnose faults and prevent abuse. Account security controls may temporarily process sign-in attempts. Journal contents, recordings and passwords are not intentionally included in diagnostic logs.

If you contact support, we receive the information you choose to send, including your email and any attachments. Please include journal content only if you want us to review it for your request. We do not sell personal information or use journal, HealthKit or Health Connect data for targeted advertising.

7. Community, shared content and messages

Community is optional and uses Google Firebase/Google Cloud services to store and deliver the information needed for profiles, discussions, interactions, moderation and messages. Creating an account or enabling backup does not publish your journal or create a public community profile by itself.

When you create and save a community profile, the details you choose to display can be seen by other people using Community. These may include your display name, unique handle, bio, manually entered location, links, avatar and cover, favourite techniques, title, level and profile appearance. Your email address and sign-in credentials are not shown on your public profile. Profile edits remain a draft until you press Save.

Posts, replies, photos, links and feature requests you submit are stored with your account identifier, relevant dates and interaction information. Published contributions are visible in Community. We also store likes, follows, votes, blocks, notification preferences and title-gift records so these features work. Follower and following information and published contributions may be visible through community profiles. Blocking and visibility controls apply where offered.

Featuring a dream or adding one to a public showcase shares a copy of the title and text you select, together with any ratings or tags you choose to include. It does not share the rest of your journal, recordings, health records or account backup. If you enable the dream calendar, the app shares daily dream-logging dates and counts for the current month and can update those counts while sharing remains enabled. It does not publish dream text through the calendar. You can turn calendar sharing off and hide recent community activity using the available profile controls.

Submissions awaiting approval can be viewed by their author and authorised moderators. Reports, moderation reasons, decisions and contribution restrictions are processed to enforce the community guidelines and prevent abuse; reports and internal moderation records are not public. Authorised moderators may review submitted or reported content, remove it, correct public profile information or restrict contributions. Community moderation does not itself give moderators access to your private journal or health records. Contribution restrictions do not remove access to the rest of the app or community browsing.

Private conversations can take place between members and with the developer. We store message content, sender and recipient account identifiers, request status, dates and read information to provide messaging, support and safety. You can accept or decline a new member conversation, switch member messages off, and block or report members. These conversations are visible to the participants and are not public posts. Moderators do not receive general access to member-to-member transcripts. When you report a conversation, you can choose to include relevant messages or the entire available conversation; the preview shows what will be sent to authorised moderators. Developer inbox conversations can be accessed by authorised developer accounts for support. Removing a conversation or using Delete all messages clears your inbox view; other participants keep their copies. Unclaimed title gifts are claimed before the inbox is cleared. You can use community-data deletion controls or contact us about deletion; limited safety and moderation records may be retained as described below.

With notification permission, community alerts use Firebase Cloud Messaging and the relevant Apple or Google delivery service. We store device notification tokens and your preferences to deliver alerts such as replies, mentions, moderation updates and developer messages. You can change the available categories in the app, including messages from Lucidity Level, or disable notifications in device settings. Turning off push alerts does not delete inbox messages.

Community content remains until it is deleted or removed, or your community data is deleted. Some activity and moderation notices are scheduled to expire after 90 days, resolved review records after 30 days, and moderation audit records after 365 days. These periods do not apply to every inbox item or private conversation, and automatic cleanup may take additional time. Necessary restriction records may remain to prevent an existing contribution restriction being bypassed. We do not sell community content or private messages or use them for targeted advertising.

External links and previews

Links in posts, profiles or developer messages may lead to websites operated by others. The app shows a confirmation before opening supported external links. To display a thumbnail or website information, the confirmation screen may fetch a preview before you choose Open website. This can contact the destination website or its content providers and disclose ordinary network information, such as your IP address. Opening the website is subject to that website’s privacy practices. Avoid including private information in links you share.

8. Import, export and previous accounts

Importing a file adds the supported dream information you select to the device journal. It can then be included in a connected cloud backup. Exporting uses the destination you choose; exported files and copies you share are outside the app’s deletion controls. Journal file exports are not a complete replacement for account backup.

Where previous-account recovery is offered, your supplied credentials are used to verify the old account and retrieve supported dream records. Only those dreams are brought into the new journal; old progression is not migrated. Recovering previous dreams does not delete or merge the old account. Deleting the new account does not delete that old account. Contact us if you need help with a previous account.

9. Retention, deletion and your choices

You can delete your community profile and shared contributions using the community privacy controls without deleting your app account or private journal. This removes your profile, shared dream copies, posts and replies, uploaded community media, interactions, title gifts, inbox conversations and community notification registrations. Other people’s replies may remain under anonymous deleted-post placeholders. Minimal restriction and deletion-status records, and de-identified moderation history, may remain for safety and to complete deletion. Removing a post does not delete other people’s replies or copies they have already saved.

Local information remains until you remove it or the device/app storage is removed. Connected account data is retained to provide the account and backup, including a saved backup after a subscription expires, unless you replace or delete it. Obsolete backup objects are cleaned up by the service; temporary copies may remain while an update or cleanup completes.

You can request account deletion inside Profile & Settings → Your Account → Delete Account & Server Data. A brief sign-in confirmation protects against accidental or unauthorized deletion; it is not a request for an identity document. This removes the Lucidity Level account, its journal data from our account service, and associated community data, subject to the limited retention described here. If interrupted, deletion may need connectivity and service retries to finish; check the app’s confirmation. If you no longer have the app, email support@luciditylevel.com with the subject “Delete my Lucidity Level account” and the email address used for the account. We will verify ownership and process deletion without requiring you to reinstall the app.

Account deletion does not delete your device journal, your Apple or Google account, separate iCloud copies, exported files or an old Android account. It does not cancel an App Store or Google Play subscription. Manage subscriptions separately in your Apple account or Google Play account. Use Journal Storage for the available iCloud deletion controls.

Limited transaction, support or security records held by us or our providers may be retained where needed for legal obligations, fraud prevention or resolving an issue. Contact support@luciditylevel.com to request access, correction or deletion of personal information, or to exercise other rights available under your local law. You may also contact your local privacy regulator. We may need to verify that a request relates to your account.

10. Security and international processing

We use authentication, access controls and provider security measures to protect information. No service can guarantee absolute security. Keep your device and sign-in credentials secure and check that a backup has completed before removing your local copy.

Firebase, Apple and RevenueCat may process information outside your country, including in the United States. Applicable provider safeguards and data-processing terms apply. Where data protection law requires a legal basis, we process information to provide requested services, with permission for optional features, for legitimate security/support needs, or to meet legal obligations, as applicable.

11. Children, updates and contact

Lucidity Level is not directed to children below the age permitted by applicable law. If you believe a child has provided personal information without required authorization, please contact us so we can address it.

We will update this policy when our practices change and show the revised date here. Where required, we will provide additional notice or request consent before a new use of your information.

Privacy contact: Nathan Woolmore
support@luciditylevel.com