Todobar is local-first by design. Every task, setting, and reminder you create lives on your device inside the app’s webview storage. Nothing is sent to a server, no analytics are collected, and no background sync runs. This page explains exactly where your data lives today, what storage keys are used, and how future AI and connector features will handle data when they ship.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/Leonxlnx/todobar/llms.txt
Use this file to discover all available pages before exploring further.
Local storage model
All data is stored in browserlocalStorage inside the Tauri webview. This is the same storage mechanism used by web apps, scoped entirely to the Todobar process. The data never leaves your machine in the current version — there are no network requests, no telemetry endpoints, and no third-party SDKs that phone home.
Because data is stored in
localStorage, it is tied to the Tauri webview profile on your device. Clearing webview storage or reinstalling the app will remove your tasks unless you export them first. SQLite-backed storage with proper import/export is planned for a future release.Storage keys
Todobar uses the followinglocalStorage keys:
| Key | Contents |
|---|---|
todobar.sidebar.settings.v27 | Appearance and layout settings (theme, panel width, dock edge, motion speed, etc.) |
todobar.today.v1 | Today’s task list |
todobar.month.v1 | Calendar-scheduled tasks |
todobar.custom-lists.v1 | Custom task lists and their contents |
todobar.notified-reminders.v1 | Keys of reminders that have already fired, used to prevent duplicate toasts |
v27 suffix on the settings key reflects the settings schema version. If the schema changes in a future release, the key version will increment and defaults will be applied to any new fields.
No analytics, no telemetry
The current version of Todobar contains no analytics layer and makes no network requests during normal use. There is no crash reporter, no usage tracking, and no third-party monitoring SDK. If you open your system network monitor while using Todobar, you will see no outbound traffic attributable to the app.Future AI and MCP features
AI suggestions and MCP context connectors are planned for later versions. When they ship, they will follow these rules:- Optional by default. No AI or connector feature is enabled unless you explicitly turn it on.
- Permissioned access. Each connector will request a named permission scope (for example,
github:read:issuesorcalendar:read:today). The UI will display scopes in plain language before you grant them. - No silent reads. An AI action cannot read context from a file, calendar, or external service unless you have selected or authorized that context for that action.
- No silent writes. No AI or MCP action will write to an external system without a visible confirmation step.
- Audit trail. Every connector action — reads and writes — will create an audit event that you can review.
- Core app remains useful without AI. Todobar is designed to work as a fully capable task manager before any AI feature is installed or enabled.
API keys for AI providers will be stored in native secure storage, not in the webview or in plain configuration files. They will not appear in logs or be accessible to the renderer process.