SuprFlow 1.0.0 initializes TelemetryDeck in release builds and sends named usage events. Its normal transcription-completed event does not intentionally send the complete dictated paragraph. It does send operational details such as model, formatter, language, durations, a text-length bucket, and the active mode's name. Other events can send error descriptions. “No full transcript in the usual event” is therefore a narrower claim than “no telemetry” or “no user content can leave.”
The live privacy policy discloses that telemetry is present and says its exact fields, destinations, and controls need release-specific review. Ask for the current signed build's telemetry fields before relying on a no-content assertion.
What the event fields mean
| Field or path | Why a professional buyer should care |
|---|---|
| Model, formatter, language, duration, text-length bucket | These are usage patterns, not the paragraph itself. They can still reveal when and how a workflow was used. |
| Mode name | The event schema accepts a mode name. SuprFlow 1.0.0 uses fixed names and shows no control that creates or activates custom modes. A user-authored name would be a risk if that feature becomes reachable; the current signed release needs checking. |
| Provider or local error description | Error text is truncated to 100 characters in several analytics calls. Truncation does not remove sensitive content. A custom formatter can echo request text in an error body, which the app can forward. |
| Active app identifier | An auto-mode event can report the frontmost app's bundle ID, revealing which software was in use. |
| SDK metadata and identifier | TelemetryDeck documents event type, an app-installation identifier, a timestamp, device/app metadata, and developer-supplied parameters. Its identifier treatment does not sanitize custom parameters the developer adds. |
This describes how the app is built, not a packet capture. It does not prove precisely which packets a particular signed installer sent, what TelemetryDeck retained for this app, or whether a later release differs. Those require a release-specific event inventory and controlled test.
What to request before approving the app
Ask the vendor for the signed version and an event schema: each event name, parameter, purpose, processor, retention period, and any user or administrator control. Require fixed categories in place of arbitrary mode names, custom model strings, URLs, provider responses, file paths, and exception messages. Test with a formatter that returns a synthetic echo error and a harmless dictated sentence. If the installed release offers custom modes, also test one named like a fictional client. Confirm those words do not appear in event payloads or vendor analytics. Retest after an update.
If the organization prohibits all third-party telemetry, content sanitization alone does not meet that rule. The decision then requires a verified telemetry-off configuration or a different approved build and a matching contract. Device-local speech recognition does not answer this analytics question.
Questions people ask
Does TelemetryDeck's identifier hashing protect a custom mode name?
No. TelemetryDeck says its client user identifier is hashed, while optional parameters supplied by the app developer are not automatically hashed. If a release exposes a free-form mode name, it is a separate parameter and needs its own protection or removal. SuprFlow 1.0.0 does not show a user-facing custom-mode editor.
Does an “anonymous” event prove no private information was sent?
No. An identifier may be pseudonymous while event parameters still include a client-like label or error text. Inspect the complete payload and its origin.
Can I rely on the current SuprFlow privacy policy for procurement?
The policy now acknowledges telemetry but does not enumerate its exact release fields, destinations, or controls. Obtain release-specific documentation and test the signed installer before relying on it for a regulated workflow.
Related guides
- Where does my dictation go?
- Does on-device mean no internet?
- Does cloud formatting send audio or text?
- Can dictation appear in Mac diagnostic logs?
- Test a signed release's privacy behavior
- Bank dictation vendor checklist