Account and sessions
Accounts use email, password-based sessions, and recovery receipts so a user can return to goals, guidance history, and account-backed diary entries when the backend is reachable.
Faith Companion is built around a simple boundary: sources are governed, private notes belong to the user, and the app must keep those worlds separate.
Accounts use email, password-based sessions, and recovery receipts so a user can return to goals, guidance history, and account-backed diary entries when the backend is reachable.
Diary notes, goals, and private reflections are user space. They are not reviewed doctrine, source approval evidence, clergy advice, or emergency monitoring.
The mobile app uses OS secure storage when available, supports device-lock behavior, and keeps offline source packs separate from private notes.
Operational analytics and feedback should measure product health without storing diary contents or sensitive free-text spiritual struggle as analytics payloads.
Private diary entries can be exported or deleted, and the hosted deletion page accepts either a signed-in account token for immediate deletion or an email verification request.
Downloaded packs contain source text, search data, checksums, and rights metadata. They do not contain account identity, diary notes, or private user reflections.
These product documents are available for hosted use and owner review. Final legal approval remains a release task, so the app keeps public-launch gates locked until the effective versions are approved.