Private prayer data needs plain expectations.

Morning Shepherd may store account details, invite status, prayer entries, journal imports, brief feedback, memory settings, schedule preferences, generated morning briefs, history rows, and pastoral handoff packets you choose to generate.

Prayer text is private spiritual context. Do not submit secrets, payment card numbers, protected health information, or content you do not want processed by the product.

Prayer entries are used to create and improve your account's morning brief, history, continuity, memory, and review surfaces. The product is designed around private account context, not public sharing.

Generated devotional content may use prayer context, selected scripture metadata, feedback, and product safety rules. Some processing may involve service providers that help run the application and generate content.

Deleting a prayer removes it from active prayer views and redacts it from supported history and digest surfaces. Some non-sensitive audit metadata may remain so the product can preserve integrity and explain why a generated artifact changed.

Memory reset controls clear the active personalization boundary without deleting the journal. Export surfaces are available in account settings where implemented; ask support if you need a broader account export or deletion workflow.

To request account deletion, data export help, privacy support, or a correction to account information, email [email protected]. We may need to verify account ownership before completing the request.

Deletion can affect access to morning briefs, history, exports, billing records, and support history. Production data deletion is handled carefully and may require manual operator action.

When paid billing is enabled, Morning Shepherd may store subscription status, plan, customer identifiers, checkout events, portal events, and webhook processing metadata. Payment card details are expected to be handled by the payment processor rather than stored in Morning Shepherd.

Operational logs, aggregate health checks, and error reports may be used to keep the service reliable without intentionally exposing raw prayer content.

Read the Terms, Refunds and Cancellations, and Support pages for product boundaries and help paths.