Privacy, in plain sight.

Data the app can handle

Afterhush can store onboarding preferences, sleep and mood check-ins, journal text, completed sessions, favorites, downloads, reminder choices, and subscription entitlement status. Current device-bound local storage is encrypted. Optional account sync and server features depend on configured services and your in-app choices.

Crash reports

If crash reports are on (Settings → Send crash reports; on by default after saved privacy settings load), the app sends error details to Afterhush’s Google Firebase project to help diagnose crashes. Reports include the error type, message and stack trace, platform, operating-system version, app version and update ID. We do not intentionally attach your journal entries, check-ins, profile or account identifier.

We attempt to scrub identifying details from error text, but this may not remove every personal detail appearing in a message or stack trace. Product analytics are not collected.

How it is used

Data is used to provide the features you choose, build and explain a Tonight Plan, restore continuity, and operate account or purchase features when their providers are configured. AI sharing requires explicit consent; sharing journal context requires a separate choice.

Services that receive data

Afterhush uses these services for the features described below:

Google Firebase runs optional account sign-in and sync, account deletion, crash reports, and the Afterhush server that handles AI requests. Our Firebase-hosted server receives a Firebase authentication token when you use AI features so it can verify the request and apply usage limits.
OpenRouter and model-hosting providers. After you agree to AI features, the text of a request (for example, the message you type, the check-in or plan choices it is about, and, only if you separately allow it, recent journal text) goes from the Afterhush server through OpenRouter to a provider hosting the configured AI model. We don’t add your account name, email address or account ID to requests sent to OpenRouter or downstream model-hosting providers. Information you include in your messages or permitted journal excerpts is sent as part of that text.
RevenueCat, Google Play, and the Apple App Store process purchases and report whether a subscription is active. For identified Afterhush accounts, we send your Firebase account ID to RevenueCat so Premium access can follow that account across devices.
Expo Updates The app automatically checks for updates using Expo’s update service at u.expo.dev. These requests include an installation identifier, platform and app-runtime information to find and deliver compatible updates.

Your choices

You can manage reminders, AI sharing, and crash reports in Settings, export your data, and delete local data in the app. For help deleting synced data, follow the data deletion instructions or email support@afterhush.com.

Contact

Questions about privacy or your data: support@afterhush.com.