Your habits belong to you.

Information you choose to provide

If you join the updates list, we collect your email address and basic subscription information through Mailchimp so we can send product updates, Android availability news and occasional future beta invitations. You can unsubscribe from any email.

If you contact support, we receive the information you include in your message. Please avoid sending passwords, authentication tokens, or private habit details that are not needed to explain the issue.

Data in the app

Habits, completion history, preferences and related app state are stored locally on your device. You can use the core habit loop without an account.

Habit reminders are scheduled on your device. Version 1.0.4 is live on the App Store and offers a Morning, Afternoon, Evening or Night window for each habit. You can turn all reminders off in Settings. Private habit names can be hidden from reminder copy; reminders do not include goals, notes, Why text or reflections. Delivery depends on your device notification settings.

If you choose to sign in, Firebase Authentication handles your account identity. Pro cloud features use Firestore for supported habits, completion and skip history, schedule and pause history, reminder preferences, and earned companion Growth. Cloud service availability and successful backup are separate from signing in; check the in-app backup status.

Completion reflections stay on this device and are included in the machine-readable local export; they are not included in cloud backup. Removing device data or uninstalling the app can remove them. Save an export somewhere safe before removing local data.

When you use Pro purchase or restore features, RevenueCat processes your Firebase account identifier as its App User ID, subscription and entitlement status, store transaction information, and technical app/device information needed to provide purchase services. Apple processes iOS payments; Somehow Growing does not receive your payment-card details. Purchase processing is separate from optional product analytics.

Analytics and crash reporting

The public website does not run product analytics. It stores only your selected website companion in your browser so your choice can be restored. The interactive sample does not save habits or progress. The app includes optional product analytics and crash diagnostics controls in Privacy & Data. Both are off by default and require separate affirmative choices; declining or withdrawing either choice does not affect core app use.

When product analytics is enabled, Somehow Growing sends a small set of parameter-free events to Firebase Analytics and Meta App Events for activation, retention, Monthly Recap, feedback and the Pro funnel. Meta also receives a delayed app-activation event so we can assess launch marketing. Firebase may process standard automatic app/session events and basic app, device and session metadata. Somehow Growing does not add habit names, dates, values, history, account details, advertising identifiers or free-form text to analytics events. Automatic screen reporting, automatic purchase logging, ad audiences and personalized advertising are disabled.

Crash diagnostics are a separate choice. When enabled, Firebase Crashlytics may receive fatal crashes and selected non-fatal technical failures with stack and basic app/device context. The app sends only approved stable error categories for those recoverable failures, removes the original source error message, does not attach private habit content or user-entered text, and does not keep a separate local error log.

Service providers

• Firebase Hosting serves this website.
• Mailchimp handles updates-list signup and email delivery.
• Firebase Authentication and Firestore may handle optional account and cloud features when you choose to use them.
• RevenueCat manages subscription and entitlement information for signed-in purchase/restore features; Apple App Store processes iOS purchases and subscription management.
• Firebase Analytics and Meta App Events process optional product analytics only after the in-app analytics choice is enabled.
• Firebase Crashlytics processes optional technical crash/error diagnostics only after the separate diagnostics choice is enabled.

These providers process information for the services they supply and under their own terms and privacy commitments.

Your choices

• Use the core app locally without creating an account.
• Choose local reminder preferences, including turning reminders off in Settings and keeping an individual habit name private when that option is available in your app version.
• Turn product analytics and crash diagnostics on or off separately.
• Use optional App Lock on supported devices without sharing biometric data with Somehow Growing.
• Export a machine-readable copy of supported local app data.
• Unsubscribe from product-update email at any time.
• Contact us about updates-list data, account access or deletion questions.

Deleting local app data, signing out, deleting cloud data and deleting an account are different actions. Somehow Growing is designed to keep those scopes explicit.

Contact

Questions or privacy requests can be sent to somehowgrowing@gmail.com. This notice may change as optional services become ready; the effective date above will change when it does.