Finish more writing
Move through emails, notes, project updates, documents, and prompts while the idea is still fresh.
Turn your thoughts into emails, documents, prompts, and updates without typing every word. DictaFlow lets you choose between local dictation and more capable cloud features. Medical workflows have a separate path.
For Windows, Mac, iPhone, iPad, and Android · Business use subject to your organization’s approval
Read the review ↗It speeds up all my computer time when I’m on Claude doing Vibe Coding and other voice-to-text commands.
Kenneth L Holland · Public App Store review
Why people choose it
Use DictaFlow for messages that need context, documents that need a first draft, and prompts that are easier to explain than type.
Move through emails, notes, project updates, documents, and prompts while the idea is still fresh.
Dictate into supported text fields instead of moving every thought through a separate editor.
Use Local Offline on Windows for regular on-device dictation, or select cloud features when you want more processing power.
Confidence for work
DictaFlow is operated by SmartBids.ai Corp., a Canadian corporation. The product is designed to make the local and cloud boundaries understandable before your team decides how to use it.
Local or cloud
Local Offline and cloud features are separate processing paths. That makes the decision practical: keep regular dictation on the Windows device, or use cloud transcription and editing when those capabilities fit the work.
Regular speech-to-text processing runs on the Windows device without sending that dictation audio to cloud transcription.
Selected cloud features send the data needed to complete the request over HTTPS to DictaFlow and designated providers.
DictaFlow Medical
Standard DictaFlow is not for PHI. DictaFlow Medical is a separate product environment built for organization-reviewed, HIPAA-regulated workflows under the required agreements and safeguards.
Before using PHI: complete vendor review and the DictaFlow Business Associate Agreement, and obtain PHI-use approval for your account. Your organization should also approve the intended provider routes and apply its endpoint, access, EHR, and user-offboarding controls.
Medical builds use separate product identifiers, app and local-storage names, backend headers, legal links, and backend defaults.
The Medical backend can require BAA-covered providers and fail closed when a transcription or formatting route is not on the approved allowlist.
Medical controls include HTTPS, authenticated backend requests, PHI-oriented logging restrictions, audit and disclosure metadata, and local encryption controls where supported.
Local processing can reduce cloud exposure for supported dictation paths. Cloud transcription, formatting, sync, account, support, and security operations remain separate and must follow the approved Medical configuration.
Medical is designed not to permanently store raw audio or transcript text on the backend unless support, security, legal, or customer-requested work requires retention.
Account, subscription, usage, audit, and security records may be retained as needed. Customer-specific return, destruction, and retention terms belong in the BAA or written agreement.
For IT and procurement
Depending on the feature: audio, dictated text, selected text, formatting instructions, language, vocabulary, snippets, account identifiers, settings, plan and usage state, app version, platform, and security or request identifiers.
Cloud audio is ordinarily discarded after processing. Text may be retained for a chosen feature, supported-device sync, requested-result recovery, support investigation, or legal compliance.
Local history, notes, vocabulary, snippets, and other local content remain under device storage and access controls until removed. Organizations should apply OS sign-in, disk encryption, MDM, patching, and least privilege as required.
DictaFlow is intended for commercial and business use, subject to the selected plan, the Terms, applicable law, and the customer organization’s approval and acceptable-use rules.
The standard Privacy Policy identifies OpenAI, Deepgram, and Groq for transcription and related AI processing, plus authentication, hosting, billing, email, security, analytics, and support providers.
Users can request deletion through available controls or the account deletion page. Limited legal, billing, fraud-prevention, or security records may remain where required.
Send this page to your reviewer, or email the questionnaire, intended platforms, data classification, and deadline for a direct response.
Frequently asked
No. DictaFlow’s first-party policy is not to use customer audio, text, prompts, vocabulary, snippets, or other customer data to train AI models. Selected cloud providers process requests under their applicable contractual and security terms.
No. On Windows, regular dictation can be processed on the device. Account, plan, billing, security, update, sync, and support functions may still communicate with DictaFlow services or providers. Cloud editing remains a separate path.
Yes. DictaFlow is intended for commercial and business use, subject to your selected plan, the Terms, applicable law, and your organization’s approval. Standard DictaFlow must not be used for PHI.
This page makes no blanket claim about every device or storage location. Data sent to services is protected in transit with HTTPS. Local data relies on operating-system, device, identity, and organization controls.
No certification is represented here. DictaFlow Medical provides a separate Medical environment and HIPAA-oriented controls. The customer must complete vendor review, execute a BAA where required, approve the configuration, and operate the workflow under its own safeguards.
Use the standard app for everyday work. If your workflow involves PHI, use the separate Medical path.