Replies: 1 comment
|
+1 I'd absolutely like to stop things like my bank's website from recording. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Dayflow can block an entire app from recording, but blocking a site currently means blocking the whole browser. I would like to add domain-level exclusions so pages such as banking or admin tools never reach stored screenshots or an AI provider.
My proposed scope is to extend Recording privacy with a simple blocked-domain list. Before each screenshot, when a supported browser is frontmost, Dayflow would read its active-tab URL through the browser scripting interface. An exact hostname or subdomain match would save the existing privacy placeholder instead of page pixels. If the URL cannot be read while domain rules are configured, Dayflow would fail closed by redacting that browser capture.
This would start with browsers that expose a reliable active-tab URL (for example Safari, Chrome, and Arc/compatible Chromium browsers). Unsupported browsers would be called out explicitly; there is no reliable system-wide URL API, so they cannot honestly offer the same guarantee without a browser extension or Accessibility access.
If this direction fits the project, I am happy to implement it as a small extension of the existing privacy path.
All reactions