Yes. Some diagnostic console output in SuprFlow 1.0.0 can contain recognized words. In that release, several transcription paths print the first 60–80 characters of a result, and some filtered or deduplicated phrases are printed in full or in part. This is a separate local-copy question from the in-app Transcriptions list and a separate network question from analytics. Treat console logs from the app as potentially containing dictated words.
Whether a particular print is retained, visible in Console, or included in a support bundle depends on how the app is launched and how the Mac collects diagnostics. That behavior is enough to reject a blanket promise that no dictated words can enter diagnostic output; it is not a measurement of what every installed release actually stored.
Where SuprFlow 1.0.0 prints words
| Recognition path | What is printed | Why it matters |
|---|---|---|
| Live streaming callback | Prints up to 60 characters each from confirmed and unconfirmed text. | A partial phrase may contain a client name or matter fact even before the final note is accepted. |
| Short-recording batch fallback | Prints the first 80 characters of the cleaned result. | A quick one-sentence note can appear in a diagnostic message. |
| Tail or chunk recovery | Prints the first 80 characters of tail or chunk results. | Longer dictation can produce multiple separate excerpts. |
| Vocabulary-hallucination filter | Prints the filtered text when the model echoes a prompt term. | A dictionary word or name can enter output even when no final transcript is inserted. |
| Duplicate-phrase removal | Prints up to 60 characters of the removed phrase. | Editing out repeated words does not prevent those words entering a diagnostic message. |
The formatting fallback also prints an arbitrary error description from a provider. A provider error can echo text submitted in the formatting request; the same error is relevant to the telemetry audit. This is why a privacy test should include failures as well as a successful sentence.
A safe release test
Use a distinctive fictional phrase such as “Project Linden has not approved 714 units.” On a test Mac, record the signed app version and macOS version. Try a normal sentence, a very short sentence, and a longer sentence that exercises streaming or chunk recovery. Have the product/security team inspect the app's standard output and any collected diagnostics through an approved method. Search for the fictional phrase and its fragments. Then test a harmless formatter failure using a test endpoint; never use client text for this exercise.
Keep the test report separate from the diagnostic output. Before sending logs to support, search them for names, amounts, document titles, account details, paths, tokens, and sample content. Apple's Console guide explains that log messages can be viewed and shared; sharing a diagnostic package can turn a local disclosure into an external one. In-app Clear All addresses SuprFlow history, not independently collected console or support logs.
What this means for the current release
In SuprFlow 1.0.0, treat console output and any diagnostic bundle as potentially containing excerpts of dictated words and provider error descriptions. Check each new release with fictional text before assuming those excerpts are gone. Removing them from the app's own messages would not by itself establish that every dependency or operating-system diagnostic is content-free. A full release test must re-audit logging, analytics, crash reports, and support-export paths.
Questions people ask
Does deleting SuprFlow history remove these logs?
No conclusion about system or support logs follows from clearing the app's transcription-history file. They are distinct storage paths with different retention and access rules.
Does local speech recognition prevent this?
No. Speech can be recognized entirely on the Mac and still be written into a local diagnostic message by the app. The issue here is local exposure and possible later sharing, not a cloud speech API.
Is the whole transcript printed on every dictation?
SuprFlow 1.0.0 prints excerpts on particular paths, not a full transcript on every path. A short note might still fit within an excerpt. Test the installed release before quantifying how often output is collected.
Related guides
- Where does my dictation go?
- What does SuprFlow history save?
- What usage telemetry can reveal
- How to verify the signed release
- Bank dictation vendor checklist