DailyCanvas.ai Privacy

The app stores account identity, workspace state, captures, responsibilities, actions, reviews, and attachment evidence needed to operate the private canvas. These records are personal operating memory, not public content. They may describe unfinished work, life pressure, health signals, obligations, or decisions that should stay inside the workspace.

The product is designed around one private personal workspace. That means the app should treat ordinary notes with more respect than a generic notes field, because ordinary notes are often where real life appears first: a screenshot, a symptom, a deadline, a promise, a person to contact, or a decision that still needs proof.

Board, Capture, Life Map, Review, and Find must work without AI. That is a product promise, not a technical detail. Future AI assistance is optional and should be treated as an explicit data-sharing boundary, used only when it makes the user's life easier enough to justify the trust.

AI can be useful when it reduces effort: summarizing a messy note, suggesting where a capture belongs, or helping prepare a review. But the main product should never depend on a model to understand the user's day. A private LifeOS has to be useful even when AI is off, unavailable, or not desired.

Source evidence is preserved so records can be checked later. A capture should not become a detached memory fragment with no origin. If a screenshot, PDF, or note caused an action, the user should be able to return to the proof instead of trusting a vague recollection.

Exports and backups contain sensitive workspace data and should be protected accordingly. The long-term direction is that a user can understand, move, back up, restore, and delete their own data without guessing what the product kept behind the curtain.