Responsible developer: John Nanda.

Privacy and data

Clairvoyant uses Firebase Authentication, Cloud Firestore, Cloud Functions, optional Firebase Analytics and messaging, and Google's Gemini API. This page explains how the app uses your information.

Accounts and posts

Email/password or Google sign-in links your account to a Firebase user ID. Profile information may include your email and display name. We store your posts, dates, tags, series, preserved originals, saved text versions, and matching records to provide the journal. Original text is preserved when you edit a post.

Posts can be read by signed-in members. Do not treat the journal as private, anonymous, or end-to-end encrypted. Blocking restricts access between accounts; moderation may make a post unavailable. Other people may retain independently authored copies of information they previously saw.

AI processing

Eligible original Dream text is sent through the server to Gemini for internal summaries and similarity matching. Optional AI edits and missing-detail suggestions send additional text when enabled. AI may be inaccurate or inappropriate. Google's applicable service terms and your developer's service configuration govern provider processing; this app does not promise that providers never retain data or use it for other purposes.

Optional device services

Voice input uses your device's speech-recognition provider, which may process audio remotely. The application stores resulting text rather than uploading audio recordings itself. Read-aloud uses installed text-to-speech providers, some of which use network services. You can type without granting microphone access.

Optional notifications use device tokens, your reminder preference, and the device's IANA timezone. The app does not request GPS permission. Denying notifications leaves journaling available. Linked HTTPS images and websites contact their own operators, who may receive network or device information.

Analytics choice

Usage analytics are off by default. You may enable or disable them in Settings. When enabled, Firebase Analytics may collect automatic usage, device, and network data; the app's explicit screen events contain screen names, not post text. Analytics do not enable an advertising feature. Essential Firebase authentication, database, and security traffic continues when analytics are off. Firebase services may use installation identifiers independently of Analytics.

Safety, retention, and deletion

We store community-standards acceptance and your blocked list. Reports include a content snapshot, reason, optional details, and account references for moderator review. Do not place unnecessary personal information in a report. Reports expire after 30 days and are removed by an hourly cleanup job. Moderation decisions can restrict access until reversed or the account is deleted.

Live account records and posts are retained until you request account deletion. Home → Settings → Delete account requires password or Google verification and explicit confirmation. It queues removal of your Auth account, profile, posts and versions, devices and inbox, derived matching records, stored suggestions citing deleted posts, blocks, report references, and operational limits. Failed cleanup is retried. A security tombstone remains for 24 hours after completion and is removed by an hourly sweep.

This cleanup does not erase independently authored copies, provider logs, backups, or previously collected analytics history. The main Firestore database and application functions use us-central1; this does not promise that every provider processes data only there.

Review community standards before posting. Use in-app reporting for safety concerns, and the developer support contact when available for privacy questions or access problems.