SECURITY

Private by architecture, measured by evidence.

Identity, household records, story work, media, billing, privacy jobs, and operations sit behind separate authorization and least-privilege boundaries.

01

Account boundary

Firebase Authentication owns Google and verified-email access. Recent authentication is required for purchases, export, deletion, session changes, and other sensitive actions.

02

Data boundary

The Android app does not directly read business data from Firestore or private Storage. The API rechecks account state, household role, object ownership, and entitlement.

03

Device boundary

Offline packages are encrypted with non-exportable Android Keystore-backed keys. The local device gate is a convenience control, never a replacement for server identity.

04

Operations boundary

Support sees masked references and minimal state. Story content is closed by default; future break-glass access must be reason-bound, audited, and security reviewed.