With Little is built local-first: your journal, calendar, prayers, profile, and daily notes live on your device first. Signing in is optional — it backs everything up and syncs across your phone, tablet, and computer. We do not sell your data, run ads, or track you across the web.
The short version
You own what you write here. Without an account, it stays in your browser. With an account, a private copy is stored in a database tied only to you — so you can pick up on another device. Nobody else can read it. We built the app as plain HTML and JavaScript (no app store, no build step) and use Supabase only for sign-in and backup when you ask for it.
What lives on your device
Everything you enter — daily ledger, weekly and monthly reviews, journal entries, prayer log, calendar, projects, ideas, mentorship notes, and your Profile — is saved in your browser’s local storage as you type. The app works fully offline. Edits autosave after a short pause; you’ll see Saved in the top bar when they’re written locally.
If you never sign in, your data never leaves your device unless you export it yourself or clear your browser data.
Optional cloud sync (Supabase)
When you choose to sign in under Settings → Cloud sync, the app connects to Supabase — an open-source backend that handles authentication and a small private database. Sign-in uses a magic link emailed to you; we never ask for or store a password in the app.
After you verify the link, your local data is merged with your cloud account. From then on, changes sync automatically: the app pushes JSON snapshots of your data to a table called app_data, keyed by your user ID. When you open the app on another signed-in device, it pulls the latest copies. If the same record was edited in two places, the newer timestamp wins.
Database access is locked down with Row Level Security: each row is tagged with your user ID, and Supabase only allows you to read or write rows that match the account you signed in with. Even with the app’s public connection key, another user cannot query your data.
What syncs — and what does not
Synced when signed in:
- Daily, weekly, and monthly records — ledger entries, reviews, scores
- Journal entries — body text, gratitude lists, custom prompts
- Calendar & stewardship data — goals, projects, tasks, habits, schedule blocks, themes, reflections
- Prayer log, ideas hub, projects, mentorship notes
- Profile — the personal context you enter for future coaching
- Settings — anchors, categories, and other app preferences stored in shared config keys
Stays on this device only:
- Large idea attachments — images or files attached to ideas (kept local so sync stays fast)
- UI preferences — a few display toggles that don’t need to follow you across devices
Separate accounts, separate data
Each email address is its own account. If two people sign in on the same browser, they see only their own cloud data. Signing out stops syncing but leaves your local copy on that device — useful if you want offline access without uploading further changes until you sign back in.
How the app is made
With Little is a single-page web app: HTML, CSS, and JavaScript files you can open in any modern browser. There is no npm install, no framework bundle, and no native app wrapper. Modules (faithfulness-store.js, calendar-ui.js, profile-ui.js, and others) each own a slice of the UI and talk to one shared storage layer.
That storage layer writes to localStorage on your machine. The optional sync layer watches the same keys and mirrors them to Supabase when you’re signed in. Fonts load from Google Fonts; Supabase’s client library loads from their CDN when you open the page. We do not embed analytics, ad pixels, or third-party tracking scripts.
Profile & future coaching
Your Profile (name, rhythms, goals, non-negotiables, coaching preferences) is stored like everything else — locally always, and in your cloud account when signed in. A future in-app coaching feature will read that context to personalize responses. That coaching has not shipped yet; when it does, it will use your Profile text only to tailor guidance inside the app, not to train external models on your identity.
Deleting your data
On this device: Settings → the ⋯ menu → Reset all data wipes local storage for the app (you’ll be asked to type RESET to confirm).
In the cloud: Sign in, then sign out on each device if you wish. To remove server-side copies entirely, delete your Supabase auth user or contact whoever operates this deployment — cloud rows are tied to your auth user and go away when that user is removed.
Last updated July 2026. This page describes how the app works today; if sync or coaching changes, this text will be updated to match.