Continuum is local-first. Understanding which local store you are using is the most important part of its current data boundary.
Local-first by design
Documents, folders, shared variables, archives, settings, onboarding progress, quick drafts, and theme choices are stored locally. Continuum does not require an account and does not provide cloud synchronization in the current production build.
Backups are explicit JSON files you create and control. Calculations are derived from the authored source rather than stored as an opaque remote artifact.
Separate data stores
The hosted browser app, packaged desktop continuum://app origin, and desktop development server use separate browser-style storage. They do not automatically transfer or reconcile documents. Use backup and restore when you intentionally want to move work.
Analytics
The hosted production app uses Umami only on the canonical production host. It records page loads and a small set of meaningful product events such as the first rendered calculation and preview use. It does not track every keystroke, slider movement, close action, or hover.
Packaged desktop pages and local/preview deployments do not activate this hosted analytics integration.
Feedback and release updates
The marketing landing includes a voluntary form, and the hosted production workspace may show the same choices in a compact prompt after a completed calculation is later updated. The workspace prompt is delayed, dismissible with Escape, outside click, its close control, or Not now, and does not reappear in the same session. It is not shown in the packaged desktop app, local development, preview hosts, or the embedded landing demo.
Neither form preselects an intent. Stay updated collects only a required email. Leave anonymous feedback collects only a required message. Feedback + updates collects both. Choosing either update path is explicit consent for occasional release updates; the submitted Formspree record is the consent record and the release-update list is handled manually.
All form submissions include an ISO submission date, the selected intent, the originating Continuum surface, message and email fields, and the release-update decision. Fields that are not relevant to an intent are submitted as empty strings. Messages are trimmed and limited to 3,000 characters.
“Anonymous feedback” has a deliberately limited meaning: Continuum does not request or submit a name or email in that mode, including an address previously entered under another choice. Formspree still processes the submission and technical request information for delivery and spam prevention, so this is not a promise of network-level anonymity.
This externally submitted form data is separate from calculation documents and quick drafts, which remain in the local stores described above. Landing feedback events use Vercel Analytics; workspace events use Umami. Analytics receives only the source and intent, never the email address or message.