A record on your Mac.
Your activity timeline starts with the native application.
Understand what stays on your Mac, what goes to your selected AI provider, and where optional cloud-backed context fits into the workflow.
Different features use different data paths. Start with what is stored, where it is processed, and what is optional.
Local-first storage of your working day.
Relevant activity context is sent for processing.
Can upload screenshots and use cloud storage.
Cloud-backed context with a local mirror.
Your activity timeline starts with the native application.
Provider analysis and hosted features involve services beyond your device.
Screen activity can contain information that matters to you. A useful journal should make its recording and processing boundaries understandable.
Explore these examples with sample data, then review the settings in the actual application before capturing your own work.
Explore the privacy overviewPause capture when you want an activity left out. Review the readable timeline on your Mac.
Choose Claude Code or Codex CLI for analysis. Your provider receives relevant context under its own terms and usage limits.
Read-only answers cite recorded activity. Follow the citation to check the context behind a summary.
Read the day on your Mac, or return to optional hosted knowledge.
Read the timeline and revisit the activity behind a recap.
Cloud-backed context with an offline mirror. Review its separate data path.
Choose what you are comfortable recording, know how to pause capture, and review the provider you use for analysis. Your provider’s terms and account limits still apply.
Keep optional hosted context distinct from the local timeline. Explore the example workflow before bringing your own activity into it.
Explore the example workflow without recording your screen.
Explore DayflowNo. Every product example on this site uses illustrative activity. Opening the browser preview does not install Dayflow or start recording.
Dayflow’s activity timeline is local-first. Provider analysis and optional hosted features introduce additional data paths; local-first does not mean that all processing stays on the device.
Relevant activity context is sent to the provider selected in Dayflow for analysis. Claude Code and Codex CLI require their own installation and authentication. Provider terms and usage limits apply.
Yes. Capture can be paused in the Mac application. The switch on this site’s privacy overview is only an illustrative control and cannot change recording on your Mac.
Optional hosted Wiki is cloud-backed and has an offline mirror. Context can sync from the Mac directly to the hosted service; it is not simply an entirely local feature.
Optional hosted features can upload screenshots and use cloud storage. Review the specific feature and its settings before choosing to use it.
The verified chat experience is grounded and read-only. Its purpose is to help you understand activity and follow supporting citations.
This is a product data-handling overview. It does not establish a legal policy, compliance certification, security audit result, or service commitment.