Safety, privacy & trust
Protection belongs in the build.
Protection is part of the product, not a promise added later. Each build should explain its terms plainly, collect and expose only what its current purpose requires, keep consent and human safety visible, and name unfinished safeguards without spin.
- Intent
- Offer faith-centred support only by choice, without turning Scripture, AI or pastoral language into a claim of spiritual authority, guaranteed change or clinical care.
- Implemented so far
- Scripture Mode is opt-in and uses RECALL's existing account, consent, privacy, export, offline and crisis-routing architecture. The shared structure avoids a second identity, data store, signup or set of product terms.
- Honest current position
- FAITHCALL inherits RECALL's unfinished production and safety verification. Its faith content, pastor-oriented surfaces and policy language must remain aligned with the shared product and clear about the limits of automated support.
Technical foundation
What the build is made of.
Source-backed snapshot, last reviewed October 12, 2026. Named technology is evidence of implementation—not proof of deployment, security or certification.
- Application stack
- FAITHCALL uses RECALL's React/Vite PWA and the same managed Supabase Postgres, Auth, Storage and Deno Edge Function architecture. It does not introduce a second application or database.
- Services & integrations
- The optional mode shares RECALL's ElevenLabs voice paths, Resend transactional email, Sentry monitoring, offline fallback, account, export and crisis-routing systems.
- Data & persistence
- Scripture preferences and faith-centred interactions remain inside the same RECALL account and consent boundary. No duplicate signup, identity store or policy surface is intended.
- Assurance boundary
- FAITHCALL inherits RECALL's unresolved production, privacy, safety and legal-review obligations. The implementation does not establish spiritual authority, clinical effectiveness or compliance certification.
Privacy-law references describe a design and review posture only. Applicability depends on the people, data and jurisdictions involved; no PIPA, PIPEDA, GDPR or other compliance certification is claimed here.
FAITHCALL is RECALL’s optional Scripture Mode—not a separate app, startup or venture. It uses the same crisis-interruption product while offering faith-centred grounding, surrender language and pastor-oriented support surfaces for people who choose them.
Relationship to RECALL
People use RECALL with Scripture Mode turned on. The shared account, database, setup, history, check-in, privacy, export, offline and safety architecture is intentional. FAITHCALL does not require a separate signup, dashboard or pricing product.
What is built
- Scripture-mode labels, presentation and navigation within RECALL.
- Faith-centred grounding and surrender language.
- Optional faith anchors within the shared Chosen Voice system.
- Pastor-oriented support surfaces.
- The same five-part interruption, follow-up, privacy and safety systems used by RECALL.
Public state and boundaries
FAITHCALL is available by turning on Scripture Mode inside the public RECALL experience at recall-app.ca. It is faith-based, non-clinical support. It is not therapy, coaching, emergency services, spiritual authority or a clinically validated outcome system, and it does not promise safety, behaviour change or spiritual results.
AI role
Runtime models can support personalized grounding and pastor-oriented conversation. Accounts, recordings, session state, offline fallback and crisis routing are separate shared RECALL systems. A model does not replace emergency resources, professional care, human judgment or a person’s faith community.
Next gate
Continue the same safety, release and production verification as RECALL while keeping the Scripture Mode relationship clear everywhere it appears.
