Explanation
Why the site and the app are separate
The site is public reading; the app is a signed-in workspace on its own origin. No session cookie touches a public page; signup lives only on the app.
You read this page on the public site. You run your family on the app, at a different address. That split is deliberate.
No cookie on public pages#
The app sets a session cookie scoped to its own host. The site never sets one and never reads family data. A public page cannot leak a session, cannot be cached with private data in it, and cannot be confused by a browser extension into sending it anywhere.
Different cache rules#
Public pages are static files that any cache may keep for a long time. The app's shell must never be cached that way, because a stale shell could talk to a newer server. Keeping them apart lets each be correct.
One place to sign up#
Create your family and Sign in always open the app. There is no second signup form on the site, so there is no second account system to secure.
What you can do from here#
Read every doc and guide without an account. Follow a link into the app when you want to do something. Come back for help; docs are the same for every family.
In practice#
Site: marketing, docs, guides, privacy, terms, changelog. App: everything else, including your family's privacy and terms pages, which say the same thing.