Help Center
How Disciple.Quest Works
Find practical help for formation flow, research, citations, account data, and common issues.
Your account and your data
Who owns what. Saltware Accounts owns your sign-in, your name and email, and the account itself. Disciple.Quest keeps your formation: the journeys, prayers, reflections, and practices you create here.
Signing out. Signing out of Disciple.Quest signs you out of your Saltware account everywhere. Other Saltware apps stop renewing their sessions and will ask you to sign in again once their current session ends.
Other Saltware products. The apps button at the top opens other Saltware products through Saltware Accounts. If you aren’t signed in to Saltware Accounts yet, you’ll sign in there once.
Cookies. Cookie preferences can be changed from the footer or Settings at any time.
Deleting your account. You delete your account in Saltware Accounts. Disciple.Quest has no separate delete, and deleting your account ends your access to every Saltware product.
When your Saltware account is deleted, Disciple.Quest deletes your formation data with it:
- Prayers, journal entries, goals, and inspirations
- Journeys and Trail Marker progress
- Everyday practices and what you noticed
- Commitments and reminders
- Notes, highlights, and notebook entries
- Study workspaces, projects, and saved citations
- Research questions you asked are disconnected from your account.
- Reading progress saved in your browser stays on that device until you clear it.
- Backups expire on their regular schedule.
- Each other Saltware product handles the data it keeps; see its help.
Getting Started
- Sign in with your Saltware account to save progress. New to Saltware? Create your account at Saltware Accounts first.
- Use Dashboard to continue your current formation work.
- Use Learn, Reflect, and Pray from the left navigation to move through the main rhythm.
- Ask a research question from Research or the search shortcut when you need source-grounded help.
Research & Sources
- Research answers are limited to approved source collections available in the app.
- Retrieved passages are selected from the current corpus and shown with source context where available.
- If the corpus does not support an answer, Disciple.Quest should say so instead of inventing one.
The Shepherd
- The Shepherd helps connect learning, reflection, prayer, and research prompts.
- It should stay within Disciple.Quest source boundaries and avoid pretending to be pastoral, medical, legal, or crisis care.
- AI-generated responses can be useful starting points, but they should be checked against cited sources.
Citations & Provenance
- Citation and provenance tools show which source material supports a response.
- Use source details to inspect where a claim came from and whether the evidence is direct, limited, or missing.
- Treat uncited or weakly supported claims as prompts for further study rather than final answers.
Troubleshooting
- If sign-in fails, request a fresh link and make sure you open it in the same browser.
- If research fails or sources appear missing, try again later and include the question in a support request.
- If a page looks wrong, refresh once and send a support request; it includes the page and browser for you.
- Never send passwords, sign-in links, or the words of your prayers or journal entries to support. We will never ask for them. If a sign-in link fails, request a new one instead of forwarding it.
Still need help?
Send a support request from inside Disciple.Quest so we can include the product, page, and account context needed to troubleshoot.
Contact Support