A local-first planner app — your data stays on your device

A local-first application stores your data on your device as the primary source of truth. The app reads and writes locally, so it is fast, works offline, and does not depend on a server to function.

In WeekFlux, your tasks, time blocks, habits, notes, and focus sessions are stored in your browser's local database. When you open the planner, it reads directly from your device — no loading spinners waiting for a server response, no 'you are offline' blocks.

By default, everything stays on your device. Your task list, your weekly time blocks, your habit tracker data, your notes, and your focus session history are all stored locally. None of it is sent to a server unless you explicitly choose to enable sync.

This includes the contents of your tasks — the titles, descriptions, and scheduling — as well as the structure of your week, your habit streaks, and anything you write in notes. The default is complete locality.

Sync changes where encrypted copies can travel, not the basic local-first workflow. Your device still remains the place where you plan, edit, and use WeekFlux; sync is an optional continuity layer for people who want more than one device involved.

That means the privacy tradeoff is explicit. You choose whether cross-device access is worth adding an account and encrypted sync to an otherwise local planning setup.

By default, WeekFlux does not receive the contents of your planner because the planner works locally. Your task titles, notes, habit completions, and time blocks are not sent to a server just so the app can function.

WeekFlux also does not use in-app analytics to turn your planning behavior into engagement metrics. The product is built around planning utility, not behavioral tracking.

If you want your plan accessible on more than one device, WeekFlux offers encrypted sync as an opt-in Pro feature. It is off by default and stays off until you choose to set it up.

When enabled, sync uses end-to-end encryption: your data is encrypted on your device before it is sent, and the server stores encrypted data rather than readable planner contents. The exact recovery behavior depends on the sync setup you choose.

Local-first also means you can take your data with you. WeekFlux supports exporting your planner data in standard formats, so you are never locked in. Backups are encrypted using the same scheme as sync, keeping your data protected even in transit or at rest outside the app.

You can export your data, back it up, move it between devices manually, or restore from a backup — all without depending on a cloud service to release your own information to you.

Your calendar, tasks, habits, notes, and focus history are behavioral data. WeekFlux is built to keep that data under your control by making the device the default home for planning data.

The practical model is simple: local planning first, optional encrypted sync second, export and backup as your escape hatch. That gives you a usable planner without making the cloud the starting point.

A weekly planner is unusually personal. Your calendar, tasks, habits, notes, and focus history are behavioral data. They reveal what you care about, when you work, what you avoid, and what routines you are trying to build.

WeekFlux is built to keep that data under your control. Local-first storage reduces unnecessary exposure by keeping the default copy on your device instead of making a cloud database the starting point.

WeekFlux ships with no in-app analytics. There are no third-party tracking SDKs, no behavioral analytics measuring how you plan, and no usage data being sent to a dashboard. What you do in your planner is between you and your device.

This is not a privacy 'mode' you have to find in settings — it is the default. The app does not collect analytics because it was not built to.

For the broader privacy model, read private planner without tracking, encrypted sync Pro, and backup, export, and restore.