01
Your household context
Schedules, Scripture, responsibilities, family communication, and emerging assisted workflows belong to the household experience.
Security & data handling
Family data deserves plain commitments.
Shprd holds intimate household context. We would rather explain the current posture conservatively than publish a wall of broad security claims that have not earned your trust.
Household-first permissionsParents should understand what is shared—and choose it.
A simple trust map
Know what is yours, what is shared, and what governs it.
This is the mental model Shprd's public experience should make clear. It is not a substitute for the formal policies linked below.
02
Permissioned connections
A family should choose whether a church, ministry, or support relationship connects to that household context.
03
Formal policy language
Privacy rights, terms, and legal obligations remain defined by the app-hosted policy documents.
What we can say today
Modest language. Meaningful boundaries.
Shprd is still in early access. These statements summarize the intended product posture and deliberately avoid pretending this page is a certification or formal assurance report.
- 01No advertising-data model
Shprd is not built around selling household data or targeting families with advertising.
- 02Household-first sharing
Church and ministry relationships should begin with an explicit family choice, not silent access.
- 03Permission before support
Product help and research should not become a blank check to browse private family content.
- 04Careful AI boundaries
Shprd AI is an additional surface. Public language should match the providers, permissions, and controls actually in use.
- 05Formal policies stay authoritative
This page explains posture in plain language; the linked legal pages carry the governing policy text.
- 06Claims grow with evidence
We will expand public assurance language only when implementation and review support it.
Important boundaries
What this page does not claim.
A plain-language page should make uncertainty easier to see, not hide it under reassuring design.
Not a certification
No badge substitutes for review.
This page does not claim an audit, certification, or assurance scope that is not named and evidenced.
Not silent church access
Connection is not surveillance.
A church relationship should not imply that leaders can inspect private household activity by default.
Not local-only AI
Roadmap direction is not present fact.
Future local AI work does not mean every current AI-assisted feature runs only on customer-owned hardware.
Policies & questions
Read the sources that govern the app.
Use the formal pages for policy language. If you still have a question, the waitlist form includes room to tell us what your household needs to understand.
See also: church connection posture and the Shprd waitlist.