Your pages belong to you.

This describes the current implementation. The operator must confirm its legal identity, contact details, provider retention, and final store disclosures before store release.

Your content and account

Device-only planner content stays on the device. Optional accounts send your email and authentication requests to Supabase. When signed in, your private planner collection is stored under your account with row-level access controls. Depending on what you enter, this may include journal text, plans, reading records, financial entries, wellness reflections, and optional birth details and preferences.

Storage and offline use

The website uses browser storage. The mobile app encrypts local planner copies and credentials with a device-protected key. Offline edits stay on that installation until they sync. Conflicting cloud edits require your choice. Exported backups and shared files are outside the app’s control and may contain sensitive content.

External services

Supabase processes authentication and private collections; Netlify hosts the website. Birthplace searches send the typed location query to Open-Meteo/GeoNames. Optional Spotify embeds, archival images, and external links may contact their providers and expose ordinary connection information such as IP addresses. This build does not add advertising identifiers, ad SDKs, analytics SDKs, HealthKit, Health Connect, contacts, camera, or GPS access.

Deletion and retention

Delete your account and private collection on the web, or use Account → Delete account in the app. Deletion removes the active account and its private-document row. Provider backup and security-log retention must be confirmed by the operator. Local guest pages and previously exported files are separate; remove them on each device or destination. Uninstalling the app removes its local files and can lose unsynced pages.

Supabase privacy information · Netlify privacy information · Return to Luméryn