An employee can choose Default formatting in SuprFlow, which uses local cleanup. A team policy that says “choose Default” is a useful instruction, but it is not a technical lock. In SuprFlow 1.0.0, the formatting provider is stored as a user preference, the settings screen lets a user choose Cloud API or Ollama when available, and the active mode normally uses that provider. We found no verified fleet control that prevents an employee from changing the setting. Ask the vendor to confirm this for the current signed release before relying on a contractual assertion.
That distinction matters when a bank or law firm asks, “Can staff dictate client information without sending transcript text to an external AI?” The recognition path is local, but optional Cloud API formatting can send transcript text to the selected provider. Ollama can be local or remote depending on its endpoint. The data-flow guide describes those routes, and the AI-training guide explains why a product-wide “never used for training” promise needs provider and contract scope.
What to test before writing a policy
| Control question | What SuprFlow 1.0.0 does | What an enterprise buyer should verify |
|---|---|---|
| Is local cleanup the default? | Local cleanup with no AI formatter is the default, displayed as Default. | New-user behavior in the signed release, including migrated settings. |
| Can a user select Cloud API? | Settings expose Cloud API and provider credentials. | Whether the feature is available on the team's license and device. |
| Can a mode override the provider? | Voice-to-text mode forces the Default formatter; other modes use the selected provider. | Every approved mode, after changing the general provider. |
| Does “Ollama” mean this Mac? | The endpoint can be configured. | Resolved host and network route; see the Ollama guide. |
| Can IT lock the choice? | No central enforced preference or policy was found in SuprFlow 1.0.0. | Vendor documentation, a demonstration on the signed build, and a change-control test. |
A practical rule for sensitive material
For a pilot, specify the permitted mode and formatter, prohibit unapproved cloud API keys and remote endpoints, and test with fictional text. Ask the vendor whether it provides a managed setting that hides or blocks Cloud API formatting, is tamper-resistant for ordinary users, survives updates, and can be audited. If the answer is no, call this a user-managed configuration in the approval, not an enforced local-only fleet setting. A network egress rule may reduce reachable hosts, but it needs its own validation and may affect account, update, or model-download functions; it does not by itself prove what a new release does.
Even with a local formatter, the output can enter a synced document, mail client, CRM, clipboard manager, or backup. An approved workflow should name the destination and retention rules too. A managed-Mac rollout checklist captures the version, device, permission, and destination tests.
Questions people ask
If an employee selects Default, is local-only use guaranteed forever?
It describes the selected formatting path at that time. The preference is user-changeable and can be affected by later configuration or updates. Verify it in the signed release and revisit it after changes.
Does voice-to-text mode force local formatting?
In SuprFlow 1.0.0, that preset forces the Default formatter, with no Cloud API or Ollama step. Test the installed version and check that the employee actually used that mode for the sensitive dictation.
Can a firewall replace an app-level local-only lock?
It can be part of a managed defense, but it is not the same control. Confirm every intended network path, error behavior, offline function, and update effect. Request a product-level enforced setting if your policy requires one.
Related guides
- Choose local or cloud formatting
- Check whether Ollama is really local
- Deploy SuprFlow on managed Macs
- Bank dictation vendor checklist