Guide
A screen-recording app sees whatever your display shows when it captures a frame. That includes private browsing windows, notification previews, revealed passwords and open documents. Masked password fields usually show only dots. Dayflow captures one frame every 10 seconds and stores recordings on your Mac. With Local AI, analysis stays on-device. If certain work must never be recorded, a handwritten log is the better choice.
You install an app that promises to remember your day, grant it permission to record your screen, and then about an hour later a thought arrives. You just logged into your bank. A friend’s message preview slid in at the top right. You had a private browser window open for something you would rather not explain. Did the app capture all of that?
The question tends to grow from there. Where do the captures go? Who reads them, a model on your Mac or a server somewhere? Could someone else open them later? Most people never get a straight answer, so they either uninstall the app in a mild panic or stop thinking about it, and neither is a good outcome.
This guide explains what a screen-recording app can and cannot see, why private tabs do not hide anything from it, and how to keep passwords and sensitive work out of the record using mostly habits and built-in macOS settings. Dayflow is our product, and it gets one section near the end, along with an honest section on when you should not use it. The Dayflow details come from its published product facts for version 2.2.0, reviewed on 2026-09-06. Nothing here comes from lab testing.
The simplest way to think about it: the app sees what a person looking over your shoulder would see, at the moments it looks. It does not read your files directly or know which window is “private.” It gets an image of the screen and that is all.
That has a few consequences many people find surprising.
Private tabs look like any other tab. A private or incognito window means the browser will not keep history, cookies or form data after you close it. It does nothing to the pixels on your display. To a screen recorder, a private window is a window.
Password fields usually show dots. When you type into a standard password field, the screen shows masked characters, so a captured frame shows masked characters too. The exposure comes from the moments when the real text is visible: you tap the eye icon to check a password, you open an entry in your password manager and reveal it, you paste an API key into a config file, or a set of backup codes sits in a note you left open.
Anything on screen counts, not only your own work. Notification banners with message previews, other people’s faces and shared screens on video calls, email threads, a colleague’s document you were asked to review. If it was on your display, it can be in the frame.
Timing matters, but do not lean on it. An app that captures a frame every few seconds will often miss something that flashed past briefly, and it will almost certainly catch something you left open for a minute. “It probably missed it” is not a privacy plan.
There are really three questions hiding inside “what does it see?”:
The steps below deal with all three.
Before you change any settings, spend ten minutes writing down what actually appears on your screen in a typical day. Not what you do, what is visible. Banking, health portals, client files, private chats, the password manager, the HR system, a personal journal.
Then mark each item with one of three labels: fine to record, fine if it stays on this Mac, never record.
An illustration: someone who freelances might write “client design files: fine on this Mac”, “invoicing in the bank’s site: never record”, “group chat with family: never record”, “browser research: fine to record”. That list turns a vague worry into four specific decisions.
After a week: look at the list again. If you have actually handled each “never record” item in a deliberate way (steps 2 to 5 below), it is working. If you find yourself thinking “oh, I forgot about that” more than once, the list needs another pass.
The cheapest protection is to make sure real passwords rarely appear on screen at all.
An illustration: a person who used to keep a “logins” note pinned on one side of the screen moves its contents into the password manager and deletes the note. Now nothing readable sits in view all day.
After a week: count the times you had to reveal a password. If it was zero or once, and that once was deliberate, this is working. If you kept revealing them to paste somewhere, find the autofill option for that site or app.
Notification banners are the most common way private content lands on screen without you choosing it. A message preview from a friend, a two-factor code, a calendar alert with a meeting title you would rather not log.
In System Settings, open Notifications and set “Show previews” to “When Unlocked” or “Never”. You still see that a message arrived, but not what it says. For the apps that matter most, you can switch banners off entirely.
An illustration: someone sets message previews to “Never” and turns off banners for their personal chat app during work hours. They still check messages, but they open the app to read them, which also means they read them on purpose.
After a week: think about whether any private message content flashed onto your screen uninvited. If not, it is working. If two-factor codes still pop up in banners, check the settings for that specific app.
Some things should simply never be on the screen that gets recorded. The cleanest way to handle them is separation, not vigilance.
Options, from simplest to most involved:
An illustration: a consultant bound by a confidentiality agreement keeps one client’s work in a separate user account and switches to it when working on that project. Everything else happens in the main account where the recorder runs.
After a week: check whether the separation held up in real life. If you kept “just quickly” opening the sensitive thing in the main account, the setup is too awkward. Make it easier (a second device, a fixed time) rather than relying on willpower.
macOS will not let an app capture your screen unless you have given it permission. That permission lives in System Settings, under Privacy & Security, in the screen recording section. Every app with access is listed there, and you can switch any of them off.
Two habits help:
An illustration: someone who handles payroll for a small family business quits the recorder before opening the payroll site each Friday, then reopens it afterward. A sticky note on the monitor says “Payroll: quit first.”
After a week: if you used the off switch every time you meant to, and it took seconds, this is working. If you forgot, put the reminder where the sensitive task starts, such as a note on the bookmark folder or the paper checklist.
Capturing is only half of it. The bigger question with any app that analyzes your screen is where that analysis happens. There are usually three possibilities: on your Mac, on a cloud service you choose and pay for, or on the vendor’s own service.
Before you grant permission, find the app’s privacy page and answer three questions in writing:
If you cannot answer those from the vendor’s own pages, that is your answer for now.
An illustration: someone compares two settings in an app, one labeled local and one labeled cloud, and writes down that the cloud one sends selected screenshots to a provider with its own terms. They pick local for workdays with client files.
After a week: if you could explain to a friend in two sentences where your recordings live and who analyzes them, you have done this properly.
A record you never look at is a record you cannot correct. Once a week, spend ten minutes scrolling through whatever the app produced. You are looking for two things: anything that should not be there, and whether the summary is even accurate.
This is also where many people discover the record is useful. Seeing the shape of a week, not just the tasks you remember, answers the question in where did my day go better than memory does. If you want to compare that with what you thought happened, the where does my week go calculator is a quick way to write down your guess first.
An illustration: on Friday afternoon someone scrolls through the week, spots a block on Tuesday where a personal medical portal was open, and realizes they forgot step 5 that day. They add a note to quit the recorder before opening that portal.
After a week: if the review takes under fifteen minutes and turns up no surprises, the earlier steps are holding.
The reason to put up with any of this is that an automatic record removes two chores: remembering to start a timer, and reconstructing the day from memory at 6pm. That is the appeal of Mac time trackers that run in the background.
Dayflow records the screen at one frame every 10 seconds and has AI write the day into a readable timeline. Here is what its published facts say about where things go:
The app is $0, MIT licensed, and runs on macOS 14 or later. More detail is on the local and cloud processing page and in the privacy policy, and is Dayflow safe? covers common questions.
Dayflow publishes this article.
A screen-recording app sees what your screen shows, no more and no less. Private tabs do not hide anything, masked passwords mostly stay masked, and notifications are the leak most people forget. Write down what you never want recorded, keep it off screen or in a separate account, learn where the macOS permission switch is, and confirm where the analysis happens before you say yes. If any work must stay entirely unrecorded, a handwritten log is the better tool for that work.
It sees what the screen shows. A standard password field displays dots, so a frame captured while you type usually shows dots too. The risk comes from moments when the real characters are visible: a show-password toggle, a password manager entry you have revealed, recovery codes in a note, or a key printed in a terminal. Treat anything readable on screen as something the recorder can capture.
No. Private browsing changes what the browser saves, such as history and cookies. It does not change what is drawn on your display. A screen recorder captures pixels, so a private window looks the same to it as any other window. If you want a site kept out of a recording, the window has to be off screen or the recorder has to be stopped.
Open System Settings, go to Privacy & Security, then the screen recording section, and switch the app off. Without that permission, macOS blocks it from capturing your screen. Quitting the app also stops it while it is closed. Check the list now and then, since apps you installed once and forgot about can still hold the permission.
Dayflow stores full screen recordings and a local timeline on your Mac. What happens during analysis depends on the mode. Local AI keeps screenshot analysis on-device. Your own cloud provider or Dayflow Pro processes selected screenshots off-device. Under the privacy policy, Dayflow Pro deletes screenshots after processing and may retain Activity Data for sync.
Only if you choose a cloud mode. With Local AI, a supported model runs on your Mac through Ollama or LM Studio, and screenshot analysis stays on-device. With your own provider, selected screenshots go to the provider you configure, and that provider's terms apply. With Dayflow Pro, Dayflow manages cloud analysis and deletes screenshots after processing under its privacy policy.
It depends on the assistant. In Dayflow, an assistant can receive the Dayflow data it retrieves during your conversation. If that assistant runs in the cloud, the retrieved data leaves your Mac for that conversation, even though the recordings themselves are stored locally. Local storage does not make a cloud assistant conversation local.
Probably not. If some of your work must never appear in any recording, such as client data under strict confidentiality, a handwritten or typed log you fill in yourself beats Dayflow. You decide every word that goes in it, and nothing captures your screen. A daily work log template takes a few minutes at the end of each day and needs no permissions.
Yes, if they appear on screen. A notification banner with a message preview is part of the display while it is showing, so a frame captured at that moment includes it. You can reduce this by setting notification previews to show only when the Mac is unlocked, or never, in the Notifications section of System Settings.
Start with anything that would cause harm if someone else read it: passwords, recovery codes, banking and medical pages, private messages, and work covered by a confidentiality agreement. Then decide how to keep each out, either by keeping it masked, keeping it off this Mac, moving it to a separate user account, or turning off recording while you handle it.
Dayflow is $0 and open source. Full recordings stay on your Mac, with local AI available for on-device analysis.
Download for MacOS macOS 14+ · MIT licensed · no account required