SuprFlow asks for macOS Accessibility permission so it can insert dictation into other apps. In SuprFlow 1.0.0, it also captures context from the focused app at recording start: the app name, window title, browser URL when available, field type and label, placeholder, and up to 300 characters of text already in the focused field. It skips an Accessibility field whose role is AXSecureTextField. That is a useful privacy boundary, but it is not a promise that every sensitive field is classified correctly by every app.
Apple says Accessibility access lets a third-party app access and control the Mac and should be granted only to software you trust. The exact access granted by macOS is broader than a product's current use of it. For a law firm or bank, the right question is both what the permission allows and what this particular signed app does with it.
Why the app reads context
SuprFlow captures this context when recording starts. The app uses it to suggest a formatting preset when automatic mode detection is enabled. For example, it can distinguish a search field from an email or chat field. The app also contains a routine that could turn app, window, site domain, field details, and existing text into an LLM prompt. In SuprFlow 1.0.0, that routine is not called by the formatter path.
That conclusion is limited to SuprFlow 1.0.0. It is not a certification of any signed binary, future release, extension, or custom integration. The optional Cloud API formatter does send the dictated transcript and instructions to the selected endpoint. Do not mix that transfer with the separate, currently local context capture.
What a field can reveal
| Captured detail | Example using fictional data | Decision for a confidential workflow |
|---|---|---|
| Window title | “Matter Acorn — draft note” | Titles may contain client or project names. Test how the destination app labels windows. |
| Browser URL | An internal CRM record URL | Even a URL can identify an account or matter. Confirm whether the reviewed release transmits it. |
| Field label and placeholder | “Client summary” | A label can reveal the purpose of a form without its full content. |
| Existing field text | Last 300 characters of a focused note | This is content already in another app. Do not assume an empty new dictation prevents access to it. |
| Secure field | Password role AXSecureTextField | Current capture skips this role. Test the actual application; nonstandard password-like fields may differ. |
The app reads a browser URL from an Accessibility attribute or browser UI when available. It is not a screen recording or a crawl of every tab. It reads the active context at the moment recording begins. If the wrong window has focus, the captured context and eventual paste destination may be wrong as well.
How to evaluate the permission
Use a synthetic browser form or document with a made-up customer name. Record the signed app version, macOS version, destination app, selected formatting mode, and whether automatic mode detection is on. Start recording with the intended field focused, then repeat with a different field. Check which mode SuprFlow proposes and where the text lands. A product team can instrument a test build or inspect a signed build's process and network behavior with test content; a marketing claim alone is insufficient evidence for a regulated buyer.
Review the permission in System Settings → Privacy & Security → Accessibility. Turning it off may prevent direct insertion; the app's onboarding says text can then be copied to the clipboard. Decide whether that fallback is acceptable for the workflow. Apple explains how to review and change Accessibility access.
Questions people ask
Does SuprFlow read everything on my screen?
SuprFlow's context capture targets the frontmost app, focused window, browser URL when available, and focused field at recording start. It does not prove the app reads every window or screen pixel. The macOS permission is powerful, so verify the signed product behavior and future updates rather than generalizing from one function.
Are existing words sent to a cloud formatter?
In SuprFlow 1.0.0, the captured context, including existing field text, is not passed into the formatter request. The dictated transcript itself is sent if Cloud API formatting is selected. The two data categories should be disclosed and tested separately.
Does the secure-field check cover a bank's custom login form?
Only if the focused element is exposed to the app as AXSecureTextField. A custom control may report another role. Use synthetic credentials in a test environment to check the actual field; do not test with a real password.
Related guides
- Does SuprFlow use the clipboard?
- Where does my dictation go?
- Why dictation did not paste
- Bank dictation vendor checklist