Security at SoLo Family Plan

Identity and Household Access

SoLo Family Plan combines authenticated sessions, server-side household checks, and database access policies to scope data to the appropriate household. Roles remain specific to the app, and a household manager does not receive platform-wide administrative access.

• Supabase provides account authentication and session handling.
• Protected routes require an authenticated user.
• Server operations check household membership and role requirements.
• Row-level database policies add a second boundary around household records.

Household Content and Files

Calendar items, chores, meals, messages, memories, and documents are treated as private household content. File operations use authenticated ownership checks and private storage controls rather than relying on hidden links as the security boundary.

Payments and Integrations

Stripe Checkout collects payment details for subscriptions, so SoLo Family Plan does not place full payment card numbers in its household database. Stripe webhook signatures are verified before subscription events are processed. External retailer, support, notification, and AI services are kept behind scoped integration boundaries and may be unavailable when their credentials are not configured.

What You Can Do

• Use a unique password and protect access to your email account.
• Invite only trusted household members and review member roles.
• Sign out on shared devices and keep browsers and the Android app updated.
• Do not place passwords, payment card numbers, or unnecessary sensitive information in household content.
• Contact us if an invitation, sign-in, or household change looks unfamiliar.

Security Is an Ongoing Process

No online service can guarantee absolute security. We review protections as the product changes and prioritize reports that could expose household data, bypass authorization, compromise accounts, or affect billing integrity.